The BSOD might have been due to RAM issues.
The BSOD might have been due to RAM issues.
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-rf7...sp=sharing
Minidump after turning off Hyper-V:
https://drive.google.com/file/d/1mxWVapa...sp=sharing
And I am not sure It is related to RAM.
OCCT screenshot:
https://imgur.com/a/TXClXrT
View: https://imgur.com/a/TXClXrT
The initial observation is that the RAM configuration doesn’t match. There are two sets of KHX3200C16D4/8GX sticks in slots A1 and B1, and another pair in slots A2 and B2. Although they appear similar, mixing different RAM types is generally not recommended. The two pairs have varying CL timings, which explains the differences. It’s standard practice to purchase RAM in matched sets so internal timing remains consistent.
When BSODs occur that might be linked to faulty or mismatched RAM, it’s important to address the issue with the first pair—likely the ones in A1 and B1, as most boards prefer two sticks in A2 and B2. If the problem persists after replacing one matched pair, download and use the SysnativeBSODCollectionApp, then upload the generated zip file to a cloud service with a link. This tool aggregates troubleshooting information and does not store personal data. It’s widely trusted by reputable Windows forums, including this one. I’m a senior BSOD analyst on the Sysnative forum, so I can confirm its reliability.
Feel free to review the contents of the zip file before uploading, though avoid modifying or removing any files. For details on each file, refer to the provided link.