Overclock.net › Forums › AMD › AMD Motherboards › ROG Crosshair VI overclocking thread
New Posts  All Forums:Forum Nav:

ROG Crosshair VI overclocking thread - Page 1044

post #10431 of 17830


11hr30min of slightly looser timings wins
Quote:
Originally Posted by r4m0n View Post

I'm in a similar situation, though mine is getting errors quite a bit more than 1 per 8h. I'm trying messing with the VDDR and VSOC to see if it helps, while you try the timings. Just one thing, 1 error in 8h is a bit too low, with non-ECC memory we are all vulnerable to the eventual cosmic ray flipping a bit. It may be that you are stable already and just got unlucky.

You're probably right. I didn't heed the full instructions to close needless background applications before testing and thats probably why I got that error.
post #10432 of 17830
Quote:
Originally Posted by TwoBeers View Post

Not necessarily true, right now you can't change VID p0, as we already know, or it will leave you in a state between p0 and p1 the whole time.

But you can change the VID of p1 and p2, as long as you don't set too low. I would advise to not change p1 at all but for power saving purposes change the VID of p2 to something around 0.6V (including offset).
If you set your Vcore offset to +01V. for example, you can set the VID of p2 to 0.55V.

trust me, i tried changing the VID of my Pstate2 and I got locked at 2200mhz in windows until I reverted it. Of course you can aslo raise the speed of that pstate but you'd still be locked in it. Right now you can only use offset and unwantingly raise the voltages of your pstate1 and beyond in doing so until that gets fixed.

consequently, if you change the VID of pstate0 the pstate wont activate at all.
Edited by Reikoji - 4/20/17 at 4:57pm
post #10433 of 17830
Quote:
Originally Posted by dorbot View Post

Ok, Just flashed the 0003 bios, and after I had changed my trousers, had to clr cmos after getting stuck on 94 with the white LED..
Last time I saw this message was a bad day, lol.



Elmor wrote that this message will happen with 0003 because it is actually updating the EC. Nothing to worry. smile.gif
post #10434 of 17830
Quote:
Originally Posted by TwoBeers View Post

Elmor wrote that this message will happen with 0003 because it is actually updating the EC. Nothing to worry. smile.gif
yeah, I know. I just put the picture there for posterity and for those of us that have seen it before with a less than optimal conclusion..... I knew it was coming but I still crapped my pants ,lol.
I'm actually looking forward to turning this rig on tomorrow morning.

I suppose someone else will have to follow up on the hairdryer trick......
smile.gif
Edited by dorbot - 4/20/17 at 5:10pm
post #10435 of 17830
Quote:
Originally Posted by TwoBeers View Post

Elmor wrote that this message will happen with 0003 because it is actually updating the EC. Nothing to worry. smile.gif

So using this method there's no way to get my pstate over 99 for FID? Max clock of 3.825?

BEcause if I understand correct I screw up the speed stepping by changing the other values, correct?
post #10436 of 17830
Quote:
Originally Posted by alucardis666 View Post

So using this method there's no way to get my pstate over 99 for FID? Max clock of 3.825?

BEcause if I understand correct I screw up the speed stepping by changing the other values, correct?

after 99 its A0
post #10437 of 17830
Quote:
Originally Posted by Raja@ASUS View Post

Two of us have found that setting ProcODT to the correct value for the memory config solves a lot of POST issues. One just needs some patience to tune it.
Quote:
Originally Posted by Raja@ASUS View Post

With the way the platform is setup currently, getting 3200+ often requires a kit that is binned for a higher frequency. For me, getting DDR4-3200 stable with 32GB requires the use of a DDR4-3600 kit (Intel validated kit, not AMD). Also note, I'm using UEFI build 0079 for my results. And one last thing is that the SoC voltage can be sensitive, with higher values resulting in instability (same as when it's set too low).

Make that 3, though I'm on a 3200Mhz kit thumb.gif 0083 BIOS.

