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

ROG Crosshair VI overclocking thread - Page 2844

post #28431 of 32958
Quote:
Originally Posted by lordzed83 View Post

You could also try swaping DDRs in to A1+B1 from A2+B2 that i assume You are using.


I would scrap Corsair Link and move to Ryzen Timing checker tongue.gif


Anyhow Hows 1703 for You ?? I see You got good Sticks for Ryzen so try Slits 3466cl15 setting smile.gif I'm using that atm with extra tune to max it out smile.gif

3333 Works fine, like before.

Tested 3466 CL14 and 2T and gives errors in HCI sometimes so it is not stable.

Tested VRAM: 1.42V and VSOC: 1.1V

I think CL15 won't help much....

Weeks ago I changed DIMMS from A1/B1 to A2/B2, nothing major happened.

I use Corsair link to change my AIO speeds (sometimes). I just made it not open on Windows startup. I think that was the culprit.

Show me your 3466 timings and I will try but @ 3333 I am only stable with 2T (100% stable) or 1T GearDown enabled (99% stable).

Also VSOC and VRAM.

For gaming and overall use: 3333 CL14 vs 3466 CL15 would be a nice thing to benchmark if I am stable. (I can benchmark 1080Ti some games and 3dmark).
Edited by Frikencio - 10/17/17 at 7:08am
post #28432 of 32958
Quote:
Originally Posted by Frikencio View Post

3333 Works fine, like before.

Tested 3466 CL14 and 2T and gives errors in HCI sometimes so it is not stable.

Tested VRAM: 1.42V and VSOC: 1.1V

I think CL15 won't help much....

Weeks ago I changed DIMMS from A1/B1 to A2/B2, nothing major happened.

I use Corsair link to change my AIO speeds (sometimes). I just made it not open on Windows startup. I think that was the culprit.

Show me your 3466 timings and I will try but @ 3333 I am only stable with 2T (100% stable) or 1T GearDown enabled (99% stable).

Also VSOC and VRAM.

For gaming and overall use: 3333 CL14 vs 3466 CL15 would be a nice thing to benchmark if I am stable. (I can benchmark 1080Ti some games and 3dmark).


Im running 1.45 on memory. When benchmarking on Forza 7 that i play atm 3333cl14 is 5fps on average slower than 3466cl15. But ill see how Destiny 2 runs in a week biggrin.gif


Not knowing much about AIO's supoort as i got full lop but cant You controll it off motherboard pump header ??
post #28433 of 32958
Quote:
Originally Posted by lordzed83 View Post

Im running 1.45 on memory. When benchmarking on Forza 7 that i play atm 3333cl14 is 5fps on average slower than 3466cl15. But ill see how Destiny 2 runs in a week biggrin.gif

BIOS update didn't change performance for me.

post #28434 of 32958
Quote:
Originally Posted by Frikencio View Post

BIOS update didn't change performance for me.


Well Its most of fixes in my case I can OC cpu more and system is more stable on same settings that 15xx one
post #28435 of 32958
Quote:
Originally Posted by lordzed83 View Post

Well Its most of fixes in my case I can OC cpu more and system is more stable on same settings that 15xx one

Can you tell me your timings? I got HCI errors on CL15.



Tried to overclock more as you told me you can OC better and looks like I can do 3.8Ghz at almost same volts as 3.7Ghz. Gonna try more tests.
Edited by Frikencio - 10/17/17 at 8:05am
post #28436 of 32958
Quote:
Originally Posted by Frikencio View Post

Can you tell me your timings? I got HCI errors on CL15.



Tried to overclock more as you told me you can OC better and looks like I can do 3.8Ghz at almost same volts as 3.7Ghz. Gonna try more tests.

You are using the program wrong again dude.. doh.gif
hurricane
(13 items)
 
  
CPUMotherboardGraphicsRAM
AMD RYZEN 1600 Asus Crosshair hero 6 MSI GTX 970 gaming 4G G.Skill F4-3200C14D-16GFX 
Hard DriveCoolingOSMonitor
Samsung 950 pro, 256 GB Alphacool Eisbaer 360 Windows 10 Pro Asus VG248Q 
KeyboardPowerCaseMouse
Logitech G910 Cooler Master V850 Phanteks Enthoo Luxe tempered glass Logitech G900 
Audio
logitech Z-2300 
  hide details  
Reply
hurricane
(13 items)
 
  
CPUMotherboardGraphicsRAM
AMD RYZEN 1600 Asus Crosshair hero 6 MSI GTX 970 gaming 4G G.Skill F4-3200C14D-16GFX 
Hard DriveCoolingOSMonitor
Samsung 950 pro, 256 GB Alphacool Eisbaer 360 Windows 10 Pro Asus VG248Q 
KeyboardPowerCaseMouse
Logitech G910 Cooler Master V850 Phanteks Enthoo Luxe tempered glass Logitech G900 
Audio
logitech Z-2300 
  hide details  
Reply
post #28437 of 32958
Quote:
Originally Posted by hurricane28 View Post

You are using the program wrong again dude.. doh.gif

I am not testing ram here just fast IMC and happens to give errors.

If that passes, I would do it properly.

I know what I am doing.
post #28438 of 32958
Just close Corsair link when you open anything else that checks your memory.
post #28439 of 32958
Quote:
Originally Posted by lordzed83 View Post


