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

[Panit]

Salve!

Doppia schermata blu in un mese, pc che sembra un attimo ingolfato.
Vediamo se ho capito come fare

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


Loading Dump File [C:\Users\Administrator\Desktop\102815-15366-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 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows Vista Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.19018.amd64fre.win7sp1_gdr.150928-1507
Kernel base = 0xfffff800`02e13000 PsLoadedModuleList = 0xfffff800`0305a730
Debug session time: Wed Oct 28 23:36:10.230 2015 (GMT+1)
System Uptime: 0 days 0:07:32.274
*********************************************************************
* 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 2
*** 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
......
Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8006e12010, fffff8800703ee80, 0, 2}

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

***** 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: dxgkrnl!_TDR_RECOVERY_CONTEXT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: dxgkrnl!_TDR_RECOVERY_CONTEXT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: dxgkrnl!_TDR_RECOVERY_CONTEXT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: dxgkrnl!DXGADAPTER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Unable to load image \SystemRoot\System32\drivers\dxgmms1.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for dxgmms1.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgmms1.sys
Probably caused by : atikmpag.sys ( atikmpag+ae80 )

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

[Blue_screen_of_death]

Mancano i symbols. Configura come riportato al post n.1

[Panit]

Non riesco a capire quale symbols scaricare ne ho scaricati due (W7 server pack 1) ma non funziona

Ecco, oggi ad esempio mi dà problemi ancora con lo streaming e il semplice caricamento di FB...

[Blue_screen_of_death]

Originariamente inviato da Panit

Non riesco a capire quale symbols scaricare ne ho scaricati due (W7 server pack 1) ma non funziona

Ecco, oggi ad esempio mi dà problemi ancora con lo streaming e il semplice caricamento di FB...

Usa la stringa
SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols

come riportato nel primo post.

[Panit]

Oddio, non riesco a capire
Brutto essere ignoranti in materia

[Blue_screen_of_death]

Originariamente inviato da Panit

Oddio, non riesco a capire
Brutto essere ignoranti in materia

Apri WinDbg
File - Symbols File Path
Incolla questa stringa:

SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols

Conferma
Carica il file dmp

[Panit]

Ah ok, così è chiaro, grazie della pazienza

Ecco cosa mi riporta

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


Loading Dump File [C:\Users\Administrator\Desktop\102815-15366-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:

Non dovrebbe essere più lungo?

[Blue_screen_of_death]

Originariamente inviato da Panit

Ah ok, così è chiaro, grazie della pazienza

Ecco cosa mi riporta

Non dovrebbe essere più lungo?

Infatti, devi aspettare un po' perché sta scaricando i symbols dai server Microsoft

[Panit]

L'ho fatto ripartire

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


Loading Dump File [C:\Users\Administrator\Desktop\102815-15366-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows Vista Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.19018.amd64fre.win7sp1_gdr.150928-1507
Kernel base = 0xfffff800`02e13000 PsLoadedModuleList = 0xfffff800`0305a730
Debug session time: Wed Oct 28 23:36:10.230 2015 (GMT+1)
System Uptime: 0 days 0:07:32.274
Map \SystemRoot\system32\ntoskrnl.exe:
Image region 23fa00:236200 does not fit in mapping
*** 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 116, {fffffa8006e12010, fffff8800703ee80, 0, 2}

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

***** 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: dxgkrnl!_TDR_RECOVERY_CONTEXT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: dxgkrnl!_TDR_RECOVERY_CONTEXT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: dxgkrnl!_TDR_RECOVERY_CONTEXT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: dxgkrnl!DXGADAPTER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+ae80 )

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

[Eress]

Ti conviene usare BlueScreenViewer per l'analisi del file dmp. ci sono problemi coi simboli. Comunque sembra un problema con i driver video.

[tmviet]

Vai nel sito del tuo PC, individua quale sk video monta ed aggiorna all'ultimo driver.

Consiglio spassionato salvati su hdd esterno i tuoi files, dopo fai una installazione pulita e passa a Windows 7 sp1

[bunzello]

buongiorno chi mi spiega da cosa è causta la schermata blu?
==================================================
Dump File : 111815-24133-01.dmp
Crash Time : 18/11/2015 07:56:26
Bug Check String : REGISTRY_ERROR
Bug Check Code : 0x00000051
Parameter 1 : 00000000`00000001
Parameter 2 : fffff8a0`00023370
Parameter 3 : 00000000`00ddf000
Parameter 4 : 00000000`00000374
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\111815-24133-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 278.928
Dump File Time : 18/11/2015 07:58:41
==================================================

[Blue_screen_of_death]

Originariamente inviato da bunzello

buongiorno chi mi spiega da cosa è causta la schermata blu?
==================================================
Dump File : 111815-24133-01.dmp
Crash Time : 18/11/2015 07:56:26
Bug Check String : REGISTRY_ERROR
Bug Check Code : 0x00000051
Parameter 1 : 00000000`00000001
Parameter 2 : fffff8a0`00023370
Parameter 3 : 00000000`00ddf000
Parameter 4 : 00000000`00000374
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\111815-24133-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 278.928
Dump File Time : 18/11/2015 07:58:41
==================================================

Problemi al registro, al file system o all'hard disk.

[bunzello]

Originariamente inviato da Blue_screen_of_death

Problemi al registro, al file system o all'hard disk.

Quindi cosa dovrei provare a fare?

[Blue_screen_of_death]

Originariamente inviato da bunzello

Quindi cosa dovrei provare a fare?

Un ripristino di sistema ad un punto precedente, e, se non dovessi risolvere, un controllo al.disco con chkdsk

[tmviet]

Da Start / promt dei comandi scrivi:

chkdsk /F

Dove tra... dsk e /F devi inserire uno 'spazio'

[Jeremy01]

Sapreste dirmi qualcosa? (sistema a default, sotto linx per testare il sistema in seguito a dei freeze)

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, ffffe0007f425028, fa000000, 400405}

