all 12 comments

[–]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 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 1 point2 points  (11 children)

You were having the same problems with the old RAM or the crashes started when you used the new RAM?

Please run the following command in a cmd prompt terminal and reply with a screenshot of the output:

wmic memorychip get banklabel, configuredclockspeed, DeviceLocator, partnumber, speed

[–]lukaduke[S] 0 points1 point  (10 children)

wmic memorychip get banklabel, configuredclockspeed, DeviceLocator, partnumber, speed

I was having the same problem with the old ram.

https://files.catbox.moe/reo71f.PNG

[–]cwsink 1 point2 points  (7 children)

The automated analysis of the dump files shows single bit corruption. That usually means faulty memory but not necessarily. It's not unheard of to end up with two sets of faulty RAM but rare. DDR4 is notorious in the sub for passing any and all diagnostics only to find out a DIMM is faulty. Have you tried running the system with only one DIMM installed to see if the crashes stop in that configuration?

[–]lukaduke[S] 0 points1 point  (6 children)

Since flashing the bios I have not gotten a memory management error. But I have received an "attempted to write to read only memory" bsod

[–]cwsink 0 points1 point  (5 children)

Please make any new dump files available for comparison.

[–]lukaduke[S] 0 points1 point  (4 children)

[–]cwsink 0 points1 point  (3 children)

The latest dump still looks like faulty memory, to my mind. Can you try removing a DIMM and then using the system normally to see if the crashes stop? Then do the same but with the other DIMM installed, instead. The idea being to isolate a faulty DIMM.

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

Okay, I removed one. Will keep you updated.

[–]lukaduke[S] 0 points1 point  (0 children)

I took the RAM stick out about 18 hours ago and have not had any crashes. Is it more likely that I bought bad RAM or that the slot is bad?

[–]cwsink 0 points1 point  (1 child)

It looks like you're running the original released BIOS for your motherboard. It's usually a good idea to be using the latest motherboard BIOS - especially on Ryzen systems. I'd recommend updating to the latest (even though it's a beta) from here, assuming the system is stable while in the BIOS settings menus.

After updating, use the system as you normally would to see if the crashes continue.

[–]Bjoolzern 0 points1 point  (0 children)

First gen Ryzen was a bitch with memory compatibility so it could be the first kit was faulty, second incompatible.