BSOD making the pc unusable

[MarTorb]

I built a pc for my little brother in the summer. After a short while he started getting bsod, it got worse and worse and in the end he got multiple a day. Right now when I tried to get the information needed for this post it has blue screened three times.

 

The most common bluescreens error messages:

machine check exception

page fault in nonpaged area

whea uncorrectable error

 

Steps I have tried:

Change the ram configurations different amount and slots

Update bios, drivers and windows reinstall.

SFC scan and chkdsk

 

Any ideas on how to fix it?

 

Specs:

 

Windows 10 1909 x64

Original OS windows 7 pro

OEM version first now full retial

6 moths old hardware, not the ram and disks though

Age of OS a couple of weeks, just reinstalled

i7-9700k

rtx 2080 gaming x trio from msi
mpg z390 gaming pro carbon ac from msi

Corsair RM750X v2 PSU

desktop

 

 

Files from Resource and Performance Monitor and Sysnative BSOD Dump:

https://drive.google.com/open?id=1wTFExFzk6ezWIyQUrU_kzqzlFiHFVkMX

https://drive.google.com/open?id=1hVh54TjmzM4zByOyqyFJKajzV3IUmDsI

 

 

[xAcid9]

Is it overclock?

[MarTorb]

5 minutes ago, xAcid9 said:

Is it overclock?

No everything is stock

[scottyseng]

I would try running RAM (memtestx86) and CPU stress tests (Intel Burn Test or other test) to see if those are the issues.

 

You could also double check the SMART data of the OS drive to make sure there's no errors there as well.

[xAcid9]

Yeah can you run Memtest+? I suspect RAM or storage error related because your eventlog spit out lots of errors from Origin, MSI Dragon Center, Razer Synapse, Resolve, etc. 

 

Also can you run Msconfig>Diagnostic Startup and see if problem persist??

[MarTorb]

2 minutes ago, xAcid9 said:

Yeah can you run Memtest+? I suspect RAM or storage error related because your eventlog spit out lots of errors from Origin, MSI Dragon Center, Razer Synapse, Resolve, etc. 

 

Also can you run Msconfig>Diagnostic Startup and see if problem persist??

Yes I am working on it Currently running memtestx86

[MarTorb]

2 hours ago, scottyseng said:

I would try running RAM (memtestx86) and CPU stress tests (Intel Burn Test or other test) to see if those are the issues.

 

You could also double check the SMART data of the OS drive to make sure there's no errors there as well.

It passed the memtest and the intelburn test at standard. The drives are also okay according to cmd.

[scottyseng]

5 hours ago, MarTorb said:

It passed the memtest and the intelburn test at standard. The drives are also okay according to cmd.

Ah, run it at maximum. Standard is a bit weak.

I'm curious if it survives memtestx86.
 

The other only time I had this happen in a friend's build was a bad sata data cable (it got cut by accident when closing the side panel)

[MarTorb]

13 hours ago, xAcid9 said:

Yeah can you run Memtest+? I suspect RAM or storage error related because your eventlog spit out lots of errors from Origin, MSI Dragon Center, Razer Synapse, Resolve, etc. 

 

Also can you run Msconfig>Diagnostic Startup and see if problem persist??

It worked fine in diagnostic startup when just idling, however when he opened davinci resolve he blue screened immediately

[xAcid9]

41 minutes ago, MarTorb said:

It worked fine in diagnostic startup when just idling, however when he opened davinci resolve he blue screened immediately

 

 

Can he share latest minidump files? Located in C:\Windows\Minidump

Just zip the whole folder and upload it somewhere.

[MarTorb]

16 hours ago, scottyseng said:

Ah, run it at maximum. Standard is a bit weak.

I'm curious if it survives memtestx86.
 

The other only time I had this happen in a friend's build was a bad sata data cable (it got cut by accident when closing the side panel)

I could not quite run it at maxmium not enoguh ram because I have taken someout for troubleshooting, but I did run it at 4000 mb and it passed it. And also happy new year

[MarTorb]

9 hours ago, xAcid9 said:

 

 

Can he share latest minidump files? Located in C:\Windows\Minidump

Just zip the whole folder and upload it somewhere.

Here is the link for the minidump:

https://drive.google.com/open?id=1m4gqXISuduB9cLQcvPdY0FpRpU6Xgtix

 

And happy new year

[scottyseng]

8 hours ago, MarTorb said:

I could not quite run it at maxmium not enoguh ram because I have taken someout for troubleshooting, but I did run it at 4000 mb and it passed it. And also happy new year

Did it survive memtest?

[MarTorb]

3 minutes ago, scottyseng said:

Did it survive memtest?

Yes

[scottyseng]

2 hours ago, MarTorb said:

Yes

I would try replacing the sata data cable anyway just to see if it helps any. I'm running out of ideas though. Could be a bad driver?

[MarTorb]

18 hours ago, scottyseng said:

I would try replacing the sata data cable anyway just to see if it helps any. I'm running out of ideas though. Could be a bad driver?

Will try it, thank you for your advice

[Mark Kaine]

41 minutes ago, MarTorb said:

Will try it, thank you for your advice

Since you pretty much excluded a hardware issue - did you check for updates? 

 

Because this is usually either a hardware issue or a driver issue and Windows update just may fix it sometimes. 

 

 

If that doesn't work I would remove all storage devices and try installing windows on another,  preferably known to be good hard-drive and see if the issue persists.

 

Yes, it could also be a faulty cable,  however I think that's unlikely. 

[MarTorb]

1 hour ago, Mark Kaine said:

Since you pretty much excluded a hardware issue - did you check for updates? 

 

Because this is usually either a hardware issue or a driver issue and Windows update just may fix it sometimes. 

 

 

If that doesn't work I would remove all storage devices and try installing windows on another,  preferably known to be good hard-drive and see if the issue persists.

 

Yes, it could also be a faulty cable,  however I think that's unlikely. 

Yes the system is update. I will check the drive situation. Thank you for the tips

[scottyseng]

4 hours ago, MarTorb said:

Will try it, thank you for your advice

Yeah, you might also try resetting CMOS as well