It's finally here Just waiting for one final OS drive clone to finish, then it's teardown (and rebuild!) time!
Damn nice cpu oc at that voltage. Impressive.So, I started tinkering with my build a bit more. I'm running a 1600X on an MSI B350M Gaming Pro, and have successfully got my cpu running at 4 GHz @ 1.3v with LLC @ mode4. G.skill Ripjaws V are at DDR4-3200 with timings at 14-14-14-34 @ 1.35v with 1T command rate. It's Prime95 stable so far!
I do still have plans to get a 1700, or 1700X, and a Taichi at some point though. Or I might just keep this and wait for Vega.
So far so good though!
Nice. It does exist. Let us know the results.It's finally here Just waiting for one final OS drive clone to finish, then it's teardown (and rebuild!) time!
Damn nice cpu oc at that voltage. Impressive.
Now just leave it and dont thinker with it any more.....
Except perhaps 3466 c14 with new bios....
And...
What is Aida reporting of latency for the ram at 3600?AGESA 1.0.0.6 continues to bring interesting surprises.
After wasting a lot of time trying to get DDR4-3600 stable (not happening yet; I can get it to run almost everything except y-cruncher), I went back to the drawing board and decided to see what kind of subtimings AMD gave me using Ryzen Master to set DDR4-3200 14-14-14-32 (actually I went for 28 this time) as I had in the past. I went through my old routine, booted it up, confirmed that it was working, and then took a look in the UEFI to see what was going on.
Curiously the UEFI was showing the current timings/subtimings that had been set by Ryzen Master, but it was showing the DIMM's XMP settings as what was currently set in the UEFI. For example, it showed CAS/CL as 14 but the config field was set to 17. Booting into Windows asserted the Ryzen Master settings provided I changed nothing in the UEFI. Changing settings in the UEFI apparently "cancelled out" whatever Ryzen Master was trying to do. It did not overwrite settings changed by hand.
I can go back and record all those settings and post them here if you want to see exactly what Ryzen Master and the older pre-1.0.0.6 AGESA revisions were doing when setting the DDR4-3200 strap.
So anyway, I got 3200 stable (preditably) without changing anything. Using 1.4v vDIMM and 1.175v SoC voltage (LLC level 3) I got DDR4-3333 working with the exact same timings as what Ryzen Master set for DDR4-3200 14-14-14-28. Cool! AIDA64 reports ~52.8 GB/s read and 69.2 ns latency. Then I ran Firestrike to compare it to my Firestrike score from when I was running DDR4-3600 18-19-19-36 (1T and 2T; it made no difference at all).
The main thing that jumped out at me was the combined score. When running DDR4-3600, I only had the CPU at 3.6 GHz, and I got a combined score of over 5200 using a stock Powercolor 390. When running the CPU at 4 GHz with RAM at DDR4-3333 14-14-14-28, I got a combined score of ~4900 with the same Powercolor 390.
It seems to me that fabric speed is a major limiter of combined score performance in Firestrike.
What is Aida reporting of latency for the ram at 3600?
Will do. Good thing I have flexible work, that means I can spend most of tomorrow setting this up (including the custom water loop). Kind of funny when the last component you're missing for a PC build is a funnel I just hope very very much that I can fit the rad in the top of my Fractal R4. I won't be able to replace the case for a while yet (did anyone mention that custom loop water cooling is really expensive?), so I'll have to run it in there for a few months, no matter how silly it will look. I just want to avoid using the rad as an intake if at all possible.Nice. It does exist. Let us know the results.
There is also the possibility that your stick has been SPD corrupted by either Asus Aura or Gskill's LED software rather than the stick being completely dead/bad:
http://www.overclock.net/t/1624603/rog-crosshair-vi-overclocking-thread/17660_20#post_26125524
If this is the case, a complete uninstall and scrubbing of Aura and/or Gskills LED app from your machine THEN using Thaiphoon Burner to re-write the SPD of the RAM stick in question may help avoid the potential RMA difficulties.
But mine is not RGB and I didn't install Aura SW.
Checking the stick with Thaiphoon Burner wouldn't hurt. There might be something wrong that can be reprogrammed.
Does that board support hot-pluggable RAM? Just thinking outside the box. There was, back in the day, a way to "hotflash" corrupted BIOSes. I think I might have even had to do it once.I am unable to boot to Windows with the bad stick inserted.
@ bauerbrazil2014
It could be static damage to that stick , maybe you could review static precautions before replacement.
Does that board support hot-pluggable RAM? Just thinking outside the box. There was, back in the day, a way to "hotflash" corrupted BIOSes. I think I might have even had to do it once.
I am unable to boot to Windows with the bad stick inserted.
May the motherboard apply excessive voltage when training?
Guys, I used to know a lot about HW like 15 years ago, but my last build was in 2009, so I am not aware of current stuff.
Is it possible that the RAM is in some weird state caused by the motherboard training the RAM? Is it possible that an updated BIOS could fix this if this is the case?
May the motherboard apply excessive voltage when training?
I remembered I was trying to set a RAID array and never touched the RAM settings, everything was on "Auto", so it had a lot of boot cycling and training.