Question Random BSODs on New build

[PersistantPro]

Since I built my PC in November I have had BSODs at random no matter what I am doing. This is a new build so Nothing has changed in it, besides swapping out ram to test.
My specs:

• MB: Gigabyte B450 Auros Pro Wifi
• CPU: Ryzen 5 3600X
• Ram: Corsair Vengeance LPX 2x8gb 3200mhz in dual channel mode
• GPU: EVGA RTX 2070 Super
• PSU: I salvaged my PSU from my first build it is 5 years old if that matters, but it is a EVGA 750W Gold rated
• SSD: Samsung 860 evo 1TB
• OS: Windows 10 64 bit

I have a few minidumps from the last 2 days if you guys would like to look through them https://drive.google.com/drive/folders/1sMz56znN3x3LV1hrF85VxBTCQOqkAcuB?usp=sharing

• I have run memtest no errors
• formatted SSD and reinstalled windows
• SFC scan
• Obvious malware and virus scan (nothing)
• reseated all of my components, etc
• Uninstalled nvidia drivers
• Updated Bios
• Everything under the sun

They just happen at random. I could be playing RDR2, or browsing chrome, or even just opening an app and i'll get a crash. A lot of the minidumps say it is a memory error but memtest and windows memory diagnostic say nothing is wrong. Or it'll say my drivers are faulty, but even after a fresh windows install I get these errors. I truly appreciate taking the time to help with my errors! I wonder at this point if it's my PSU being somewhat old, but not even sure. It has been a frustrating few months to say the least.

 

[PersistantPro]

Okay so running memtest again I just got like 1000 errors. Assuming this means my new set of ram is busted?

 

[gardenman]

Hi, run 1 RAM module at a time in the first slot. See if one, or both, are bad. If both, then it could be another problem (maybe the motherboard). If only 1 is bad, then it's likely a bad RAM module.

Ryzen's are also more sensitive to RAM. If one chip is bad, you might want to send both back and get a new matching "set".

I've read the dump files and here are the results: https://nummaryfan.htmlpasta.com/

Spoiler

File information:	012720-9046-01.dmp (Jan 27 2020 - 16:08:35)
Bugcheck:	ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (FC)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 1 Hour(s), 01 Min(s), and 53 Sec(s)

File information:	012720-8828-01.dmp (Jan 27 2020 - 16:11:56)
Bugcheck:	FAST_ERESOURCE_PRECONDITION_VIOLATION (1C6)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 02 Min(s), and 24 Sec(s)

File information:	012620-8390-01.dmp (Jan 26 2020 - 14:01:58)
Bugcheck:	DPC_WATCHDOG_VIOLATION (133)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 44 Min(s), and 38 Sec(s)

File information:	012620-8046-01.dmp (Jan 26 2020 - 17:29:38)
Bugcheck:	MEMORY_MANAGEMENT (1A)
Probably caused by:	memory_corruption (Process: steamwebhelper.exe)
Uptime:	0 Day(s), 3 Hour(s), 12 Min(s), and 38 Sec(s)

File information:	012720-8828-02.dmp (Jan 27 2020 - 17:31:45)
Bugcheck:	ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (FC)
Driver warnings:	*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 02 Min(s), and 47 Sec(s)

BIOS info was not included in the 1st dump file. This can sometimes mean an outdated BIOS is being used.

One of the crashes was also caused by the NVIDIA driver nvlddmkm.sys. I would worry about the RAM first. But, there are a few things you can do to fix this problem. First off, try a full uninstall using DDU in Safe Mode then re-install the driver (more information). Or try getting the latest version of the driver. Or try one of the 3 most recent drivers released by NVIDIA. Drivers can be found here: http://www.nvidia.com/ or you can allow Windows Update to download the driver for you, which might be a older/better version.

I'll also ask @Colif to look at this thread.

 

[PersistantPro]

Hi, run 1 RAM module at a time in the first slot. See if one, or both, are bad. If both, then it could be another problem (maybe the motherboard). If only 1 is bad, then it's likely a bad RAM module.

Ryzen's are also more sensitive to RAM. If one chip is bad, you might want to send both back and get a new matching "set".

I've read the dump files and here are the results: https://nummaryfan.htmlpasta.com/

Spoiler

File information:	012720-9046-01.dmp (Jan 27 2020 - 16:08:35)
Bugcheck:	ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (FC)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 1 Hour(s), 01 Min(s), and 53 Sec(s)

File information:	012720-8828-01.dmp (Jan 27 2020 - 16:11:56)
Bugcheck:	FAST_ERESOURCE_PRECONDITION_VIOLATION (1C6)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 02 Min(s), and 24 Sec(s)

