Vista/7 - Schermate blu (bsod):individuazione cause dell'errore e possibili soluzioni

[Blue_screen_of_death]

Potresti fare anche un test della RAM.

http://www.hwupgrade.it/forum/showthread.php?t=1189286

[gaevulk]

grazie,eseguiro' anche questo test

[gaevulk]

niente da fare,ancora bsod,ho notato che non ho solo il codice 03b ma ne appaiono anche altri sempre nella schermata blue

BCCode: 3b

BCP1: 00000000C0000005

BCP2: FFFFF80002CC2AC5

BCP3: FFFFF8800DF839C0

ora provo col test sulle ram poi l'unica e' formattare mi sa

[Eress]

Si ma dov'è l'analisi del file dmp, quello è solo il codice di bsod. Comunque sembra causato dai driver video.

[gaevulk]

Originariamente inviato da Eress

Si ma dov'è l'analisi del file dmp, quello è solo il codice di bsod. Comunque sembra causato dai driver video.

ho scaricato tutti i symbols per win7 ,alla fine mi dice sempre che non uso i symbol corretti,comunque,in 10 giorni ho avuto molti bsod,se provo col windebug usando i symbol che ho ora ho questo

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

Symbol search path is: E:\Symbols
Executable search path is:
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`02c51000 PsLoadedModuleList = 0xfffff800`02e94890
Debug session time: Sat Dec 20 13:58:47.546 2014 (UTC - 8:00)
System Uptime: 0 days 2:41:06.295
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff88006aeea4d, fffff88007154a80, 0}

Unable to load image \SystemRoot\system32\drivers\afd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for afd.sys
***** 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 ***
*** ***
*************************************************************************
Probably caused by : afd.sys ( afd!AfdTLConnectComplete2+7d )

Followup: MachineOwner
---------


Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


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

Symbol search path is: E:\Symbols
Executable search path is:
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`02c0e000 PsLoadedModuleList = 0xfffff800`02e51890
Debug session time: Thu Dec 18 12:49:59.963 2014 (UTC - 8:00)
System Uptime: 0 days 3:53:49.697
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002c7bac5, fffff8800d04b9c0, 0}

***** 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 ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+6dac5 )

Followup: MachineOwner
---------



questi gli ultimi 2

[Blue_screen_of_death]

Esito di memtest?
Poi aggiorna anche i driver del controller ethernet.

p.s. hai configurato male i symbols

[gaevulk]

Originariamente inviato da Blue_screen_of_death

Esito di memtest?
Poi aggiorna anche i driver del controller ethernet.

p.s. hai configurato male i symbols

2 ore di memtets passati senza errori,non riesco a capire come configurare i symbols

[Blue_screen_of_death]

Hai fatto il test su tutti i moduli installati insieme?
Per le schermate blu usa BlueScreenView. Allega qualche screenshot.

[gaevulk]

Originariamente inviato da Blue_screen_of_death

Hai fatto il test su tutti i moduli installati insieme?
Per le schermate blu usa BlueScreenView. Allega qualche screenshot.

io ho lanciato memtest da usb ed e' partito da solo il test senza che io abbia selezionato nulla,bluescreenwiew l'ho usato ma mi da molti bluescreen dovuti ai test in overclock nei quali avevo dei crash dovuti al vcore basso,gli ultimi 4-5 li ho avuti con cpu e vga a default pero',dopo allego il testo del risultato,grazie dell'aiuto

[Lupalbe]

Il pc si avviava normalmente nonostante qualche errore, dovuto probabilmente ad un o più virus.
Forzandolo attraverso services, per entrare in modalità provvisoria con F8 non funzionava, mi è uscita per la prima volta questa schermata e ora continua ad apparire per brevissimo tempo e si riavvia automaticamente, proponendo le opzioni di ripristino sistema.
I codici di errore sono i seguenti: ***STOP 0x000000F4 (0x0000000000000003, 0xFFFFFA8008D5EB30, 0XFFFFF80008D5EE10, OXFFFFF80003398270), quelli tra parentesi variano sempre.

Non posso utilizzare il lettore CD perchè non funziona.
Diagnostica memoria Windows non rileva alcun errore.
Grazie

[Blue_screen_of_death]

Puoi allegare i minidump che trovi in C:\Windows\Minidump? (Se vengono generati...)

[Lupalbe]

Non posso fare questo perchè non arrivo al desktop.
Compare la schermata blu, si riavvia, scelgo Avvia strumenti ripristino -> impossibile ripristinare il pc automaticamente.
Schermata: opzioni di ripristino -> seleziono Ripr. config. di sistema, seleziono una data, mi rileva disco locale C: (sistema) e nient'altro (D: non lo vede), e non posso proseguire.
Purtroppo sono vincolata al dos, se mi può essere utile.
Quell'errore guardando in giro pare sia un problema legato all'HD, qualche settore danneggiato, esistono programmi avviabili da USB, come ad es. HDTune, per verificare questa ipotesi? O ci sono altre possibilità?
Quello che a me interessa è arrivare alla schermata desktop, salvare quello che mi interessa, poi penserò alla formattazione, lettore Cd permettendo.

[Blue_screen_of_death]

Se l'unico obiettivo è quello di salvare dati (e non sei interessata al recupero dell'installazione di Windows), la soluzione migliore è quella di avviare una distro in modalità live tramite USB (sempre se la macchina supporta il boot da USB).
Potrai copiare tutti i dati che ti interessano su un altro supporto USB, come un hard disk esterno.
Poi procederai alla formattazione tramite sempre tramite USB.

[Lupalbe]

