I get WHEA_UNCORRECTABLE_ERROR on Windows 10 frequently!!

[PHANTOM1147]

It just randomly blue screening. Sometimes it works fine for hours, most of the time it crashes in 5-10min. It always crashes when I play Genshin Impact.

It also blue screened when I tried to install windows.

After blue screening a few times it show "Windows couldn't load properly"

I really need help its been like this for a month. Thanks.

 

My system specs are,

• i5-9400f
• MSI H310M pro-m2 plus
• ADATA D30 3200MHz 16GB (8*2)
• MSI GTX1650 super
• ADATA Ultimate SU650 240GB SSD
• Seagate BarraCuda 1TB HDD and two 6-7y old Hard Drives
• Raidmax RX-400xt PSU

 

Fixes I have tried:

• Re-installed windows
• Uninstalled windows updates 
• Booted with only SSD connected
• Installed windows into a different HDD
• Tested HDD with SeaTools and UBCD
• Reseated RAM, CPU and GPU
• Tested RAM with Windows Memory Diagnostic and MemTest86
• Tested CPU with Intel Processor Diagnostic Tool
• Reset CMOS
• Updated BIOS
• Reset MSI afterbuner overclocks
• Using RAM from a different PC

I don't have any overclocks on BIOS and I have XMP turned off.

Both CPU and GPU under 80°C while playing games.

 

Memory Dump analysis is down below. 

 

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: ffffb88fb6103028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000ba000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000020179, Low order 32-bits of the MCi_STATUS value.

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 2

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on VULCAN

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 28

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

    Key  : Analysis.System
    Value: CreateObject

BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffb88fb6103028

BUGCHECK_P3: ba000000

BUGCHECK_P4: 20179

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXWINLOGON: 1

PROCESS_NAME:  nvsphelper64.exe

