0x124 WHEA_UNCORRECTABLE_ERROR

Chris2005 · 02 Nov 2013

Since about August, I would say, my computer has been completely locking up and restarting, then I check the dump files and I'm told that the culprit module is either ntoskrnl.exe or hal.dll.

Since I have more than 4GB of RAM, full dumps haven't been made, but I see that I can do such by some alterations... which I will do, in the event it occurs again.

The weird thing is, I redid Windows on the 12th of September, and until the 31st of October, the computer was fine, no BSOD, etc. For almost 50 days, there wasn't a single issue...

I updated the video card drivers on the 20th of October... until then I'd been using 320.18 which was released on May 23, 2013, after redoing Windows, until the 20th of last month, then I updated the drivers to 320.49 which was released on July 01, 2013... then on the 31st of last month (October), my computer's freezes and restarts started happening... it's only done it once since the 20th, which was on the 31st. Which is what the attached dump file is for.

I've uninstalled those drivers completely after the freeze and restart and installed the latest drivers, 331.65 that were released on the 28th of October.

I don't think it's a overheating issue, because I can run my system at full load without problems... for example, I've been rendering with 3ds max all day and not a problem, which really taxes my RAM and CPU.

The freeze/BSOD seems to happen when the system is either idle or virtually idle, for example, I'll be browsing the internet or watching a blu-ray.

WhoCrashed Dump Analysis:
On Thu 10/31/2013 11:57:52 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\103113-12921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADE7C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8004C098F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Arc · 03 Nov 2013

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

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. Also set the BIOS to default, too.
How To Clear CMOS (Reset BIOS)

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator

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.

Let us know the results.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8004c098f8, 0, 0}

Probably caused by : GenuineIntel

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: fffffa8004c098f8, 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:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`031af6f0 fffff800`032cdca9 : fffffa80`04c098d0 fffffa80`03cff040 fffffa80`0000000c 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031afc10 fffff800`031aee97 : fffffa80`04c098d0 fffff800`032282d8 fffffa80`03cff040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031afc40 fffff800`03116285 : fffff800`03289b40 00000000`00000001 fffffa80`04c33d20 fffffa80`03cff040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031afc80 fffff800`0308c261 : fffff880`0118be00 fffff800`03116260 fffffa80`03cff000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031afcb0 fffff800`03320bae : 04f07c83`08438bff fffffa80`03cff040 00000000`00000080 fffffa80`03cec040 : nt!ExpWorkerThread+0x111
fffff880`031afd40 fffff800`030738c6 : fffff880`02f63180 fffffa80`03cff040 fffff880`02f6dfc0 33fff48e`62e9fc45 : nt!PspSystemThreadStartup+0x5a
fffff880`031afd80 00000000`00000000 : fffff880`031b0000 fffff880`031aa000 fffff880`031af110 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

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

Chris2005 · 03 Nov 2013

I ran Memtest86+ back when this started occurring, all turned out fine, ran it for several hours.

I haven't stress tested the GPU using any software, however, I use a lot of programs that really tax the video card... but I will run Furmark. :)

As with the GPU, I haven't stress tested the CPU using an actual software program designed for that, but 3ds Max causes 100% CPU usage while rendering... always has. I was rendering something for over 15 hours, so for 15 hours the CPU was being used 100% and no overheating issues.

I don't overclock anything, everything is default settings.

My PSU is adequate, it's a SilverStone Stride 750W, that calculator gave me a recommendation of at least 453W...

My computer just finished rendering something for 2.5-3 hours, I've attached the Speccy summary. Of course, that's with stuff under load...

However, I get different results with AIDA64... AIDA64 reports my CPU temperature around 3-4 degrees cooler than Speccy. AIDA64 reports my GPU at 7-8 degrees cooler than Speccy.

So, what does that bugcheck analysis reveal? It's all Greek to me, even as a moderate computer person, lol.

Arc · 03 Nov 2013

Let us know the results of the tests those are suggested.

Chris2005 · 03 Nov 2013

I'll stress test the GPU right now... then move onto the CPU...

Chris2005 · 03 Nov 2013

I ran FurMark... does it have a time limit or does it keep running for as long as you let it?

The temperature peaked at around 82-83 C...

I've ran Prime95... temperatures seem to be fine... CPU hasn't even gone over 50 C yet...

Update:

Prime95 Results:

Code:

[Sun Nov 03 03:37:02 2013]
Self-test 8K passed!
Self-test 8K passed!
Self-test 8K passed!
Self-test 8K passed!

Arc · 03 Nov 2013

OK ... now follow it: Stop 0x124 - what it means and what to try

Chris2005 · 03 Nov 2013

Everything listed there has been done.

Short of 9, since I don't have parts to swap in and out.

Chris2005 · 03 Nov 2013

Ran the Windows Memory Diagnostic and...

Results:
The Windows Memory Diagnostic tested the computer's memory and detected no errors

Chris2005 · 01 Dec 2013

Hasn't reoccurred yet... since I updated to the (then) latest Nvidia drivers... not sure if it was the 320.49 drivers or what... but it happened after I updated to them and hasn't happened since I removed them and updated to the (at the time) latest 331.65... the current latest version is 331.93.