BSOD Issues

[Bhameck]

About a week ago I started to have issues with my PC bluescreening. They happen many times a day, and I have no idea what is causing them. I reset windows a few times, and then did a fresh install of windows as well. I also installed missing drivers, however that did not help. I get the BSODs in every way imaginable, sometimes I'd be away from my computer for a while and when I come back and press one key, it bluescreens. Other times I don't have any issues for an hour or two and it randomly fails out of nowhere. I have not seen any connection between programs and the bluescreens. I do get crashes where my monitor freezes and I have to reboot manually, and they commonly occur after a bluescreen. I have reseated my ram, GPU, and M.2 as well as run Memtest. I have also looked at many different forums, but I couldn't find the issue I was having. My specs are:

R7 3700X

RTX 2070 Super

Asrock B550 Steel Legend

Samsung 970 Evo M.2

EVGA 800w 80+ Gold

16gb 8x2 3600 MHZ RAM 

 

I copied my dump files and a Perfmon Report below. Please tell me if I need to add something.Dump Files.zip

[Digideath]

Ok ive read your dumps. Multiple failures on ntoskrnl.sys and one rather interesting one caused by the amd processor driver.

First the obvious. Are you overclocking? Cpu maybe or xmp? Turn off the overclocks and check stability.
Also are your drivers and bios up to date? The ntoskrnl errors are being caused by software.

With regards to the cpu driver one. Do the following.

Click Start
Type: regedit
Right click regedit
Click Run as administrator

Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\amdppm
Change Start to have a value of 4.

Exit then restart to see if the system is more stable. That should hopefully take care of the cpu driver one.

[ChopstickWarrior]

i dont know really much about this, but i was having quite same problem last month. And the problem is from the motherboard battery, im just curious that day what would happen if i change the battery and untill now i never facing any bsod again. sometimes the problem is right under your nose, but i dont know if that will work too for your pc but that is worth a shot i guess. hope it will worked, and i hope you can fix it very soon

[Bhameck]

15 minutes ago, Digideath said:

Ok ive read your dumps. Multiple failures on ntoskrnl.sys and one rather interesting one caused by the amd processor driver.

First the obvious. Are you overclocking? Cpu maybe or xmp? Turn off the overclocks and check stability.
Also are your drivers and bios up to date? The ntoskrnl errors are being caused by software.

With regards to the cpu driver one. Do the following.

Click Start
Type: regedit
Right click regedit
Click Run as administrator

Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\amdppm
Change Start to have a value of 4.

Exit then restart to see if the system is more stable. That should hopefully take care of the cpu driver one.

I am not overclocking and I disabled XMP. I updated my bios and drivers a few days ago, and I changed Start value to 4, and I am still getting BSODs. I have also gotten a new type of BSOD where my main monitor goes black, then it shows the BSOD and it is very low resolution on my second monitor. 

[Digideath]

4 minutes ago, Bhameck said:

I am not overclocking and I disabled XMP. I updated my bios and drivers a few days ago, and I changed Start value to 4, and I am still getting BSODs. 

Not good. I was hopping that would fix it. It means your cpu is highly suspect. The amd cpu driver stopped responding with a dcp watchdog violation error. I've seen that error before a few times with bad cpus.

Try this. Get prime 95 if you can and run the small fft test. Look out for 2 things. Blue screens caused by prime or prime failing with rounding errors. If it does blue screen, get the error name.

[Bhameck]

11 minutes ago, Digideath said:

Not good. I was hopping that would fix it. It means your cpu is highly suspect. The amd cpu driver stopped responding with a dcp watchdog violation error. I've seen that error before a few times with bad cpus.

Try this. Get prime 95 if you can and run the small fft test. Look out for 2 things. Blue screens caused by prime or prime failing with rounding errors. If it does blue screen, get the error name.

I ran prime and nothing went wrong during the test. But after the test, almost immediately, it bluescreened with the error name irql less or not equal.