Possible problem with Gigabyte GA-P67A-UD4-B3

Associate
Joined
16 Mar 2011
Posts
9
Hi guys

Playing around with my new build (GA-P67A-UD4-B3 + i5 2500k) and have run into an issue.

Got it running happily last night at 4.5ghz - and set up 2 BIOS profiles, [email protected] and [email protected] (which I'd be using most of the time).

This morning, I put it to sleep and it wouldn't wake up - so I went into the BIOS (@3.3) - to make sure I had enabled the 'wake with mouse/keyboard). Did it, saved the BIOS and rebooted.

This is where the issue has started. It won't reboot. Power comes on, CPU fan spins then slows, no output from VGA... then it switches off - for about 5 seconds then powers up again. This cycle is just repeated...

I've cleared the CMOS jumper but to no avail. Currently got the battery out leaving it for a while.

I'm using an ANtec 300 case and there is no speaker - so getting no POST errors.

Any ideas?

Thanks
Si
 
I know there was a issue with one of the sleep functions before (B2 boards) and there was a BIOS update that fixed that. So I suspect there is a re-occurrence of that little sleep issue again.

Once you are running again it might be a good idea to update to the latest BIOS if you have not done so already.

Now to getting your system to boot.

Re-boot with only one stick of ram.

Once you are in the BIOS set to your desired preference, reboot and go all the way to OS. Once in OS power down and add the balance of your ram.

Your board should boot fine there after.
 
Well - left the battery out for an hour..... booted with 1 stick of ram and we are running again. There was a message though from the BOIS - a checksum error so it gave me the option to use 'last known' working BIOS.

It is the latest BIOS version - checked on G's website yesterday.

Thanks for your help!
 
Mine does exactly the same (as does that of many others, as a quick search will show) - i.e. cyclic restarts. I found the easiest way to stop it is to remove the power cable from the back, leave it for 5 minutes and then restart - should then come back up with last good bios config.
There is a beta F3B bios available on tweaktown but I have not tried it yet.
 
I am having a problem with the sleep S3. The system is stuck at 1600mhz when it resumes. I have tried to F3d bios, but no joy. Anyone had any luck with this?
 
Unless you are stressing your system the CPU-z will show 1.6GHz that is the EIST and speedstep kicking in. Stress your system, run super PI and keep a CPU-z open you will (should) see your CPU running at rated speed. Try it and post back if not doing so.
 
No, its stuck at 1600mhz for sure. When i prime 95 the temps dont go above 30C and cpuz reports 1600mhz, when i prime 95 on 4.6ghz temps hit 60C
 
When i have disable speed stepping and sleep the system at 4.6 ghz, it wakes at 4.6 ghz, but the voltages do not resume the OC setting (seeing this in HW monitor) and a core will fail under prime 95 in seconds
 
Ah right - I suggest you do a full clear CMOS and then flash your bios to F3 - remember to have your system at default clocks and volts.

LINK

It is the official and latest BIOS. You should then go into the bios and set up your S3 and S6 options. Or what ever wake or sleep settings you are using. Should be all good after that.
 
When the bios is set to defaults and no OCing it all works fine, but then again 3.3ghz doesnt require a change in voltage. It all seems to come down to the voltages not ramping back up after a resume. I have posts on the Gigabyte forums and a user responded with this

'This is probably caused by CPU PLL Overvoltages, this is disabled on resume from S3 so you probably can't reach the same multiplier as you could with it enabled before you put the system to sleep.
I am not sure if they will be able to fix this, or if it's an Intel Microcode fault? It's been a known issue for a while, so it may be something they cannot address.'

Thanks for all the ideas anyway, hopefully i can get this cleared up as i love this 2500K running at 4.6Ghz, but its a pain not having the sleep function :)
 
you should not need pll overrider for 4.5GHz - it should only be needed when going over 5GHz

Maybe try with it disabled.
 
bump,

Just to see if anyone else is having problems with this. I still cant find a solution and am trying with Gigabyte support to work it out.
 
Back
Top Bottom