Schermata blu su Windows7

surfsound · 14-12-2011, 09:42

Salve a tutti.
Premesso che non sono molto esperto di pc... è da un paio di un giorni(ma non sempre) che mi appare un problema piuttosto frustante ovvero il computer si riavvia all'improvviso e mi appare una schermata blu e la stessa cosa succede ogni qual volta che torno alla schermata su windows 7.
Poi mi appare questa scritta:

Firma problema:
Nome evento problema: BlueScreen
Versione SO: 6.1.7600.2.0.0.768.3
ID impostazioni locali: 1040

Ulteriori informazioni sul problema:
BCCode: a
BCP1: 000000000007F000
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF80003499F64
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

File che contribuiscono alla descrizione del problema:
C:\Windows\Minidump\121311-30685-01.dmp
C:\Users\Giuseppe\AppData\Local\Temp\WER-54397-0.sysdata.xml

Leggere l'informativa sulla privacy online:
http://go.microsoft.com/fwlink/?link...8&clcid=0x0410

Se l'informativa sulla privacy online non è disponibile, leggere quella offline:
C:\Windows\system32\it-IT\erofflps.txt

Aiuto please

Eress · 14-12-2011, 09:48

Serve il file dmp per l'analisi, leggi qui

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

surfsound · 14-12-2011, 12:19

Io ho seguito tutto alla lettera però sembra che mi dia un problema con i simboli. Riporto qui 1 dei tanti chash dump:

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

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

Symbol search path is: C:\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 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`03411000 PsLoadedModuleList = 0xfffff800`0364ee70
Debug session time: Tue Dec 13 23:30:53.323 2011 (UTC + 1:00)
System Uptime: 0 days 0:03:14.227
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
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {7f000, 2, 1, fffff80003499f64}

***** 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+88f64 )

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

surfsound · 14-12-2011, 12:29

un altro crash mi da questo problema
***************************************************
Probably caused by : hardware ( win32k!zzzInitTask+6 )

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

Nella cartella di minidump in tutto sono 50, perchè?

Eress · 14-12-2011, 15:37

Quote:

Originariamente inviato da surfsound

un altro crash mi da questo problema
***************************************************
Probably caused by : hardware ( win32k!zzzInitTask+6 )

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

Nella cartella di minidump in tutto sono 50, perchè?

Inizia testando l'HD con CrystalDiskInfo
Per analizzare i file dmp puoi usare il più semplice Bluescreenview

14-12-2011, 09:42	#1
surfsound Junior Member Iscritto dal: Dec 2011 Messaggi: 3	Schermata blu su Windows7 Salve a tutti. Premesso che non sono molto esperto di pc... è da un paio di un giorni(ma non sempre) che mi appare un problema piuttosto frustante ovvero il computer si riavvia all'improvviso e mi appare una schermata blu e la stessa cosa succede ogni qual volta che torno alla schermata su windows 7. Poi mi appare questa scritta: Firma problema: Nome evento problema: BlueScreen Versione SO: 6.1.7600.2.0.0.768.3 ID impostazioni locali: 1040 Ulteriori informazioni sul problema: BCCode: a BCP1: 000000000007F000 BCP2: 0000000000000002 BCP3: 0000000000000001 BCP4: FFFFF80003499F64 OS Version: 6_1_7600 Service Pack: 0_0 Product: 768_1 File che contribuiscono alla descrizione del problema: C:\Windows\Minidump\121311-30685-01.dmp C:\Users\Giuseppe\AppData\Local\Temp\WER-54397-0.sysdata.xml Leggere l'informativa sulla privacy online: http://go.microsoft.com/fwlink/?link...8&clcid=0x0410 Se l'informativa sulla privacy online non è disponibile, leggere quella offline: C:\Windows\system32\it-IT\erofflps.txt Aiuto please

14-12-2011, 09:48	#2
Eress Senior Member Iscritto dal: Jan 2010 Messaggi: 37091	Serve il file dmp per l'analisi, leggi qui http://www.hwupgrade.it/forum/showthread.php?t=1955371 __________________ Analemma - Slowdive - Facebook Motto Microsoft: "If it's broken, and I'm the one who broke it, don't fix it!"

14-12-2011, 12:19	#3
surfsound Junior Member Iscritto dal: Dec 2011 Messaggi: 3	Io ho seguito tutto alla lettera però sembra che mi dia un problema con i simboli. Riporto qui 1 dei tanti chash dump: Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\121311-30685-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: C:\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 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16841.amd64fre.win7_gdr.110622-1503 Machine Name: Kernel base = 0xfffff800`03411000 PsLoadedModuleList = 0xfffff800`0364ee70 Debug session time: Tue Dec 13 23:30:53.323 2011 (UTC + 1:00) System Uptime: 0 days 0:03:14.227 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 .... ******************************************************************************* * * * Bugcheck Analysis * * * ***************************************************************************** Use !analyze -v to get detailed debugging information. BugCheck A, {7f000, 2, 1, fffff80003499f64} * 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+88f64 ) Followup: MachineOwner ---------

14-12-2011, 12:29	#4
surfsound Junior Member Iscritto dal: Dec 2011 Messaggi: 3	un altro crash mi da questo problema *************************************************** Probably caused by : hardware ( win32k!zzzInitTask+6 ) Followup: MachineOwner --------- Nella cartella di minidump in tutto sono 50, perchè?

Strumenti
Mostra una versione stampabile Invia questa pagina per email