Probably caused by : GenuineIntel

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe0007f425028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000fa000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000400405, Low order 32-bits of the MCi_STATUS value.



DUMP_TYPE:  1

BUGCHECK_P1: 0

BUGCHECK_P2: ffffe0007f425028

BUGCHECK_P3: fa000000

BUGCHECK_P4: 400405

BUGCHECK_STR:  0x124_GenuineIntel

CPU_COUNT: 4

CPU_MHZ: 966

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 1e

CPU_STEPPING: 5

CPU_MICROCODE: 6,1e,5,0 (F,M,S,R)  SIG: 5'00000000 (cache) 5'00000000 (init)

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  linpack_xeon64

CURRENT_IRQL:  f

ANALYSIS_SESSION_HOST:  HM

ANALYSIS_SESSION_TIME:  02-15-2016 01:43:11.0463

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

STACK_TEXT:  
ffffd000`d5517cf8 fffff803`de1e1213 : 00000000`00000124 00000000`00000000 ffffe000`7f425028 00000000`fa000000 : nt!KeBugCheckEx
ffffd000`d5517d00 fffff803`ddbdae4d : 00000000`00000001 ffffe000`7b5e9160 ffffe000`7b5e9160 ffffe000`7f425028 : hal!HalBugCheckSystem+0xcf
ffffd000`d5517d40 fffff803`de1e16a0 : 00000000`00000728 00000000`00000001 ffffd000`d5518130 00000000`00000000 : nt!WheaReportHwError+0x22d
ffffd000`d5517da0 fffff803`de1e1a0d : ffffe000`00000010 ffffe000`7b5e9160 ffffd000`d5517f48 ffffe000`7b5e9160 : hal!HalpMcaReportError+0x50
ffffd000`d5517ef0 fffff803`de1e18f8 : ffffe000`7b5e8bb0 00000000`00000001 00000000`00000001 00000000`00000000 : hal!HalpMceHandlerCore+0xe1
ffffd000`d5517f40 fffff803`de1e1b42 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4
ffffd000`d5517f80 fffff803`de1e1ccf : ffffe000`7b5e8bb0 ffffd000`d55181b0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
ffffd000`d5517fb0 fffff803`ddb75dbb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
ffffd000`d5517fe0 fffff803`ddb75b71 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
ffffd000`d5518120 00000001`402cc511 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171
00000000`0263efe0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00000001`402cc511


STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  a46f769f9bb88b377fa260529f59dcef5f50e990

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  29312a4267facee58b38f6e4355aa4f81a0aa678

THREAD_SHA1_HASH_MOD:  dcad533a74a3db89beeba48522fb4c242f2efae0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_MAE

PRIMARY_PROBLEM_CLASS:  0x124_GenuineIntel_PROCESSOR_MAE

TARGET_TIME:  2016-02-15T00:08:42.000Z

OSBUILD:  9600

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 8.1

OSEDITION:  Windows 8.1 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2015-12-30 15:49:56

BUILDDATESTAMP_STR:  151230-0600

BUILDLAB_STR:  winblue_ltsb

BUILDOSVER_STR:  6.3.9600.18185.amd64fre.winblue_ltsb.151230-0600

ANALYSIS_SESSION_ELAPSED_TIME: 184a

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x124_genuineintel_processor_mae

FAILURE_ID_HASH:  {7c95de0c-286c-8226-45c2-422b4de101d6}

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

[Eress]

Difficile da dire, ma sembra un problema collegato alla CPU

https://msdn.microsoft.com/en-us/lib...or=-2147217396

[tmviet]

Evento 1040 Cod. id:124

Potrebbe essere un problema driver della scheda video ?

[mat-91]

Ciao a tutti, improvvisamente (non ho installato nessuna periferica) ho avuto questo errore.

L'unica cosa strana che posso segnalare è che nelle ultime accensioni non è riuscito a configurare correttamente degli aggiornamenti e, se non ricordo male l'ultima volta che l'ho spento (anche mio fratello usa il mio pc ogni tanto) avevo provato a far installare solo una parte degli aggiornamenti per cercare di idividuare, per eliminazione, quale aggiornamento non riuscisse ad installare.

Adesso il pc non si avvia nemmeno, dopo un po che appare la schermata di caricamento di windows crasha e da questa schermata (talmente velocemente che ho dovuto estrarre un fotogramma da un video).

PS: non parte nemmeno in modalità provvisoria (nessuna delle 3), ho provato quindi a fare un ripristino con il disco di installazione e da che no riesce a ripristinare automaticamente.


Qualcuno ha un idea di cosa potrei provare a fare prima di procedere con una formattazione?

PS: scusate se le immagini le ha caricate così grandi...