Having trouble finding the cause of random BSOD errors

[Popperonii]

Hey there,

I have been having trouble determining the root cause of these odd BSOD errors that I have been getting more often in the recent month. It primarily happens when playing games, but 9/10 times there is never an issue and once or twice it has crashed while my computer was in sleep mode which I didn't even know was possible. This all started happening when I upgraded my build from an Intel i7-8700k to an AMD Ryzen 9 5900X back at the end of July this year. My intel build ran solid, same RAM, same GPU, same everything except the Mobo and CPU. I've had a terrible impression on the AMD platform ever since. I first started noticing these odd intermittent stutters that lasted about 3 seconds, typically when playing a game or joining a voice chat, but sometimes they happened when just browsing the desktop. I did some research and found that it could be from faulty RAM modules. My RAM modules are somewhat old, 5 years and I had XMP enabled on them since I bought them. It worked great on my intel build. I dismissed the issue because it really didn't effect my work/playtime and just thought of it as an odd issue stemming from switching to Ryzen and not reinstalling windows and just doing /chkdsk to re-verify system integrity. Now these issues have escalated to BSOD errors, and I worry there is something more sinister at play with my system.

From what I've browsed, the people on this forum are very intelligent and I trust you guys can at least point me in the right direction on what to do next. I have built many systems over the years so I know my way around a PC, if I need to buy new RAM, that is fine. I was looking to upgrade soon anyway! What I fear, is that it's my GPU causing these issues. After all, I usually experience a crash when playing games. It's an Nvidia RTX 3080 Ti that I bought new in March of this year, but I haven't overclocked it. In fact, I underclocked the card to reduce heat, from my understanding, it's pretty hard to damage a card by giving it not enough voltage.

Here are my full system specifications:
Ryzen 9 5900X (July 2022)
NZXT N7 B550 Motherboard (July 2022)
Corsair Vengeance RGB Pro 32GB 3000MHz (4x8GB) (June 2017)
Nvidia RTX 3080 Ti FE (March 2022)
Corsair H150i Elite Capellix AIO (July 2022)
Samsung 970 Evo 500 GB M.2 (Boot Drive) (September 2020)
Corsair Force MP500 120GB M.2 (April 2017)
Samsung 870 Evo 500GB and 1TB SSD (2017-2018)
Toshiba X500 5TB HDD (October 2016)
Seagate 1TB HDD (January 2015)
Corsair RM850x Power Supply (July 2022)

I would say all of my temps are safe. My CPU doesn't pass 70c when gaming, and sits between 30-50 when doing anything but gaming. My GPU ramps to 83 and then lowers clocks, which I believe is stock, I've never messed with it. RAM modules are around 45 on the desktop and towards 50 when gaming.

I have also attached the Speccy .txt file for further details on my specifications, along with the Sysnative collection .zip.

I installed this Windows 10 Pro 64-bit OS myself probably about 2 years ago, and I have yet to re-install the OS, saving it as a last resort thing.
I believe driver verifier is disabled, I just disabled it. I never ran it myself, so the only time it would have ran is if windows did it automatically.
I am only using the Windows Defender Anti-virus
I am not using any VPN, proxy, etc.
I am not using and disk image tools
I do currently have a CPU overclock, a modest one set by Ryzen master at 5.05 Ghz. I did disable it a few weeks ago but it didn't change the BSOD errors so I re-enabled it. However, I will turn off the curve optimizer tonight because that maybe could be the issue as well.

I will also say that when crashes happen during games, a BSOD doesn't show up. It makes the screen look kind of wierd, most of it goes black, but some elements of the screen turn to red, blue or yellow, and then it restarts after (im assuming windows finishes it's memory dump). It is kind of hard to explain so I will attach an image. I have had a failing GPU before a 1080 Ti, but the computer never BSOD, it just locked until I restarted it with no BSOD dump following. But I suppose not all GPUs fail the same way.

That is about all the information I can think of. Hopefully, you guys can see a clear explanation as to what is going on. From my amateur BSOD analysis I am leaning towards RAM issues, but I don't know entirely what I am looking at. I pray that my GPU isn't to blame as I did buy it back in March for a somewhat fair price, but still overpaid as you can imagine, and would hate to buy a new one!

EDIT: Forgot to mention that I did use Memtest a few weeks ago, but it passed with 0 errors. However, I heard that Memtest isn't the best tool for Ryzen CPUs for some reason, unsure if thats true. I'll attach that as well.

 

[ngrid]

Blackscreen underload no BSOD system just reboots sounds like GPU issue given the context and you have various dumps in the event viewer and dxdiag output of the crashes. I know you said you never overclocked but as you have undervolted the card this automatically means possibility and grounds for an unstable system put it back to stock volt and test by playing games make sure you know what that is or at least make sure you know your voltage limits as you don't want to fry the card.

I didn't look extensively and someone else may be able to pin point further or offer some more insight.

 

[Popperonii]

Blackscreen underload no BSOD system just reboots sounds like GPU issue given the context and you have various dumps in the event viewer and dxdiag output of the crashes. I know you said you never overclocked but as you have undervolted the card this automatically means possibility and grounds for an unstable system put it back to stock volt and test by playing games make sure you know what that is or at least make sure you know your voltage limits as you don't want to fry the card.

I didn't look extensively and someone else may be able to pin point further or offer some more insight.

I should add that I did bring back stock speeds and it still crashes, even setting the power limit on GPU to 95 percent crashes. I did however take off my overclock on my CPU, so far so good, we will have to see what happens.
I have so many variables that make it a pain in the ass. I also gave the thought of my CableMod cables causing some issues, but CableMod staff has repeatedly told me that their cables should not be an issue on their end, and I believe them, as it was working fine until I switched to Ryzen.

 

[ngrid]

I initially skimmed over the part where you said you had a 5ghz OC as it was late here when i read this thread changes the whole dynamic Ryzen master does not really sound like a good idea either tbh if you OC your CPU it should be done in the bios/ufei no real enthuiset is going to go anyware near software to OC unless they have to or if its GPU OC of course. Otherwise those software solutions are targeted for people that don't really know what they are doing and are also a trojan horse of sorts. Ryzen Master is 100% your problem also being at 5ghz which is at the end of your headroom too then software OC is also something less savy ocers would go towards no insult intended but its a factor as most serious people won't be software oc.

Do it properly in the Bios and tone it down 1000mhz at least while you get it stable push it through various stress tests and then go up like a few hundred mhz test again then all the way up to 5ghz once you know for sure that its stable.

 

[ngrid]

5 ghz is also going to be best case scenario does not mean that everyone's CPU is going to make it there as its at the end of what people are running those cpu at. Top end clocks mean there is many factors involved for you to achive that sort of clock and not every CPU is going to run at top end either you need to determine this through testing. Top end also means less margin and high error there is all sorts of states and settings that you are probably not going to get in software master too idk never used it but its probably missing lots of good settings that you need access to when ocing which will only be accessed in the bios.