The only suggestion I would make at this point is change Command rate in your ram timings from 1T to 2T. 2T is what is called for in your SPD JEDC specs for those timings and is more stable than 1T.
The 800MHz is correct. Remember you are running DDR3, which stands for Double Data Rate so 800 X 2 = 1600MHz
You should also see if there are any updated drivers on your Motherboard's web site http://www.gigabyte.com/products/pro...id=4965#driver
Thanks, essenbe.
Assuming that's tCMD in the advanced memory timings in the BIOS then I've just set it to 2 on both channels. Let's see how that goes...
All the drivers are up to date, I believe. Some of the Intel ones are from Intel's own site as Gigabyte seems a little slow to update.
They are all slow to update unless you have the latest chipset. And some are slow even then.
Hi, essenbe.
You may have read that I have two theoretically identical PCs both exhibiting the same problem.
I made the command rate change you suggested on PC#1 yesterday and I see that CPU-Z now reports 2T on the Memory tab. It's too early to say whether that's fixed the problem on PC#1 so to speed up testing I applied the same change to PC#2.
PC#2's BIOS reports 2T but CPU-Z continues to show 1T and nothing I've tried will get it to say any different.
So has the change taken effect on PC#2? Or is CPU-Z not reporting correctly?
I would be inclined ti think it hasn't changed or that your BIOS is Not reporting correctly.
Alan, My motherboard is an Asus, but we had a bad bios bug in the code at one point where the same thing would happen. We could change bios, but it would not transfer to the OS. After a lot of complaints, they finally were able to reproduce it and came out with an new BIOS file which fixed it. I'm just curious if your board may have the same thing. I would try to update my bios if there is a newer one, as long as you think the computer is stable enough to update it. If you get a BSOD during the update, it will take an RMA for a new bios chip to fix it. During the problem I had, I could update the bios with the same version I had and it would work fine until I saved everything and went back into the OS, then it was the same thing. But, CPUz is pretty much the standard everyone goes by to find their settings. I don't know of anything more accurate. I usually accept whatever CPUz says over anything else. Most in the Overclocking community do.
I've got it to take the 2T setting on PC#2 now - CPU-Z correctly reports it. The trick seems to have been a cold reboot: disconnect power, wait five minutes, boot, set BIOS, all OK. Perhaps when doing PC#1 I turned off the power for some other reason which is why it worked first time there.
Thanks for your continuing help. Now back to waiting...
That's pretty strange. I have an Asus board and sometimes it works the same way, a reboot won't take it. I have to completely shut down and it takes a cold boot to load things. Crazy isn't it.
Three weeks further on I thought it time to post an update...
The 2T command rate change unfortunately had no effect on the stability: both machines would still randomly crash on entering or during sleep.
As you know, I've long thought this is a problem related to sleep so I started using hibernation rather than sleep. Since then both machines have been perfectly stable.
This says to me that the hardware doesn't properly support sleep. As an experiment I disabled C6/C7 State Support and went back to using sleep but within a couple of days there was a BSOD.
So I'm now using just hibernation and all is well. Of course, this is a workround not a solution and even though these machines wake quickly from hibernation it would be good to have the even quicker benefit of sleep. If there are any other ideas I'd really appreciate them.
Alan, do you have the latest BIOS version for your board? At default settings, is C6/C7 enabled or Disabled? This has been a problem since Haswell and actually since Sandy Bridge was released. Haswell just added more C states. Your PSU says it is Haswell compliant which means it should work. With most boards, the problem seems to be that the CPU will wake up, but some of the drivers do not.
Quote