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

ROG Crosshair VI overclocking thread - Page 1128

post #11271 of 17462
Quote:
Originally Posted by ggdfdgd3 View Post

I'm currently using 0.95 SOC and other volts apart from vcore on auto, gonna try increasing the SOC voltage next if switching to the standard nvme driver doesn't help and if that doesn't help either probably gonna give a shot to increasing the other voltages although I've been hesitant to mess with those. Thanks for the tip smile.gif

Think AMDMatt and myself found that pumping extra volts here and there (not much just bit) When using BCLK gives better benchmark scores. I pump volts cause i got 6 external USB devices connected 2 memory card readers on internal ports. Thats why i gotten this Motherboard over Asrock biggrin.gif

I would look in to volts always can change back to what it was smile.gif
post #11272 of 17462
Quote:
Originally Posted by Secret Dragoon View Post

I'm coming over from the Gigabyte thread to ask a question.

While trying to reach 3600Mhz RAM (Usually by setting BCLK to 135) I get QCode 15 pre-Post. This should mean that the Northbridge/SoC initialization failed. Has anyone ran into this problem? What would be the solution?

what volts u on ?? Im one of people that got 3600 stable here from 3200 cl16 kit with crappy cl18.

Besides that cpu ?? and ram kit ?? Throw us a bone to go from biggrin.gif
Edited by lordzed83 - 4/24/17 at 3:09pm
post #11273 of 17462
Quote:
Originally Posted by Mumak View Post

Sorry, just saw those screenshots from BIOS. That looks indeed wrong - probably a problem with readout of DIMM SPD EEPROM.
Can you please run a let's say 3 times HWiNFO in Debug Mode and attach the Debug Files produced? I will then check the raw data to see what's going on there.
You might also try to use the RW-Tools and dump SPD data a few times. Then check the difference - for a particular module the content should not change. And if you have the same modules then the raw data should differ only by serial numbers and checksum.

I ran debug x3 and have the three debug files, however when trying to attach them here I get from the forum:

AJAX response unable to be parsed as valid JSON object.
post #11274 of 17462
Quote:
Originally Posted by SpecChum View Post

I've done 3 runs, not allowing me to post on here for some reason, JSON error.

https://1drv.ms/u/s!AipiGCTl1HL_g6EtM-EvaXSISw_21A

Well.. The SPD EEPROM content between your both modules is different and looks like parts of the EEPROM were overwritten with erratic data. In your case the affected parts of EEPROM fortunately don't seem to contain vital information.
I'm not sure why that happened, if it's some fault of the modules or something in the system tried to overwrite the content.
post #11275 of 17462
Quote:
Originally Posted by lordzed83 View Post

Think AMDMatt and myself found that pumping extra volts here and there (not much just bit) When using BCLK gives better benchmark scores. I pump volts cause i got 6 external USB devices connected 2 memory card readers on internal ports. Thats why i gotten this Motherboard over Asrock biggrin.gif

I would look in to volts always can change back to what it was smile.gif

I'm using 100 BCLK though. Something intresting I noticed after switching to the stock driver and restaring: the NVMe Idle Timeout value got hidden again and the ValueMax reset to 60000ms. SEC NVMe Idle Timeout didn't get rehidden nor it's ValueMax reset BUT the actual value it was set to got reset back to 60000 (so its possible this value is something specific to the samsung drivers). After unhiding the NVMe Idle Timeout again it was already set to 60000 so the change did persist despite it getting hidden but it seems that values past 60000 don't stick as I suspected could be the case. I'm gonna test the stock driver with 60000ms now just to be sure incase higher values don't apply (though it seems like higher values simply get dialed back to 60000) and hope for the best.
post #11276 of 17462
Quote:
Originally Posted by Mumak View Post

Well.. The SPD EEPROM content between your both modules is different and looks like parts of the EEPROM were overwritten with erratic data. In your case the affected parts fortunately don't seem to contain vital information.
I'm not sure why that happened, if it's some fault of the modules or something in the system tried to overwrite the content.

Well, I do know that Aura controls the RGB lights by writing to SPD, you can probably guess the rest.

So, if that's right, not only does Aura break the lights on the motherboard, it has potential to knock out RGB RAM sticks.

Nice.

@elmor @Raja@ASUS

If my suspicions are correct I think you need to look into this...
Edited by SpecChum - 4/24/17 at 3:09pm
post #11277 of 17462
Not just issue with Aura IMO. See this video, then what G.Skill said to that video maker, link .
XPS - R7 1700
(14 items)
 
XPS - i5 4690K
(12 items)
 
XPS - Q6600
(8 items)
 
