Windows 10: Frequent BSOD Error Code 0_124 WHEA_UNCORRECTABLE_ERROR

I recently purchased a computer about 3 months ago. Ever since I have been getting frequent BSOD when I play Dota 2 and randomly when using the computer. I have even BSOD while watching NETFLIX.


Other times the computer has BSOD without me touching it at all.


I have gone back and forth 2-3 times every week getting it checked and fixing but the technician cannot find any issues. However, the BSOD continues.


What I have done so far:

Windows Memory Diagnostic Testing - No errors found

Disk Fragmented

Switched Ram with another computer - still BSOD

Motherboard - ASRock Phantom Gaming 6 Z390 - switched to Gigabyte Z390 - Still crashed with BSOD

Graphics Card - Replaced it and switched upgrading it to better current - GEForce GTX 1660 Super

Power Supply - had issues with it not turning on, changed from a 450 > 650 > now 850 Corsair Gold Certified

C Drive - Upgraded brand new Kingston 500GB SSD M.2 on motherboard to a Samsung 500GB SSD M.2 - still BSOD

Hard Drive and SSD - I have 2 SSDs both 2 TB, 1TB old HDD and 120GB used to have windows installed but is now a normal hard drive

Power Point - running direct connection to power supply from another power point with extension cord


Current Computer Specs:

Processor - IntelR CoreTM i7-8700k CPU @ 3.70GHz 3.70 GHz

Ram - 2 x 16GB Corsair RGB Ram

Motherboard - ASRock Phantom Gaming 6 Z390

Graphics Card - GeForce GTX 1660 Super

System Type - 64 Bit Operating System

Windows - Windows 10 Home


I have recently been searching how to fix this BSOD because it is too frequent and everything is BRAND NEW! All parts are brand new!


I have not changed the CPU or the current RAM with the shop yet as the technician says there is nothing wrong with them.


I have just ran the windbg to try identify the source but I am a little confused, I think it is the CPU but temperatures in BIOS show 45 degrees CPU, M/B 31 degrees, CPU voltage 1.056.


Here is the code that I have debugged, any help or confirmation of the main issue would be of great help.


Microsoft R Windows Debugger Version 10.0.20153.1000 AMD64

Copyright c Microsoft Corporation. All rights reserved.





