BSOD stop 0x00000124 intermittently on HTPC

[Ender27182818]

I'm running a 64-bit Windows 7 HTPC that I build myself. Some quick hardware:

Kingston ValueRAM 2GB (2 x 1GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) Dual Channel Kit Desktop Memory Model KVR800D2N5K2/2G
ASUS P5N7A-VM LGA 775 NVIDIA GeForce 9300/nForce 730i HDMI Micro ATX Intel Motherboard
Intel Pentium E6300 Wolfdale 2.8GHz LGA 775 65W Dual-Core Processor BX80571E6300
Hauppauge WinTV-HVR-1600 ATSC/ClearQAM/NTSC TV Tuner White Box 1101 PCI Interface - OEM
SILVERSTONE Black 8.0mm aluminum front panel, 0.8mm SECC body GRANDIA GD04B Micro ATX Media Center / HTPC Case
Some local PSU

The OS is the original for the system, Full Retail version, as I am the system OEM
The hardware is roughly half a year old
The OS install is the same age - put it all together at the same time

This problem has been going on, near as I can tell, the life of the system, and it's starting to get annoying and I'm running out of ideas. Ergo - I throw myself on the mercy of anonymous Internet denizens.

I've attached the required BSOD files. I've also attached the minidumps that I found in the windows directory, though I know they don't represent all of the crashes, as the thing will wake itself up and crash during the night 2 times a week, sometimes more.

Wanting to be slightly self-sufficient I downloaded the Windows SDK and attempted my own crash analysis, as far as that goes. Text from WinDBG follows:

1: kd> .reload
Loading Kernel Symbols
..................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
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: fffffa8002c6a838, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, 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:  0

STACK_TEXT:  
fffff880`02fd56b0 fffff800`02f22a79 : fffffa80`02c6a810 fffffa80`015d3680 00000000`0000000b 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02fd5bd0 fffff800`02e045a7 : fffffa80`02c6a810 fffff800`02e7d5f8 fffffa80`015d3680 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02fd5c00 fffff800`02d6cb85 : fffff800`02edf360 fffffa80`02c59e68 fffffa80`02c59e60 fffffa80`015d3680 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02fd5c40 fffff800`02ce5861 : fffff880`00dd2e00 fffff800`02d6cb60 fffffa80`015d3680 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02fd5c70 fffff800`02f7da86 : 4cf73535`ff38d21a fffffa80`015d3680 00000000`00000080 fffffa80`015c1040 : nt!ExpWorkerThread+0x111
fffff880`02fd5d00 fffff800`02cb6b06 : fffff880`009ea180 fffffa80`015d3680 fffff880`009f4f40 3136a23d`33433130 : nt!PspSystemThreadStartup+0x5a
fffff880`02fd5d40 00000000`00000000 : fffff880`02fd6000 fffff880`02fd0000 fffff880`02fd51b0 00000000`00000000 : nt!KxStartSystemThread+0x16


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_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

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

1: kd> lmvm hardware
start             end                 module name
Mini Kernel Dump does not contain unloaded driver list

Aside from the the BSOD (Blue Screen of Death) I occasionally get "Disk Read Error" on startup. This will usually go away with time.

My first thought is perhaps I have a bad power supply, it being the weakest hardware in the whole system. I don't know who makes it, it's about 2 years old, though it wasn't used in a system except for some brief troubleshooting before going into this computer. But, I'm wondering if there's some kind of short. Or it's not supplying enough power to the system components.

But, I thought I'd get other's opinions first. I have yet to pull out any hardware from the system - it's a huge pain to pull the system out of where it's mounted in the living room - though I have tried a bit of driver updates. I'm more than willing to (re)try anything if you have ideas or experience.

Thanks.

 

[richc46]

http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

Vague BC. Follow the above.

It is usually due to hardware. Be sure to check RAM and Hardrive
Due to travel status I was not able to open your mini dump reports.

 

[Ender27182818]

Thanks, good guide, I'll post back as more develops, though it seems like information about my particular problem won't really help anyone else, since stop 124 errors are so hardware-particular

 

[cluberti]

Thanks, good guide, I'll post back as more develops, though it seems like information about my particular problem won't really help anyone else, since stop 124 errors are so hardware-particular

Well, sort of - you can run errrec against the WHEA block:

1: kd> !errrec fffffa8002c6a838
===============================================================================
Common Platform Error Record @ fffffa8002c6a838
-------------------------------------------------------------------------------
Record Id     : 01cb22f29457d021
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 7/14/2010 1:19:27
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa8002c6a8b8
Section       @ fffffa8002c6a990
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : BUS error
Operation     : Generic
Flags         : 0x00
Level         : 0
CPU Version   : 0x000000000001067a
Processor ID  : 0x0000000000000000

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa8002c6a900
Section       @ fffffa8002c6aa50
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000000
CPU Id        : 7a 06 01 00 00 08 02 00 - bd e3 00 0c ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa8002c6aa50

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8002c6a948
Section       @ fffffa8002c6aad0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : BUSL0_SRC_ERR_M_NOTIMEOUT_ERR (Proc 0 Bank 0)
  Status      : 0xf200084000000800

That error (BUSL0_SRC_ERR_M_NOTIMEOUT_ERR) means the processor sent out a read request to L0 cache, and there was a delay in return (either a cache miss, or invalid data in cache). This dump doesn't have an MCi_Status block, so what you see above is it.

Is this CPU overclocked, or overheating? Does it pass stress testing without failing?

 

[Ender27182818]

Overclocked? No. Overheating? It could be. I'll take a look at the temps, but I have run this thing for hours at a time watching movies/TV and it goes just fine, so it seems unlikely. However, I don't usually get this blue screen at any time other than when I'm not around and it's coming on to record TV. Usually at night.

 

[richc46]

Anything is possible, but give careful consideration to the post that I made. That information was found to be correct in 99% of the cases and it was written by one of our best.

 

[Capt.Jack Sparrow]

Hello,

Run a Hardware Diagnostic Hardware Diagnostic !! « Captain Debugger

- Captain

 

[cluberti]

Agreed - the one thing your CPU would do while it wasn't in use is sleep, and I've seen many a bad CPU have issues in S3 or S4.

 

[Ender27182818]

Well, over the weekend I tested the memory. No problems. I'm moving on to the hard drive next.

 

[Ender27182818]

Finished the hard drive test - used the Ultimate Boot CD and the Seagate app on there. No errors found. I pulled out my Hauppauge TV card - now there are no cards in the machine - and left it suspended all night. This morning I woke up and I didn't have the BSOD I've come to expect - but the system was hung. We'll wait and see if I can hit the BSOD again or not.

 

[Ender27182818]

So, I hit the BSOD again with the card out. That means the TV card isn't the problem. I'm now down to the motherboard, CPU, or power supply. I'm going to assume power supply at this point, since it seems the likely candidate based on manufacturer, age, etc. I've now removed the old power supply and replaced it with a new one. I also changed out the CPU fan - the old one was a 3 pin, and I had an OEM Intel 4-pin that it came from that was far less noisy. The thing runs significantly quieter, and so far I haven't had any problems. I'll reserve judgment for after I've run it for a week or so.

 

[CarlTR6]

I hope you have solved your problem.

 

[Ender27182818]

Well, couple of days and no BSOD. I also have the sleeping feature working correctly, thanks to MCE Standby Tool. Great little tool. I'm calling this fixed until I see otherwise. Thanks everyone!