Karli Watson
New Member
Hello experts!
I've recently been experiencing a very regular BSOD on my PC. I'm fairly sure it's a hardware issue (minidumps here: View attachment Minidumps.zip) as I've had a look at the minidump and it's a 124 error (0x124_GenuineIntel or X64_0x124_GenuineIntel_PROCESSOR_BUS depending on which dump I open). I thought that heat might have been the problem, so I've cleaned the (admittedly large amount of) dust from the innards, but it doesn't seem to have helped. Still could be the problem I guess, especially as the problem appears to become more severe (every 5 mins instead of every hour, say) when it's switched on for a long time. But then it also happens whenever I try anything processor-intensive (I think - haven't tested that extensively).
Two interesting points to note:
1) I have a dual boot Win 7 / XP system and the BSOD happens on both (lending weight to the hardware problem guess).
2) This started shortly after I installed a multitouch simulator for WP7 development on windows 7 (see Step by Step Tutorial : Installing Multi-Touch Simulator for Silverlight Phone 7 | Michael Sync). I have subsequently uninstalled, but the very first BSOD happened seconds after installation - coincidence?
I also could swear that I recently heard a mysterious loud "crack" noise, but I don't know when and I don't know if it came from the computer. But it's possible. Probably best to ignore that one.
I am currently running the win 7 memory test tool, but it's taking hours. I'll report back and edit this post if it comes back with any results.
In the meantime, if anyone can take a look at those minidump file and help out I'd be eternally grateful!
Here's a snippet of sample output from the most recent minidump:
Cheers,
Karli
I've recently been experiencing a very regular BSOD on my PC. I'm fairly sure it's a hardware issue (minidumps here: View attachment Minidumps.zip) as I've had a look at the minidump and it's a 124 error (0x124_GenuineIntel or X64_0x124_GenuineIntel_PROCESSOR_BUS depending on which dump I open). I thought that heat might have been the problem, so I've cleaned the (admittedly large amount of) dust from the innards, but it doesn't seem to have helped. Still could be the problem I guess, especially as the problem appears to become more severe (every 5 mins instead of every hour, say) when it's switched on for a long time. But then it also happens whenever I try anything processor-intensive (I think - haven't tested that extensively).
Two interesting points to note:
1) I have a dual boot Win 7 / XP system and the BSOD happens on both (lending weight to the hardware problem guess).
2) This started shortly after I installed a multitouch simulator for WP7 development on windows 7 (see Step by Step Tutorial : Installing Multi-Touch Simulator for Silverlight Phone 7 | Michael Sync). I have subsequently uninstalled, but the very first BSOD happened seconds after installation - coincidence?
I also could swear that I recently heard a mysterious loud "crack" noise, but I don't know when and I don't know if it came from the computer. But it's possible. Probably best to ignore that one.
I am currently running the win 7 memory test tool, but it's taking hours. I'll report back and edit this post if it comes back with any results.
In the meantime, if anyone can take a look at those minidump file and help out I'd be eternally grateful!
Here's a snippet of sample output from the most recent minidump:
Code:
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: fffffa8004e25038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000001040080f, 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: svchost.exe
CURRENT_IRQL: f
STACK_TEXT:
fffff880`009ec9d8 fffff800`03402903 : 00000000`00000124 00000000`00000000 fffffa80`04e25038 00000000`b2000000 : nt!KeBugCheckEx
fffff880`009ec9e0 fffff800`02f9a593 : 00000000`00000001 fffffa80`04e25ea0 00000000`00000000 fffffa80`04e25ef0 : hal!HalBugCheckSystem+0x1e3
fffff880`009eca20 fffff800`034025c8 : 00000000`00000728 fffffa80`04e25ea0 fffff880`009ecdb0 fffff880`009ecd00 : nt!WheaReportHwError+0x263
fffff880`009eca80 fffff800`03401f1a : fffffa80`04e25ea0 fffff880`009ecdb0 fffffa80`04e25ea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009ecbd0 fffff800`03401dd5 : 00000000`00000002 00000000`00000001 fffff880`009ece30 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009ecc10 fffff800`033f5e88 : 00000000`00004000 00000000`00004000 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009ecc40 fffff800`02e82fec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009ecc70 fffff800`02e82e53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009ecdb0 fffff800`02e7b4e4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`07997658 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!memmove+0xb4
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_BUS
BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_BUS
Followup: MachineOwner
---------Cheers,
Karli
