TUF X570 Gaming unstable using DOCP profile.

[Superfly1611]

Hello,

I built a new PC a couple of weeks ago.
Important bits:

• Motherboard: TUF Gaming X570 Plus WI-FI
  
• CPU: Ryzen 3900X
  
• Memory: G.Skill Trident Z Neo RGB DDR4 @3600Mhz (2x16GB)
  

When I first got it up and running I noticed the memory was running much slower than expected (2133MHz).
I enabled the default D.O.C.P profile which boosted the clock speed up-to 3600MHz which has worked fine for almost 2 weeks.

Problem
Today I attempted to turn on the PC and it failed to post and the yellow QLED light was on.
After rebooting several times achieved nothing I checked the manual which suggested the light was a DIMM problem.

I have tried taking out the memory and replacing individually one at a time, no luck.
I then tried resetting the CMOS to defaults (via CLRTC).

This worked, the PC booted back up but (as would be expected) the memory was now running back at 2133MHz.

There are several QVLs listed for my motherboard:

• Memory_QVL_3rd_Gen_AMD_Ryzen_Processors_X570
  
• TUF_GAMING_X570-PLUS_WIFI_Device_QVL
  
• Another aimed at 2nd Gen Ryzen Processors which I presume I can ignore

My DIMMS (F4-3600C16D-32GTZNC) do appear in the first list and their DOCP profile does appear to mirror the recommended settings.
However they do not the second. Would this be the problem?

[patrick_revell]

I ended up ordering some different memory to try. And sure enough. It's a world of difference. I've got stable overclock and memory timing tuned with DRAM Calc.

This is the memory I got, made sure it was on the QVL this time:
OLOy DDR4 RAM 32GB (2x16GB) 3600 MHz CL18 1.35V 288-Pin Desktop Gaming UDIMM (MD4U1636181CHKDA)

[devilarms2099]

Superfly1611 wrote:
Hello,

I built a new PC a couple of weeks ago.
Important bits:

• Motherboard: TUF Gaming X570 Plus WI-FI
  
• CPU: Ryzen 3900X
  
• Memory: G.Skill Trident Z Neo RGB DDR4 @3600Mhz (2x16GB)
  

When I first got it up and running I noticed the memory was running much slower than expected (2133MHz).
I enabled the default D.O.C.P profile which boosted the clock speed up-to 3600MHz which has worked fine for almost 2 weeks.

Problem
Today I attempted to turn on the PC and it failed to post and the yellow QLED light was on.
After rebooting several times achieved nothing I checked the manual which suggested the light was a DIMM problem.

I have tried taking out the memory and replacing individually one at a time, no luck.
I then tried resetting the CMOS to defaults (via CLRTC).

This worked, the PC booted back up but (as would be expected) the memory was now running back at 2133MHz.

There are several QVLs listed for my motherboard:

• Memory_QVL_3rd_Gen_AMD_Ryzen_Processors_X570
  
• TUF_GAMING_X570-PLUS_WIFI_Device_QVL
  
• Another aimed at 2nd Gen Ryzen Processors which I presume I can ignore

My DIMMS (F4-3600C16D-32GTZNC) do appear in the first list and their DOCP profile does appear to mirror the recommended settings.
However they do not the second. Would this be the problem?

Hey Man I just got mine to boot today running at 3200MHZ try putting the ram in slots A1 and A2. I know that's not what the manual says but for some reason it worked.

[RedSector73]

devilarms2099 wrote:
Hey Man I just got mine to boot today running at 3200MHZ try putting the ram in slots A1 and A2. I know that's not what the manual says but for some reason it worked.

That is not really a fix, what you have is single channel 3200DDR4x2 sticks working. Instead, dual channel 3200DDR4x2 sticks working.
That is around 20% or more performance hit on whatever you paid for your ram. I would be taking the RAM back rather than accepting that as a fix.

[PerfectImbecile]

I had this EXACT same problem with G.Skill Ripjaws 3600Mhz DDR4 on the same motherboard.

This was frustrating as hell, but I seem to have fixed the problem with a suggestion I found on another forum:

Change VDDCR SOC Voltage to offset mode, +.

Why we need to be fixing Asus bios problems for them is beyond me.

[2loki4u]

PerfectImbecile wrote:
I had this EXACT same problem with G.Skill Ripjaws 3600Mhz DDR4 on the same motherboard.

This was frustrating as hell, but I seem to have fixed the problem with a suggestion I found on another forum:

Change VDDCR SOC Voltage to offset mode, +.

Why we need to be fixing Asus bios problems for them is beyond me.

I'm going to give this a try now - I ran in to this problem after seeing benchmarks showing my g.skill trident z rgb 3200 (2x16gb) set in a1 & b1 slots - was severely under-performing - I read and saw a vid on youtube that talked about using the DOCP profile and this was a safe change (without overclocking or messing with any other settings) -

After booting and running "user benchmark" analysis - everything looked like it was on par with the majority of similarly configured machines - major improvement - but when I went and tried OCCT benchmark tool - it threw errors like crazy - upon a reboot I started getting all sorts of issues with files and such crashing at the windows 10 login page - couldn't even login - had to turn off DOCP and go back in then run a full scandisk at boot (using cmd command) - scandisk found a sh*t ton of errors on the drive (running a super fast mvne 1tb ssd) took nearly 20min to repair and I only have about 400g on the drive...

Not sure if anyone else found any solutions - or had any different luck - LMK please!!! I'll followup after some testing...

btw - i'm running the 570 w/ryzen 7 3700 (stock boost enabled as i found stock it runs better than at fixed overclock values) - powered by an evga gold strd 600w psu & a rog strix 5600xt (switching to 5700 strix tomorrow i think as one of the fans died after install and sounds like a playing card stuck in the spokes of a bicylce)

[ragp13]

PerfectImbecile wrote:
I had this EXACT same problem with G.Skill Ripjaws 3600Mhz DDR4 on the same motherboard.

This was frustrating as hell, but I seem to have fixed the problem with a suggestion I found on another forum:

Change VDDCR SOC Voltage to offset mode, +.

Why we need to be fixing Asus bios problems for them is beyond me.

Set it to +. by how much? I thought you had to enter a value for how much you want to offset it. Or is this some kind of bug where you don’t have to enter a number?

[ManVinGo]

HI,

I struggled with the same issue for quite some time. The following solved it for me:

1) RAM Sticks in A2, B2 slots
2) BIOS update to latest v 2802
3) SOC Voltage: offset, +, Auto

I enabled the DOCP after running in base 2133 MHz mode for two days.

RAM GSkill Ripjaws V F4-3600C16D-32GVKC

Hope this info helps someone solve his issue.

Cheers

[christizzz]

ManVinGo wrote:
HI,

I struggled with the same issue for quite some time. The following solved it for me:

1) RAM Sticks in A2, B2 slots
2) BIOS update to latest v 2802
3) SOC Voltage: offset, +, Auto

I enabled the DOCP after running in base 2133 MHz mode for two days.

RAM GSkill Ripjaws V F4-3600C16D-32GVKC

Hope this info helps someone solve his issue.

Cheers

can you take a picture of the "SOC VOLTAGE" setting in the bios how it is supposed to be ? i dont understand what you mean with : offset, +, Auto

[PepoX]

I had the same problems like two weeks ago, but apparently it was finally fixed with the last bios update, all I did was update the bios, activate the docp profile, and that's it, hope it works for everyone.

[davirock80]

PepoX wrote:
I had the same problems like two weeks ago, but apparently it was finally fixed with the last bios update, all I did was update the bios, activate the docp profile, and that's it, hope it works for everyone.

I have a Crosshair VIII impact and bios 3003 did not solve the problem...

But IT SEEMS I SOLVED FOLLOWING A SUGGEST BY A GUY FROM ANOTHER FORUM. He was using this with other DRAM and with a Threadripper...

--> I set AddrCmdDrvStern at 30 Ohm (default set was Auto)

Since 3 days my computer (Ryzen 3900 Pro, Crosshair VIII Impact, F4-3600C16D-32GTZNC in DOCP) is posting all the times I switch it on.

Davide