File information:	012620-8390-01.dmp (Jan 26 2020 - 14:01:58)
Bugcheck:	DPC_WATCHDOG_VIOLATION (133)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 44 Min(s), and 38 Sec(s)

File information:	012620-8046-01.dmp (Jan 26 2020 - 17:29:38)
Bugcheck:	MEMORY_MANAGEMENT (1A)
Probably caused by:	memory_corruption (Process: steamwebhelper.exe)
Uptime:	0 Day(s), 3 Hour(s), 12 Min(s), and 38 Sec(s)

File information:	012720-8828-02.dmp (Jan 27 2020 - 17:31:45)
Bugcheck:	ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (FC)
Driver warnings:	*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 02 Min(s), and 47 Sec(s)

BIOS info was not included in the 1st dump file. This can sometimes mean an outdated BIOS is being used.

One of the crashes was also caused by the NVIDIA driver nvlddmkm.sys. I would worry about the RAM first. But, there are a few things you can do to fix this problem. First off, try a full uninstall using DDU in Safe Mode then re-install the driver (more information). Or try getting the latest version of the driver. Or try one of the 3 most recent drivers released by NVIDIA. Drivers can be found here: http://www.nvidia.com/ or you can allow Windows Update to download the driver for you, which might be a older/better version.

I'll also ask @Colif to look at this thread.

Appreciate the help, I did the memtest again and one of the sticks was definitely bad in different slots while the other was fine. So replacing that stick through amazon. I’ll try the driver complete uninstall and reinstall tomorrow!

 

[Colif]

Never seen one of those errors before but it appears to be a driver error - FAST_ERESOURCE_PRECONDITION_VIOLATION - like the rest can be.

Its possible they are all caused by Nvidia drivers, i would avoid the newest and use older ones or run windows update and let windows find its Nvidia drivers that are more stable.

its strange the RGB fusion has a driver from 2008 but it might be okay.

Ram also causes random errors you don't normally see so I would just not do anything unless you keep getting BSOD,

 

[PersistantPro]

Hi, run 1 RAM module at a time in the first slot. See if one, or both, are bad. If both, then it could be another problem (maybe the motherboard). If only 1 is bad, then it's likely a bad RAM module.

Ryzen's are also more sensitive to RAM. If one chip is bad, you might want to send both back and get a new matching "set".

I've read the dump files and here are the results: https://nummaryfan.htmlpasta.com/

Spoiler

File information:	012720-9046-01.dmp (Jan 27 2020 - 16:08:35)
Bugcheck:	ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (FC)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 1 Hour(s), 01 Min(s), and 53 Sec(s)

File information:	012720-8828-01.dmp (Jan 27 2020 - 16:11:56)
Bugcheck:	FAST_ERESOURCE_PRECONDITION_VIOLATION (1C6)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 02 Min(s), and 24 Sec(s)

File information:	012620-8390-01.dmp (Jan 26 2020 - 14:01:58)
Bugcheck:	DPC_WATCHDOG_VIOLATION (133)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 44 Min(s), and 38 Sec(s)

File information:	012620-8046-01.dmp (Jan 26 2020 - 17:29:38)
Bugcheck:	MEMORY_MANAGEMENT (1A)
Probably caused by:	memory_corruption (Process: steamwebhelper.exe)
Uptime:	0 Day(s), 3 Hour(s), 12 Min(s), and 38 Sec(s)

File information:	012720-8828-02.dmp (Jan 27 2020 - 17:31:45)
Bugcheck:	ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (FC)
Driver warnings:	*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 02 Min(s), and 47 Sec(s)

BIOS info was not included in the 1st dump file. This can sometimes mean an outdated BIOS is being used.

One of the crashes was also caused by the NVIDIA driver nvlddmkm.sys. I would worry about the RAM first. But, there are a few things you can do to fix this problem. First off, try a full uninstall using DDU in Safe Mode then re-install the driver (more information). Or try getting the latest version of the driver. Or try one of the 3 most recent drivers released by NVIDIA. Drivers can be found here: http://www.nvidia.com/ or you can allow Windows Update to download the driver for you, which might be a older/better version.

I'll also ask @Colif to look at this thread.

Quick question, in the DDU it gives me an option to remove C:\Nvidia driver folders. I’m assuming I do this?

 

[PersistantPro]

Never seen one of those errors before but it appears to be a driver error - FAST_ERESOURCE_PRECONDITION_VIOLATION - like the rest can be.

Its possible they are all caused by Nvidia drivers, i would avoid the newest and use older ones or run windows update and let windows find its Nvidia drivers that are more stable.

