Sparse BSOD 0x00000124 (hal.dll+12a3b, ntoskrnl.exe+75bc0) Win7-64bit

[koboldofthesea]

I bought my computer last year 7/27/2013. Custom build. Everything was working fine until January 20th this year. I experienced my first BSOD on this machine. I've tried rolling back graphics drivers which were the only ones I had installed recently, and it didn't help because 4 days later the same BSOD happened. The next BSOD didn't happen for another month. And recently this is my 4th one that I am attaching in the log compilation. The other dmp's were erased by me by accident but they all said the same thing when I opened them in BlueScreenView.

I will try reseating hardware and more stress tests when I have time, but I'm really lost here as its such a sparse occurrence that it makes it really hard for me to test in a reasonable amount of time. I'm hoping someone here can see what my inexperienced eyes are missing.

Here's what I do know:
- I didn't install any drivers for a while (month or so?) other than the nvidia driver which I rolled back.
- I am not overclocking and just running stock and default BIOS. Though since my 3rd BSOD I have turned on XMP for my RAM (didn't make anything worse I guess).
- The BSOD happens very randomly. Twice while I was playing fairly low resource demanding games. Once while I was just on desktop dragging/organizing files. And most recently while browsing Twitch.tv on Chrome. There seems to be nothing in common, which is really frustrating.
- It doesn't seem to be related to how long my computer has been running. The most recent happened ~7 minutes after turning my computer on.
- I have a minor suspicion it could be my sound because it's always given me issues (distorting/not being detected randomly at startup). But it is onboard and I have no idea how to begin testing it.

I will post updates as I perform further tests (will be running memtest+ thru the night, last time only ran for 2 hours). Please let me know any good suggestions. Thanks a lot!

 

[koboldofthesea]

I apologize ahead of time for losing the other 3 memory dumps, though they all appeared the same I'm sure there was useful information in there. I deleted them by accident via diskcleanup utility. I will post memory dmps as they happen in this thread, but for now if anyone sees a potential problem or has any advice to test please let me know.

 

[Arc]

Hi.

A stop 0x124 is usually a hardware failure, but its scope is often wider than simple hardware.

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know the wattage of the PSU.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall the program at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

Let us know the results.

__________________________________________

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8009104028, be000000, 100110a}

Probably caused by : GenuineIntel

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

2: 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: fffffa8009104028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000100110a, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  f

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

STACK_TEXT:  
fffff880`0336da58 fffff800`03408a3b : 00000000`00000124 00000000`00000000 fffffa80`09104028 00000000`be000000 : nt!KeBugCheckEx
fffff880`0336da60 fffff800`02f9d463 : 00000000`00000001 fffffa80`09105d30 00000000`00000000 fffffa80`09105d80 : hal!HalBugCheckSystem+0x1e3
fffff880`0336daa0 fffff800`03408700 : 00000000`00000728 fffffa80`09105d30 fffff880`0336de30 fffff880`0336de00 : nt!WheaReportHwError+0x263
fffff880`0336db00 fffff800`03408052 : fffffa80`09105d30 fffff880`0336de30 fffffa80`09105d30 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`0336dc50 fffff800`03407f0d : 00000000`00000004 00000000`00000001 fffff880`0336deb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`0336dc90 fffff800`033fbe88 : 00000000`00000000 fffffa80`0abd0060 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`0336dcc0 fffff800`02e854ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`0336dcf0 fffff800`02e85313 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`0336de30 fffff800`02e8e159 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`0a942870 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeRemoveQueueEx+0x299


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x124_genuineintel_processor_cache

FAILURE_ID_HASH:  {270f58cb-a20a-a72d-6d81-eb8c82f01f7a}

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

http://pcsupport.about.com/od/fixtheproblem/tp/clearcmos.htm

 

[koboldofthesea]

Thanks for the quick response.
Heres some updates on my PSU. I have this running rated at Max 600W Newegg.com - HighPower Astro PT 600W, Digital, 80+ Platinum, Single +12 Rails, SLI/Cross Fire ready, Module, Active PFC Power Supply. And the site for calculating reports 307W min 357W recommended.

I am not overclocking. Other than XMP turned on I am running all defaults. Defaults do show an adaptive power plan for CPU though.

I ran the CPU test Prime95 and I think it is getting fairly hot about half an hour in on the mixed test, so I actually just stopped it there.
Temps were showing ~80c. My Idle temps are 35-40c. I've always thought these were a little high, but I am running a uATX with a small case so maybe that is why? When I play games it reaches around 51c-60c. ~46c for less demanding games. After long hours the numbers don't rise that much, I've tested this in the past, and as noted in my earlier description, the crashing seems to have no relation to how long I've had my computer on or what I'm actually doing at the time.

I will run memtest86+ tonight and post results in morning. I also have an early version of the bios F6. I believe there are 2 newer versions since, F7 and F8, on the manufacturer website. If nothing else is working I was going to flash bios next.

Again, thanks a bunch for taking the time to help me.

 

[koboldofthesea]

First round Memtest86+ went through 6 times overnight no failures. Will test again when have a chance.

 

[Arc]

You need to run memtest for 8 passes, not times. 8 consecutive passes.