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

ROG Crosshair VI overclocking thread - Page 989

post #9881 of 16839
Quote:
Originally Posted by SpecChum View Post

Mine did as elmor said. My VID voltage is 1.395v and my offset was 0.2525.

When using P-States it uses the "default" 1700 voltage of 1.175v + my offset, but when that failed it went back to VID + 0.2525, giving me 1.6475v, which is what I saw when I entered BIOS.

Just like this, I believe 'VID' goes down once you apply tinkered oc settings.

iirc, before I mess with anything in bios, HWinfo reports the VID for an 1800x being 1.55v and it doesnt move. after messing with stuff VID is maxing at 1.35 with lowest being .886 (vid of pstates) and applying my offset from there, which is then reported in voltage readouts below, maxing at 1.512 with 0.15 offset.

I think since offsets and other bios settings settings don't get returned to default when a post fails, but pstate gets lost and since frequency target in extreme weaker isn't touched, VID will return to default but still have your offset applied thus resulting in much higher voltage than you desire.


One possible yet probably undesireable work around is to setup bios with the lowest CPU speed you can do without having to increase the offset, then use one of the windows softwares to raise the speed/offset to what you want. These don't actually change bios so when you crash from something or get post fails, no crazy offsets will be applied to the default VID.
Edited by Reikoji - 4/18/17 at 5:23am
post #9882 of 16839
Quote:
Originally Posted by noko59 View Post


Installed AMD chipset drivers since they were newer than the ASUS one's. This allowed installation of Aura but same problem as before, it crashes as soon as you try to open it.
Now AISuite3 just crashes when attempting to open. Not sure what is going on - all other programs seem to work fine without issue.
Aren't access violation errors typically caused by an unstable memory overclock/bad RAM?
post #9883 of 16839
Quote:
Originally Posted by NotAgain View Post

Aren't access violation errors typically caused by an unstable memory overclock/bad RAM?

not neccesarily. thats not really a new ai suite 3 error. its been around since it was introduced. what that is saying is even though it appears to have been installed successfully, some things didnt go so well.

Try reinstalling AI suite but rightclick the setupfile and run as administrator. for me it was fan expert error until i installed it this way. i also changed the installer capatibility to windows 7 but that may not be a requirement. if you do that ignore the capatibility errors that pop up.
Edited by Reikoji - 4/18/17 at 6:01am
post #9884 of 16839
Quote:
Originally Posted by SpecChum View Post

Mine did as elmor said. My VID voltage is 1.395v and my offset was 0.2525.

When using P-States it uses the "default" 1700 voltage of 1.175v + my offset, but when that failed it went back to VID + 0.2525, giving me 1.6475v, which is what I saw when I entered BIOS.


Thats the one booted to windows with them volts Crap chip is still cap and wont do more than ~3955 stable so **** him tongue.gif
Would be great if there was option of NO BOOT if voltage exceeds voltage u select lets starting from 1.5.


3605 cl18/17/17/17/37 T1. Bet i could have 3600 cl16@ T2


Edited by lordzed83 - 4/18/17 at 6:17am
post #9885 of 16839
Finally got all my parts. I don't want to overclock just now, since the bios still seems a bit unstable and I don't want to accidentally give the CPU a high voltage.

I just want to double check if I got everything right for when I build the system:

- flash BIOS to 079/081/082
- clear CMOS
- load defaults
- set DRAM voltage manually to 1.35 (people are reporting 1.45v on default settings)
- set strap to 3200

Anything else I am missing?
post #9886 of 16839
Quote:
Originally Posted by skyworxx View Post

Finally got all my parts. I don't want to overclock just now, since the bios still seems a bit unstable and I don't want to accidentally give the CPU a high voltage.

I just want to double check if I got everything right for when I build the system:

- flash BIOS to 079/081/082
- clear CMOS
- load defaults
- set DRAM voltage manually to 1.35 (people are reporting 1.45v on default settings)
- set strap to 3200

Anything else I am missing?

clear cmos first, then bios flash. safer.
post #9887 of 16839
What are the chances that accidentally fat fingering 1.14 SOC as 1.4 SOC and trying to boot will have a lasting negative impact?
Jigglypuff
(9 items)
 