Loading Dump File [C:\Windows\Minidump\080320-8578-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available



Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 19041 MP 12 procs Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Edition build lab: 19041.1.amd64fre.vb_release.191206-1406

Machine Name:

Kernel base = 0xfffff802`59c00000 PsLoadedModuleList = 0xfffff802`5a82a310

Debug session time: Mon Aug 3 17:34:51.931 2020 UTC + 10:00

System Uptime: 0 days 6:11:48.619

Loading Kernel Symbols

...............................................................

................................................................

................................................................



Loading User Symbols

Loading unloaded module list

...............

For analysis of this file, run !analyze -v

nt!KeBugCheckEx:

fffff802`59fddb60 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff802`5e2478f0=0000000000000124

0: 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: ffffd9896a278028, Address of the WHEA_ERROR_RECORD structure.

Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.

Arg4: 0000000000080005, Low order 32-bits of the MCi_STATUS value.



Debugging Details:

------------------



fffff8025a80f2a8: Unable to get Flags value from nt!KdVersionBlock

fffff8025a80f2a8: 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 ***

*** ***

*************************************************************************

fffff8025a80f2a8: 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 ***

*** ***

*************************************************************************

*** WARNING: Unable to verify checksum for win32k.sys



KEY_VALUES_STRING: 1



Key : Analysis.CPU.mSec

Value: 4484



Key : Analysis.DebugAnalysisProvider.CPP

Value: Create: 8007007e on DESKTOP-NR3SHTO



Key : Analysis.DebugData

Value: CreateObject



Key : Analysis.DebugModel

Value: CreateObject



Key : Analysis.Elapsed.mSec

Value: 37556



Key : Analysis.Memory.CommitPeak.Mb

Value: 94



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: 0xb200000000080005



Key : WHEA.MCiStatus.McaError

Value: 0x0005



Key : WHEA.MCiStatus.ModelError

Value: 0x0008



Key : WHEA.MCiStatus.Reserved

Value: 0x00000000





ADDITIONAL_XML: 1



OS_BUILD_LAYERS: 1



BUGCHECK_CODE: 124



BUGCHECK_P1: 0



BUGCHECK_P2: ffffd9896a278028



BUGCHECK_P3: b2000000



BUGCHECK_P4: 80005



BLACKBOXBSD: 1 !blackboxbsd





BLACKBOXNTFS: 1 !blackboxntfs





BLACKBOXPNP: 1 !blackboxpnp





BLACKBOXWINLOGON: 1



CUSTOMER_CRASH_COUNT: 1



PROCESS_NAME: System



STACK_TEXT:

fffff802`5e2478e8 fffff802`5a0bfd5a : 00000000`00000124 00000000`00000000 ffffd989`6a278028 00000000`b2000000 : nt!KeBugCheckEx

fffff802`5e2478f0 fffff802`567815b0 : 00000000`00000000 ffffd989`6a278028 ffffd989`629dd5b0 ffffd989`6a278028 : nt!HalBugCheckSystem+0xca

fffff802`5e247930 fffff802`5a1c401e : 00000000`00000000 fffff802`5e2479d9 ffffd989`6a278028 ffffd989`629dd5b0 : PSHED!PshedBugCheckSystem+0x10

fffff802`5e247960 fffff802`5a0c1681 : ffffd989`6a2b8070 ffffd989`6a2b8070 ffffd989`629dd600 ffffd989`629dd5b0 : nt!WheaReportHwError+0x46e

fffff802`5e247a40 fffff802`5a0c19f3 : 00000000`00000000 ffffd989`629dd600 ffffd989`629dd5b0 00000000`00000000 : nt!HalpMcaReportError+0xb1

fffff802`5e247bb0 fffff802`5a0c18d0 : ffffd989`5f6f4060 00000000`00000001 00000000`00000000 00000000`00000000 : nt!HalpMceHandlerCore+0xef

fffff802`5e247c00 fffff802`5a0c1b21 : 00000000`0000000c 00000000`00000001 00000000`00000000 00000000`00000000 : nt!HalpMceHandler+0xe0

fffff802`5e247c40 fffff802`5a0c0d8b : 00000000`00000000 00000000`00000000 fffff802`5e247ed0 00000000`00000000 : nt!HalpMceHandlerWithRendezvous+0xc9

fffff802`5e247c70 fffff802`5a0c35d5 : ffffd989`5f6f4060 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0x5f

fffff802`5e247ca0 fffff802`5a118d59 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x35

fffff802`5e247cd0 fffff802`59fecbba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9

fffff802`5e247d00 fffff802`59fec877 : fffff802`00000000 fffff802`59fec7ac 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7a

fffff802`5e247e40 fffff802`7303138f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277

fffff802`5e21c5e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x1f





MODULE_NAME: GenuineIntel



IMAGE_NAME: GenuineIntel.sys



STACK_COMMAND: .thread ; .cxr ; kb



FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_BANK0_MSCOD0008_MCACOD0005_PCC_UC_IMAGE_GenuineIntel.sys



OS_VERSION: 10.0.19041.1



BUILDLAB_STR: vb_release



OSPLATFORM_TYPE: x64



OSNAME: Windows 10



FAILURE_ID_HASH: {420afa50-bcf9-29b3-b2fd-21a20a397f2b}




Followup: MachineOwner

:)

 

WHEA_UNCORRECTABLE_ERROR - Random reboots and 0x124 error

Thanks, axe0

How do I explain what steps I took... I ran dm_log_collector.exe but not sure how results were actually acquired/interpreted.

I need to be able to explain steps I took and steps taken to reproduce.

Attachment 162250

thanks, in advance!

 

Frequent System crash with the error WHEA_uncorrectable_error

Hello Janey,

Please help us with the below information to help you better.

• What is the model of your computer?
• What is the exact error message/code you see?

If you receive a blue screen error (also known as a stop code), it means that your PC has shut down suddenly to protect itself from data loss. If you see the text “WHEA_UNCORRECTABLE_ERROR”, it means that a hardware error has occurred.

As an initial step I would suggest you to install all the pending updates on your computer.

Suggest you to refer to the below article and check if it helps in addressing your issue.

Troubleshoot blue screen errors

https://support.microsoft.com/en-us/help/14238/windows-10-troubleshoot-blue-screen-errors

Blue screen error could also appear due to outdated or corrupted drivers on your computer, I would suggest you to update you Display, Graphic and all other drivers on your computer, it may help you to resolve the issue.

Update drivers in Windows 10

https://support.microsoft.com/en-us...566-b983195752c1/update-drivers-in-windows-10


Let us know about the status of the issue. We would be happy to help you further