cancel
Showing results for 
Search instead for 
Did you mean: 

Processors

TheillnessX
Journeyman III

5800x WHEA_UNCORRECTABLE_ERROR

I recently purchased a 5800x to replace my 3600 (which ran trouble free). Now within 10-30 mins of any game I play it blue screens and restarts the system. Has anyone else had these issues and know a possible fix? Super frustrating that everything worked before the upgrade. 

My system is 

  • AMD 5800x
  • EVGA 3080 
  • 32gb Trident Neo 3600mhz cl16
  • ASUS Strix b550-i - Bios 1202
23 Replies
buildorbust
Adept II

i too(super frustrating)

  • AMD 5950x
  • Gigabyte 2070 super 
  • 32gb Gskill 3600mhz cl16
  • MSI X570 tomahawk wifi 
TheillnessX
Journeyman III

8: 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. Try !errrec Address of the WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffff868511c03028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000fc800800, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000060c0859, Low order 32-bits of the MCi_STATUS value.

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

fffff8041300f340: Unable to get Flags value from nt!KdVersionBlock
fffff8041300f340: Unable to get Flags value from nt!KdVersionBlock
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION                ***
***                                                                   ***
*************************************************************************
fffff8041300f340: Unable to get Flags value from nt!KdVersionBlock
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION                ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3311

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-5IPAIVJ

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 11930

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 84

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1

    Key  : WHEA.MCiStatus.Code
    Value: 0xfc800800060c0859

    Key  : WHEA.MCiStatus.McaError
    Value: 0x0859

    Key  : WHEA.MCiStatus.ModelError
    Value: 0x060c

    Key  : WHEA.MCiStatus.Reserved
    Value: 0x00800800


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffff868511c03028

BUGCHECK_P3: fc800800

BUGCHECK_P4: 60c0859

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  FSD-WinGDK-Shipping.exe

