New build problem with GA-P35-DS3P

[EdibleTarget]

Hey guys, two problems.

I put together a Q6600 + GA-P35-DS3P system about 2 weeks ago. It had been relatively painless until vista put the machine to sleep, and the computer wouldn't come back from sleep. I then proceeded to shut down the computer and start it up again. The computer would not boot, there was no display on the monitor, and I would hear a clicking noise that would seem to come from the hard drive. To solve this problem I figured out I could unplug the PSU from the power strip, wait 5 seconds, then plug it back in again. The computer would then start up fine. I have now noticed that this seems to happen fairly often, as it happens when my computer is plugged in for awhile and then cold started, but can also happen when it crashes and I try to boot it back up.

I have 2GB of Corsair RAM, and I was thinking of making sure that all those voltages are set to 2.1V, I did this and the problem was still there. Thats when I opened up CPU-Z and noticed my other problem. CPU-Z said that there are only 2 cores detected, although it recognizes that the CPU is a Core 2 Quad Q6600.

Is there a way to solve both of these? Or am I looking at an RMA?

Other specs:
620W Watt Corsair PSU
8800GTS 640MB
WD 400GB SATA HDD
WD 320GB IDE HDD as secondary
Audigy 2 Platinum
Windows Vista Ultimate 64 bit

 

[KyleY]

Hey EdibleTarget,
Resurrecting your old question here. Just wondering if you ever got your sleep problems figured out with this motherboard (I have the same one and the same problems). Mine will go to sleep, but sometimes it will reboot before finishing going to sleep. More often though it will sleep fine, but when I try to bring it back sometimes it comes back but most of the time it starts doing constant reboots where it doesn't even post until I turn off the PSU. Like you, everything else with this system is fine. S3 is enabled in the BIOS. Anyone else having similar problems? Anyone finding solutions? Thanks,
--Kyle

 

[EdibleTarget]

I ended up RMAing one board, and got another with the same problem. Sent that one back and got an eVGA 680i and the problems went away.

 

[Conroy9]

Originally posted by: KyleY
Hey EdibleTarget,
Resurrecting your old question here. Just wondering if you ever got your sleep problems figured out with this motherboard (I have the same one and the same problems). Mine will go to sleep, but sometimes it will reboot before finishing going to sleep. More often though it will sleep fine, but when I try to bring it back sometimes it comes back but most of the time it starts doing constant reboots where it doesn't even post until I turn off the PSU. Like you, everything else with this system is fine. S3 is enabled in the BIOS. Anyone else having similar problems? Anyone finding solutions? Thanks,
--Kyle

I have the same problem. I've only tried sleep once, and when I tried to resume, it went into a constant reboot thing. Cutting off the power and turning it back on didn't even help; I had to cut off power then wait 10 seconds before trying to power on again. I'm afraid to try sleep again.

I'm using the F9 bios

Any ideas?

 

[justsomeguy6575]

hmmm... well I have this board rev 1.1
I was using bios F5 and had no problems ever with sleep and resume. Just yesterday I updated to the newest F9 bios and then was not able to resume from sleep mode. Did the "constant reboot thing". When I flashed to F9, first thing I did was to go change the setting in the bios back to what I had them at before. Since my e6420 is OC'd to 3.2GHz. Well long story short I dicovered what the problem is, at least with mine. If you manually change the cpu voltage in the bios to anything but "Normal" or "Auto" it will not resume from sleep mode.

I reset my cpu settings all back to stock with nothing overclocked and if I change the voltage setting to anything but Normal or Auto it doesn't work. Even if I manually set the voltage to 1.35 which is default for my cpu it still won't work.

The F9 changelog on the website says something about changes super I/O code. I gonna flash back to the F8 bios and see if the problem still exists.

Hope this helps........

 

[justsomeguy6575]

UPDATE:

Did some testing.........
I flashed back to the F8 bios and still had the same problem. Couldn't resume from S3 sleep mode if the cpu voltage was set to anything besides "Normal". Just to check my sanity I then went back to the F5 bios, which I had been using without issue. Everything worked fine. So definitely a bios issue. I then flashed back to F8 bios to verify problem still existed and of course it did. Ok, so to flash to the F7 bios........ WOW...... it worked fine. Everything appears to be functioning correctly again. I can change cpu voltage and resuming from S3 sleep mode works fine.

So don't know if this may be anyone else's issue but I thought I'd post my finding incase it may help someone else out.

Just a small word of CAUTION however. If you are using a Yorkfield based cpu DO NOT flash your bios to anything before F7. If you do your board will no longer recognize your CPU, as support for those CPUS wasn't added till F7.

 

[Conroy9]

Thanks for doing the tests!

I emailed gigabyte about a month ago about this, and never got a response. I guess I'll try again with your added information and maybe they'll have a better idea of how to fix the problem.

 

[kaiserx]

@justsomeguy6575

thanks for the info I appreciate it. Was also having the same problem with p35-ds3p rev1.0 after flashing to F9 and I was gonna flash bios back to F4 but since you said that it works fine if vcore is set to normal, and it did I guess i'll just have to stick with this until they resolve this issue. Anyways I only needed 1.325v for my E6750 to get 3.4ghz, have to settle to normal(1.35v). I've also emailed gigabyte (before you posted) that I couldn't get s3 to wake after i flashed bios to F9 from F4 and gave them this forum link for them to know that this is not an isolated issue, they advised not to update bios if your not having problems (their way of telling me not to fix it if its not broken ).. well the reason is getting ready for yorkfield.

 

[ScurvyPig]

I think the sleep issue is a known Vista problem. Try googling "Vista sleep issues" and you will get a ton of hits on this subject.

 

[justsomeguy6575]

Yes Vista does have a known sleep issue. However I switched back to XP from Vista 6 months ago. Some people's problem may be related to Vista but Gigabyte definitely has an issue here that is separate from the Vista problem. It is a good point though.

 

[justsomeguy6575]

Conroy9 and kaiserx

Glad it helped.... gigabyte seems to release new bios fairly often. would be nice if they resolve it quickly. Would be curious to know if either of you get a response to your emails.

 

[kaiserx]

heres their response and btw im using xp and not vista. the problem is definitely their bios in my case.

Dear Sir,

Thank you for your kindly mail and inquiry. About the issue you mentioned, would you update latest motherboard drivers to see if problem remains.

In fact, new version BIOS can fix some known system problem or improve H/W compatibility. But, sometimes, new version BIOS is possible to cause new system problem with some specific system configuration. Therefore, usually, if the system works well with earlier version BIOS, we do not recommend you updating MB BIOS to the newest version immediately. Sorry for the inconvenience and trouble you encounter by our product.


At last, if you still have any further question or suggestion about our products/service, please do not hesitate to contact with us directly. We will try our best to help you resolve the problem ASAP.

******** Thank you for supporting Gigabyte products ***********

at least they responded the next day i emailed them.