11-05-2011, 03:47 AM
Safe mode also causes BSOD. The very annoying thing is, that I thought many times I fixed the problem and the system ran for a couple of days without any problem. But then, bang, BSOD. System was started again, three hours later BSOD, system started again, no BSOD for 2 days, then 3 a day and so on... no matter what I'm doing, surfing, writing or nothing, this error isn't reproducable by running a special process. I even tried a computer game and prime95 to get the system to it's max, but nothing happened. I can play a game for an hour and it works, then I leave the NB alone for making a telephone call for instance, then it had BSOD while I was away.
When it is running on batteries, I get much more BSODs, I think. Last time I tried I got BSOD every time I started the computer and the system never ran more than five minutes. This and the minidump made me thinking vcore might be the problem. Or the CPU really is broken.
Complete Crashlog:
It is not always intelppm.sys, but the log always says that the problem was caused by the CPU.
Specs: LX86, i5 430M, Radeon HD 5650, 640GB HD, 4GB DDR3.
Thank you very much for your help.
When it is running on batteries, I get much more BSODs, I think. Last time I tried I got BSOD every time I started the computer and the system never ran more than five minutes. This and the minidump made me thinking vcore might be the problem. Or the CPU really is broken.
Complete Crashlog:
Quote:Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\110311-32058-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`03418000 PsLoadedModuleList = 0xfffff800`03655e70
Debug session time: Thu Nov 3 13:17:55.060 2011 (UTC + 1:00)
System Uptime: 2 days 15:05:12.605
Loading Kernel Symbols
...............................................................
................................................................
............................................................
Loading User Symbols
Loading unloaded module list
..............................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8007ac6028, be000000, 800400}
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 : hardware
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: fffffa8007ac6028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
BUGCHECK_STR: 0x124_GenuineIntel
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: f
STACK_TEXT:
fffff880`009f0a58 fffff800`03a06903 : 00000000`00000124 00000000`00000000 fffffa80`07ac6028 00000000`be000000 : nt!KeBugCheckEx
fffff880`009f0a60 fffff800`0359e293 : 00000000`00000001 fffffa80`07a9c010 00000000`00000000 fffffa80`07a9c060 : hal!HalBugCheckSystem+0x1e3
fffff880`009f0aa0 fffff800`03a065c8 : 00000000`00000728 fffffa80`07a9c010 fffff880`009f0e30 fffff880`009f0e00 : nt!WheaReportHwError+0x263
fffff880`009f0b00 fffff800`03a05f1a : fffffa80`07a9c010 fffff880`009f0e30 fffffa80`07a9c010 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009f0c50 fffff800`03a05dd5 : 00000000`00000004 00000000`00000001 fffff880`009f0eb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009f0c90 fffff800`039f9e88 : 00000000`00000001 fffff880`009e8180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009f0cc0 fffff800`03486e6c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009f0cf0 fffff800`03486cd3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009f0e30 fffff880`05602c61 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`0391bc98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm+0x2c61
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE
BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE
Followup: MachineOwner
---------
It is not always intelppm.sys, but the log always says that the problem was caused by the CPU.
Specs: LX86, i5 430M, Radeon HD 5650, 640GB HD, 4GB DDR3.
Thank you very much for your help.