its strange the RGB fusion has a driver from 2008 but it might be okay.

Ram also causes random errors you don't normally see so I would just not do anything unless you keep getting BSOD,

I have uninstalled the latest drivers using safe mode and DDU, and installed drivers from november

 

[gardenman]

I usually delete the C:\NVIDIA folder after driver updates. If it's still there, move it to the Desktop or somewhere safe for a few days. If everything still works right, then delete it. It's usually only used as a temporary location for the setup files.

I hope everything works out, let us know. If you have additional crashes upload the dump files.

 

[PersistantPro]

I usually delete the C:\NVIDIA folder after driver updates. If it's still there, move it to the Desktop or somewhere safe for a few days. If everything still works right, then delete it. It's usually only used as a temporary location for the setup files.

I hope everything works out, let us know. If you have additional crashes upload the dump files.

I’ll let you guys know how it goes tomorrow when I put the new ram in, thanks for all the help I appreciate it

 

[PersistantPro]

Hey @gardenman and @Colif i've had another BSOD. https://drive.google.com/drive/folders/1Wk8WYMlD3cPc8d4sa0KBjSXISkpFVJcE?usp=sharing is the newest minidump. Appreciate the help guys

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://healthiestibis.htmlpasta.com/

File information:	012920-8703-01.dmp (Jan 29 2020 - 21:39:59)
Bugcheck:	SYSTEM_SERVICE_EXCEPTION (3B)
Driver warnings:	*** WARNING: Unable to verify timestamp for aswArPot.sys
Probably caused by:	memory_corruption (Process: Battle.net.exe)
Uptime:	0 Day(s), 1 Hour(s), 22 Min(s), and 56 Sec(s)

Crashing driver:

Sep 06 2019

aswArPot.sys

Avast Antivirus http://www.avast.com/

It looks like Avast crashed. You can try to reinstall it, temporarily remove it, or wait and see if you have more problems.

 

[PersistantPro]

I ran the dump file through the debugger and got the following information: https://healthiestibis.htmlpasta.com/

File information:	012920-8703-01.dmp (Jan 29 2020 - 21:39:59)
Bugcheck:	SYSTEM_SERVICE_EXCEPTION (3B)
Driver warnings:	*** WARNING: Unable to verify timestamp for aswArPot.sys
Probably caused by:	memory_corruption (Process: Battle.net.exe)
Uptime:	0 Day(s), 1 Hour(s), 22 Min(s), and 56 Sec(s)

Crashing driver:

Sep 06 2019

aswArPot.sys

Avast Antivirus http://www.avast.com/

It looks like Avast crashed. You can try to reinstall it, temporarily remove it, or wait and see if you have more problems.

Uninstalled. Thanks, i'll update you if I have any other errors. What does that say about battle net did that crash too or something? it's been giving me problems trying to launch Modern Warfare

 

[gardenman]

Battle.net crashed but it was Avast that was the problem (or so I believe). We usually don't blame software (Battle.net) for BSODs, but we blame drivers or hardware. Avast comes with many drivers. Battle.net also communicates over the internet, so does Avast, so if you continue having problems, maybe look at updating the networking drivers (if available). I wouldn't do that just yet though, wait to see if you continue having problems first.

 

[PersistantPro]

Been a couple weeks but got another crash @gardenman @Colif https://drive.google.com/open?id=1sDdjxgZCnIpup47vRcHRj1yJsfIAAPES

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://sulkiermission.htmlpasta.com/

File information:	021320-7890-01.dmp (Feb 13 2020 - 13:39:44)
Bugcheck:	SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:	memory_corruption (Process: Battle.net.exe)
Uptime:	0 Day(s), 3 Hour(s), 06 Min(s), and 34 Sec(s)

It looks like Battle.net crashed again. Maybe Colif has more ideas.

Edit:
Results for below dump file: https://squabbiestshake.htmlpasta.com/

File information:	021420-8187-01.dmp (Feb 14 2020 - 13:05:17)
Bugcheck:	SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:	memory_corruption (Process: csrss.exe)
Uptime:	0 Day(s), 2 Hour(s), 10 Min(s), and 14 Sec(s)

 

[PersistantPro]

I ran the dump file through the debugger and got the following information: https://sulkiermission.htmlpasta.com/

File information:	021320-7890-01.dmp (Feb 13 2020 - 13:39:44)
Bugcheck:	SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:	memory_corruption (Process: Battle.net.exe)
Uptime:	0 Day(s), 3 Hour(s), 06 Min(s), and 34 Sec(s)

It looks like Battle.net crashed again. Maybe Colif has more ideas.

Strange I've tried uninstalling and reinstalling it. Maybe cause it's not on my C drive?

 

