BSOD Every Week. What's wrong?

[Novabutter]

I've recently upgraded my rig back in September, and ever since then I've had crashing almost every week from Windows. I usually right down what the error is, and I've caught a few. 

 

The telltale that the system is usually going to crash is when a program running in the background unexpectedly quits with a problem. About 10 seconds to a minute later, the whole system goes down and reboots. Generally, after a reboot, it happens once more with a different error, then I'm fine for the rest of the week.

 

My crashing most commonly occurs when running/using the following programs independently or all together:
- Listening to music through the Desktop Spotify Application

- Running Asus Aura Sync's Music Mode

- Opening Google Chrome for the first time after a boot (Page says "Aw Snap", then the system dies)

- Sometimes while gaming in any game.

 

No hardware is overclocked, and memory is running at stock 2133 Mhz speeds. 

 

This is my system:

https://pcpartpicker.com/list/gmt2hq

 

Most recent recorded BSOD screens say the following:
 

1) SYSTEM_SERVICE_EXCEPTION; What failed: Npfs.SYS

2) SYSTEM_SERVICE_EXCEPTION; What failed: dxgmms2.SYS

3) Running Windows driver verifier, not even being able to successfully boot into the Windows OS: 

(All I caught was the following phrase) FINETHYRAMAS (I think...)

 

Here is a link to my latest Minidump files within the past 30 days: 

https://drive.google.com/open?id=11CV7WKIv0xCa1Q09bV8VyNPfRoVyiw74

 

At least tell me where to post this for more help. I've already posted to Microsoft.

 

Any thoughts?

[Tsuki]

Im getting bad ram, or bad drivers, or even corrupt OS

 

honestly, i'd first try reinstalling the OS first. unless you can swap the ram out

[RenaKry]

From past experience, when I have Aw, Snap! errors on Chrome, it was caused by a bad RAM overclock. Bad RAM overclock means unstable memory, so I think your RAM is bad, although the fact that they are TridentZ RGB sticks leaves me to believe that bad memory is not the case. Try applying the RAM's XMP profile; run them at their rated speeds and timings. 

[Novabutter]

43 minutes ago, Tsuki said:

Im getting bad ram, or bad drivers, or even corrupt OS

 

honestly, i'd first try reinstalling the OS first. unless you can swap the ram out

I'm thinking I'll try reinstalling the OS this weekend as a first attempt. Corrupt OS or bad drivers would be fixed by reinstalling. If it's bad RAM, G.Skill is going to hate me.

[Novabutter]

41 minutes ago, nelsonpong said:

From past experience, when I have Aw, Snap! errors on Chrome, it was caused by a bad RAM overclock. Bad RAM overclock means unstable memory, so I think your RAM is bad, although the fact that they are TridentZ RGB sticks leaves me to believe that bad memory is not the case. Try applying the RAM's XMP profile; run them at their rated speeds and timings. 

I'm running the RAM at stock speeds. When I did put them up to ratings (3000 Mhz max cause of my slower kit), my BIOS always told me originally that the boot failed. When I selected what drive to boot from in BIOS after that, I had no problems [booting. I still had BSODs.]

This week, I added that 3200 Mhz kit to the system, and I just left the speeds on the RAM at 2133 Mhz. Passed BIOS's test, and went to the system. That's where I got the first 2 above BSODs. Thing is, I'm not even overclocking my RAM. Ryzen is known for corrupting G.Skill's "Intel" sticks, especially the RGB ones. 

 

And right? If these TridentZ RGB sticks are the issue, G.Skill would hate me, but I don't think it is, because I RMA'd my Corsair RGB RAM originally and swapped it out for G.Skill. The BSODs followed still (although they may not be from the same issues, but probably). 

 

With all this said, I'm pretty sure it has something to do with memory or the OS.

[RyeIII]

3 hours ago, Novabutter said:

 

I have this issues also, running a ryzen 6 1600 all in stock, most of the time Im getting 'Memory_management' BSOD