• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

High CPU Core Voltage (stock settings)

Just had an afterthought (sorry) - better to run a short benchmark like CPU-Z's integrated bench or Cinebench or something, first. So we can see the max volts/temps when on load also listed in the screenshots.
 
cpu

GAo0qLH.jpg

xq6J47y.jpg


ram (2 sticks but info in both was identical)

2vXV2CY.jpg


mobo (i'm not sure what you needed from here so this is the default view - let me know what you need specifically)

5ngr9GE.jpg


let me know if you need anything else
 
Oh dear. Those aren't the shots needed. :D

If I'd known there was a different place in the app (I haven't seen that before, maybe new version or something but you definitely want the Sensors information not the General Info or whatever) I'd have warned you. It's these in the Sensors page (taken screenshot of mine so there's no mistake):


uDBxKAo.png


4JPeT6e.png


V77zcnq.png



Notice how the +5v reading and +3.3v etc readings are realistic, unlike on the original HWMonitor screenies you posted. And how much info it displays (it will vary from motherboard to motherboard a bit). The only unrealistic readings are the AUXTIN1 and 3, which is a common glitch.
 
ok so a little update. after resetting to bios defaults and enabling xmp, i managed to run csgo for around 20 minutes without issue, then bf1 for about 10 minutes before it locked up, this time i got a stop code in win10 - CLOCK_WATCHDOG_TIMEOUT, which I believe is related to the CPU. temps during this time weren't very high, playing csgo peaked at around 55°C, bf was warmer, but not massively high at 69°C so it seems overheating isn't an issue.

What are my options at this point? Would I be best off just adjusting the voltage to the CPU in increments from the stock voltage and see if I can get it stable?
 
billyonecan said:
I've flashed the bios to the latest revision. Core voltage is now 1.217v (auto [down from the 1.419v]) but it's not stable in Windows. I've completed frozen 3 times trying to write a reply. Another thing I've noticed is that all cores appear to be running at their boost clock speed all the time (4.4ghz reported in BIOS and by CPU-Z). Is this the intended behaviour or is there something else happening here as well?

Just to give you a little extra information. This build is over 2 years old, I bought on Black Friday 2014 from overclockers. As far as I'm aware, it'll have been running at this voltage since bought :/ I've never had any instability issues, and have never experienced any crashing. The only reason I noticed is because I'd moved the components in to a new case, and on a whim decided to install hwmonitor and cpu-z, and noticed the temperatures on load were high (this was with the stock cooler). I replaced the stock cooler with the Corsair H75, the temperatures are slightly lower (maxed at 85°C) but are still too high
Click to expand...


Sorry to here this

I have had a few builds with gigabyte boards with this kind of issue on x87 & z97 ..can be down to memory XMP or memory itself ... a corrupt bios even when re flashing bios and or faulty board ...

Its a little alarming that its been running at these volts for a few years that is a concern ....

was it a pre built from OC or did you build ...

Now the GIGABYTE Z97X-SOX has a ton of physical hardware features as i am aware so i would get your manual out and make sure all settings on the board are set at default then tackle the bios ...

Like i said reflash the bios again... i have had some gigabyte boards that where buggy with there bios and it took 3 flashes before they where right ....

Also try just one stick of ram ....
 
billyonecan said:
ok so a little update. after resetting to bios defaults and enabling xmp, i managed to run csgo for around 20 minutes without issue, then bf1 for about 10 minutes before it locked up, this time i got a stop code in win10 - CLOCK_WATCHDOG_TIMEOUT, which I believe is related to the CPU. temps during this time weren't very high, playing csgo peaked at around 55°C, bf was warmer, but not massively high at 69°C so it seems overheating isn't an issue.

What are my options at this point? Would I be best off just adjusting the voltage to the CPU in increments from the stock voltage and see if I can get it stable?
Click to expand...

them temps are better but you should be able to run on stock / default without any issues and at the correct volts ...if not then there is a issue somewhere as stated in my last post
 
To rule out an unstable CPU as the problem just temporarily underclock it, set the cpu ratio to x35 and same for the uncore ratio. Also check the XMP profile for your ram, there might be more than one, i have several profiles in my XMP settings and most of them are unstable as they set the memory timings too low, so i choose the one with the highest timings and its fine.
 
Last edited:
XMP enabled is usually the main culprit but it can be many factors ....The main problem is that board as a ton of features not just bios but on barod too great for tweaking OC but trying to use at default / stock well as you know not doing too well but it should be able too...

in the end it looks like you will have to tame the the board with the rest of the parts manually ...not a bad thing means you have control ...you just have to understand the settings once you do all will be good with the correct volts ect

i doubt you have any hard ware at fault

here is a guide to help as trying to explain in this thread would be endless

hope this helps

http://www.overclock.net/t/1490835/the-gigabyte-z97x-overclocking-guide
 
billyonecan said:
ok cpu clock ratio and uncore ratio are now both at 35.

i had a look at the xmp profile and it looks fine, the ram timings are 11-11-11-31 which match up with what's stated on the product page: https://www.overclockers.co.uk/team...hannel-kit-tlaed38g2133hc11adc-my-037-tg.html
Click to expand...

Yes its not the timings that will be an issue its more to do how the cpu mem controller & motherboard handle that voltage's on auto XMP its usually sky high with gigabyte boards ...well that's my experiences with z87 97 GA boards...

hope that guide helps its looks like you will have to setup the bios manually once you find the sweet spot make sure you save the bios setting profile in the bios or jot the setting down
 
ok with the underclock bf1 froze while loading, appears less stable

when going back in to the bios to remove the underclock and set back to auto, i noticed the vcore voltage was 0.9v, so the motherboard appears to be setting it dynamically. it's setting it at 1.217v with stock (auto) settings

the ram voltage is set by xmp @ 1.65 which i think is correct, or is there something else i should be looking for?
 
Last edited:
Please disable XMP entirely and load BIOS optimised defaults then test again. XMP is technically overclocking and will do things like raise voltages and power limits for entirely unrelated components. We need to eliminate this as a contributing factor.
 
ok so i managed to play a full game of bf1 for the first time without issue with xmp disabled.

is there a better way i can test without stressing the components too much?

max temperature reached 68°C which is a hell of a lot better than it was
 
okay so i've reflashed the bios, loaded optimised defaults and the only thing i've done is enabled the xmp profile for my ram

ltron said:
Can you download Aida64 from here: http://download.aida64.com/aida64extreme580.exe
Open Aida then go to tools, system stability and run the default stress test for an hour and see if it crashes. If it doesn't crash then maybe the GPU is at fault.
Click to expand...

ok installed aida and ran it, crashed with bsod after around 30 seconds (CLOCK_WATCHDOG_TIMEOUT)
 
You must log in or register to reply here.
Back
Top Bottom