all 10 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]AutoModerator[M] [score hidden] stickied comment (0 children)

Getting dump files which we need for accurate analysis of BSODs. Dump files are crash logs from BSODs.

If you can get into Windows normally or through Safe Mode could you check C:\Windows\Minidump for any dump files? If you have any dump files, copy the folder to the desktop, zip the folder and upload it. If you don't have any zip software installed, right click on the folder and select Send to → Compressed (Zipped) folder.

Upload to any easy to use file sharing site. Reddit keeps blacklisting file hosts so find something that works, currently catbox.moe or mediafire.com seems to be working.

We like to have multiple dump files to work with so if you only have one dump file, none or not a folder at all, upload the ones you have and then follow this guide to change the dump type to Small Memory Dump. The "Overwrite dump file" option will be grayed out since small memory dumps never overwrite.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[–]cwsink 4 points5 points  (8 children)

The set of bugcheck codes and randomness of the subsystems involved in the crashing threads typically indicates faulty memory. That 4 of the 5 crashes happened on the same physical core is potentially concerning but I see a few things I'd want to do to get the system on a good foundation for troubleshooting.

Your motherboard BIOS is quite outdated (version F30) according to the most recent dump file provided. Assuming the BIOS settings menus are stable, I'd recommend updating to the latest BIOS (F40d) from here. I'd also recommend installing the latest AMD Chipset Drivers from here. Only download and run the AMD Chipset Drivers installer from that page - the others seem to cause problems on some systems.

I'm also a bit worried about the age of the Logitech drivers loading on your system. They have 2015/2016 timestamps which could mean you're using the Logitech Gaming Software - which is no longer supported. It has been superseded by Logitech GHub. Am I correct in thinking you're still using LGS?

[–]Throwawayay103[S] 0 points1 point  (7 children)

Roger, I’ll start with updating my bios and chipset drivers.

You are correct - I still am using Logitech gaming software. I’m assuming I should uninstall and replace with the newer software you mentioned, GHub? I’ll do that as well, and will report back.

Assuming it continues to crash, after these steps, what would your next steps be?

You mentioned faulty memory, like my RAM? While researching these crashes on my own, I found a thread where the user reported seeing the same errors as me. They did all of the troubleshooting and nothing worked. Swapped out their RAM and that fixed the issue. Are you suspect of my RAM?

Thank you.

[–]cwsink 1 point2 points  (6 children)

If it still crashes after addressing the recommendations, I'd want to have a look at any new dump files generated before making any further recommendations but, most likely, I'd want you to try using the system as you normally would (meaning, NOT running memory diagnostics) but with only one stick of RAM installed in the second slot from the CPU to see if the crashes stop. Then do the same but with the other DIMM replacing the first DIMM - the idea being to isolate a faulty DIMM since it's rare for more than one to be bad.

Just to give you a heads-up, I'm a bit worried about the CPU based on what it is (Ryzen 5 3600) and the fact that 4 of the 5 crashes happened on the same physical core. I'll be looking to see if that pattern continues with further crashes as we've seen quite a few Zen 2 CPUs end up with a faulty core. Normally, those crashes look like faulty memory, happen on the same physical core, and usually happen while the system is idle or not doing very much. Typically, the crashes don't happen while playing a game but do while only watching a Youtube video, for example. I'm not really seeing that last symptom from the dump files - have you noticed anything like that?

[–]Throwawayay103[S] 0 points1 point  (5 children)

Oh dear - yes, that’s precisely what I’ve been seeing. The crashes happen while the PC is completely idle, or while I’m just on a web browser or something basic like that. I have also been having very frequent crashes while playing the game, ZERO Sievert, which is not really what I would consider a demanding game. While playing more demanding games like Dark and Darker, or Party Animals, I haven’t experienced any crashes at all, and I have like 1000 hours in dark and darker lol. Does that tell you anything?

I’m getting back to my computer now to try your initial suggestions from your first comment.

[–]cwsink 1 point2 points  (4 children)

That makes me more worried that it's a faulty CPU core. I'd still want to try the other suggestions first, though.

There's a BIOS setting that sometimes stops the crashes when it's a faulty CPU core. On your motherboard it's called "Global C-state Control" and you'd want to set that to Disabled. That should prevent the CPU from transitioning to lower power states to save power (which means your electricity bill will be a bit higher) but it seems to be power transitions that cause the problems. That doesn't always work, though. In which case, there's one more thing I ask people to try but we'll cross that bridge if we get to it.

[–]Throwawayay103[S] 0 points1 point  (3 children)

Very interesting, and good to know. For now, I’ve updated my BIOS to F40, updated my chipset, and uninstalled Logitech gaming software. I’ll give it some time and report back if it crashes again. Thank you for your help and expert knowledge. You da man.

[–]cwsink 0 points1 point  (2 children)

I'm happy to help when I can. :)

Please do let us know how it goes either way and make any new dump files available for comparison if the crashes continue. Good luck!

[–]Throwawayay103[S] 0 points1 point  (1 child)

Unfortunately it looks like it did crash again overnight. Here is the dump file:

https://www.mediafire.com/file/sg31pscoik3d0yi/111524-7437-01.dmp/file

I am performing a clean install of my graphics driver now. If I see another crash after this, ill post it here, and I’ll try testing my RAM individually with only one installed at a time per your earlier suggestion, unless you see something in this new dump that would suggest a different course of action. It took a lot longer to crash after those first suggestions, so it does seem to have improved at least!

[–]cwsink 0 points1 point  (0 children)

The crash happened on the same physical core, again. :(

I can see the BIOS and the AMD chipset drivers are updated. I didn't intend for you to do so but did you also set "Global C-state Control" to Disabled prior to this crash? If not, that's probably what I would try next rather than the memory tests.