******Gigabyte GA-P67A-UD4 Discussion Thread******

[jwfowble]

I flashed my GA-P67A-UD4-B3 with bios F5 (thought I'd give touchbios a try) and noticed something odd with speedstep started happening. Maybe most people disable the Cstate, EIST, and SpeedStep features, but I noticed that after returning from sleep things ran a little slower than my 4.5 GHz 2500k CPU should. Upon further investigation with RealTemp, i7 turbo GT app, and CPU-z I could see that, after the computer went to sleep (presumably S3 as the bios is set to do) that the multiplier became locked at 16x and never jumped up again until I rebooted. I cleared the bios back to failsafe defaults and re-flashed with F5 and had the same thing happen. Maybe I'm just unfortunate, but I thought I'd report it in case anyone else has encountered this problem. My overclock is prime95 stable but sleep may put special stresses on the system for all I know.
I'm headed back to F4 bios to see if that clears things up. After a few runs of the touchbios program it stopped launching (well, the process crashed and seemed to keep 25% of my CPU occupied until I manually killed the process).

Just an update on my 16x multiplier lock after resuming from sleep (in case anyone encounters this).
F4 bios didn't change the 16x multiplier nor did adjusting most of the various EIST/C1 and S1/S3 sleep states. I had manually re-entered all my overclock settings so I went back to system defaults and noticed things resumed from sleep just fine. I went back to F5 bios and am headed back up in overclocking with similar bios settings except with Real Time Multiplier Changes in OS set to disabled and things are working fine with sleep resume up to 42x so far. I'll keep playing with things and report back if I ever find what setting seemed to be the trigger.... right now I'm thinking unstable OC (though fine for 2 hr prime95) or real-time multiplier change in OS being enabled. Weird.

Update: And the culpret seems to be that enabling real time multiplier change in OS caused the multiplier to lock to 16 after sleep. It's a bios option I only did after deciding to try the touchbios program, which became buggy and crashed every time I tried to start it after only a few uses. I can't think of any reason to enable this outside of trying a windows-based overclocking program so I won't miss it.