Question BSODs probably caused by RAM corruption ?

[vanyagetc]

Hey everyone, I'm sorry if I'm posting in the wrong forum, but I need your help.
I'm getting BSODs.

Minidumps before turning off Hyper-V:
https://drive.google.com/file/d/1H3l-rf7cUhR8BLHHb6Wsk5hcIVbO9td2/view?usp=sharing

Minidump after turning off Hyper-V:
https://drive.google.com/file/d/1mxWVapa8860OR-9Vy67rSQun0NLjy19K/view?usp=sharing

And I am not sure It is related to RAM.

OCCT screenshot:

https://imgur.com/a/TXClXrT

View: https://imgur.com/a/TXClXrT

 

[ubuysa]

Th first thing I notice from the dumps is that you're using mismatched RAM. You have two sticks of KHX3200C16D4/8GX in slots A1 and B1 and two sticks of KHX3000C15D4/8GX in slots A2 and B2. Whilst they look similar it is always unwise to mix RAM. You can see different CL timings on those two pairs for starters. That's why RAM is sold in packs of matched sticks, so that all the internal timings match.

Whenever we see BSODs that can be caused by bad RAM and we see mixed RAM then that's always the first thing to focus on. I suggest that in the first instance you remove on pair of RAM sticks, probably those in A1 and B1 (since most motherboards want two sticks in A2 and B2) and see whether these BSODs continue.

If you do still get BSODs with on one matched pair of RAM sticks installed then please download and run the SysnativeBSODCollectionApp and upload the resulting zip file to a cloud service with a link to it here. The SysnativeBSODCollectionApp collects all the troubleshooting data we're likely to need. It DOES NOT collect any personally identifying data. It's used by several highly respected Windows help forums (including this one). I'm a senior BSOD analyst on the Sysnative forum where this tool came from, so I know it to be safe.

You can of course look at what's in the zip file before you upload it, most of the files are txt files. Please don't change or delete anything though. If you want a description of what each file contains you'll find that here.