EP45-UD3P Q6600@3.2 S3 mode reboot loops

[Chike]

This look like a BIOS problem to me, if it wouldn't reume at all might be settings, but if it resume once and won't resume the second than GB should look into it.
Still it might be work around it.
Compare ET6 settings see if anything changes after resuming from S3.

[Lsdmeasap]

You may need to try less Vtt and more ram voltage, or a combo of it all. Keep at it though and you will find the sweet spot.

tRD is blank in memset sometimes because it is disabled I do believe, this option can be disabled in the BIOS and I think sometimes that is what Auto does if you do not use performance enhance turbo or extreme with tRD in auto. When you see someone post a screenshot of Memset with auto tRD and it shows a value for tRD then they are likely using Turbo or Extreme Performance Enhance. This is not always the case though, but I have noticed it myself. As for the actual tRD disabled, that is just my assumptions because I know it can be disabled, and using a higher PE option seems to enable it again.

Same applies to X58 BIOS and B2B settings, if in Auto it will be disabled, but at least memset/cpu-tweaker now shows disabled when this is the case

[Gixxer1kr]

I'll try those later. Do you think this value is ok "MCH Core…1.100....1.36v"? I remember that setting helping others in the past but no one has suggested changing in this thread just curious.

[Lsdmeasap]

MCH Core should not need to be 1.36, that is a lot. For 3.2Ghz and 8GB of ram, maybe you need 1.26-1.32 but maybe not. I would not start with 1.36.

What I would do if I was you, is use ONLY one set of that memory and sell the other so you can buy a matched set. You can resume from S3 properly with one set only right? You probably would have to lower some voltages maybe but I think this is a large part of your issues

[Chike]

Originally Posted by Gixxer1kr

I'll try those later. Do you think this value is ok "MCH Core…1.100....1.36v"? I remember that setting helping others in the past but no one has suggested changing in this thread just curious.

The reason I have never mentioned is it look like you already set it manually, and with the amount of memory I assumed you have already tweaked this option.

[Gixxer1kr]

I got home and decided to start from scratch. I redid all my settings to AUTO. I set as follows:

Robust Graphics to - Auto
CPU Clock Ratio -8
CPU Freq - 3.2ghz
CPU Host Freq - 400
PCI Express - 100
(G) MCH Freq Latch - 400mhz
System Memory Multiplier - 2.00D

Everything else to Auto. I then tried to resume and it worked the first time only. So, I went back in and change only my DRAM from Auto to 2.180v. After that I rebooted and was able to resume sleep 3 times in a row.Going to try for a 4th time ! !

[Lsdmeasap]

Nice to see you are getting somewhere!

I do suggest you shut down often between resumes, multiple resumes only could end up causing you issues possibly

[sbarton]

Originally Posted by Sunburn74

If you're trying to get your system stable for s3, give it up. I've got a system that can run 24hr prime runs overclocked and it still can't s3 sleep. Its a bios issue, not an user issue. The only thing you can do is pressure gigabyte and hope they finally get off their asses and fix the problem thats plaguing 50-75% of their boards.

If you really really want s3,the only things you can do are

1)back your overclock down by lowering the fsb to where s3 is still working. It usually is around 400 fsb. It'll give you alousy overclock, but s3 will still work.

2) buy an MSI, ASUS, or Ibit board. Asus boards occasionally have overclock s3 problems, but for the most part they are few and far between. MSI and Ibit have almost non existent issues.

but again man its not you. nothing you can do in your bios will fix it. its a hal detection, windows sum, bios engineer thing that plagues pretty much every p45 board gigabyte has out on the market.

cheers.

^^ This

Your spinning your wheels and 6 pages is only glossing around the real issue. There is a serious BIOS or manufacturing issue with GB motherboards that leads to this issue when overclocking certain CPU combinations. Trust me, I've read virtually every post from every forum imaginable and this is the cold hard truth. Regardless, Its probably something that can't be fixed or it would have by now.

[toslat]

I also have same issue and have had to turn off my overclock.

Its obviously a BIOS/implementation issue, and adjusting settings is like hunting in the dark for a work around.

Most disappointing is the fact that the issue has been around for so long, and yet there is neither a resolution, nor even a clear definition of the source of the problem. This is likely my first and last Gigabyte board. Will stick with ASUS and MSI.