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

[Pierq]

ho un problema, il il debugging tool mi dice che non uso i simboli corretti però ho seguito tutte le procedure spiegate nel primo post. Ho installato il debugging tool, ho scaricato il file symbol da qui:
- http://msdn.microsoft.com/en-us/wind...g463028.aspx#d

Ho windows 7 service pack 1 a 64 bit ed ho scaricato sia il file retail symbol che quello checked sumbol e li ho installati separatamente però mi da sempre lo stesso problema. come posso farE?

[~Jaco~]

Nota bene: Se il controllo del file dump mostra a video "Your debugger is not using the correct symbols", inserite come percorso dei symbols il link che segue dopo aver eliminato quelli precedentemente installati (al posto di c:\Windows\symbols potete usare una qualsiasi cartella di vostra preferenza)

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

[~Jaco~]

Anche a me faceva lo stesso: rimuovi l'installazione dei simboli che hai scaricato e installato e dal debugging tool a "symbol file path" incolli l'indirizzo "SRV*C:\......." lanci l'analisi e tutto dovrebbe andare a buon fine

[Eress]

Originariamente inviato da Pierq

Ho windows 7 service pack 1 a 64 bit ed ho scaricato sia il file retail symbol che quello checked sumbol e li ho installati separatamente però mi da sempre lo stesso problema. come posso farE?

Puoi anche usare il semplice strumento alternativo Bluescreenview (che non si installa nemmeno) come specificato nella prima pagina del thread

[~Jaco~]

Ho eseguito il comando clean come era scritto nel post ma quando arrivo a scollegare l'hard disk non me lo scollega ugualmente da rimozione sicura e mi continua a dare a gestione dispositivi il punto esclamativo segnalandomi risoluzione problemi per l'hard disk esterno...
Ho formattato creando un file system ntfs... non so davvero piu cosa fare per utilizzare questi hard disk che andavano
Qualche altro suggerimento?

[deidara80]

ho avuto un'altra schermata blu, e anceh se o seguito la guida in prima pagina non ho nessuna cartella minidump.

ho fatto una foto alla schermata.



*** STOP: 0x000000F4 (0x000000000000000003, 0xFFFFFA8005287B30, 0xFFFFFA8005287E10
0xFFFFF8000319c8B0)

sapete cosa può essere?

grazie

[djalexal]

Altra schermata blu

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


