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

[garamant]

Originariamente inviato da Blue_screen_of_death

Intanto, http://www.hwupgrade.it/forum/showthread.php?p=41563071
Disattiva ogni eventuale overclock.
L'alimentatore è di marca? E' adeguato per la configurazione?

l'alimentatore è un enermax liberty 500w ha circa 4 anni di vita. Overclock non ne è stato fatto il processore è un intel g620. Possibile che sia l'alimentatore a non reggerla?

[bunzello]

adobe reader può mandare in crash il sistema con schermate blu se non è aggiornato?

[Blue_screen_of_death]

Originariamente inviato da garamant

l'alimentatore è un enermax liberty 500w ha circa 4 anni di vita. Overclock non ne è stato fatto il processore è un intel g620. Possibile che sia l'alimentatore a non reggerla?

Prova con una versione meno recente ma stabile dei driver video. Magari quelli del sito della schedà madre.

Originariamente inviato da bunzello

adobe reader può mandare in crash il sistema con schermate blu se non è aggiornato?

Le BSOD possono essere causate da qualsiasi problema, hardware o software. Fai l'analisi del minidump e vedi che esce ffuori.
Meglio aggiornare Adobe, anche per ragioni di sicurezza. Se vuoi un alternativa, free e leggerissima, dai un'occhiata a Foxit Reader.

[bunzello]

ecco perchè do la colpa a adobe il mio portatile non sarà stato segnalato.
Adobe ha rilasciato un aggiornamento per Adobe Reader che risolve alcuni problemi segnalati. Acer raccomanda l'aggiornamento all'ultima versione di Adobe Reader. Scaricare l'ultima versione sulla home page di Adobe Reader.
http://acer-it.custhelp.com/app/answ...adobe-reader-x

[Blue_screen_of_death]

Ripeto, bisogna partire dal minidump per capire le cause. Poi si cerca una soluzione.

[bunzello]

Originariamente inviato da Blue_screen_of_death

Ripeto, bisogna partire dal minidump per capire le cause. Poi si cerca una soluzione.

non si crea il minidump non lo vedo

[bunzello]

dove scarico Foxit Reader italiano?

[Blue_screen_of_death]

Originariamente inviato da bunzello

non si crea il minidump non lo vedo

Dovrebbe essere in C:\Windows\Minidump.
Se non viene creato, allora è disattivato nelle impostazioni del sistema oppure hai un file di paging troppo piccolo. Per creare il minidump serve un pagefile di almeno 400MB.

Per Foxit Reader:

Qui per il download: https://www.foxitsoftware.com/downloads/
Per l'italiano qui: http://languages.foxitsoftware.com/i...age=2&proid=56 E' un .xml da mettere nelle cartelle del programma.

Come vedi le traduzioni sono fatte da utenti "volontari" che collaborano gratuitamente. Quindi non sempre sono complete.
http://languages.foxitsoftware.com/i...age=2&proid=56

[bunzello]

Originariamente inviato da Blue_screen_of_death

Dovrebbe essere in C:\Windows\Minidump.
Se non viene creato, allora è disattivato nelle impostazioni del sistema oppure hai un file di paging troppo piccolo. Per creare il minidump serve un pagefile di almeno 400MB.

Per Foxit Reader:

Qui per il download: https://www.foxitsoftware.com/downloads/
Per l'italiano qui: http://languages.foxitsoftware.com/i...age=2&proid=56 E' un .xml da mettere nelle cartelle del programma.

Come vedi le traduzioni sono fatte da utenti "volontari" che collaborano gratuitamente. Quindi non sempre sono complete.
http://languages.foxitsoftware.com/i...age=2&proid=56

Ho visto che ho adobe air installato ma non aggiornato potrebbe essere questa la causa di malfunzionamento di adobe reader X?

[Blue_screen_of_death]

Che problemi hai con Adobe?

Per le schermate blu, attiva la generazione del minidump nelle Impostazioni, e accertati di aver attivato un file di paging di dimensioni adeguate.

Se non viene generato alcun minidump, disattiva il riavvio automatico dopo errore di sistema e posta il contenuto della schermata blu (codici di stop, errore e riferimenti a files\drivers).

[bunzello]

Originariamente inviato da Blue_screen_of_death

Che problemi hai con Adobe?

Per le schermate blu, attiva la generazione del minidump nelle Impostazioni, e accertati di aver attivato un file di paging di dimensioni adeguate.