STACK_TEXT:  
ffffe101`cbbae938 fffff804`128b31ca     : 00000000`00000124 00000000`00000000 ffff8685`11c03028 00000000`fc800800 : nt!KeBugCheckEx
ffffe101`cbbae940 fffff804`117315b0     : 00000000`00000000 ffff8685`11c03028 ffff8685`100f3bb0 ffff8685`11c03028 : nt!HalBugCheckSystem+0xca
ffffe101`cbbae980 fffff804`129b4d3e     : 00000000`00000000 ffffe101`cbbaea29 ffff8685`11c03028 ffff8685`100f3bb0 : PSHED!PshedBugCheckSystem+0x10
ffffe101`cbbae9b0 fffff804`128b4af1     : ffff8685`1790e900 ffff8685`1790e900 ffff8685`100f3c00 ffff8685`100f3bb0 : nt!WheaReportHwError+0x46e
ffffe101`cbbaea90 fffff804`128b4e63     : 00000000`00000008 ffff8685`100f3c00 ffff8685`100f3bb0 00000000`00000008 : nt!HalpMcaReportError+0xb1
ffffe101`cbbaec00 fffff804`128b4d40     : ffff8685`0ef025c0 00000000`00000000 ffffe101`cbbaee00 00000000`00000020 : nt!HalpMceHandlerCore+0xef
ffffe101`cbbaec50 fffff804`128b4285     : ffff8685`0ef025c0 ffffe101`cbbaeef0 00000000`00000000 01d6bc8e`e057307e : nt!HalpMceHandler+0xe0
ffffe101`cbbaec90 fffff804`128b6a45     : ffff8685`0ef025c0 00000000`00001a2c 00000000`00000020 0064006d`0061030a : nt!HalpHandleMachineCheck+0xe9
ffffe101`cbbaecc0 fffff804`1290c179     : 00010000`00006bdd 00000000`00580068 00010000`000008d6 01d5acdd`cecc6218 : nt!HalHandleMcheck+0x35
ffffe101`cbbaecf0 fffff804`128042fa     : 01d6c83c`32aff413 00000000`00003000 00000000`000026cc 00000000`00000020 : nt!KiHandleMcheck+0x9
ffffe101`cbbaed20 fffff804`12803fb7     : 00000000`00000000 00000000`00000000 00000147`e86d14d0 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffffe101`cbbaee60 00007fff`8c1f5d8d     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277
0000000c`5c174e50 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`8c1f5d8d


MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD.sys

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x124_0_AuthenticAMD_BANK0_MSCOD060C_MCACOD0859_UC_IMAGE_AuthenticAMD.sys

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {af26fd66-1025-e79d-1f5b-29ede38d49c6}

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

0 Likes

I am getting the same error with the 5800x

I am running the gigabyte  b550i on the most updated F11n bios.

RAM: Crucial Ballistix 32gb cl16 - tried at default 2666 and with xmp profile loaded

Note: the middle dial on Ryzen Master goes red right before the BSOD

Has anyone found a fix yet?

0 Likes

Not that I have seen. 

Keep reporting the issue to your motherboards support department and AMD:

https://www.amd.com/en/support/contact-email-form

0 Likes

I went through this form and the representative eventually linked me the warranty page.

I tried 3 different bios versions.

The chipset driver off the amd site. Then the chipset driver off the gigabyte site.

Running the processor in ECO mode, this seemed to significantly accelerate how long it took to crash, sometimes as soon as I launched game.

Swapped processors with my friend running a 3800x.  He crashed with my 5800x in his system, I did not crash with his 3800x in mine.

The processor maxed out at about 70C in the Ryzen master stress test and would rarely break 65C in game so temps couldn't have been the issue.

Long story short if you are getting this BSOD error, you probably have a faulty processor.  I just submitted my warranty form now I will update in a few weeks.

0 Likes
xesap58662
Adept II

I fixed my WHEA errors

But I was not getting BSOD like you

0 Likes
xxppx
Journeyman III

Same problem here but I found a solution :

 

Set CPU Frequency to 4600

Set Core Voltage to 1201mV

Stable, very nice temps (but you lose 5% on single core perf).

0 Likes

Hi I seem to have a similar problem.

My CPU can run Cinebench 23 on its own without crashing but in games the system either restarts or posts a BSOD with WHEA_UNCORRECTABLE_ERROR after <10 minutes. Interestingly, if I run furmark and Cinebench together then I also get a crash (no crash with just Cinebench).

My CPU temperatures are not great - I hit 90 degrees running cinebench multi core (mid 70s on single core). In games, temperatures go up to upper 70s.  Nonthelesss, I don't think temperatures are reason for crashes (system crashes even if temperatures are in low 70s).

The only solution I have found so far is to turn off PBO and Core performance boost, which clearly impacts overall speed of the system.

Any idea on what could be a more satisfactory solution?

Full specs are:

Ryzen 5800x CPU

MSI B550m Mortar (with latest 7C94v154 BIOS)

RTX 3080 CPU

Galahad 240mm AIO cooler

Deep Cool 750W DQ750ST PSU

Thanks!

0 Likes

Loot at my solution...

60°C max peak in games

75°C max peak with Cinebench/AIDA64

You will lose 5% on single core benchmarks but there is no impact for games (same score with 3Dmark) and, especially your PC won't crash.

0 Likes

Definitely appears the voltage settings in the vendor's BIOS updates are stuffed and that's why the 'auto' settings keep crashing computers. Hopefully, in a few more months they will have the earlier adopter errors smoothed out.

luckyjj10
Journeyman III

same as problems here:

https://www.overclock.net/threads/replaced-3950x-with-5950x-whea-and-reboots.1774627/page-27

 

I have this too on my 5800x I've tried anything I could with bios settings and many late nights of time wasted.  After still crashing even with defaults in games I've tried starting the RMA process.  I haven't done it before and its my first real AMD thing and this experience sucks.  The cpu is unstable like an overclocked cpu while at its default boosting settings.

To be clear I've tried 3 different bios versions and different updates of chipset drivers.  The cpu is just plain unstable.

I'm waiting to hear on AMD now and I hope the process is painless and I'm not out of a computer for too long.  but I'm expecting the worst with how things have been so far.

Hi guys,

I too was experiencing this error on an Asus Dark Hero VIII and a 5950x. Memory is 32GB Trident Z Neo 3600mhz CL14 memory at 1.45V (Advertised XMP). The problem appears to be linked to a number of voltage settings and automatic power states in the bios. I could not activate the advertised speeds on my memory without constant reboots and BSOD/WHEA errors. My windows was also corrupted about 5 times. At first, I had to turn off CPB  and PBO for my system to allow me to use the DCOP/XMP profile on my memory and become stable. However, I found a way around this allowing me to get the full potential out of my CPU and memory. These are the steps I took to make the system relatively stable after spending 2 days reading forums. This solution has also worked for others:

  1. Install latest BIOS for your motherboard, BETA if it is available.
  2. Make sure you have all the latest Windows 10 updates installed.
  3. Download AMD adrenaline which will automatically install all the latest drivers for your CPU/chipset and motherboard that are AMD related. These are almost always more updated than your motherboard vendors' site. I do not recommend using your motherboard vendors automatic updates or the drivers on their page, source them directly from their creator, like Realtek, AMD, etc.
  4. Turn off C-States in your BIOS. When you seem to be doing low demand tasks, not enough power gets to the CPU and the computer encounters an error resulting in BSOD/WHEA.
  5. Leave your window's power profile balanced.
  6. Manually set your XMP/DCOP settings for memory, or activate XMP/DCOP and change any settings from auto to the required setting advertised by the manufacturer.
  7. Change your FCLK frequency from auto to the required setting. Mine is set at 1800Mhz.
  8. Increase your DRAM voltage incrementally till stable, I had to increase my memory from DCOP 1.45V to 1.46V.
  9. Change your SoC voltage to somewhere between 1.1V - 1.2V, increase incrementally. Mine is currently at 1.125V.
  10. CPB and PBO are enabled.

I hope this helps and please pass this on to any motherboard manufacturer/AMD technicians you are currently talking to. Thank you.

It took a couple of weeks but AMD did come through with a replacement.  Everything works fine now

0 Likes

I've this problem too, with a 5800x and a B550m TUF gaming.

In stress tests everything is ok, but on gaming i get a BSOD with 

WHEA_UNCORRECTABLE_ERROR (124)

is it CPU fail? In this case RMA is the solution?

0 Likes

Hi 

Have temporary fix, by going to BIOS and changing the override CPU Voltage to 1.25v. I also disabled PBO.

but is there a final solution? by the brand

0 Likes

me too.

I have changed another 5800x cpu, it still crashed.

The same hardware, use 5600G it works well.

Read lots of reference, I have closed CPB, for now, it works well. 

The 5800X cannot work on Core performence boost mode.

0 Likes

0 Likes
hanvey
Journeyman III

Yes, I have the same problems for sevral days. I am tired, anyone fixed it?

WHEA_UNCORRECTABLE_ERROR  for less 10 mins.

My system:

MB: MSI MAG B550M Mortar

CPU: AMD 5800X

Mem: Kingston FURY Beast 3600 16G*2

Disk: Lexar nm800 512G

Graphic: Maxsun RX580 8G 2048SP

 

0 Likes

@hanvey - There is no fix. Return it. Some users got "functional" samples after their second or even THIRD CPU RMA. It is up to you.

However, there is an workaround available, which is the Fixed clock usage, disabling the CPB/PB/PBO function. PB/PBO are the responsible for these crashes, AMD knows and does nothing.

Here is my post about it: Ryzen 5000 Crashes (WHEA Errors) will get a "Silen... - AMD Community

Wish you luck!

0 Likes

I have return the CPU, and got a new one. The problem still there.

I return the  CPU again, waiting for another new one.

Every AMD Zen3 5800X is in that? Or I am unluckly?

0 Likes
kingfish
Volunteer Moderator

" Every AMD Zen3 5800X is in that? Or I am unluckly?"

Unlucky is just another word for.....

0 Likes
Hirotrex
Journeyman III

Hi everyone,

I struggled with this issues for a long time and didnt want to lose time to RMA my cpu, after days of tweaking i finally found a fix that dont reduce drasticly performances.

I think the issues is that, sometimes, when the cpu enter or exit boost mode, it will draw too much current and trip the motherboard security or windows security and make a WHEA BSOD or simply shutdown the pc.

The solution is to prevent the CPU from drawing too much current and triggering these securities.

I tried locking the voltage at 1.4v all the time but your cpu will heat more and wont decrease its power consumption when at idle so not ideal and pc is still crashing, just less often.

You could also lock the clock of the cpu but no more sleep and no more boost so big performance loss.

I also tried to mess with the Pstate0 and reducing the boost clock but it disable thermal throttle and as i have a SFF case, i have a small radiator for it so it would kill the cpu.

The solution I setteled with is to simply downclock the boost frequency of the cpu, it is now 100% stable with only a loose of like 0.15Mhz in boost mode so i am happy with it. Not what i payed for and ideal but it is stable and i dont need to RMA it so i am happy.

To do this, go to BIOS, set PBO to advanced, enable negative boost override.

You then test at which negative override your pc dont crash. For me it is 150.

Hope this post saves someones days

0 Likes
Morgan2
Journeyman III

As i had the same BSOD, after many researches, i found an "OC Genie" button in the BIOS (my MB is MSI and processor is AMD FX Black Edition idk-which-one-exactly), i disabled it and for now everything seems to work as before, but i think i'll change my processor anyway. I lost so much time with that issue... And it's not done yet because i reinstalled Win10 and i have a lot of softwares to reinstall still

0 Likes