STACK_TEXT:  
fffff805`7f8998e8 fffff805`7aeb41aa : 00000000`00000124 00000000`00000000 ffffb88f`b6103028 00000000`ba000000 : nt!KeBugCheckEx
fffff805`7f8998f0 fffff805`78a915b0 : 00000000`00000000 ffffb88f`b6103028 ffffb88f`b38d83c0 ffffb88f`b6103028 : nt!HalBugCheckSystem+0xca
fffff805`7f899930 fffff805`7afb60ee : 00000000`00000000 fffff805`7f8999d9 ffffb88f`b6103028 ffffb88f`b38d83c0 : PSHED!PshedBugCheckSystem+0x10
fffff805`7f899960 fffff805`7aeb5ad1 : ffffb88f`b3c20650 ffffb88f`b3c20650 ffffb88f`b38d8410 ffffb88f`b38d83c0 : nt!WheaReportHwError+0x46e
fffff805`7f899a40 fffff805`7aeb5e43 : 00000000`00000000 ffffb88f`b38d8410 ffffb88f`b38d83c0 00000000`00000000 : nt!HalpMcaReportError+0xb1
fffff805`7f899bb0 fffff805`7aeb5d20 : ffffb88f`b2cd0910 00000000`00000001 00000000`00000000 00000000`00000000 : nt!HalpMceHandlerCore+0xef
fffff805`7f899c00 fffff805`7aeb5f71 : 00000000`00000006 00000000`00000001 00000000`00000000 00000000`00000000 : nt!HalpMceHandler+0xe0
fffff805`7f899c40 fffff805`7aeb51db : 00000000`00000000 00000000`00000000 fffff805`7f899ed0 00000000`00000000 : nt!HalpMceHandlerWithRendezvous+0xc9
fffff805`7f899c70 fffff805`7aeb7a25 : ffffb88f`b2cd0910 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0x5f
fffff805`7f899ca0 fffff805`7af0d3d9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x35
fffff805`7f899cd0 fffff805`7ae062fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9
fffff805`7f899d00 fffff805`7ae05fb7 : 00000000`00000000 00000000`00000000 00000000`00000005 00000000`00000000 : nt!KxMcheckAbort+0x7a
fffff805`7f899e40 00007ff9`76cbcab0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277
000000ec`f11ff590 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`76cbcab0

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel.sys

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {4c8f3f5e-1af5-ed8b-df14-d42663b1dfa7}

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

Edited September 15, 2021 by PHANTOM1147

[Levent]

Since you havent provided us with more important things like your system details, this issue is because one of these I listed below:

• CPU overheating/unstable
• RAM overheating/unstable
• (not likely) GPU core overheating/unstable
• (very unlikely) PSU is dying

[aisle9]

Reset your CMOS first. This is usually an error tied to bad BIOS settings (which are usually tied to a bad overclock, so if you've been doing that...here you go).

 

Next, from within Windows, open up a command prompt with admin rights and run sfc /scannow. That will look for OS errors and try to fix them, and that error is one that can be caused by the OS itself. Then update your motherboard BIOS once that's done and test the system from here. One or more of these steps is almost certainly going to solve the problem without you having to mess with hardware or do anything destructive.

 

If that doesn't solve it, start by testing your RAM one stick/one slot at a time until you identify the problem or rule it out. Next step would be getting everything you care about off the computer and doing a full wipe with a fresh reinstall of Windows. If that still doesn't handle it, you're into the realm of CPU hardware problems. But let's be real--your CPU is not dying. In all likelihood, it's something in the BIOS that will be cleared by the CMOS reset or the BIOS update, and that's a really easy fix for a really annoying problem.

[PHANTOM1147]

On 9/12/2021 at 2:01 AM, Levent said:

Since you havent provided us with more important things like your system details, this issue is because one of these I listed below:

• CPU overheating/unstable
• RAM overheating/unstable
• (not likely) GPU core overheating/unstable
• (very unlikely) PSU is dying

Sorry about that.

i5-9400f

MSI H310M pro-m2 plus

ADATA D30 3200MHz 16GB (8*2)

MSI GTX1650 super

ADATA Ultimate SU650 240GB SSD

Raidmax RX-400xt PSU

 

 

CPU is always under 80°C even when I playing games.

I tried re-installing windows few times, updating BIOS, reseating ram cpu and gpu. Nothing worked.

sometimes it works fine 4-6h without bluescreening.

[PHANTOM1147]

On 9/12/2021 at 2:13 AM, aisle9 said:

Reset your CMOS first. This is usually an error tied to bad BIOS settings (which are usually tied to a bad overclock, so if you've been doing that...here you go).

 

Next, from within Windows, open up a command prompt with admin rights and run sfc /scannow. That will look for OS errors and try to fix them, and that error is one that can be caused by the OS itself. Then update your motherboard BIOS once that's done and test the system from here. One or more of these steps is almost certainly going to solve the problem without you having to mess with hardware or do anything destructive.

 

If that doesn't solve it, start by testing your RAM one stick/one slot at a time until you identify the problem or rule it out. Next step would be getting everything you care about off the computer and doing a full wipe with a fresh reinstall of Windows. If that still doesn't handle it, you're into the realm of CPU hardware problems. But let's be real--your CPU is not dying. In all likelihood, it's something in the BIOS that will be cleared by the CMOS reset or the BIOS update, and that's a really easy fix for a really annoying problem.

I tried resetting CMOS, testing RAM, fresh installing windows and updating BIOS none of that worked for me.

 

I haven't tried "open up a command prompt with admin rights and run sfc /scannow"

I'll try that. thanks

[PHANTOM1147]

4 hours ago, PHANTOM1147 said:

I tried resetting CMOS, testing RAM, fresh installing windows and updating BIOS none of that worked for me.

 

I haven't tried "open up a command prompt with admin rights and run sfc /scannow"

I'll try that. thanks

It didn't work  

[aisle9]

7 hours ago, PHANTOM1147 said:

I tried resetting CMOS, testing RAM, fresh installing windows and updating BIOS none of that worked for me.

 

I haven't tried "open up a command prompt with admin rights and run sfc /scannow"

I'll try that. thanks

Have you done this? Take out all of your RAM. Put one stick in the slot furthest from your CPU. Test it. If it works fine, move to the next slot. Then so on and so forth until you get the error. If you don't, do the same with your other stick, then again with any more sticks, etc. The idea is that by using one stick and only one stick in one slot at a time, you'll expose any hardware errors.

 

Another thought: have you pulled your CPU and checked for bent pins on the board?

[PHANTOM1147]

On 9/13/2021 at 9:29 PM, aisle9 said:

Have you done this? Take out all of your RAM. Put one stick in the slot furthest from your CPU. Test it. If it works fine, move to the next slot. Then so on and so forth until you get the error. If you don't, do the same with your other stick, then again with any more sticks, etc. The idea is that by using one stick and only one stick in one slot at a time, you'll expose any hardware errors.

 

Another thought: have you pulled your CPU and checked for bent pins on the board?

Yeah, I tried that too but it didn't work.
although I haven't tried using a RAM from a different PC, I'm going to try that.

 

Also, I edited my post yesterday I put every fix that I have tried so far.
Thanks.

 

Edit : I tried using a RAM from a different PC and it didn't work out either.

 

Is there a any chance that this could cause by the GPU or the SSD?

 

Edit : It's definitely not the SSD, I tried installing windows into a different HDD and when I made it to the Desktop it blue screened.

Edited September 15, 2021 by PHANTOM1147