CPUMotherboardGraphicsRAM
Ryzen 7 1700 Asus Crosshair VI Hero Sapphire Fury X@1145/545 G.Skill Trident Z 2x 8GB 3200MHz C14 
Hard DriveCoolingCoolingCooling
Samsung Evo 840 ThermalRight Archon IB-E X2 + 2x TY143 ThermalRight TY-143 2x front case intake Arctic Cooling F12 + 2x F9 as rear case exhaust 
OSMonitorKeyboardPower
Win 7 Pro x64 / Win 10 Pro x64 Asus MG279Q Cherry MX-Board 3.0 Cooler Master V850 
CaseMouse
SilverStone TJ06 Logitech G700S 
CPUMotherboardGraphicsRAM
i5 4690K@4.9GHz 1.255V Asus Maximus VII Ranger Sapphire Fury X@1145/545 HyperX Savage 2x8GB 2400MHz C11 
Hard DriveCoolingOSMonitor
Samsung Evo 840 TR Archon SB-E X2 Win 7 Pro x64 / Win 10 x64 Asus MG279Q 
KeyboardPowerCaseMouse
Cherry MX-Board 3.0 Cooler Master V850 SilverStone TJ06 Logitech G700S 
CPUMotherboardGraphicsRAM
Intel Q6600 G0 Asus P5K Premium Black Pearl Sapphire Toxic HD5850 Corsair Dominator 4GB 
Hard DriveCoolingOSPower
Crucial MX 100 256GB TR TRUE Rev.A Win 7 Pro x64 Cooler Master V650 
  hide details  
Reply
XPS - R7 1700
(14 items)
 
XPS - i5 4690K
(12 items)
 
XPS - Q6600
(8 items)
 
CPUMotherboardGraphicsRAM
Ryzen 7 1700 Asus Crosshair VI Hero Sapphire Fury X@1145/545 G.Skill Trident Z 2x 8GB 3200MHz C14 
Hard DriveCoolingCoolingCooling
Samsung Evo 840 ThermalRight Archon IB-E X2 + 2x TY143 ThermalRight TY-143 2x front case intake Arctic Cooling F12 + 2x F9 as rear case exhaust 
OSMonitorKeyboardPower
Win 7 Pro x64 / Win 10 Pro x64 Asus MG279Q Cherry MX-Board 3.0 Cooler Master V850 
CaseMouse
SilverStone TJ06 Logitech G700S 
CPUMotherboardGraphicsRAM
i5 4690K@4.9GHz 1.255V Asus Maximus VII Ranger Sapphire Fury X@1145/545 HyperX Savage 2x8GB 2400MHz C11 
Hard DriveCoolingOSMonitor
Samsung Evo 840 TR Archon SB-E X2 Win 7 Pro x64 / Win 10 x64 Asus MG279Q 
KeyboardPowerCaseMouse
Cherry MX-Board 3.0 Cooler Master V850 SilverStone TJ06 Logitech G700S 
CPUMotherboardGraphicsRAM
Intel Q6600 G0 Asus P5K Premium Black Pearl Sapphire Toxic HD5850 Corsair Dominator 4GB 
Hard DriveCoolingOSPower
Crucial MX 100 256GB TR TRUE Rev.A Win 7 Pro x64 Cooler Master V650 
  hide details  
Reply
post #11278 of 17462
Quote:
Originally Posted by ggdfdgd3 View Post

I'm using 100 BCLK though. Something intresting I noticed after switching to the stock driver and restaring: the NVMe Idle Timeout value got hidden again and the ValueMax reset to 60000ms. SEC NVMe Idle Timeout didn't get rehidden nor it's ValueMax reset BUT the actual value it was set to got reset back to 60000 (so its possible this value is something specific to the samsung drivers). After unhiding the NVMe Idle Timeout again it was already set to 60000 so the change did persist despite it getting hidden but it seems that values past 60000 don't stick as I suspected could be the case. I'm gonna test the stock driver with 60000ms now just to be sure incase higher values don't apply (though it seems like higher values simply get dialed back to 60000) and hope for the best.

Its getting better and better biggrin.gif if driver wont help deffo try volts. What memory speed You are on ?? In my case i can boot up with Soc 0.95 but found that anything below 1.125 under heavy load makes me loose performance or crash. Same with VDDP in my case helped with making oc stable where nothing else did.
Btw I'm using LLC2 auto gave me crash here and there not to mention i had to bump cvore so much i would idle at 1.46 tongue.gif
post #11279 of 17462
Quote:
Originally Posted by elmor View Post

Quote:
Originally Posted by S1L3N7D3A7H View Post

Still doesn't apply when system wakes from sleep.

Thanks for you efforts, I put in the time to overclock using the stock P1 and P2 voltages.


So if you sleep and resume, the applied settings are reverted to defaults?

Suggestion for your P-States App: can you add BCLK parameter in the app?

My ram won't post at certain BCLK levels but if I turn it down and change it after I'm booted using Asus VCore i reach good ram speeds and it is stable. If your app could do the BCLK tinkering after booting up, it would add much more value to the app.


Sent from my iPhone using Tapatalk
post #11280 of 17462
Quote:
Originally Posted by SpecChum View Post

Well, I do know that Aura controls the RGB lights by writing to SPD, you can probably guess the rest.

So, if that's right, not only does Aura break the lights on the motherboard, it has potential to knock out RGB RAM sticks.

Nice.

@elmor @Raja@ASUS

If my suspicions are correct I think you need to look into this...

ahh this was what i changed recently and recieved my Coldbug problems!!
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: AMD Motherboards
Overclock.net › Forums › AMD › AMD Motherboards › ROG Crosshair VI overclocking thread