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

ROG Crosshair VI overclocking thread - Page 1149

post #11481 of 17579
Quote:
Originally Posted by majestynl View Post

Yes im using offset! But isn't that the same when setting Pstates in bios.? That's how i run my P0 states normally whens set in bios.
So if thats the case ZenStates inst working with offset modes? And by the way, still weird to get 1.6v

No, ZenStates sets the absolute voltage, so if you set 1.4v for P0 and have an offset of 0.2v in BIOS, you're getting 1.6v.

Just set ZenStates to the voltage you need for each state.
post #11482 of 17579
My memory modules were sentient - and spiteful!

My rig was restarting with a Windows Update, after which I would do a final shutdown before shipping the four sticks of DRAM back to wherever the final resting place for returned G.Skill is. I have been running a pretty conservative configuration, so restarts had not been an issue if nothing is changed.

Sure enough the restart failed, and I was caught in an interminable loop of boot attempts. Not sure how many tries it took but it was a lot.

I think those modules were hanging on the edge of insanity, and knowing they were about to be pulled and stuffed in a box pushed them over the edge. ohno-smiley.gif

I feel for them, I really do. So beautiful, so much potential, all tragically cut short by electroshock to the brain by nasty Aura behavior. Rest in Peace, G.Skill RGB modules, it was not your fault.
post #11483 of 17579
Quote:
Originally Posted by CeltPC View Post

My memory modules were sentient - and spiteful!

My rig was restarting with a Windows Update, after which I would do a final shutdown before shipping the four sticks of DRAM back to wherever the final resting place for returned G.Skill is. I have been running a pretty conservative configuration, so restarts had not been an issue if nothing is changed.

Sure enough the restart failed, and I was caught in an interminable loop of boot attempts. Not sure how many tries it took but it was a lot.

I think those modules were hanging on the edge of insanity, and knowing they were about to be pulled and stuffed in a box pushed them over the edge. ohno-smiley.gif

I feel for them, I really do. So beautiful, so much potential, all tragically cut short by electroshock to the brain by nasty Aura behavior. Rest in Peace, G.Skill RGB modules, it was not your fault.

I'm getting awfully close to putting this Ryzen build in a closet with a lock and key, and not let myself touch it anymore for a few months. Least enjoyable build I've ever had, and I started building over 15 years ago.
post #11484 of 17579
Quote:
Originally Posted by Bart View Post

G.Skill has a 3600 CL15 kit, which I assume is Sammy B's as well. Or so I hope since I bought it. Not cheap stuff though, especially with the ryze in DDR4 prices (paid $300CDN). If this cold boot issue ever gets fixed, I'll put it through it's paces. Messing with ram on this board now is maddening due to that issue.

Even I had Cold boot oc failed 2 days ago. First time in 3 weeks for no reason biggrin.gif But i can deal with that since i had 290x with black screen issue so my 2500k would not boot up EVERY SECOND TIME !!!
post #11485 of 17579
Quote:
Originally Posted by y0bailey View Post

I'm getting awfully close to putting this Ryzen build in a closet with a lock and key, and not let myself touch it anymore for a few months. Least enjoyable build I've ever had, and I started building over 15 years ago.

Quite opposite i like when stuff does not work and i get it runnign after hours and hours of messing about. But i got time to do so tongue.gif Since i flash stuff while doing weights and body weigh training at home next to pc biggrin.gif
post #11486 of 17579
Quote:
Originally Posted by lordzed83 View Post

Even I had Cold boot oc failed 2 days ago. First time in 3 weeks for no reason biggrin.gif But i can deal with that since i had 290x with black screen issue so my 2500k would not boot up EVERY SECOND TIME !!!
I get cold boot problems every single time with BIOS 0083. Every...single....time. Even at 2933. It's driving me nuts! Plus I can't seem to make my RAM jive at 1T. It's 2T every time for some reason. If this was my main rig, I'd have put it through a wall already. biggrin.gif
FireBox
(17 items)
 
 
CPUMotherboardGraphicsRAM
i7 3820 Asus Rampage IV Gene Zotac GTX 980 x 2 16 GB Corsair Dominator Platinum CL9 
Hard DriveHard DriveHard DriveCooling
256GB ADATA S900 x 2 RAID0 3TB x 2 RAID1 1TB x 2 single storage Custom water loop 
CoolingCoolingOSMonitor
XSPC EX360 rads x 1 / AlphaCool Monsta 360 x 2 ... Dual D5 variable pumps Windows 7 64 bit SP1 Samsung 27" LED 
KeyboardPowerCaseMouse
Logitech G110 Corsair AX750 Case Labs Magnum M8 Logitech G500 
  hide details  
Reply
FireBox
(17 items)
 
 
CPUMotherboardGraphicsRAM
i7 3820 Asus Rampage IV Gene Zotac GTX 980 x 2 16 GB Corsair Dominator Platinum CL9 
Hard DriveHard DriveHard DriveCooling
256GB ADATA S900 x 2 RAID0 3TB x 2 RAID1 1TB x 2 single storage Custom water loop 
CoolingCoolingOSMonitor
XSPC EX360 rads x 1 / AlphaCool Monsta 360 x 2 ... Dual D5 variable pumps Windows 7 64 bit SP1 Samsung 27" LED 
KeyboardPowerCaseMouse
Logitech G110 Corsair AX750 Case Labs Magnum M8 Logitech G500 
  hide details  
Reply
post #11487 of 17579
Quote:
Originally Posted by lordzed83 View Post

Quite opposite i like when stuff does not work and i get it runnign after hours and hours of messing about. But i got time to do so tongue.gif Since i flash stuff while doing weights and body weigh training at home next to pc biggrin.gif

Yea I suppose if you have the time, but I don't. And when I make the time, the next BIOS update undoes it all anyways.
post #11488 of 17579
Quote:
Originally Posted by S1L3N7D3A7H View Post

ZenStates modifies the VID. If you have a voltage offset and are adjusting the ZenStates voltage, you are adding more voltage than you're intending.

Quote:
Originally Posted by SpecChum View Post

No, ZenStates sets the absolute voltage, so if you set 1.4v for P0 and have an offset of 0.2v in BIOS, you're getting 1.6v.

Just set ZenStates to the voltage you need for each state.

Thanks guys but again when is 1.35v + 0.0625(my offset) = 1.6v
post #11489 of 17579
BIOS offset +0.075 V + Zenstate (0.2) 1.35 V = 1.425 V here.
post #11490 of 17579
Quote:
Originally Posted by y0bailey View Post

I'm getting awfully close to putting this Ryzen build in a closet with a lock and key, and not let myself touch it anymore for a few months. Least enjoyable build I've ever had, and I started building over 15 years ago.

The 1.0.0.5 AGESA update is close, so support for higher RAM speeds will be here. Slower RAM speeds in the short term shouldn't be seen as a problem. Lighting on your RAM....and having SPD get corrupted because of software...not the fault of the platform. To be honest, while it can be annoying for SOME that new BIOS updates are being released CONTINUALLY to help improve performance, things don't seem that bad outside of the whole "RAM that is certified at a speed on Intel systems isn't running at that speed YET on Ryzen" issue. Overclocking....new platform, not a basic evolution of everything else out there.

Blame the whole "flashing lights on my RAM being a way to ruin your RAM via software" on the RAM manufacturer(s) that are at fault. When SPD can get corrupted due to software, that isn't good...you should expect that to be locked at the factory and not subject to updates by users.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: AMD Motherboards
Overclock.net › Forums › AMD › AMD Motherboards › ROG Crosshair VI overclocking thread