80ohm allows me to run my F4-3200C15D-32GTZKW at 3200Mhz with loose timings (18-14-14-14-34). One notch lower on ProcODT for 2933Mhz.

Ran HCI Memtest to 400% and boots every single time. Samsung E die if I'm not mistaken.
Quote:
Originally Posted by elmor View Post

The DRAM form has been quite useful, so I made another one for bug reports https://docs.google.com/forms/d/e/1FAIpQLSeWovVLyETJTI4-6r0h5SDzj8muLTjAGfoszKqZoySBOb684w/viewform

Would it be useful to restart the DRAM form with ProcODT settings? Different values enable different frequencies for me (currently at 3200 with 32GB dual-rank wink.gif)
post #10438 of 17830
Quote:
Originally Posted by Reikoji View Post


You're probably right. I didn't heed the full instructions to close needless background applications before testing and thats probably why I got that error.

Well, other pieces of software would have to actively be trying to interfere with the memory test to actually cause errors, so leaving other programs running isn't exactly a problem. It was either a random error or really some little instability left.

Just messing with voltages didn't solve the issues here, but I'm currently running clean after upping the VDDR to 1.425, lowering VSOC to 1.0 and relaxing the timings to 18-18-18-38. Haven't tried 18-17-17-38 with those voltages, maybe that will work as well, as you're managing to do 18-17-17-39.
    
CPUMotherboardGraphicsGraphics
AMD Ryzen 1800X Asus Crosshair IV Hero NVidia GTX 980 Ti NVidia GTX 660 
RAMCoolingCoolingCooling
G.SKILL 64GB (4 x 16GB) Ripjaws V Series DDR4 3... EK-Supremacy MX EK-FC980 GTX Ti WF3 EK-CoolStream XE 360 
KeyboardPowerCaseMouse
Corsair K90 EVGA Supernova 850 T2 Cooler Master - K280 Corsair M60 
  hide details  
Reply
    
CPUMotherboardGraphicsGraphics
AMD Ryzen 1800X Asus Crosshair IV Hero NVidia GTX 980 Ti NVidia GTX 660 
RAMCoolingCoolingCooling
G.SKILL 64GB (4 x 16GB) Ripjaws V Series DDR4 3... EK-Supremacy MX EK-FC980 GTX Ti WF3 EK-CoolStream XE 360 
KeyboardPowerCaseMouse
Corsair K90 EVGA Supernova 850 T2 Cooler Master - K280 Corsair M60 
  hide details  
Reply
post #10439 of 17830
Quote:
Originally Posted by Reikoji View Post

after 99 its A0

So this is correct? thumb.gif

post #10440 of 17830
Quote:
Originally Posted by Reikoji View Post

after 99 its A0
After 99 is 9A, after 9F is A0 :-)
    
CPUMotherboardGraphicsGraphics
AMD Ryzen 1800X Asus Crosshair IV Hero NVidia GTX 980 Ti NVidia GTX 660 
RAMCoolingCoolingCooling
G.SKILL 64GB (4 x 16GB) Ripjaws V Series DDR4 3... EK-Supremacy MX EK-FC980 GTX Ti WF3 EK-CoolStream XE 360 
KeyboardPowerCaseMouse
Corsair K90 EVGA Supernova 850 T2 Cooler Master - K280 Corsair M60 
  hide details  
Reply
    
CPUMotherboardGraphicsGraphics
AMD Ryzen 1800X Asus Crosshair IV Hero NVidia GTX 980 Ti NVidia GTX 660 
RAMCoolingCoolingCooling
G.SKILL 64GB (4 x 16GB) Ripjaws V Series DDR4 3... EK-Supremacy MX EK-FC980 GTX Ti WF3 EK-CoolStream XE 360 
KeyboardPowerCaseMouse
Corsair K90 EVGA Supernova 850 T2 Cooler Master - K280 Corsair M60 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: AMD Motherboards
Overclock.net › Forums › AMD › AMD Motherboards › ROG Crosshair VI overclocking thread