Se ci fosse una soluzione ben venga!
Ho fatto una live di ubuntu, e ho copiato alcune cose.
Per curiosità provando 2/3 cd dvd, giusto il dvd che mi interessa ovvero quello di Win 7 non va
Forse è difettoso, ho guardato sul retro ed è leggermente rigato mah...
Quindi per ora sono senza dvd di installazione, ho chiesto a micorsoft e mi è stato risposto che non hanno più copie di win 7.
Sbadatamente non ho mai fatto un'immagine del SO.

[Blue_screen_of_death]

No problem. Per W7 sono disponibili le ISO scaricabili gratuitamente e legalmente.

http://www.hwupgrade.it/forum/showpo...45&postcount=4

Questo è per la versione Pro. Per ottenere l'installer multiversione, basta che cancelli il file ei.cfg contenuto nella cartella support, prima di masterizzare la ISO.

Ovviamente, per l'attivazione dovrai usare la licenza in tuo possesso.

[Lupalbe]

Non sapevo di questa opportunità. Grazie dell'info.
Sempre dalla live di linux ho provato a cercare la cartella che mi hai indicato ma non l'ho trovata.
Ho trovato un utility sul sito WDigital avviabile da dos, per 'testare le condizioni fisiche' dell'hd.
Volendo fare una nuova installazione, con un errore 'STOP 0x000000F4' è possibile avere problemi? Es. installazione non riuscita o errore di vario genere?

[Blue_screen_of_death]

Se ci sono problemi hardware, ad esempio all'hard disk, potresti non riuscire a portare a termine l' installazione.
Se il problema è software (es virus o problemi al registro) dopo l' installazione dovrebbe funzionare tutto correttamente.

[MRO]

continui crash da quando ho portato a casa il pc - WIN 8.1
riferimento al thread:
http://www.hwupgrade.it/forum/showthread.php?t=2692227


DMP del
05 gen 2015 - 11.30 AM: se puoi aiutami a capire se si tratta di hardware o periferica: anche se le abbiamo tolte tutte... disinstallo tutti i driver?

================================

Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


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


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17415.amd64fre.winblue_r4.141028-1500
Machine Name:
Kernel base = 0xfffff801`5de8f000 PsLoadedModuleList = 0xfffff801`5e168250
Debug session time: Mon Jan 5 11:23:29.411 2015 (UTC + 1:00)
System Uptime: 0 days 0:37:26.115
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a00f59a26dc71d, b3b71bdff4ecfe9c, ffffe00172bf1c20, 1c}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See http://www.microsoft.com/whdc/driver...tPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a00f59a26dc71d, Reserved
Arg2: b3b71bdff4ecfe9c, Reserved
Arg3: ffffe00172bf1c20, Failure type dependent information
Arg4: 000000000000001c, Type of corrupted region, can be
0 : A generic data region
1 : Modification of a function or .pdata
2 : A processor IDT
3 : A processor GDT
4 : Type 1 process list corruption
5 : Type 2 process list corruption
6 : Debug routine modification
7 : Critical MSR modification

Debugging Details:
------------------


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x109

PROCESS_NAME: System

CURRENT_IRQL: 2

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

STACK_TEXT:
ffffd001`15cdd1c8 00000000`00000000 : 00000000`00000109 a3a00f59`a26dc71d b3b71bdf`f4ecfe9c ffffe001`72bf1c20 : nt!KeBugCheckEx


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION:

BUCKET_ID: BAD_STACK

FAILURE_BUCKET_ID: BAD_STACK

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:bad_stack

FAILURE_ID_HASH: {75814664-faf6-4b70-bbc7-dc592132ecdd}

Followup: MachineOwner
---------

3: kd> lmvm Unknown_Module
start end module name

[Eress]

Originariamente inviato da MRO

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x109

PROCESS_NAME: System

CURRENT_IRQL: 2

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

STACK_TEXT:
ffffd001`15cdd1c8 00000000`00000000 : 00000000`00000109 a3a00f59`a26dc71d b3b71bdf`f4ecfe9c ffffe001`72bf1c20 : nt!KeBugCheckEx


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION:

BUCKET_ID: BAD_STACK

FAILURE_BUCKET_ID: BAD_STACK

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:bad_stack

FAILURE_ID_HASH: {75814664-faf6-4b70-bbc7-dc592132ecdd}

Followup: MachineOwner
---------

3: kd> lmvm Unknown_Module
start end module name

Come puoi vedere tu stesso il risultato parla di Analisi inconcludente.
Prova ad analizzare i file dmp con BlueScreenView e posta qui i risultati.
Per adesso si potrebbe pensare ad un driver difettoso che ha intaccato il kernel.
Vediamo i risultati di BSV, ma intanto potresti provare ad aggiornare/cambiare versione dei driver principali, video, rete, ecc.

[MRO]

eccolo (grazie) sì vedo che al 90% è un driver ma non capisco quale:
ci sono oltre 80 drivers caricati

===

Crash ListCrash List


Created by using BlueScreenView
Dump File Crash Time Bug Check String Bug Check Code Parameter 1 Parameter
2 Parameter 3 Parameter 4 Caused By Driver Caused By Address File
Description Product Name Company File Version Processor Crash Address
Stack Address 1 Stack Address 2 Stack Address 3 Computer Name Full Path
Processors Count Major Version Minor Version Dump File Size Dump File Time

010515-36093-01.dmp 05/01/2015 13.54.55 0x00000109 a3a01f58`ac28b95b
b3b72bde`fea7f0ea ffffe000`14d92790 00000000`0000001c ntoskrnl.exe
ntoskrnl.exe+1509a0 x64 ntoskrnl.exe+1509a0
E:\010515-36093-01.dmp 8 15 9600 290.048 05/01/2015 13.56.56