View Full Version : Blue Screen notebook nuovo
djalexal
13-08-2011, 17:30
Ho acquistato un notebook acer 5750G da due settimane circa in una famosa catena di negozi di elettronica...il pc ha le seguenti caratteristiche:
Windows 7 home premium 64 bit
Intel core i5-2410M
Nvidia geforce gt 540m
4gb ram ddr3
500gb hard disk
Il problema e che senza motivo e senza che faccia qualche azione in particolare il pc si blocca e mi si presenta la schermata blu di errore...ovviamente ho installato qualche programma durante l uso del pc....all'inizio pensavo fosse legato al surriscaldamento del pc tant è che ho installato speedfan per controllare la temperatura, ma queste si attestavano al massimo sui 50 gradi per la cpu quindi non credo sia quello il problema...leggendo su internet avevo scoperto che l SO o la cpu vanno in contrasto quando vengono avviate alcune funzioni della GPU...cosi ho installato tutti i tipi di aggiornamenti sia per la gpu, adobe flash, windows update, disinstallato applicazioni inutili, provato ad usare altri browser e cosi via...ma il problema continua a ripresentarsi senza capire quale sia il motivo, e non succede mai in modo continuo, in giorni succede che si blocchi in altri no. ho fatto scansioni con antivirus ma non ha trovato niente..non riesco a venirne fuori. I dati del problema sono questi:
Firma problema:
Nome evento problema: Blue screen
Versione SO: 6.1.7601.2.1.0.768.3
ID impostazioni locali: 1040
Ulteriori informazioni sul problema:
BCCode: 9c
BCP1: 0000000000000000
BCP2: FFFFF8800316DB70
BCP3: 0000000000000000
BCP4: 0000000000000000
OS version: 6_1_7601
Service Pack: 1_0
Product: 768_1
File che contribuiscono alla descrizione del problema:
c:\Windows\Minidump\081311-29546-01.dmp
c:\ Windows\Temp\Wer-31793-0sysdata.xml
Aiutatemi!
Per capirci qualcosa serve analizzare il file dmp
http://www.hwupgrade.it/forum/showthread.php?t=1955371
postalo qui che gli diamo una controllata
djalexal
14-08-2011, 16:00
Questo è il primo tipo di errore:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\081211-18345-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`02e4e000 PsLoadedModuleList = 0xfffff800`03093670
Debug session time: Fri Aug 12 19:00:03.767 2011 (UTC + 2:00)
System Uptime: 0 days 1:51:52.016
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 fffff80002e17818 to fffff80002ecac40
STACK_TEXT:
fffff880`0316db38 fffff800`02e17818 : 00000000`0000009c 00000000`00000000 fffff880`0316db70 00000000`00000000 : nt!KeBugCheckEx
fffff880`0316db40 fffff800`02e16f57 : 00000000`00000004 00000000`00000000 00000000`00000004 00000000`00000000 : hal!HalpMcaReportError+0x164
fffff880`0316dc90 fffff800`02e0ae88 : 00000000`00000001 fffff880`03165180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x9f
fffff880`0316dcc0 fffff800`02ec952c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`0316dcf0 fffff800`02ec9393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`0316de30 fffff880`05b47c61 : 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`05b47c61 ?? ???
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
---------
djalexal
14-08-2011, 16:04
Questo è il secondo tipo di crash:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\081311-29546-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Mini Kernel Dump does not have process information
Symbol search path is: SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Unable to load image Unknown_Module_284a0026`48002648, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_284a0026`48002648
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_284a0026`48002648
Debugger can not determine kernel base address
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`02e62000 PsLoadedModuleList = 0xfffff800`030a7670
Debug session time: Sat Aug 13 17:43:41.811 2011 (UTC + 2:00)
System Uptime: 0 days 5:25:11.059
Unable to load image Unknown_Module_284a0026`48002648, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_284a0026`48002648
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_284a0026`48002648
Debugger can not determine kernel base address
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}
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
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:
------------------
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
BUGCHECK_STR: 0x9C_GenuineIntel
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002e2b818 to fffff80002edec40
STACK_TEXT:
fffff880`0316db38 fffff800`02e2b818 : 00000000`0000009c 00000000`00000000 fffff880`0316db70 00000000`00000000 : 0xfffff800`02edec40
fffff880`0316db40 00000000`0000009c : 00000000`00000000 fffff880`0316db70 00000000`00000000 00000000`00000000 : 0xfffff800`02e2b818
fffff880`0316db48 00000000`00000000 : fffff880`0316db70 00000000`00000000 00000000`00000000 00000000`00000000 : 0x9c
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: CORRUPT_MODULELIST
Followup: MachineOwner
---------
djalexal
14-08-2011, 16:05
Questi postati sono crash avvenuti prima dell installazione di windows debbugging tools...prima della sua installazione non si sono ancora verificati crash
Da quel log non si capisce assolutamente niente, del resto il risultato è analisi inconclusiva
djalexal
14-08-2011, 18:02
Quindi che dovrei fare? Se non si è capito non sono molto bravo ad usare questi programmini :D
Per ora non puoi fare niente, ma solo aspettare la prossima bsod sperando che il file dmp sia analizzabile :D
Comunque essendo il pc così nuovo un giro dalle parti dove l'hai preso ce lo farei, non intendo con la mazza da baseball, ma col pc :D
djalexal
14-08-2011, 19:08
Ci sono già tornato purtroppo per cambiare pc, perché il primo che mi avevano dato aveva lo schermo rotto, aveva enormi crepe e si notava solo con schermo acceso.....aspettiamo il prossimo crash!
djalexal
14-08-2011, 19:38
Altro crash con schermata blu! Comunque succede durante la riproduzione di video su internet.
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\081411-21372-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`02e15000 PsLoadedModuleList = 0xfffff800`0305a670
Debug session time: Sun Aug 14 20:27:58.168 2011 (UTC + 2:00)
System Uptime: 0 days 4:05:39.417
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 fffff80003410818 to fffff80002e91c40
STACK_TEXT:
fffff880`031dfb38 fffff800`03410818 : 00000000`0000009c 00000000`00000000 fffff880`031dfb70 00000000`00000000 : nt!KeBugCheckEx
fffff880`031dfb40 fffff800`0340ff57 : 00000000`00000004 00000000`00000000 00000000`00000004 00000000`00000000 : hal!HalpMcaReportError+0x164
fffff880`031dfc90 fffff800`03403e88 : 00000000`00000001 fffff880`031d7180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x9f
fffff880`031dfcc0 fffff800`02e9052c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`031dfcf0 fffff800`02e90393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`031dfe30 fffff880`05bbbc61 : 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`05bbbc61 ?? ???
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
---------
djalexal
18-08-2011, 14:17
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
---------
Quest'ultimo è relativo all'Intel Processor Driver
djalexal
18-08-2011, 18:51
Quindi cosa dovrei fare?
djalexal
23-08-2011, 20:07
Ancora crash
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
---------
C'è un problema col processore e i driver, prova a reinstallarli o ad agigornarli
djalexal
28-08-2011, 23:48
Ho aggiornato di tutto chipset, schede video, anche bios....ho preso tutti i tipi di aggiornamenti sia dal sito dell intel che dal sito acer, purtroppo i diver del processore non possono essere aggiornati perchè mi da incompatibilità...comunque sia il pc continua a crasharsi.....ho provato a vedere se il mio pc rientra nella lista di quelli difettati a causa di un problema di design del processore sandy bridge, ma non rientra tra quelli sembra essere a posto, non so davvero più che fare, l unica speranza è quella di darlo in garanzia.
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\082811-22604-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`02e1a000 PsLoadedModuleList = 0xfffff800`0305f670
Debug session time: Sun Aug 28 22:17:45.500 2011 (UTC + 2:00)
System Uptime: 0 days 2:11:43.749
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 fffff80003415818 to fffff80002e96c40
STACK_TEXT:
fffff880`031dfb38 fffff800`03415818 : 00000000`0000009c 00000000`00000000 fffff880`031dfb70 00000000`00000000 : nt!KeBugCheckEx
fffff880`031dfb40 fffff800`03414f57 : 00000000`00000004 00000000`00000000 00000000`00000004 00000000`00000000 : hal!HalpMcaReportError+0x164
fffff880`031dfc90 fffff800`03408e88 : 00000000`00000001 fffff880`031d7180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x9f
fffff880`031dfcc0 fffff800`02e9552c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`031dfcf0 fffff800`02e95393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`031dfe30 fffff880`05bbfc61 : 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`05bbfc61 ?? ???
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
---------
A sto punto ti conviene mandarlo in RMA
vBulletin® v3.6.4, Copyright ©2000-2025, Jelsoft Enterprises Ltd.