bluescreen irritante..dubito causato da scheda ATI 4850

Pagina 2 di 2
prima
1 2
Visualizzazione dei risultati da 11 a 14 su 14
  1. #11

    Predefinito

    L'alimentatore è un Tecnoware Fal500 Pro3
    I tools di microsoft li avevo già scaricati ma non ci capisco molto!!!
    Ho provato ad aprire il file dmp da "File/Open crash dump..."
    e mi appare il risultato che vedete di seguito, dal quale mi sembra di capire che il problema siano i driver della sk video, ma non so proprio cosa fare.
    Suggerimenti??

    Loading Dump File [C:\Windows\Minidump\Mini123008-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path. *
    * Use .symfix to have the debugger choose a symbol path. *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0x81a14000 PsLoadedModuleList = 0x81b2bc70
    Debug session time: Tue Dec 30 19:02:20.234 2008 (GMT+1)
    System Uptime: 2 days 2:16:00.587
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..............
    Loading User Symbols
    Loading unloaded module list
    ..........
    Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for dxgkrnl.sys
    *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 116, {83e6b008, 8b4163ee, 0, 2}

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Probably caused by : atikmdag.sys ( atikmdag+103ee )

  2. #12
    gibibyte
    Registrato
    Dec 2005
    Età
    41
    Messaggi
    1,280

    Predefinito

    Cambia alimentatore

  3. #13

    Predefinito

    Dici che non regge? In effetti, avevo già in mente di cambiarlo ma sono indeciso su marca e potenza.

  4. #14
    gibibyte
    Registrato
    Dec 2005
    Età
    41
    Messaggi
    1,280

    Predefinito

    enermax corsair

Pagina 2 di 2
prima
1 2

Informazioni Thread

Users Browsing this Thread

Ci sono attualmente 1 utenti che stanno visualizzando questa discussione. (0 utenti e 1 ospiti)

Discussioni simili

  1. [driver] scheda video Ati Hd 4850 vapor-x 1gb ddr3
    By Keldorm in forum Assistenza tecnica
    Risposte: 1
    Ultimo messaggio: 06-02-2010, 13:11
  2. BlueScreen con Ati Sapphire HD4890 1Gb!!!
    By demonlink in forum Assistenza tecnica
    Risposte: 8
    Ultimo messaggio: 09-08-2009, 15:25
  3. Risposte: 1
    Ultimo messaggio: 30-06-2009, 16:20
  4. problema scheda ati sapphire hd 4850 X2 2gb
    By Draco79 in forum Assistenza tecnica
    Risposte: 6
    Ultimo messaggio: 13-04-2009, 11:50
  5. Temperatura ati 4850
    By Nacsucau86 in forum -= Schede video e acceleratori =-
    Risposte: 7
    Ultimo messaggio: 08-04-2009, 09:39

Tags

Regole d'invio

  • Non puoi inserire discussioni
  • Non puoi inserire repliche
  • Non puoi inserire allegati
  • Non puoi modificare i tuoi messaggi
  •  
nexthardware.com - © 2002-2022