I can get a stable 4.0 ghz OC (14-18 hrs Prime95 Blend setting) on my e8400 with the following settings (Gigabyte DS3L mobo):
CPU Bios VCC = 1.300 ----> CPU-Z voltage reports 1.248 under load, 1.264 at idle
PC1066 DDR2 @ 2.14v BIOS -----> 2.1v through Everest (or like SW monitoring utility). OZC recommends 2.1-2.2, so I went with 2.1 if proven stable.
MCH= 1.2v in BIOS. Can't find a utility to report voltage in Vista.
Note: I don't push my MCH higher than 1.2 because intel spec says don't go above 1.21 AND I don't have physical space to zip-tie on a fan. Stability seems unaffected when running FSB at only 445 mhz with 1:1 divider (890 mhz RAM clock).
So if all this is stable under stress testing, why does my BIOS reboot the PC 4-6 times before deciding to reset to defaults IF and only IF the system has been powered down for a couple hours? It doesn't happen when the system has been off for only a few minutes or even an hour. Also, the MOBO is brand new so it isn't the battery (if the board even has one...) and also, when I don't overclock and stick to auto-detected settings, this problem doesn't happen. It has to do with overclocking. Mild overclock (from 3.0 to 3.6 ghz by bumping FSB from 333 to 400 mhz) DOES NOT trigger this problem, either. It seems to be only after hitting 4.0 ghz.
Help. Please.
CPU Bios VCC = 1.300 ----> CPU-Z voltage reports 1.248 under load, 1.264 at idle
PC1066 DDR2 @ 2.14v BIOS -----> 2.1v through Everest (or like SW monitoring utility). OZC recommends 2.1-2.2, so I went with 2.1 if proven stable.
MCH= 1.2v in BIOS. Can't find a utility to report voltage in Vista.
Note: I don't push my MCH higher than 1.2 because intel spec says don't go above 1.21 AND I don't have physical space to zip-tie on a fan. Stability seems unaffected when running FSB at only 445 mhz with 1:1 divider (890 mhz RAM clock).
So if all this is stable under stress testing, why does my BIOS reboot the PC 4-6 times before deciding to reset to defaults IF and only IF the system has been powered down for a couple hours? It doesn't happen when the system has been off for only a few minutes or even an hour. Also, the MOBO is brand new so it isn't the battery (if the board even has one...) and also, when I don't overclock and stick to auto-detected settings, this problem doesn't happen. It has to do with overclocking. Mild overclock (from 3.0 to 3.6 ghz by bumping FSB from 333 to 400 mhz) DOES NOT trigger this problem, either. It seems to be only after hitting 4.0 ghz.
Help. Please.