Weird Game Crashes and Bluescreen Errors

[jaketyler1]

Hi everyone, I was not sure what the best category to post this under was, so I chose a broad one. 

Today, for the first time that can remember my computer started crashing after a few minutes while playing games. My specs are a Gigabyte Aorus Pro Wifi, Ryzen 7 3700x (overclocked to 4.2), RTX 2070 Super (+100 on clock speed, +500 on memory speed), 16 gb memory (running at 3566, XMP enabled), ssd os drive, hdd for game storage. As I said, this has not been a problem before powering on today. This system has worked in this configuration for several days.

Throughout the day, I also got two bluescreen crashes in addition to game crashes. The first one said: Stop code: Attempted Write To Read Only Memory         What failed: portcls.sys. It was after this one rebooted that I went into the bios and noticed everything was back to stock format, including my saved overclocked profile. The other crash said: Kmode Exception Not Handled. From the research that I did, I found that these are both memory related, although I am not entirely sure what they really mean or how to fix them.

My games would run for 10-20 minutes perfectly fine, but then all of a sudden they would just freeze and crash. I reinstalled video drivers, and all of my temperatures are normal which I monitored after the first two crashes on HW Monitor. This would happen on easy games to run such as CS:GO and more difficult games to run such as GTA V.

If anyone has experienced similar things or has some knowledge that could help me out, I am open to anything and everything. Thanks!

[SansVarnic]

-= Topic moved to Troubleshooting =-

[TetraSky]

As always, whenever you want to troubleshoot random crashes, the first step you need to take is : GET RID OF ANY AND ALL OVERCLOCK. On the CPU and the GPU. (RAM can be at their proper setting, but not over)

 

Even if it was "stable" for the longest of time, the simple fact that it is crashing now means that it isn't stable. Don't be like all those other people who say "well it's been stable for x days/weeks/months! It can't be that!". Just do it.

 

Once you've gotten rid of the overclock, see if the issue persist within the time frame you've already determined while gaming. (10~20 minutes)

If it doesn't crash, it means your OC was NOT stable and you'll need to tweak the settings. Have fun finding new settings that will not crash. (Be sure to test it properly, playing a game is NOT the proper way of testing an OC. You're better off using Prime95 Small FFT and Furmark. Or even Cinebench... Or some of the many 3DMark benchmark/stress tests)

 

-If it does still crash, well that's great! Because we've at least ticked one box on the troubleshooting list.
Next, since it's likely a memory issue as mentioned, do run memtest for at least 12 to 24 hours (run it overnight if you want as little "down time" as possible). Usually if there's a memory issue, it will appear within the first few hours.

Now, even if memtest comes out clean, I would personally suggest also running Prime95 on BLEND for an hour or two, this will test the memory and is often quicker at finding memory faults. As a bonus, it tests the CPU as well. (In my experience, memory issues are found within 10 to 30 minutes, but it can vary. If after 6 hours there's still nothing, it likely is fine)

 

-If the RAM comes out clean, next step is the GPU. Run Furmark/Kombustor for an hour or two. Yes, temps be high. Yes, you should probably leave your side panel open during this time to give it as much cool air as possible.

 

If everything comes out working and you're still having issues. Come back for more.

As a bonus, you can check if there's a BIOS update for your motherboard. AMD updated the AGESA to 1.0.0.6 earlier this month, so it's possible you got an update pending.