Before anyone says that its a rubbish MOBO, i'm getting 3.6GHz stable at stock voltages, its getting higher than that thats the issue.
Since the BIOS has no static vCore option, i have to use vCore offset, setting this to +0.03v to get 3.7GHz should be fine (stock voltages hover around 1.18v) However, the voltage never actually applies to the CPU, it shows in the BIOS as the offset voltage, however, if i check HWINFO, the CPU vCore still sits at 1.188v on each core, vCore read straight from the BIOS registers the offset value however. To make matters even worse, under load, the vCore will drop to 1.144v on stock voltages, if i increase the offset, it actually drops more, which basically makes getting a higher OC than 3.6GHz impossible.
Gigabytes BIOS was awful enough to actually force me into OC'ing in the first place, since leaving everything on auto caused vCore to spike to over 1.4v when SCT was hit (3.7GHz), though, according to the BIOS, the vCore when the multiplier was set to auto was about 1.38v (seriously gigabyte? 3.2GHz on almost 1.4v...)
Any ideas?
Since the BIOS has no static vCore option, i have to use vCore offset, setting this to +0.03v to get 3.7GHz should be fine (stock voltages hover around 1.18v) However, the voltage never actually applies to the CPU, it shows in the BIOS as the offset voltage, however, if i check HWINFO, the CPU vCore still sits at 1.188v on each core, vCore read straight from the BIOS registers the offset value however. To make matters even worse, under load, the vCore will drop to 1.144v on stock voltages, if i increase the offset, it actually drops more, which basically makes getting a higher OC than 3.6GHz impossible.
Gigabytes BIOS was awful enough to actually force me into OC'ing in the first place, since leaving everything on auto caused vCore to spike to over 1.4v when SCT was hit (3.7GHz), though, according to the BIOS, the vCore when the multiplier was set to auto was about 1.38v (seriously gigabyte? 3.2GHz on almost 1.4v...)
Any ideas?