Pc won’t boot with docp enabled

Dec 4, 2018
3
0
10
Whenever I enable docp the pc either boot loops, freezes or crashes.

MOBO: Asus Prime b450 plus
CPU: Ryzen 2700x
Ram: g skill trident z 2400mhz
 
Solution
How many modules do you have installed? Are they installed in the A2 and B2 slots, which are the 2nd and 4th slots over from the CPU socket?

If they are NOT in those slots, they need to be. Also, as Lutfij has already indicated, make sure you are on the latest bios version for your motherboard before even bothering with trying to get DOCP enabled.

Also, after you make sure they are in the right slots and that you are on the latest bios version, try using only one module in the A2 slot with DOCP enabled. If it WILL run that way, then try bumping the DRAM voltage up minimally and then save settings, shut down, install the other stick and try to see if it will boot again.
How many modules do you have installed? Are they installed in the A2 and B2 slots, which are the 2nd and 4th slots over from the CPU socket?

If they are NOT in those slots, they need to be. Also, as Lutfij has already indicated, make sure you are on the latest bios version for your motherboard before even bothering with trying to get DOCP enabled.

Also, after you make sure they are in the right slots and that you are on the latest bios version, try using only one module in the A2 slot with DOCP enabled. If it WILL run that way, then try bumping the DRAM voltage up minimally and then save settings, shut down, install the other stick and try to see if it will boot again.
 
Solution


It’s updated, I tried setting them manually and it failed
 


it boots with 1 stick, boots with 2 if I set the dram to 1.35v
 
It should be at 1.35v anyhow, for DDR4 at speeds higher than 2133mhz. At least in most cases. There is no harm in leaving the memory at 1.35v if it works normally with that voltage, but I would STILL test the memory configuration using Memtest86 to be sure it is stable. Unstable memory configurations are no joke. They will quickly corrupt your file system and data and there is no way to "fix" it once it is corrupted. Make sure the configuration is stable ANYTIME you are running memory beyond the default JEDEC SPD configuration whether it is there by way of a manual configuration OR XMP/AMP/DOCP settings. They are STILL a form of overclock, even if the manufacturer has specified them to be mostly stable at that configuration.

They obviously do not test them on every platform, in every conceivable configuration. That is up to the user to do and it is highly recommended to do so. You would be surprised how many systems I have seen that were not stable at the XMP profile and needed either some minor tuning to the primary timings or a slight bump in voltage to eliminate errors even though they were at the exact settings specified in the XMP profile.

Most people don't even realize this, or even suspect it, because they never bother to check and simply assume that the XMP profile WILL be stable because that is what they advertise for those modules. Then down the road when problems develop they want to blame it on something else such as a corrupt Windows update, virus, malware, bad drive, etc., when in fact the corruption is due to incremental micro errors that have degraded the OS and probably also many of their files.

*Resolving memory problems and setting up XMP/DOCP/AMP profiles