New
#1
BSOD stop 0x00000124 intermittently on HTPC
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:
Aside from the the BSOD (Blue Screen of Death) I occasionally get "Disk Read Error" on startup. This will usually go away with time.Code: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
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.