Erratic BSOD on New PC.

[Solaire1080p]

Hello.

I recently upgraded MOBO and CPU

and now, I've been BSODing Non-stop. The timeframe of which is random as sometimes it could take hours, sometimes a whole day. 

I have attached the PERFMON and Dumpfiles.

 

 

OS - Win10

x64

The PC is 2-3 Years old, but the mobo and cpu are new.

Ryzen 7 3700X 

Gigabyte Aorus b450 Pro

Gigabyte Aorus RTX 2070

Corsair XC650 650W

HyperX 8GB DDR4 2400MHz XMP Off

Desktop

 

 

Perfmonndumps.zip

[Streetguru]

19 minutes ago, Solaire1080p said:

 

Did you reinstall windows?

[Solaire1080p]

1 minute ago, Streetguru said:

Did you reinstall windows?

Yeah. 

[Streetguru]

Just now, Solaire1080p said:

Yeah. 

Can it survive a RAM stress test or a PSU stress test like Prime 95 without crashing?

Alternatively you could see what happens running from a Linux USB and installing Steam there

[Solaire1080p]

1 minute ago, Streetguru said:

Can it survive a RAM stress test or a PSU stress test like Prime 95 without crashing?

Alternatively you could see what happens running from a Linux USB and installing Steam there

I have tried a RAM test and it was fine, but not a PSU stress test.

 

[fade2black001]

Download a program called WhoCrashed and find out what the problem is

[Solaire1080p]

2 hours ago, fade2black001 said:

Download a program called WhoCrashed and find out what the problem is

Tried it, sadly it can't identify the driver  

On Wed 30 Oct 2019 11:20:28 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\103019-9312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1220)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF800144AFEE9)
Error: 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
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.

[fade2black001]

That' is saying that the kernal is at fault which is windows itself. Best thing is to reformat or reinstall.