x570D.O.C.P issue with Asus Tuf X570 Gaming Plus Wi-Fi
x570D.O.C.P issue with Asus Tuf X570 Gaming Plus Wi-Fi
However, it adjusts those parameters automatically when I change from Auto to DOCP (appreciate the details). I'll give it a shot. Thanks once more.
I successfully increased the clock speed to 3200Mhz with a cas latency of 16-16-17-18-38. The key was turning off the PC and clearing CMOS after saving and restarting. It seems the motherboard won't boot after applying the settings in BIOS and then restarting. I plan to try 3600Mhz this weekend.
You're facing the same issue. The Asus Tuf X570 WiFi isn't compatible with your 3600 GSKILL Trident. Let me know if you'd like help finding a solution. Time to reset CMOS and rest.
Did you ever figure this out? I'm facing the same problem with RipJaw 3600 too.
Many motherboards recommend using slots A2 and B2 for a 2 stick setup. I've noticed people often fix their RAM issues by selecting the right slots. Also, keeping BIOS updated is important. @LittleCarlito @Anestis
I managed to fix the issue. By adjusting the BIOS DCOP settings for my RAM, I found that setting SOC to offset '+' on 'auto' helps maintain stability. Looking back, my Rip Jaw F4-3600C16D-16GVK isn’t listed in the Asus X570 tuf wifi QVL, which suggests it might not have been included. However, Rip Jaws do have the motherboard in their QVL. My other RAM, F4-3600C16D-16GVKC, shows up on the QVL and costs $50 less—planning to test it tomorrow.
I'm a hardware designer who verified on the ASUS TUF x570-Gaming WiFi board that Trident Z Neo 3600Mhz RAM won't operate at 3600Mhz until CPU overclocking is activated. Once enabled, it functions properly with DOCP. I haven’t needed to ask for details—I’ve assembled three similar setups and found that enabling CPU overclocking unlocks DOCP functionality even without prior setup.
Hi, your issue seems related to the system not responding to frequency changes despite using DOCP. Check if the settings are correctly applied and ensure the CPU is properly recognized. Overclocking can be tricky—some systems auto-activate it without you knowing. Try adjusting BIOS parameters carefully or consult the manual for guidance.