[PersistantPro]

Had another crash @gardenman @Colif Wondering if it's still battle net? https://drive.google.com/open?id=1Zcrt3B3FnZExNVDp-vVE_ZH_e4yOsbeq if so i'm just moving it to my C drive

 

[Colif]

weather has been terrible and I don't use PC when there are storms around.

battlenet seems unlikely cause. As did Avast before but we have seen it cause BSOD in the past. Dump text mentions afd.sys which is a windows process associated with Internet

Are you using the latest WIFI driver? https://www.gigabyte.com/au/Motherboard/B450-AORUS-PRO-WIFI-rev-10/support#support-dl-driver-wlanbt

If you use Ethernet, try the newest drivers here - https://www.gigabyte.com/au/Motherboard/B450-AORUS-PRO-WIFI-rev-10/support#support-dl-driver-lan

 

[PersistantPro]

weather has been terrible and I don't use PC when there are storms around.

battlenet seems unlikely cause. As did Avast before but we have seen it cause BSOD in the past. Dump text mentions afd.sys which is a windows process associated with Internet

Are you using the latest WIFI driver? https://www.gigabyte.com/au/Motherboard/B450-AORUS-PRO-WIFI-rev-10/support#support-dl-driver-wlanbt

If you use Ethernet, try the newest drivers here - https://www.gigabyte.com/au/Motherboard/B450-AORUS-PRO-WIFI-rev-10/support#support-dl-driver-lan

Intel driver updater claims i have the latest drivers for the wifi. I've had another crash now, this horror never ends https://drive.google.com/open?id=1Wv0u1GMWM8mwvoLd9IGm0ihi331SBpWP Appreciate the help guys @Colif @gardenman

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://battierborneoelephant.htmlpasta.com/

File information:	022020-8390-01.dmp (Feb 20 2020 - 23:39:39)
Bugcheck:	IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 2 Hour(s), 22 Min(s), and 54 Sec(s)

Nothing sticks out as obvious in the dump file to me. It doesn't directly point out a driver.

 

[Colif]

When you ran memtest, did you run it 4 times on each stick? just curious as cause could be a ghost moving from 1 driver to next. ram can do that.

Nvidia is always a choice I could make with a win32k.sys error. Its part of the kernel and I often see it crash alongside Nvidia. I am not sure if I am seeing things.

razer drivers can also cause BSOD.

1 way to avoid guessing is run driver verifer, if it's a driver it should tell us. Just follow the preacautions in the 2nd post here - https://forums.tomshardware.com/thr...nclude-in-blue-screen-of-death-posts.3468965/

 

[PersistantPro]

When you ran memtest, did you run it 4 times on each stick? just curious as cause could be a ghost moving from 1 driver to next. ram can do that.

Nvidia is always a choice I could make with a win32k.sys error. Its part of the kernel and I often see it crash alongside Nvidia. I am not sure if I am seeing things.

razer drivers can also cause BSOD.

1 way to avoid guessing is run driver verifer, if it's a driver it should tell us. Just follow the preacautions in the 2nd post here - https://forums.tomshardware.com/thr...nclude-in-blue-screen-of-death-posts.3468965/

Yes I ran it for 4 cycles on each stick, then both sticks together. I might uninstall the Razer drivers for a little to see if that is it. It does claim Synapse 3 is in beta so perhaps that could be the issue. I've ran driver verifier many times, and it claims there is no errors with my drivers. I will run it again and update you guys

 

[PersistantPro]

Ran verifier, got 2 crashes. Only had a minidump for one @Colif @gardenman https://drive.google.com/open?id=1jrPPI97242C5J4UYvSyS0zlfC7507SWd

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://scurrilousgopher.htmlpasta.com/

File information:	022120-8046-01 - Copy.dmp (Feb 21 2020 - 12:15:07)
Bugcheck:	DRIVER_VERIFIER_DETECTED_VIOLATION (C4)
Driver warnings:	*** WARNING: Unable to verify timestamp for RzDev_0064.sys
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 00 Min(s), and 08 Sec(s)

Looks like a Razer driver.

 

[Colif]

razer drivers can also cause BSOD.

well, what do you know...

Apr 22 2018

RzDev_0064.sys

Razer driver

odd you only have 1 installed, they normally travel in pairs.

If you have already run uninstaller and its still there, try using auto runs to stop it at startup - https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns

Try running without beta. Seems razer want to replicate logitech, have good hardware and bad drivers. Logitech learned their lesson, Razer are yet to. I avoid Razer gear because of synapse... I used to have a KB & mouse made by them, now nothing. Lets see if version 3 any better than last one.