Loading Dump File [C:\Windows\Minidump\081811-23743-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:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e56000 PsLoadedModuleList = 0xfffff800`0309b670
Debug session time: Thu Aug 18 14:43:58.940 2011 (UTC + 2:00)
System Uptime: 0 days 0:04:29.189
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {0, fffff8800316db70, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\intelppm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : intelppm.sys ( intelppm+2c61 )

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

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

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
x86 Processors
If the processor has ONLY MCE feature available (For example Intel
Pentium), the parameters are:
1 - Low 32 bits of P5_MC_TYPE MSR
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of P5_MC_ADDR MSR
4 - Low 32 bits of P5_MC_ADDR MSR
If the processor also has MCA feature available (For example Intel
Pentium Pro), the parameters are:
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
IA64 Processors
1 - Bugcheck Type
1 - MCA_ASSERT
2 - MCA_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing MCA.
3 - MCA_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
4 - MCA_FATAL
FW reported a fatal MCA.
5 - MCA_NONFATAL
SAL reported a recoverable MCA and we don't support currently
support recovery or SAL generated an MCA and then couldn't
produce an error record.
0xB - INIT_ASSERT
0xC - INIT_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
0xD - INIT_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
0xE - INIT_FATAL
Not used.
2 - Address of log
3 - Size of log
4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
AMD64 Processors
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 0000000000000000
Arg2: fffff8800316db70
Arg3: 0000000000000000
Arg4: 0000000000000000

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


BUGCHECK_STR: 0x9C_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: f

LAST_CONTROL_TRANSFER: from fffff80002e1f818 to fffff80002ed2c40

STACK_TEXT:
fffff880`0316db38 fffff800`02e1f818 : 00000000`0000009c 00000000`00000000 fffff880`0316db70 00000000`00000000 : nt!KeBugCheckEx
fffff880`0316db40 fffff800`02e1ef57 : 00000000`00000004 00000000`00000000 00000000`00000004 00000000`00000000 : hal!HalpMcaReportError+0x164
fffff880`0316dc90 fffff800`02e12e88 : 00000000`00000001 fffff880`03165180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x9f
fffff880`0316dcc0 fffff800`02ed152c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`0316dcf0 fffff800`02ed1393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`0316de30 fffff880`05bd3c61 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`0318db58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm+0x2c61


STACK_COMMAND: kb

FOLLOWUP_IP:
intelppm+2c61
fffff880`05bd3c61 ?? ???

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: intelppm+2c61

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: intelppm

IMAGE_NAME: intelppm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc0fd

FAILURE_BUCKET_ID: X64_0x9C_GenuineIntel_intelppm+2c61

BUCKET_ID: X64_0x9C_GenuineIntel_intelppm+2c61

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



Come posso risolvere?

[djalexal]

Girando su internet ho trovato questa discussione:

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

Può darsi che il problema sia quello

[Eress]

Devi cercare di estrarre il file dmp, nella guida è spiegato come fare

[djalexal]

Altra blue screen


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


Loading Dump File [C:\Windows\Minidump\082311-21434-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:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e09000 PsLoadedModuleList = 0xfffff800`0304e670
Debug session time: Tue Aug 23 17:38:19.427 2011 (UTC + 2:00)
System Uptime: 0 days 5:57:44.302
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {0, fffff880031dfb70, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\intelppm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : intelppm.sys ( intelppm+2c61 )

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

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

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
x86 Processors
If the processor has ONLY MCE feature available (For example Intel
Pentium), the parameters are:
1 - Low 32 bits of P5_MC_TYPE MSR
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of P5_MC_ADDR MSR
4 - Low 32 bits of P5_MC_ADDR MSR
If the processor also has MCA feature available (For example Intel
Pentium Pro), the parameters are:
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
IA64 Processors
1 - Bugcheck Type
1 - MCA_ASSERT
2 - MCA_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing MCA.
3 - MCA_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
4 - MCA_FATAL
FW reported a fatal MCA.
5 - MCA_NONFATAL
SAL reported a recoverable MCA and we don't support currently
support recovery or SAL generated an MCA and then couldn't
produce an error record.
0xB - INIT_ASSERT
0xC - INIT_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
0xD - INIT_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
0xE - INIT_FATAL
Not used.
2 - Address of log
3 - Size of log
4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
AMD64 Processors
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 0000000000000000
Arg2: fffff880031dfb70
Arg3: 0000000000000000
Arg4: 0000000000000000

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


BUGCHECK_STR: 0x9C_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: f

LAST_CONTROL_TRANSFER: from fffff80003404818 to fffff80002e85c40

STACK_TEXT:
fffff880`031dfb38 fffff800`03404818 : 00000000`0000009c 00000000`00000000 fffff880`031dfb70 00000000`00000000 : nt!KeBugCheckEx
fffff880`031dfb40 fffff800`03403f57 : 00000000`00000004 00000000`00000000 00000000`00000004 00000000`00000000 : hal!HalpMcaReportError+0x164
fffff880`031dfc90 fffff800`033f7e88 : 00000000`00000001 fffff880`031d7180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x9f
fffff880`031dfcc0 fffff800`02e8452c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`031dfcf0 fffff800`02e84393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`031dfe30 fffff880`05badc61 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`031ffb58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm+0x2c61


STACK_COMMAND: kb

FOLLOWUP_IP:
intelppm+2c61
fffff880`05badc61 ?? ???

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: intelppm+2c61

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: intelppm

IMAGE_NAME: intelppm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc0fd

FAILURE_BUCKET_ID: X64_0x9C_GenuineIntel_intelppm+2c61

BUCKET_ID: X64_0x9C_GenuineIntel_intelppm+2c61

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

[Eress]

Siamo sempre al solito punto, ha il driver del processore che crea problemi o ci può esesre un conflitto con altri driver, se ultimamente hai fatto qualche modifica dei driver con aggiornamenti dovresti provare a tornare indietro

[Q_Zero]

Buongiorno a tutti,
i seguenti file ntoskrnl.exe e hal.dll mi generano delle bsod sul sistema overcloccato in firma con win seven 64bit.

La cosa è un po curiosa perchè il sistema è overcloccato da più di un anno, ed stato a suo tempo testato con ore e ore di linx e prime95. Da un pò di tempo a questa parte vengono frequentemente generate bsod, sia mentre eseguo linx/prime95 sia mentre uso il sistema normalmente ma che scompaiono non appena torno tutto a default.

Vorrei sapere se la causa e derivata dall'oc (il sistema quindi si è destabilizzato con il tempo ..) oppure se il problema è legato ad aggiornamenti driver/bios...

grazie.

[Eress]

Con l'analisi dei file dmp non puoi esesre certo che sia l'oc, bisogna provare, l'unica certezza potresti averla eliminando per un po' l'OC
Dai problemi riscontrati ti converrebbe iniziare testando a fondo l'HD; scandisk e una controllata con HDTune (Error Scan) e CrystalDiskInfo

[Q_Zero]

Originariamente inviato da Eress

Con l'analisi dei file dmp non puoi esesre certo che sia l'oc, bisogna provare, l'unica certezza potresti averla eliminando per un po' l'OC
Dai problemi riscontrati ti converrebbe iniziare testando a fondo l'HD; scandisk e una controllata con HDTune (Error Scan) e CrystalDiskInfo

Ti ringrazio per la risposta inizio a testare l'HD

[x119]

Mentre gioco ad ACII, con sistemato overcloccato (ma è sempre stato una roccia) ho avuto due bsod in due giorni:

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {0, fffff8800336cb70, 0, 0}

Unable to load image intelppm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : intelppm.sys ( intelppm+39c2 )

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

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

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
    x86 Processors
        If the processor has ONLY MCE feature available (For example Intel
        Pentium), the parameters are:
        1 - Low  32 bits of P5_MC_TYPE MSR
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of P5_MC_ADDR MSR
        4 - Low  32 bits of P5_MC_ADDR MSR
        If the processor also has MCA feature available (For example Intel
        Pentium Pro), the parameters are:
        1 - Bank number
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
        4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
    IA64 Processors
        1 - Bugcheck Type
            1 - MCA_ASSERT
            2 - MCA_GET_STATEINFO
                SAL returned an error for SAL_GET_STATEINFO while processing MCA.
            3 - MCA_CLEAR_STATEINFO
                SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
            4 - MCA_FATAL
                FW reported a fatal MCA.
            5 - MCA_NONFATAL
                SAL reported a recoverable MCA and we don't support currently
                support recovery or SAL generated an MCA and then couldn't
                produce an error record.
            0xB - INIT_ASSERT
            0xC - INIT_GET_STATEINFO
                  SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
            0xD - INIT_CLEAR_STATEINFO
                  SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
            0xE - INIT_FATAL
                  Not used.
        2 - Address of log
        3 - Size of log
        4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
    AMD64 Processors
        1 - Bank number
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
        4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 0000000000000000
Arg2: fffff8800336cb70
Arg3: 0000000000000000
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x9C_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

LAST_CONTROL_TRANSFER:  from fffff800033f56e0 to fffff80002e77f00

STACK_TEXT:  
fffff880`0336cb38 fffff800`033f56e0 : 00000000`0000009c 00000000`00000000 fffff880`0336cb70 00000000`00000000 : nt!KeBugCheckEx
fffff880`0336cb40 fffff800`033f4e1f : 00000000`00000004 00000000`00000000 00000000`00000004 00000000`00000000 : hal!HalpMcaReportError+0x164
fffff880`0336cc90 fffff800`033e8e88 : 00000000`00000000 fffff880`03364180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x9f
fffff880`0336ccc0 fffff800`02e767ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`0336ccf0 fffff800`02e76613 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`0336ce30 fffff880`045839c2 : fffff800`02e85a3a 00000000`0041c82b fffffa80`057cbdd8 00000000`00000002 : nt!KiMcheckAbort+0x153
fffff880`0338cc98 fffff800`02e85a3a : 00000000`0041c82b fffffa80`057cbdd8 00000000`00000002 fffff880`03364180 : intelppm+0x39c2
fffff880`0338cca0 fffff800`02e806cc : fffff880`03364180 fffff880`00000000 00000000`00000000 fffffa80`056280f0 : nt!PoIdle+0x53a
fffff880`0338cd80 00000000`00000000 : fffff880`0338d000 fffff880`03387000 fffff880`0338cd40 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
intelppm+39c2
fffff880`045839c2 ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  intelppm+39c2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: intelppm

IMAGE_NAME:  intelppm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc0fd

FAILURE_BUCKET_ID:  X64_0x9C_GenuineIntel_intelppm+39c2

BUCKET_ID:  X64_0x9C_GenuineIntel_intelppm+39c2

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

mi pare identico a quello dell'altro utente...

[Eress]

Ho trovato questo col tuo stesso errore

http://www.overclock.net/intel-cpus/...help-0x9c.html

[x119]

Grazie, potrebbe essere...dopotutto ACII è molto cpu dipendente, quindi ho alzato due voltaggi e abbassato l'overclock...vedremo se si ripresenta!

[Azzi]

ciao a tutti,
ieri ho cambiato la scheda madre rotta al mio pc Windows 7 x64 Ultimate. Ora a ogni riavvio (un secondo dopo logo di Windows) mi compare schermata blue. Non ho nemmeno il tempo di vedere che il pc si riavvia di nuovo.

Come posso reinstallare i driver di Windows o ripulirlo...Vorrei evitare di formattare tutto...

[Eress]

Ê normale, quando cambi la scheda madre devi reinstallare l'OS

[Azzi]

normale no dai...al lavoro cambiando tutto hardware Windows 7 è partito tranquillamente...

a casa invece è tutto uguale tranne mobo . Almeno con XP c'era la possibilità di fare Repair e si sistemava tutto...