Se non viene generato alcun minidump, disattiva il riavvio automatico dopo errore di sistema e posta il contenuto della schermata blu (codici di stop, errore e riferimenti a files\drivers).

Quando sta aperto adobe tipo per un'ora il sistema si impalla fino a quando esce la schermata blu con riavvio irregolare

[Blue_screen_of_death]

In assenza di minidump\dati relativi all'errore non posso dirti altro.

[Pagno89]

Pesano un fottio i file dei symbol :o

[Blue_screen_of_death]

non è necessario scaricarli tutti. Puoi impostare la stringa di rete, in modo da axaricare solo quelli necessari all'occorrenza.

[Pagno89]

Originariamente inviato da Blue_screen_of_death

non è necessario scaricarli tutti. Puoi impostare la stringa di rete, in modo da axaricare solo quelli necessari all'occorrenza.

La stringa che intendi è quella riportata nel primo post? Se sì, mi viene questo:

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


Loading Dump File [C:\Windows\Minidump\083115-25116-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\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18933.amd64fre.win7sp1_gdr.150715-0600
Machine Name:
Kernel base = 0xfffff800`02e4c000 PsLoadedModuleList = 0xfffff800`03093730
Debug session time: Mon Aug 31 02:33:31.855 2015 (UTC + 2:00)
System Uptime: 0 days 16:53:13.229
*********************************************************************
* 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\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.........................

************* Symbol Loading Error Summary **************
Module name            Error
ntoskrnl               The system cannot find the file specified

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*** WARNING: Unable to verify timestamp for Wdf01000.sys
*** ERROR: Module load completed but symbols could not be loaded for Wdf01000.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10D, {5, 0, 1202, fffffa800d2b08a0}

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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 : Wdf01000.sys ( Wdf01000+52a46 )

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


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols

[bunzello]

Originariamente inviato da Blue_screen_of_death

Che problemi hai con Adobe?

Per le schermate blu, attiva la generazione del minidump nelle Impostazioni, e accertati di aver attivato un file di paging di dimensioni adeguate.

Se non viene generato alcun minidump, disattiva il riavvio automatico dopo errore di sistema e posta il contenuto della schermata blu (codici di stop, errore e riferimenti a files\drivers).

con win 7 dove bisogna andare per attivare la generazione del minidump?

[AlessioM88]

ciao ragazzi, è da ieri che ogni tanto mentre uso il pc esce la schermata blu, nonostante vari crash, però, nella giornata di ieri è stato salvato solo un file nella cartella di minidump.
ho provato ad usare il debugging tool, sia con i symbol checked che con gli altri, ma mi esce sempre questo messaggio :

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


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


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
OK                                             E:\Symbols
Symbol search path is: E:\Symbols
Executable search path is: 
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18798.amd64fre.win7sp1_gdr.150316-1654
Machine Name:
Kernel base = 0xfffff800`03255000 PsLoadedModuleList = 0xfffff800`0349a890
Debug session time: Thu Jul  9 02:35:51.873 2015 (UTC + 2:00)
System Uptime: 0 days 0:40:26.951
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
.......

************* Symbol Loading Error Summary **************
Module name            Error
ntoskrnl               The system cannot find the file specified

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffaf2040aff68, 0, fffff80003299bd9, 5}

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands 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+44bd9 )

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

come devo procedere adesso?
Allego immagine di bluscreenview

[Eress]

Hai un problema coi driver video. Prova ad aggiornarli o fai rollback.

[bunzello]

gli eventi nel visualizzatore eventi 6008 e 10010 da cosa sono causati?ieri mi si è freezato il pc e si è riavviato da solo dopo circa 5 minuri.

[Fear Ripper]

Salve a tutti, ho un problema con le schermate blu e non riesco a venirci a capo.

Spoiler:

Vedete, nel PC ho un gioco RTP che non mi ha mai dato problemi, poi all'improvviso lo avvio il 19 di agosto e dopo neanche venti secondi mi parte la schermata blu.
Lì per lì ho pensato a qualche infezione, ma Malwarebytes non ha rilevato nulla, nemmeno lo scandisk ha trovato niente.
Fatto strano è che mi compare solo se utilizzo quel gioco.
Non so proprio dove sbattere la testa...
Uso Windows Vista SPK2 32 bit.