BSOD persists once DOCP is activated
BSOD persists once DOCP is activated
Hello! I previously shared how I purchased a R9 7900X with Corsair Vengeance 2x16GB 5600MHz RAM and an Asus Prime Pro-P X670, but kept receiving BSODs even after Windows installation. I submitted the issue to RMA, which confirmed it was a hardware problem and issued a refund. After getting my money back, I bought a TUF Gaming X670E from Asus, set it up, and everything worked smoothly. I performed multiple reboots and ensured no blue screens occurred. Once satisfied, I enabled DOCP in BIOS but still faced BSODs. I decided against using DOCP and disabled it instead. I’m unsure what caused the issue and would appreciate any advice. Thanks!
The complete schedule is listed on the package. The CL latency comes first, followed by a more flexible timing. The Ryzen 7000 series could struggle with tighter and looser settings, similar to what you experienced with a friend's 7800x3D CL30 6000 kit that had very precise timings. Generally, your CPU may prefer certain DIMMs, so try swapping RAM modules to check if the other controller accepts the new stick. Each module has its own controller on the CPU’s I/O die, meaning swapping affects which one is used for each memory.
I've experimented with swapping the stick and dims on the old motherboard, but blue screens persisted. It might be worth trying again. Also, the RAM I purchased is listed as supported on the MB page for my previous model—blue screens still occur. Would you consider replacing the RAM? The timings are 36-36-36-76, and the chipset is CMK32GX5M2B5600C36. I've swapped the sticks and the system no longer crashes. Still unsure about enabling DOCP; it feels risky. Also, why am I only seeing DOCP? Shouldn't I have EXPO? I'm using the newest components.
In another update: I still experience blue screens. I'm testing various RAM setups to find a stable configuration.
Same issue as before—PC fails to boot when RAM is in A slots (orange light), but works with B slots and then crashes. I've tried all single and double configurations, each resulting in different errors. These issues were mentioned in my earlier post.
Edit: July 3, 2023 – Updated by kriptcs