Snorlax
(13 items)
 
 
CPUMotherboardRAMHard Drive
amd 5350 ASRock AM1H-ITX 8gb gskill 3tb wd red 
Hard DriveHard DriveOSPower
3tb wd red sandisk Debian 300w Corsair 
Case
Cooler Master Elite 130 
CPUMotherboardGraphicsRAM
R7 1800X asus ch6 hero Asus Titan X @1.5Ghz g.skill 3200 
Hard DriveCoolingOSMonitor
ocz vertex 3 h220-x, 2x ek-wb, monsta 120mmx80mm windows 10 pro rog swift 
KeyboardPowerCaseMouse
g.skill KM570 evga 750 g2 rosewill blackhawk g502 
  hide details  
Reply
Jigglypuff
(9 items)
 
Snorlax
(13 items)
 
 
CPUMotherboardRAMHard Drive
amd 5350 ASRock AM1H-ITX 8gb gskill 3tb wd red 
Hard DriveHard DriveOSPower
3tb wd red sandisk Debian 300w Corsair 
Case
Cooler Master Elite 130 
CPUMotherboardGraphicsRAM
R7 1800X asus ch6 hero Asus Titan X @1.5Ghz g.skill 3200 
Hard DriveCoolingOSMonitor
ocz vertex 3 h220-x, 2x ek-wb, monsta 120mmx80mm windows 10 pro rog swift 
KeyboardPowerCaseMouse
g.skill KM570 evga 750 g2 rosewill blackhawk g502 
  hide details  
Reply
post #9888 of 16839
Quote:
Originally Posted by NotAgain View Post

Aren't access violation errors typically caused by an unstable memory overclock/bad RAM?

That would be what I would expect but rendering 120 frame animation now in Modo at 99% cpu usage while doing other stuff. Aida stable as well. Unless AISuite3 is the ultimate stress test for memory or something I have not a clue why all of a sudden it just did not want to work any more.

I did try reinstalling AISuite3 and it did the same thing. What gives? I do not know.

Are our machines degrading that fast in front of us? I hope not.
Destroyer
(13 items)
 
  
Reply
Destroyer
(13 items)
 
  
Reply
post #9889 of 16839
Quote:
Originally Posted by skyworxx View Post

- set strap to 3200
Good luck with that.
post #9890 of 16839
Quote:
Originally Posted by Cata79 View Post

Good luck with that.

Not that hard if you work your way up. If i load my 3200mhz profile it doesnt work even resetting, if i load my 2933 profile change soc to 1.15 save and reset then change strap it works like a charm.

Needs to be done in increments on am4 because of its infancy. Cold boot issues for ram as well.
    
CPUMotherboardGraphicsRAM
R7 1700X asus crosshair 6 Sapphire R9 390 Nitro CMK16GX4M2B3200C16 
Hard DriveHard DriveCoolingCooling
Kingston HyperX 3K Seagate ST2000DM006 EKWB Supremacy Evo EK-XRES 100 Revo D5 - Acetal 
CoolingCoolingCoolingCooling
Alphacool GPX r9 390 m01 alphacool xt45 240 Alphacool xt45 360 Alphacool D5 PWM 
OSMonitorKeyboardPower
Windows 10 LG 29UM68 Corsair Strafe Corsair RM1000 
CaseMouseMouse Pad
Thermaltake X5 Corsair M65 Pro RGB Razer Goliathus Speed 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
R7 1700X asus crosshair 6 Sapphire R9 390 Nitro CMK16GX4M2B3200C16 
Hard DriveHard DriveCoolingCooling
Kingston HyperX 3K Seagate ST2000DM006 EKWB Supremacy Evo EK-XRES 100 Revo D5 - Acetal 
CoolingCoolingCoolingCooling
Alphacool GPX r9 390 m01 alphacool xt45 240 Alphacool xt45 360 Alphacool D5 PWM 
OSMonitorKeyboardPower
Windows 10 LG 29UM68 Corsair Strafe Corsair RM1000 
CaseMouseMouse Pad
Thermaltake X5 Corsair M65 Pro RGB Razer Goliathus Speed 
  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