• 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.

BCLK Reset after Sleep

Soldato
Joined
14 Feb 2006
Posts
4,644
Location
Surrey, UK
Hi all,

i5 750 overclocked to 3.2 GHz (160 * 20). Issue is that base clock (BCLK) is resetting to its default value (133MHz) after the system has slept and resumed (as reported by CPU-Z). Only way to get it back to 160 is to reboot.

This happens whether the following are enabled or not in BIOS:
* C1E
* C3/C6
* EIST

and enabling/disabling "hybrid sleep" in Windows makes no difference. The system is stable (1hr+ IBT "maximum") at the overclocked settings completes with core temperatures around the 60C mark.

CPU: i5 750
Motherboard: Gigabyte GA-P55-USB3

Turbo boost is disabled. Vcore is 1.25V and VTT is 1.2V (both set manually).

Any ideas? :confused:

Edit: This should quite clearly have been in the "Overclocking" section. Sorry mods.
 
Last edited:
Thanks for the reply :)

I'm on F9 which is the latest stable. Is it worth trying the F10 beta? (Quite new to overclocking!)

I'll bump up VTT a bit and post back.
 
Sleep saves and resumes from the memory so it could be not enough vtt voltage for the memory controller

Try f10 beta,can always flash back,use qflash though
 
Bumped VTT to 1.3V but no joy - same issue :(

The operating system itself resumes no problem - applications & documents remain open etc. It's just the BCLK that reverts.
 
DRAM voltage is 1.500V at the moment. Is it safe to increase this?

I'll give the beta BIOS a go.

Thanks for your help :)
 
Yeah you can bump up dram v to 1.55 to 1.6v to test sleep it won't hurt things

If your using easytune software try closing it,then try sleep
 
:(

Also tried DRAM 1.6V, VTT up to 1.3V and Vcore up to 1.3V. Is it worth sending Gigabyte a support request?

The problem doesn't occur in S1 sleep, as expected, but I specifically want S3 sleep to work :)
 
Back
Top Bottom