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

ROG Crosshair VI overclocking thread - Page 820

post #8191 of 16852
Quick question to those with raised BCLK: you all have HPET enabled?
main
(10 items)
 
  
Reply
main
(10 items)
 
  
Reply
post #8192 of 16852
Good posts in here. I am sure that future BIOS updates will alleviate the instability. I remember the first AM3+ board that I had from ASRock,(fatality pro) was unstable as hell for the first 3 bios revisions and then on the fourth or so update. Bam, it was solid without problem thereafter. Firmware can definitely make the hardware look like crap when it can be solid hardware. Just have patience guys. New architecture as others have mentioned, it will get better with software updates.
post #8193 of 16852
Sorry. Damn mobile website. Wrong thread reply
post #8194 of 16852
Seems like I got "kinda lucky" with RAM today. Contacted the store, apparently RAM manufacturers have a big delay with RAMs atm. They did get 1 RAM of F4-3200C14D-16GVR, so I switched my 3600 CL16 to this (had to downgrade), but don't have to wait for the whole month now.
(Please don't tell me these are not B die XD - I will literally cry after these 20y)
post #8195 of 16852
Not positive that they're Samsung B die but they are on the QVL list so you should definitely be safe.
post #8196 of 16852
Thread Starter 
Quote:
Originally Posted by noko59 View Post

I am on Bios 81, installed c7h_p0vidfix, went into bios and set P0 to VID 98(3.8ghz), FID 8 and VID to 1C (1.37v), BCLK was at 100. Anyways booting into bios it took, cpu was around 3.8ghz and voltage was at 1.37v range. Went into windows and it stayed on p1 at around 3ghz.

How does one remove the tweak? Anything did I miss?

Went back into the bios and set VID to 20 (1700x here) and PState OC is working as before.

Thanks

It's not a one time fix, the settings are lost after reboot. You need to run the fix each time you enter the OS.

Quote:
Originally Posted by Karagra View Post

No Sorry I have been overclocking non stop, and for the life of me I cannot fully replicate the issue, It may have to do with I am within a more stable range now so I am not noticing the issue anymore, One thing I noticed which is posted a bit back on the 2933mhz I can overclock between 2933-3600mhz without a failed boot. On the 3200mhz frequency I cannot boot unless i am running 3466+. Also 3200mhz frequency @3600mhz requires 18-18-18-18-42 1.425v to run while 2933mhz @3600mhz requires 16-16-16-16-36 1.37v to run. This was on every bios (did not fully test 79 with this) I am guessing this is just a wait till May type issue that will be resolved.

Subtimings are set differently for each DRAM Ratio, which is why you're getting different results even though the frequency is the same. We can't control this at the moment.

Quote:
Originally Posted by LPCobris View Post

Hello Elmor...

Are the instable fan ramping up and down bug fixed on the new bios? I have the 1002, and its very instable, even if i try to fix a RPM.
It keeps doing "spikes" on the fans... The idea here is, if i put 750rpms, it stays that way...

Also the ASUS software is way slow, controlling the temps, fans speeds, etc...
That software really needs some serious rework...

With my best Regards,

LPC

Try the c6h_tempsrc software listed above and see if it fixes your problem.

Quote:
Originally Posted by Timur Born View Post

Thanks for the answer, but this does not even remotely fit the readings in HWinfo. That is unless the "CPU socket thermistor" is different to the "CPU (Socket)" reading in HWinfo, then we would need a proper readout of that.

If "CPU (Socket)" is indeed the "CPU socket thermistor" then it seems that Tctl+5 is used up to about 60C and then some averaging algorithm is used, unfortunately with a not so clear weighting (but mostly weighted for Tctl).
Sorry, but I am not convinced. I repeatedly reproduced that "Sense Skew" is the deciding factor between the CPU safety measures happening or not happening.

Sense Skew disabled: Soft throttling (down to about x30) happens at Tctl + Offset = 95C. Hard throttling (x0.5!!!) happens at Tctl = 95C. Thermal shutdown happens at about Tctl = 115C.

Sense Skew enabled: Soft throttling happens with certain loads regardless of Tctl or at very low Tctl (if CPU at stock clock). Tctl + Offset = 95C or Tctl = 95C cannot be reached at stock clocks/voltages, as a consequence no throttling happens. Tctl = 115C cannot be reached at stock clocks/voltages, as a consequence no thermal shutdown happens! Instead the CPU crashes to Code 8 when these high temperatures happen.

In the following screenshot Tctl is reported as 66.3C, but the real CPU temperature is likely higher than 110C! Shortly after taking this screenshot I got a Code 8.



And here is Tctl at over 110C for the same load, same (disabled) cooling and especially same "CPU (Socket)" temperature without Sense Skew. Shortly after taking this screenshot I got a thermal shutdown (last reading was Tctl = 113C, SIO = 109C, couldn't save last screenshot before shutdown).

More important: Disabling Sense Skew leads to proper throttling and thermal shutdowns without producing a Code 8. Again, I reproduced this repeatedly!


This is reassuring to know. Nevertheless I would prefer if CPU safety measures would work, especially proper thermal throttling.

For the time being I disable Sense Skew and hope that Asus will change fan control to allow more than 75C and HWinfo (Martin) can come up with some logic that makes "Tdie" follow the dynamically changing Tctl offset (+0/+10/+20) and thus better compensate for it in its readings. The whole offset thing is a rather inelegant way of handling certain CPU instructions' load.

Anyone using Sense Skew with the 1800X should watch their "CPU (Socket)" temps, if they climb over 60-70C then your CPU likely is burning hot towards 100C already, regardless of what Tctl and SIO CPU claim.

That's the formual from the SIO datasheet, I can check it closer when I'm less busy (might take a while tongue.gif)

The CPU relies on the Tctl value for thermal shutdown, so obviously skewing the Tctl value will also skew the shutdown point.

Quote:
Originally Posted by S1L3N7D3A7H View Post

@elmor
I understand that, but why would the beta bios have this particular issue? I had no problems with setting it on 1002. Also, any comment about how quite a lot of us are reporting needing more volts to achieve a stable overclock vs previous BIOS'?

All due to updated microcode and SMU firmware from AMD, I have no details on the changes they made. I tested on the new bios and performance bias works fine here.

Quote:
Originally Posted by Teddyen View Post

Do you think there is any hope of using dividers higher than 2666, when using four sticks on future updates? If so, do you think B-die is a must?

I'm on the verge of selling my G.Skill RipjawsV 3200MHz 64GB CL16 (F4-3200C16Q-64GVK) and buying the same kit with CL14 if that's needed for me to go to 3200MHz, but the price is a whopping $250 more. I think the CL14 has a higher chance of being B-die, but heck, I don't even know what I have today.

People are already having success with higher than 2666 even on non B-die sticks on the current BIOSes. I'd wait at least until the May update.
post #8197 of 16852
Quote:
Originally Posted by Timur Born View Post

When I tested this I had to use +0.1 V more on Vcore to get from 4.0 to 4.05. That was with older BIOS, so I will repeat that once I am through with RAM tests. Currently I am mostly busy testing 3200-CL12 stability.

CL12 through 20 are the same on Ryzen platform. Ryzen wants speed, not low CL.
post #8198 of 16852
Quote:
Originally Posted by Frikencio View Post

CL12 through 20 are the same on Ryzen platform. Ryzen wants speed, not low CL.

CAS latency is still very relative to performance and CL12 vs CL20 will produce very different results at the same MT/s (e.g. 3200). The CPU's Infinity Fabric does see considerable gains with higher MT/s settings (e.g. 3200 vs 2133).
Edited by madweazl - 4/11/17 at 4:50am
Inferior FTW!
(22 items)
 
FrankenRyzen
(13 items)
 
 
CPUMotherboardGraphicsRAM
i5 6600K 4.5@1.320v Gigabyte Z170X-Gaming 7 Founder's GTX 1070 200/800 Corsair Vengeance LED 3200@4000 
Hard DriveCoolingCoolingCooling
MyDigitalSSD BPX 120 (RAID 0) EK-FB GA Z170X Monoblock XSPC RX360 (White) XSPC RX240 (White) 
CoolingCoolingCoolingCooling
EK Vardar F2s (x5) EK-FC1070 GTX1070 (nickel/plexi)  EK GTX1070 FE backplate EK Double Bay PWM D5 MX 
CoolingCoolingOSMonitor
Bitspower 250 Z-Multi Res EK HDC fittings (12mm) Windows 10 Samsung C32F391 
KeyboardPowerCaseMouse
Razer Blackwidow Chroma EVGA Supernova G1 1000w Phanteks Enthoo Primo Razer Naga Epic 
Mouse PadAudio
Razer Vespula Sennheiser HD598 
CPUMotherboardGraphicsRAM
Ryzen R7 1700 @3.9 Asus Crosshair VI Hero Radeon HD 6950 G.skill RGB 3200 @3500 C16 
Hard DriveCoolingOSMonitor
Samsung 960 Evo CM 212 Evo (push/pull) Windows 10 Pro 46" Sharp Aquos 
KeyboardPowerCaseMouse
Razer Anansi 750w Keian CM ATCS 840 Logitech G300 
Mouse Pad
My desk... 
  hide details  
Reply
Inferior FTW!
(22 items)
 
FrankenRyzen
(13 items)
 
 
CPUMotherboardGraphicsRAM
i5 6600K 4.5@1.320v Gigabyte Z170X-Gaming 7 Founder's GTX 1070 200/800 Corsair Vengeance LED 3200@4000 
Hard DriveCoolingCoolingCooling
MyDigitalSSD BPX 120 (RAID 0) EK-FB GA Z170X Monoblock XSPC RX360 (White) XSPC RX240 (White) 
CoolingCoolingCoolingCooling
EK Vardar F2s (x5) EK-FC1070 GTX1070 (nickel/plexi)  EK GTX1070 FE backplate EK Double Bay PWM D5 MX 
CoolingCoolingOSMonitor
Bitspower 250 Z-Multi Res EK HDC fittings (12mm) Windows 10 Samsung C32F391 
KeyboardPowerCaseMouse
Razer Blackwidow Chroma EVGA Supernova G1 1000w Phanteks Enthoo Primo Razer Naga Epic 
Mouse PadAudio
Razer Vespula Sennheiser HD598 
CPUMotherboardGraphicsRAM
Ryzen R7 1700 @3.9 Asus Crosshair VI Hero Radeon HD 6950 G.skill RGB 3200 @3500 C16 
Hard DriveCoolingOSMonitor
Samsung 960 Evo CM 212 Evo (push/pull) Windows 10 Pro 46" Sharp Aquos 
KeyboardPowerCaseMouse
Razer Anansi 750w Keian CM ATCS 840 Logitech G300 
Mouse Pad
My desk... 
  hide details  
Reply
post #8199 of 16852
Later on when P-States VID settings are fixed, should we be leaving the Vcore at auto?
Ryzen - Elmor
(13 items)
 
  
CPUMotherboardGraphicsRAM
AMD Ryzen 1700 @ 3.8Ghz ASUS ROG CROSSHAIR VI HERO GeForce GTX 1070 32GB DDR4-3466 16-15-15-35 
Hard DriveHard DriveHard DriveHard Drive
Samsung 960 EVO 1TB Samsung 830 SSD 256GB Hitachi 2TB HGST 4TB  
CoolingOSMonitorPower
Noctua NH-D15S Windows 10 Pro Acer Predator XB271HU SeaSonic PRIME Titanium 750W 
Case
Fractal Design Define R5 
  hide details  
Reply
Ryzen - Elmor
(13 items)
 
  
CPUMotherboardGraphicsRAM
AMD Ryzen 1700 @ 3.8Ghz ASUS ROG CROSSHAIR VI HERO GeForce GTX 1070 32GB DDR4-3466 16-15-15-35 
Hard DriveHard DriveHard DriveHard Drive
Samsung 960 EVO 1TB Samsung 830 SSD 256GB Hitachi 2TB HGST 4TB  
CoolingOSMonitorPower
Noctua NH-D15S Windows 10 Pro Acer Predator XB271HU SeaSonic PRIME Titanium 750W 
Case
Fractal Design Define R5 
  hide details  
Reply
post #8200 of 16852
Quote:
Originally Posted by finalheaven View Post

Later on when P-States VID settings are fixed, should we be leaving the Vcore at auto?

In theory yes
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: AMD Motherboards
Overclock.net › Forums › AMD › AMD Motherboards › ROG Crosshair VI overclocking thread