|
|||||||
|
|
|
 |
|
|
Strumenti |
03-01-2009, 11:20
|
#1 |
|
Member
Iscritto dal: Nov 2004
Città: Angri
Messaggi: 98
|
Help schermata blu
Salve ragazzi, ho da poco montato il mio nuovo pc...
Ho installato vista e ieri mentre navigavo in internet si è presentata una schermata blu... ho usato windbg per leggere il dump del crash ma non riesco a capire cosa ha provocato l'errore.. posto il contenuto del file: Codice:
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff9800d277652, The address that the exception occurred at Arg3: fffff9800d2e0a58, Exception Record Address Arg4: fffff9800d2e0430, Context Record Address Debugging Details: ------------------ ***** 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* MODULE_NAME: HTTP FAULTING_MODULE: fffff80001c00000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 4549be6a EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'istruzione a 0x%08lx ha fatto riferimento alla memoria a 0x%08lx. La memoria non poteva essere %s. FAULTING_IP: HTTP!UlPrepareAuthCacheKeyHash+2 fffff980`0d277652 4d8b2424 mov r12,qword ptr [r12] EXCEPTION_RECORD: fffff9800d2e0a58 -- (.exr 0xfffff9800d2e0a58) ExceptionAddress: fffff9800d277652 (HTTP!UlPrepareAuthCacheKeyHash+0x0000000000000002) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000000000000000 Attempt to read from address 0000000000000000 CONTEXT: fffff9800d2e0430 -- (.cxr 0xfffff9800d2e0430) rax=fffffa8004ca6700 rbx=01c96d252a185aed rcx=fffffa8004ca6700 rdx=fffffa8004cdd010 rsi=00000000000000b4 rdi=fffffa8004cdfd70 rip=fffff9800d277652 rsp=fffff9800d2e0c90 rbp=fffffa8004cdfd78 r8=0000000000000000 r9=0000000000000000 r10=0000000000000000 r11=fffffa8001cd61e8 r12=0000000000000000 r13=fffffa8004cdfd78 r14=fffffa8004cdd000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246 HTTP!UlPrepareAuthCacheKeyHash+0x2: fffff980`0d277652 4d8b2424 mov r12,qword ptr [r12] ds:002b:00000000`00000000=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WRONG_SYMBOLS BUGCHECK_STR: 0x7E CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff9800d277652 STACK_TEXT: fffff980`0d2e0c90 00000000`00000000 : fffffa80`04cdc010 ffff0000`000aa4bb 00000000`00000004 00000000`00000004 : HTTP!UlPrepareAuthCacheKeyHash+0x2 FOLLOWUP_IP: HTTP!UlPrepareAuthCacheKeyHash+2 fffff980`0d277652 4d8b2424 mov r12,qword ptr [r12] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: HTTP!UlPrepareAuthCacheKeyHash+2 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: HTTP.sys STACK_COMMAND: .cxr 0xfffff9800d2e0430 ; kb BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner ---------
__________________
ThermalTake Xaser V5000 C - Tagan TG480 Silence 480 Watt - Intel Q9550 cooled by Zalman CNPS 7000B AL-CU - 2x1 Gb Corsair cas5 (in attesa di 2x2Gb Corsair cas4) - Asus P5Q Pro - Ati x600 Pro (in attesa di Ati msi hd4850) - Maxtor 160 Gb Sata (in attesa di Maxtor 500 Gb 32 Mb cache) - DvD Asus E616P2 16x - DvD-RW Nec 3520 |
|
|
|
03-01-2009, 12:12
|
#2 |
|
Member
Iscritto dal: Nov 2004
Città: Angri
Messaggi: 98
|
me ne è appena successa un altra... avevo appena finito di scaricare Alcohol52%...
questa volta l'errore sembra dovuto ad ataport.sys Codice:
INTERRUPT_EXCEPTION_NOT_HANDLED (3d) Arguments: Arg1: 0000000000000000 Arg2: 0000000000000000 Arg3: 0000000000000000 Arg4: fffff98000524372 Debugging Details: ------------------ ***** 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* MODULE_NAME: ataport FAULTING_MODULE: fffff80001c00000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 47916a2a CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WRONG_SYMBOLS BUGCHECK_STR: 0x3D CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80001c4d6f3 to fffff80001c4d950 STACK_TEXT: fffff980`00ac77b8 fffff800`01c4d6f3 : 00000000`0000003d 00000000`00000000 00000000`00000000 00000000`00000000 : nt+0x4d950 fffff980`00ac77c0 00000000`0000003d : 00000000`00000000 00000000`00000000 00000000`00000000 fffff980`00524372 : nt+0x4d6f3 fffff980`00ac77c8 00000000`00000000 : 00000000`00000000 00000000`00000000 fffff980`00524372 01c96c3f`ba6fd38f : 0x3d fffff980`00ac77d0 00000000`00000000 : 00000000`00000000 fffff980`00524372 01c96c3f`ba6fd38f 00000000`00000000 : 0x0 fffff980`00ac77d8 00000000`00000000 : fffff980`00524372 01c96c3f`ba6fd38f 00000000`00000000 00000000`00000000 : 0x0 fffff980`00ac77e0 fffff980`00524372 : 01c96c3f`ba6fd38f 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0 fffff980`00ac77e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ataport!IdeProcessPortNotification+0x2a6 STACK_COMMAND: kb FOLLOWUP_IP: ataport!IdeProcessPortNotification+2a6 fffff980`00524372 ?? ??? SYMBOL_STACK_INDEX: 6 SYMBOL_NAME: ataport!IdeProcessPortNotification+2a6 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: ataport.SYS BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner ---------
__________________
ThermalTake Xaser V5000 C - Tagan TG480 Silence 480 Watt - Intel Q9550 cooled by Zalman CNPS 7000B AL-CU - 2x1 Gb Corsair cas5 (in attesa di 2x2Gb Corsair cas4) - Asus P5Q Pro - Ati x600 Pro (in attesa di Ati msi hd4850) - Maxtor 160 Gb Sata (in attesa di Maxtor 500 Gb 32 Mb cache) - DvD Asus E616P2 16x - DvD-RW Nec 3520 |
|
|
|
|
03-01-2009, 17:47
|
#3 |
|
Member
Iscritto dal: Nov 2004
Città: Angri
Messaggi: 98
|
help me ...
__________________
ThermalTake Xaser V5000 C - Tagan TG480 Silence 480 Watt - Intel Q9550 cooled by Zalman CNPS 7000B AL-CU - 2x1 Gb Corsair cas5 (in attesa di 2x2Gb Corsair cas4) - Asus P5Q Pro - Ati x600 Pro (in attesa di Ati msi hd4850) - Maxtor 160 Gb Sata (in attesa di Maxtor 500 Gb 32 Mb cache) - DvD Asus E616P2 16x - DvD-RW Nec 3520 |
|
|
|
|
03-01-2009, 17:47
|
#4 |
|
Messaggi: n/a
|
i symbols, devi scariare i symbols giusti per la tua versione di vista e dare il path a windbg prima di fare il debug
|
|
|
|
03-01-2009, 18:16
|
#5 |
|
Senior Member
Iscritto dal: Jun 2007
Città: Amiga Nation
Messaggi: 15562
|
1. i BSOD (Blue Screen of Death) sono sempre causati da driver difettosi.
2. riguardo al primo, molto strano, ho trovato questo su http://support.microsoft.com , http://support.microsoft.com/kb/949483/en-us/ che si riferisce a XP (!?) e ad un problema di USB. Installa questo hotfix (ignora se la descrizione dell'errore non riguarda il tuo caso. È comunque un aggiornamento all'ultima versione dei driver) che contiene gli ultimi driver di sistema per l'USB: http://support.microsoft.com/kb/956183/it e vedi se ti si ripresenta il problema, che descritto così potrebbe essere causato da troppe variabili per poterti offrire un aiuto veramente efficace...
__________________
 ASUS ROG SCAR 18 G834JY (i9-13980HX, 32GB DDR5@5600MHz, 4090 16GB 256bit 175W), 18" res: 2560x1600 240Hz con G-Sync. Amiga forever!
Ultima modifica di hexaae : 03-01-2009 alle 18:18. |
|
|
|
|
04-01-2009, 00:20
|
#6 |
|
Member
Iscritto dal: Nov 2004
Città: Angri
Messaggi: 98
|
vi ringrazio per l'aiuto..
Per NLDomy, avevo già installato i symbols ma alcune parti del file restano come le avete viste.. Per hexaae, grazie per l'aiuto.. per quanto riguarda il secondo errore cosa pensi sia dovuto ? qualke info aggiuntiva Vista 64 bit, Q9550, Corsair ddr2 cas5 2GB, Maxtor 160Gb Sata1, Ati x600 pro... sto aspettando che arrivino altri componenti del pc per questo ci sono per il momento dei pezzi vecchi... tipo l'hd e la scheda video... in realtà aspetto pure 4 gb di ram corsair cas4..
__________________
ThermalTake Xaser V5000 C - Tagan TG480 Silence 480 Watt - Intel Q9550 cooled by Zalman CNPS 7000B AL-CU - 2x1 Gb Corsair cas5 (in attesa di 2x2Gb Corsair cas4) - Asus P5Q Pro - Ati x600 Pro (in attesa di Ati msi hd4850) - Maxtor 160 Gb Sata (in attesa di Maxtor 500 Gb 32 Mb cache) - DvD Asus E616P2 16x - DvD-RW Nec 3520 |
|
|
|
|
04-01-2009, 00:25
|
#7 |
|
Member
Iscritto dal: Nov 2004
Città: Angri
Messaggi: 98
|
ho appena provato ad installare l'hotfix ma dice ke l'aggiornamento non è per il sistema da me in uso... forse però uso quello a 64 bit..
__________________
ThermalTake Xaser V5000 C - Tagan TG480 Silence 480 Watt - Intel Q9550 cooled by Zalman CNPS 7000B AL-CU - 2x1 Gb Corsair cas5 (in attesa di 2x2Gb Corsair cas4) - Asus P5Q Pro - Ati x600 Pro (in attesa di Ati msi hd4850) - Maxtor 160 Gb Sata (in attesa di Maxtor 500 Gb 32 Mb cache) - DvD Asus E616P2 16x - DvD-RW Nec 3520 |
|
|
|
|
04-01-2009, 03:25
|
#8 |
|
Bannato
Iscritto dal: Sep 2008
Messaggi: 220
|
Da dove hai preso i driver per il chipset della scheda madre, in particolare il controller ide (non mi è chiaro se è un ide p-ata o s-ata/2 quello in questione... ma mi pare che cmq sia un problema di un driver del controller ide)
prova a scaricare qua gli ultimi driver per il tuo chipset 32-bit: http://www.nvidia.it/object/nforce_vista_15.23_it.html 64-bit: http://www.nvidia.it/object/nforce_v..._15.23_it.html se nn cambia nulla o non ci reisci segui questa discussione: http://www.techsupportforum.com/micr...1-install.html |
|
|
|
|
04-01-2009, 09:46
|
#9 |
|
Member
Iscritto dal: Nov 2004
Città: Angri
Messaggi: 98
|
Come scheda madre ho l'asus p5q pro... i driver mancanti dopo l'installazione di windows li ho presi dal dvd della scheda.. non ricordo quello del disco se l'aveva già windows o no...
Cmq l'hd è sata 1.0 Ma quei driver non è che sono per chipset nvidia ?..
__________________
ThermalTake Xaser V5000 C - Tagan TG480 Silence 480 Watt - Intel Q9550 cooled by Zalman CNPS 7000B AL-CU - 2x1 Gb Corsair cas5 (in attesa di 2x2Gb Corsair cas4) - Asus P5Q Pro - Ati x600 Pro (in attesa di Ati msi hd4850) - Maxtor 160 Gb Sata (in attesa di Maxtor 500 Gb 32 Mb cache) - DvD Asus E616P2 16x - DvD-RW Nec 3520 |
|
|
|
|
04-01-2009, 09:58
|
#10 | |
|
Senior Member
Iscritto dal: Oct 2007
Città: Roma
Messaggi: 9803
|
Quote:
ehm sì quei driver sono per i chipset nvidia... |
|
|
|
|
|
04-01-2009, 14:58
|
#11 |
|
Member
Iscritto dal: Nov 2004
Città: Angri
Messaggi: 98
|
ho aggiornato i driver di chipset e sata dal sito dell'asus per vista 64 bit...
per adesso nessun blocco... vi farò sapere novità.. ma secondo voi può essere xkè sto usando un hd sata 1.0 che ho problemi ?
__________________
ThermalTake Xaser V5000 C - Tagan TG480 Silence 480 Watt - Intel Q9550 cooled by Zalman CNPS 7000B AL-CU - 2x1 Gb Corsair cas5 (in attesa di 2x2Gb Corsair cas4) - Asus P5Q Pro - Ati x600 Pro (in attesa di Ati msi hd4850) - Maxtor 160 Gb Sata (in attesa di Maxtor 500 Gb 32 Mb cache) - DvD Asus E616P2 16x - DvD-RW Nec 3520 |
|
|
|
|
04-01-2009, 17:32
|
#12 |
|
Senior Member
Iscritto dal: Oct 2007
Città: Roma
Messaggi: 9803
|
fai un test della ram con memtest
|
|
|
|
|
04-01-2009, 17:40
|
#13 | |
|
Senior Member
Iscritto dal: Jun 2007
Città: Amiga Nation
Messaggi: 15562
|
Quote:
__________________
ASUS ROG SCAR 18 G834JY (i9-13980HX, 32GB DDR5@5600MHz, 4090 16GB 256bit 175W), 18" res: 2560x1600 240Hz con G-Sync. Amiga forever!
Ultima modifica di hexaae : 04-01-2009 alle 23:33. |
|
|
|
|
|
04-01-2009, 22:29
|
#14 |
|
Member
Iscritto dal: Nov 2004
Città: Angri
Messaggi: 98
|
Ok ok...
Cmq oggi pomeriggio ho avuto un altro blocco.. ma senza schermata blu... non si muoveva più il mouse e la tastiera non funzionava... Aspetto l'hd nuovo per installarci Vista a 64 bit lì... se avrò ancora prob. passo a Vista 32 bit... per memtest lo farò...
__________________
ThermalTake Xaser V5000 C - Tagan TG480 Silence 480 Watt - Intel Q9550 cooled by Zalman CNPS 7000B AL-CU - 2x1 Gb Corsair cas5 (in attesa di 2x2Gb Corsair cas4) - Asus P5Q Pro - Ati x600 Pro (in attesa di Ati msi hd4850) - Maxtor 160 Gb Sata (in attesa di Maxtor 500 Gb 32 Mb cache) - DvD Asus E616P2 16x - DvD-RW Nec 3520 |
|
|
|
|
04-01-2009, 23:16
|
#15 |
|
Member
Iscritto dal: Nov 2004
Città: Angri
Messaggi: 98
|
Ho fermato memtest al 116 %, 0 errori... ma termina da solo si deve premere stop per farlo terminare ?
__________________
ThermalTake Xaser V5000 C - Tagan TG480 Silence 480 Watt - Intel Q9550 cooled by Zalman CNPS 7000B AL-CU - 2x1 Gb Corsair cas5 (in attesa di 2x2Gb Corsair cas4) - Asus P5Q Pro - Ati x600 Pro (in attesa di Ati msi hd4850) - Maxtor 160 Gb Sata (in attesa di Maxtor 500 Gb 32 Mb cache) - DvD Asus E616P2 16x - DvD-RW Nec 3520 |
|
|
|
|
|
| Strumenti | |
|
|
Tutti gli orari sono GMT +1. Ora sono le: 21:42.
