For those having issues getting DOCP to work at all on Gskill neo, make sure your ram is installed in the A2 and B2 slots... if you have them in A1 and B1 slots it won't work past stock speeds. On a few other forums I saw people with the same problem with the neo kits not booting at all with DOCP enabled and come to find out, they where using the wrong ram slots.
But I have an odd quirk and kinda at a lost if I should be concerned about it or not. There seems to be about a 30% chance of my kit, F4-3600C16D-32GTZNC (on Asus and Gskill QVL for the Tuf), to halt at reboot. My Tuf has its DRAM LED light on and it just halts there until I hold down my power button. I never got to try any other bios below 1403 as the first thing I did when I got the board was flash 1403. Then 1404 when it came out and finally now 1405. All three bios versions have this issue.
The odd thing about it is that, so far, been exclusive to rebooting. Not shutdown and powering back on and not from a cold boot after pulling out the power cord. But just from rebooting. And when it happens, once I hold down my power button to shutdown, and boot it back up, it boots just fine. No issues when gaming long sessions, did prime95 well when I did my initial benchmark stuff, etc. I've tried clearing cmos, reflashing my bios, manually setting FCLK to 1800 and SOC voltage to 1.1v (which is what Auto with DOCP enabled was defaulting to), etc.
I did see a guy on newegg for the Tuf complain about something that sounds very similar to what I have been enduring so it lends me to believe its a Asus bios issue. The guy was hinting at it being a DOCP issue. I am running it with DOCP. So today I decided to write down my timings that where being set with DOCP and manually set everything. But I ran into a two problems. The first problem is the very last timing to set in the bios, I forget its name, was post to be set to 0 (as 0 was the value DOCP was setting on auto) but when I put in 0, it changes it to 1. So some how auto sets it to 0 but manually I can't. The second problem was after setting all the timings, memory to 3600, FCLK to 1800, DRAM voltage to 1.35v's, and SoC voltage to 1.1v's, my computer can't post. It just halts 100% of the time on the DRAM led light. So I had to clear cmos to get back in. So either that very last timing is what's causing the manual setting to fail to post or DOCP is also enabling other stuff that I can't figure out what else. Even though everything else is on auto by default either with or without DOCP, I'm assuming DOCP changes what those auto settings default to.
So because of that it does have me a bit concerned that maybe those times where I fail to reboot are not due to an Asus bios bug, but maybe my ram or possibly motherboard isn't stable? I can't believe my 3800x would be at fault since it seems like ryzen's memory controller is solid up to 4ghz+ range. Since I still have a return window for both a refund and replacement I don't know if I should gamble it? What do you guys think? Anyone else with a similar problem? Do you think its just Asus or maybe bad ram / motherboard?
Its tcke value than if I put in 0, it sets it to 1 even though DOCP is able to set it to 0. I just checked with ryzen master. Forgot ryzen master can show timings. I also just ran a little of an hour of Ramtest from Karhusoftware that I found on OCN: [2019-12-17T03:16:30.8157191-07:00] Stopped testing after 0:01:07:38 with 1575 % coverage and 0 error(s).
So my kit at least passed Ramtest after 1575% of coverage.
ran Memtest Pro 7.0 for a little bit over an hour to hit a tad bit over 100% coverage and no errors. Ran it a few minutes after Ramtest.
So maybe its just Asus bios bug?
Last edited by orlfman; 12-17-2019 at 04:56 AM.