Question PC freezes and then blue screens, possible hardware issue

[yutuyt]

A few days ago my PC started blue screening with the stop code WHEA_UNCORRECTABLE_ERROR. Whenever I restarted it seemed to work fine for several hours and then it would occur again. Recently the blue screens have become much more frequent with new error codes such as MACHINE_CHECK_EXCEPTION and DPC_WATCHDOG_VIOLATION. From what I've seen I have a hardware problem, but I am trying to figure out what part of my computer could be causing this. My PC's temperature is not high at all so I don't think it could be causing this. I ran Memtest and got no errors. Does anyone have an idea what could be going on? My guess is that I need a new CPU. Any help would be greatly appreciated!

https://drive.google.com/drive/folders/1bSCqRFzoZIgJ7xIl3wV-sDE19o5bT2sw?usp=sharing
Here are my minidumps. Most of the WHEA_UNCORRECTABLE_ERROR ones do not exist as they never got past 0% when they collected error data and I had to force shutdown.

From WhoCrashed:
On Mon 7/12/2021 2:41:41 PM your computer crashed or a problem was reported
crash dump file: C:\windows\Minidump\071221-9250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F6B90)
Bugcheck code: 0x9C (0x80000001, 0xFFFFBE80F655BB30, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Mon 7/12/2021 2:18:43 PM your computer crashed or a problem was reported
crash dump file: C:\windows\Minidump\071221-9312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F6B90)
Bugcheck code: 0x9C (0x80000001, 0xFFFFCF015B5D5B30, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Mon 7/12/2021 1:40:04 PM your computer crashed or a problem was reported
crash dump file: C:\windows\Minidump\071221-9171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F6B90)
Bugcheck code: 0x124 (0x0, 0xFFFFBD05014DF028, 0xB2000000, 0x30005)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Mon 7/12/2021 12:31:55 PM your computer crashed or a problem was reported
crash dump file: C:\windows\Minidump\071221-6000-01.dmp
This was probably caused by the following module: intelppm.sys (intelppm+0x138f)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF802166FB320)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\windows\system32\drivers\intelppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
The crash took place in a Microsoft module. The description of the module may give a hint about a non responding device in the system.

 

[yutuyt]

I have the "Cooler Master MasterWatt 550 W 80+ Bronze Certified Semi-modular ATX Power Supply". I had another crash, KMODE_EXCEPTION_NOT_HANDLED.
This is the Minidump for it https://drive.google.com/file/d/14Kqc0VwY8ZU9sjYlRD0X49pEUt6XAufc/view?usp=sharing
I reinstalled VALORANT after the crashes still occurred even when I uninstalled the game. WhoCrashes says this error could be caused by a buggy driver, maybe it is the same one?
I'm considering running the Memtest again. Last time I ran it with 4 passes, is that enough?
I ran the GPU tests, and did not receive a crash. I noticed that my CPU was not particularly stressed during them, which makes sense, but also leads me to think it is the CPU.

 

[Colif]

CPU passsed the intel test, if you need a 2nd opinion run this

Prime 95 - https://www.mersenne.org/download/
Prime 95 how to Guide: http://www.playtool.com/pages/prime95/prime95.html

it will test ram + CPU

 

[yutuyt]

On Sat 7/17/2021 3:26:42 PM your computer crashed or a problem was reported
crash dump file: C:\windows\Minidump\071721-9843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F6F20)
Bugcheck code: 0xD1 (0xFFFFFFF4, 0xFF, 0x28, 0xFFFFFFF4)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

https://drive.google.com/file/d/1wXFNH2JgFxJJhyL0AA-ZI9Gyq_GE4GaN/view?usp=sharing

 

[gardenman]

I ran the new dump files through the debugger and got the following information: https://jsfiddle.net/k8d1c2Lu/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

Spoiler: Dump File Results

File information:	071721-9843-01.dmp (Jul 17 2021 - 15:26:42)
Bugcheck:	DRIVER_IRQL_NOT_LESS_OR_EQUAL (D1)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 4 Hour(s), 35 Min(s), and 54 Sec(s)

File information:	071621-6875-01.dmp (Jul 16 2021 - 20:14:35)
Bugcheck:	KMODE_EXCEPTION_NOT_HANDLED (1E)
Probably caused by:	memory_corruption (Process: mscorsvw.exe)
Uptime:	0 Day(s), 0 Hour(s), 11 Min(s), and 10 Sec(s)

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

Edit: Results for the dump below: https://jsfiddle.net/u70wx2bk/show

 

[yutuyt]

Is the prime 95 download page working for you guys? I click on a link and nothing happens.

 

[yutuyt]

These blue screens have been ALL over the place. Got a SYSTEM_SERVICE_EXCEPTION instead of MACHINE_CHECK_EXCEPTION this time.
On Sun 7/18/2021 1:07:23 PM your computer crashed or a problem was reported
crash dump file: C:\windows\Minidump\071821-9031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F6F20)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF806070F3F63, 0xFFFFED074740ED80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

I swapped my ram into the the unused slots, and will run another memtest tonight.
Minidump for System exception: https://drive.google.com/file/d/1Ous1XN8PvkQ8UEb3X8mn7CSNyStZV9CX/view?usp=sharing

 

[Colif]

Is the prime 95 download page working for you guys? I click on a link and nothing happens.

I see what you mean

try this one - https://www.guru3d.com/files-details/prime95-download.html

Mscorsvw.exe is a process related to Microsoft .NET framework and is used to precompile .Net framework assemblies in the background. strange parts of windows are crashing now.

which version of win 10

1. right click start
   
2. choose run...
   
3. type winver and press enter
   
4. current version is 21H1
   

notices every 2nd post he has blamed something else. its a moving target and it shouldn't be. Why Prime 95 might help.

 

[yutuyt]

I swapped my RAM into the other slots and I have not experienced a crash the entire day, even with running my CPU and GPU under heavy loads. Will wait for a few days until I declare the problem fully fixed. My windows OS build says it is version 2004.

 

[Colif]

that is odd. i looked in your manual and you can use either channel with 2 sticks so it wasn't as if you were in the wrong one
you were in 4_2 & 4_4
I assume you now in 4_1 & 4_3
so from closest to cpu to mb edge, order is
so 4_4, 4_3, 4_2, 4_1

some motherboards care if you use 1 channel over another but yours isn't worried.
top of page 10 - https://download.gigabyte.com/FileList/Manual/mb_manual_b360m-ds3h_1001_e.pdf

still strange

 

[yutuyt]

Yeah it is really strange, I guess those either one or both of those ram slots have become malfunctional.

 

[Colif]

how many times did you check each stick in memtest?

I only ask as you have had periods before with no errors.

BSOD don't wave a white flag, you don't know if its really fixed until they stop. Or if you can identify the driver to blame and remove it. Right now its in the unknown maybe state

I just want to make sure.

 

[yutuyt]

I ran the sticks 4 passes twice, since 4 was the max amount allowed by the free version.

 

[Colif]

could also be ram just needed to be reseated. I won't comment again unless you do

 

[yutuyt]

I think the crashing problem is fully fixed, but my SSD still randomly does not show up whenever I restart my PC. It'll show up after a few restarts and I can boot to it normally. Leads me to think it's the motherboard still but this is a problem that doesn't cause me much trouble so I can live with it. Thanks for all your help (both of you!)