BSOD Whea_Uncorrectable_Error while running Discord and Google Chrome

Hey, I could use some help.

Background Story.
I have this error for quite long now, it has slowly become worse over time. I remember like 1-2 years maybe 3 years ago, I started to get this error when I played counter strike global offensive. I tried to fix back then, but not really with any success and I also lost the desire to play the game. This error didn't occur in nothing else in that time. Time moved onÂ…

12 month or more from today, (it’s hard to remember precise time, hope it's okay) the error came back when I used Google Chrome. Eventually it just became more often and lest time spend on google chrome before the error occurred. I realised that the error would almost stop, if I lead a game run, while browsing, watching youtube, checking mail for longer period of time. If I stopped “playing””running” the game it would usually crash after a smaller period of time 1-8 min. I tried somethings but not much to fix it, I just moved on. 3 months later things got worse, I usually use discord when I play with friends, but the error started to occur too, when I join a call, both privately and in servers.

My problem short summary.
CanÂ’t join calls in general on discord or browse google chrome without the pc getting a BSOD Whea_Uncorrectable_Error. The error usually happens within 0-3 min on Discord. Google chrome still crashed heavily, even tho it maybe last longer before they error occur, 15 min max, but average time is prop 0-8 min. Sometimes both things just almost instant triggers the error. Just to make it clear, the computer runs internet explore fine and heavy games like Ark Survival Evolved...

I Tried.
Updated all drivers (Used Driver easy, purchased the automatic version)
Updated Windows
Scanned for driver errors in Cmd and maybe others not sure ( I am not really a expert, followed some youtube videos)
Scanned a crash report file in a program, which says it was hardware mistake, couldnÂ’t tell much more (Forgot the specific file type names, but something windows saves after a crash, forgot the program name, thinks itÂ’s a pretty common to be fair)
Factory Reset it (Complete empty / reset)
Replaced my ram (See if that worked, didnÂ’t help)
Replaced my 1xHard Drive
Replaced my 1x SCD Drive.
I moved Windows from my old SCD drive to the new I replaced and Again did a Factory reset.

I kinda given up now, until I make my next step. I donÂ’t what the next step should be. Maybe itÂ’s a software error even tho I think most Whea_Uncorrectable_Error are hardware errors (might be wrong). Maybe there are some heavy test I can run ( donÂ’t really know any test or what to go for, kinda noob in that area) Thanks a lot for reading this. All helped would be nice and considered. Let me know u need! Thanks a lot!

Update/ comment I added pc spec to my profile think it's all there otherwise let me know. I tried to attach some dump files, because I think it's needed, but it's says need administrator permission. I will remove this part once it's figured out.

   Warning

Attention:

Before posting a BSOD thread, please read the instructions here: Blue Screen of Death (BSOD) Posting Instructions

If you need to add new information, please make a new post in your initial BSOD thread. Please do not make an extra new thread.

Please do not post anything other than Windows 10 Blue Screen Of Death problems in this section.

No problem, got the data now, thanks.

3 dumps, al basically the same:

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

Code:

10: kd> !errrec ffffa08e12b91028
===============================================================================
Common Platform Error Record @ ffffa08e12b91028
-------------------------------------------------------------------------------
Record Id     : 01d66c2c4e120f88
Severity      : Fatal (1)
Length        : 872
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 8/6/2020 20:34:13 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffa08e12b910a8
Section       @ ffffa08e12b91180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Micro-Architectural Error
Flags         : 0x00
CPU Version   : 0x0000000000050654
Processor ID  : 0x000000000000000a

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ ffffa08e12b910f0
Section       @ ffffa08e12b91240
Offset        : 536
Length        : 64
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x000000000000000a
CPU Id        : 54 06 05 00 00 08 10 0a - bf fb fe 7f ff fb eb bf
                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

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffffa08e12b91138
Section       @ ffffa08e12b91280
Offset        : 600
Length        : 272
Flags         : 0x00000000
Severity      : Fatal

Error         : Unknown (Proc 10 Bank 0)
  Status      : 0xb200000000070005

This bug check is typically related to physical hardware failures. It can be heat related, defective hardware, memory or a processor that is beginning to fail or has failed. If over-clocking has been enabled, try disabling it. Confirm that any cooling systems such as fans are functional. Run system diagnostics to confirm that the system memory is not defective. It is less likely, but possible that a driver is causing the hardware to fail with this bug check.

Monitor your temps with HWmonitor, see if overheating is causing the problem. If the CPU is running hot or high, try replacing the thermal paste on the heatsink/CPU. If temps are okay then you may have a failing CPU and will need to replace it. You have a nice one:

CPU: Intel Core i7 7820X @ 3.60GHz Skylake-X 14nm Technology

If you are doing any over clocking, remove it, set everything to nominal, including memory timings.

Run the Intel® Processor Diagnostic Tool and see if it shows you anything.

Please change the default language to English so that log files can be scanned and read:
https://www.tenforums.com/tutorials/...dows-10-a.html
Change Display Language in Windows 10

Then upload a new V2.

Mismatched RAM is a confounding factor.
There can be unexpected behavior in the computer environment including unexpected shutdowns and restarts.

When selecting RAM always purchase in pairs.
Always find RAM modules on the QVL as these were tested for compatibility and performance by the motherboard manufacturer.
Consider RAM manufacturers that guarantee compatibility.
Consider RAM manufacturers that have lifetime warranties.

The Crucial scanner is a quick method to check options:
Crucial System Scanner

Often for WHEA 0x124 the software testing does not produce a definitive fail.
When software stress tests of the hardware display fail this shortens the troubleshooting.

Make sure images are posted for all steps / tests.

Take Screenshot in Windows 10
https://support.microsoft.com/en-gb/...re-screenshots
How to Upload and Post Screenshots and Files at Ten Forums

Find a camera or smartphone camera to take pictures and post images into the thread.
For any problems posting images please use share links (one drive, drop box, or google drive)


Run IPDT again and post images into the thread.
Download Intel(R) Processor Diagnostic Tool
Also post the IPDT text report using a share link.


Run Prime95 - Stress Test Your CPU
Prime95 - Stress Test Your CPU Windows 10 Performance Maintenance Tutorials
Prime95 - Stress Test Your CPU
a) Record the maximum temperature and post the maximum temperature into the thread
b) Record test duration and post the uninterrupted test duration into the thread
c) Aim for testing > 3 hrs and abort testing as needed for freezing, temperature changes (see link)
d) Use the Microsoft snipping tool to post images into the thread.
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
Take Screenshot in Windows 10