I built my pc a few months ago and ive had this problem since day one. I dont think its software related because it occured when I hd vista and its happening even now with windows 7 (64 bit).
The problem is this: whenever I try to put my pc in sleep mode it goes a bit crazy. Sometimes it immediately turns back on without me pressing anything, but usually it goes into sleep mode, but then takes ages to turn back on ( and i mean ages... well in pc terms...)
Here is my pc spec:
Intel core i7 920
Gainward gtx 285
Crucial 6gb ddr3 1333mhz
win 7 64bit
Any help would be very much appreciated, thanks.
First, download the latest BIOS for the P6T (0904) and flash it, as one of the recent fixes was "Fix system may hang after resume from S3". Now I'm not sure if they mean hang for X number of minutes, or hang permanently, but worth flashing for regardless.
If this is what fixes it, that would explain why moving to Windows 7 didn't fix the problem.
The other thing you can do is open a Command box [Run, CMD] and enter powercfg -energy. This will tell you what it sees waking up your system. It will drop an html document - typically at Users\yourname and you read it for the issues.
Bios settings can cause the system to wake up, add-in cards, sound cards, etc. I have seen the network device wake the system up from sleep. You have to go into the properties for the network adapter and there is a wake on LAN option - turn it off unless you are in a managed environment and want to do that.
Do make sure your BIOS is up to date. Win 7 seems to do a better job of finding current drivers than previous versions did.
i tried updating bios via support cd but get the message: error, support cd does not support this operating system, so i tried downloading the 0904 driver online. it downloaded as a rom file and i donnt know how to run it, when i click it it sais windows does not recoginise this file type..... any ideas?
Did you ever figure out a way to solve this problem?
I have a P6T SE has only recently started exhibiting a similar problem. Clearing the CMOS seems to solve the problem, but it has now come back a second time, requiring another CMOS reset. I'm wondering if the motherboard is going bad or if something else is wrong.