Im here from day one and So far I cant remember ANYONE killing their Ryzen CPU with volts on this Forum. If So pealse quote me post with peron taht managed to Do so smile.gif Seen few boards that got bricked by bios update (few had to RMA as flashback did not help). Seen RGB memory kits killed and few corrupted ( Repaired with spd rewrite ) and ONE Killed AIO to proof that SenseMI will stop thermal protection from working. Yet not seen Anyone posting here that their CPU got fried by overvolting smile.gif But hey im following Ryzen platform on only 3 forum in 2 languages constantly daily.

 

 

I'll dig around and find it at some point, it may have been a video from Buildzoid or something similar, as I was watching a lot of that around the same time as that news surfaced, I may not have as much overclocking experience, but I've been dealing with Ryzen just about as long as the rest of everyone here. I'm also not the only one who remembers seeing this info.

 

Quote:
Originally Posted by MishelLngelo View Post


I pushed my 1600x over 1.6v trying to go way over 4.1GHz and while it posted it got into several thermal shutdowns running benchmarks and it didn't get damaged in any way. During that time I was more concerned about my Prime x370 Pro than processor itself. During my considerably long life with computers, I managed to blow up few MBs along with few GPUs and RAM but never damaged a processor, not even at times we had to do voltage mods on 386 systems.

 

 

You don't THINK you've damaged a processor. My bet is you probably have, and just don't know it. Does that matter in the end? Maybe, maybe not, no real way to know, and everyone's case is different. Every piece of silicon is different, every single CHIP within a line is different. I simply reiterated what AMD themselves said, and that I personally don't want to go above 1.4v, I feel that if I have to do that, it's pushing too far for that particular chip, and often the heat and voltage spiking isn't worth the extra 50-100 mhz of speed. That probably doesn't make me an "extreme overclocker" and I'm ok with that.

 

Quote:
Originally Posted by Frikencio View Post



I think that the problem is when I have multiple SPD reading programs open. I think CORSAIR LINK do access to SPD.

 

 

Yeah. You definitely don't want other SPD-reading programs open at all when you're running Taiphoon to pull an SPD read on RAM, it'll not work right, or look corrupted. I made the mistake of forgetting aura was running at one point trying to do it. Definitely make sure you're using the latest Aura (others WILL corrupt RGB RAM and even some non-RGB RAM) I've had to re-flash my sticks myself. I haven't seen any further corruption since aura was fixed, but I do have SPD backups of my sticks just in case. If you aren't sure, run Elmor's SPD check tool (with no other programs running--though I believe his latest version can play "nice" with Aura). And make sure it checks out OK, if not, re-flash or RMA your sticks. Just because they "appear to be working fine" that corruption can reach the point they won't boot, then you can't re-flash them in a system, and would have to replace or RMA them.

 

Edit: As an aside, Aura, Corsairlink, CPUz, Taiphoon, all SPD-reading and using programs, possibly so is HWinfo64/parts of Asus AI Suite, etc. Basically, if you're going to use Taiphoon, try to close everything you can while using it. All of those programs make use of the SMBus, which is where the issue comes in.


Edited by PeerlessGirl - 10/17/17 at 9:12am
post #28440 of 32958
Quote:
Originally Posted by PeerlessGirl View Post


I'll dig around and find it at some point, it may have been a video from Buildzoid or something similar, as I was watching a lot of that around the same time as that news surfaced, I may not have as much overclocking experience, but I've been dealing with Ryzen just about as long as the rest of everyone here. I'm also not the only one who remembers seeing this info.



You don't THINK you've damaged a processor. My bet is you probably have, and just don't know it. Does that matter in the end? Maybe, maybe not, no real way to know, and everyone's case is different. Every piece of silicon is different, every single CHIP within a line is different. I simply reiterated what AMD themselves said, and that I personally don't want to go above 1.4v, I feel that if I have to do that, it's pushing too far for that particular chip, and often the heat and voltage spiking isn't worth the extra 50-100 mhz of speed. That probably doesn't make me an "extreme overclocker" and I'm ok with that.



Yeah. You definitely don't want other SPD-reading programs open at all when you're running Taiphoon to pull an SPD read on RAM, it'll not work right, or look corrupted. I made the mistake of forgetting aura was running at one point trying to do it. Definitely make sure you're using the latest Aura (others WILL corrupt RGB RAM and even some non-RGB RAM) I've had to re-flash my sticks myself. I haven't seen any further corruption since aura was fixed, but I do have SPD backups of my sticks just in case. If you aren't sure, run Elmor's SPD check tool (with no other programs running--though I believe his latest version can play "nice" with Aura). And make sure it checks out OK, if not, re-flash or RMA your sticks. Just because they "appear to be working fine" that corruption can reach the point they won't boot, then you can't re-flash them in a system, and would have to replace or RMA them.

Edit: As an aside, Aura, Corsairlink, CPUz, Taiphoon, all SPD-reading and using programs, possibly so is HWinfo64/parts of Asus AI Suite, etc. Basically, if you're going to use Taiphoon, try to close everything you can while using it. All of those programs make use of the SMBus, which is where the issue comes in.

Yup that happened to me and I also had to re-flash because AURA corrupted one of my sticks but since updating to the latest AURA it didn't give me any problem. AURA now works flawlessly and very fast. SPD reads CRC: OK in both sticks and I was pretty sure it was some kind of intrusion with other SPD reading programs.

Where is that "Elmor's SPD check tool" program?
Edited by Frikencio - 10/17/17 at 9:25am
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: AMD Motherboards
Overclock.net › Forums › AMD › AMD Motherboards › ROG Crosshair VI overclocking thread