WHEA_UNCORRECTABLE_ERROR 124 but no bsod

catvomit · 28 Jan 2018

Hi nerds,

My PC has twice rebooted itself with no warning. I did not see a bsod either time, so i thought it may have been a power issue at first. Both times a dump file was left, with a WHEA_UNCORRECTABLE_ERROR 124. The first crash occurred shortly after PC was powered on and temps were quite low

After the first crash, these are the things I've tried:

Installing all windows updates and drivers
Tested RAM with Memtest86, for 8 passes, no errors
Ran intelburn standard stress test, no errors,
Cleaned out dust and cat hair from case

This system is about 7 months old, all parts are new except the GPU which is second hand. I understand this error is most commonly hardware related, and the fact it reboots before showing a BSOD is kind of worrying too.

Logs attached, I suspect the PSU (i am using the one that came with the case) but I'm not too confident about my troubleshooting skills. Any help would be appreciated :)

Ztruker · 29 Jan 2018

This is a very similar problem where the resolution was to replace the mother board. Read through it, follow the test @ave0 did in that thread and see how you make out.

Random Restarts with 0x124 Dump

Cleaning the inside of the PC, applying new thermal paste are very important as is running Prime95 and checking voltages.

Let me know how you make out.

Code:

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: ffff8387acbc3538, 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.

Code:

6: kd> !errrec ffff8387acbc3538
===============================================================================
Common Platform Error Record @ ffff8387acbc3538
-------------------------------------------------------------------------------
Record Id     : 01d396fcba8490fb
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 1/26/2018 23:24:03 (UTC)
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffff8387acbc35b8
Section       @ ffff8387acbc3690
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         : 3
CPU Version   : 0x0000000000600f20
Processor ID  : 0x0000000000000000

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

Local APIC Id : 0x0000000000000000
CPU Id        : 20 0f 60 00 00 08 08 00 - 0b 32 98 3e ff fb 8b 17
                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  @ ffff8387acbc3750

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

Error         : BUSLG_OBS_ERR_*_NOTIMEOUT_ERR (Proc 0 Bank 4)
  Status      : 0xf2000010000b0c0f

catvomit · 29 Jan 2018

Ouch, that's really not what I wanted to hear

I'll check voltages and replace thermal paste to see if either of those are an issue.
Thank you for your help :)

BSODHunter · 30 Jan 2018

Hi there,

Maybe I have a little more information for you. But at the end it seems to be something strange with the hardware, like Ztruker wrote.

This is from my analysis:

Code:

0x00000124:    [SPECIAL] WHEA_UNCORRECTABLE_ERROR (2018-01-27 00:24:03) [Windows 10] 
 
CAUSED BY:     AuthenticAMD_PROCESSOR_BUS_PRV     
 
WHEA Notify:   Machine Check Exception 
     Type:     BUS error 
     Error:    BUSLG_OBS_ERR_*_NOTIMEOUT_ERR (Proc 0 Bank 4) 
 
PROCESS:       System

"BUS OBS Error": Observing error. Usually caused by hardware components, Mainboard or chipset drivers.

There are also error in windows eventlog pointing to an hardware error (maybe chipset drivers):

Code:

2018-01-07 19:28:38  Error: A fatal hardware error has occurred. Component: AMD Northbridge   
2018-01-26 23:24:45  Error: A fatal hardware error has occurred. Component: AMD Northbridge

catvomit · 31 Jan 2018

Thank you very much, I'll check the chipset drivers but I have a feeling i need to RMA my mobo

axe0 · 31 Jan 2018

BUSLG_OBS_ERR = observing error from the point of view from the CPU (ruling out the CPU automatically).

IMHO this doesn't necessarily mean the mobo is the cause since that can't be determined with a single dump.

In the thread Ztruker linked to there was another crash which was due to a write error, the only reason that I could think of that could cause corrupted data to write was a bad motherboard, this is a different issue.

catvomit · 31 Jan 2018

Thank you axe0!! I shan't give up yet then :)

Ztruker · 31 Jan 2018

Maybe beat on it by running stressing the CPU and GPU?

===================================================
Follow this tutorial to stress test your CPU:
Prime95 - Stress Test Your CPU - Windows 10 Forums

===================================================
Follow this tutorials to stress test your GPU:
FurMark - GPU Stress Test - Windows 10 Forums

If you have a AMD APU instead of a discreet GPU, try UNIGINE 3D Benchmark..

Also check the voltages in BIOS, post them here please.

catvomit · 01 Feb 2018

Attachment 175114Here are the voltages from BIOS, not sure about these as I'm clueless with this sort of thing

I'm about to run Furmark and Prime95, will post results here.

catvomit · 01 Feb 2018

Furmark ran perfectly other than a little stuttering as it got past 80 degrees. No artefacts or crashes :)

The tutorial you linked says to run prime95 for 3 hours, Axe0 has said the CPU can be ruled out, so is it still necessary to run it for that long? Just worried about it getting too hot if I leave it unattended

Prime95 has been running for about 10 minutes so far, CPU temperatures have not gone above 58C and the fans sound like a plane taking off - so far so good i suppose? :)