Only 3% overclocked and already cant boot? E6400

[SPL Tech]

The equipment I have is:

CPU: Core Two Duo 2.13 GHz. E6400
RAM: 2 GB. Corsair 800 MHz. XMS2 DDR2 (dual channel configuration)
GPU: X1900XT 512MB Connect3D
Mobo: Gigabyte GA-965P-DS3
PSU: 535 watt Enermax Whisper II
HD: 250 GB. Seagate Barracuda 16 MB.
OD: 52X DVD±RW
Monitor: Hanns-G 19" DVI LCD widescreen

This is my first time trying overclocking. I have read many articals and thought I would try it.

I started overclocking the CPU in the BIOS tonight. I got to only 2.232 GHz. and I couldn’t boot. However I know that if I leave the computer unplugged for a few seconds the mobo woill disable the overclocking and let me reboot. So I did that and entered the BIOS as soon as booted up and reenabled the overclocking and Windows started fine overclocked at 2.232 GHz. Then after I ran all my benchmarking tests and such I restarted again to overclock more. This time I choose 2.264 Ghz. I saved it in the BIOS and once again I could not boot. So I unplugged the computer again to revert to OEM settings and rebooted into the BIOS. And once again I reenabled the overclocking but this time I increased the vcore from 1.325 volts (stock voltage) to 1.33125 volts (one click up) and saved and exit. The computer restarted and once again I could not boot. So I unplugged the computer again and reverted to OEM settings and I just left the overclock off and that is where I am now.

So what’s going on? I talked to people with this same processor that said they did not even have to touch the vcore until 2.8GHz. I am but barely 5% OC’ed.

Maybe I am doing something wrong. This is how I went about things:

I started out at 2.175 Ghz. I ran PC Wizard 2006 and benchmarked the CPU. I wrote down the Whetstone (FPU) Wheitstone (SSE2) and Dhrystone results. I then keept the program open to monitor CPU temp, voltage and loading.

Then I ran two instances of Prime 95 (one for each CPU) and ran the torture test on each and choose the in-place large FFT’s for max heat consumption. I ran the program for about 4 minuets with both CPU’s loaded 100% and recorded the average CPU temperature.

Then I close Prime 95 and open CPU Stability Test 6.0 and test the computer for stability for about 4 minuets.

It was stable every time.

As far as the steps I took in overclocking and the temperature recorded I got:

1: 2.175 Ghz., 47-48 C
2: 2.207 Ghz., 48-50 C
3: 2.232 GHz., 49-50 C
4: 2.264 GHz., 50-51 C

So whats wrong?

[SPL Tech]

I raised the vcore by two steps and the RAM by +.1 and still nothing. So its not a voltage problem... hmm... wtf... this problem is anoying. :(:bang head :confused: :bang head :confused:

[(Clanger)(DOA)]

well what speed are you running the ram?? Also could the sticks of ram that you are using be D9's in that case DS3 dosent like them. Try to update you BIOS if you havent already....

[SPL Tech]

The RAM is automaticaly OC'ed by the BIOS. The more I increase the FSB of the CPU the more the RAM is OC'ed. But with the CPU at 2.264 GHz. the RAM is at about 840 MHz.

I am not sure if I have the D9's. How can I find out? All I know is its the Corsair XMX2 DDR2 800 MHz. dual 1,024 MB. sticks gameing RAM operating in a dual channel configuration.

[blockdoc]

I agree about updating your bios if you haven't already done so. It could be your RAM holding you back. Try running your memory multiplier at 2:1 and see if you can boot.

[Shelnutt2]

I agree about updating your bios if you haven't already done so. It could be your RAM holding you back. Try running your memory multiplier at 2:1 and see if you can boot.

Th lowest the DS3, and the lowest any P965 chipset memory divider is 1:1. Something about a chipset thing where you can't run lower dividers.

[malon]

Download the F8i (http://drivers.softpedia.com/progDownload/GIGABYTE-GAPDS-BIOS-Fi-beta-Download-21093.html) Bios, flash it and show results ;)

I have my E6400 @ 3.2 Ghz w/ Stock vcore.

[Shelnutt2]

Download the F8i (http://drivers.softpedia.com/progDownload/GIGABYTE-GAPDS-BIOS-Fi-beta-Download-21093.html) Bios, flash it and show results ;)

Im have my E6400 @ 3.2 Ghz w/ Stock vcore.

The offical F8 is also out, but people seem to get good results with the F8i as you suggested.

[jph1589]

Not sure I would suggest the F8I bios for someone who is just starting out and having trouble. I would recommend the production F7 bios from the gigabyte website. He just needs someone to walk him through the Motherboard intelligent tweaker page step by step and check it all first. I have the time, PM me and I'll give you a hand.

Two questions.

What bios version shows up on the post screen?

Is the PCIE set to auto on the MIT screen?

Note...you have to hit CTRL F1 on the main bios page to activate all the advanced options.

[jph1589]

The offical F8 is also out, but people seem to get good results with the F8i as you suggested.
I just checked all the Gigabyte servers and they have F7 as the latest. Was that a typo?

[jph1589]

That memory you have shows a default voltage of 2.0v. So you would need a +.2 on the memory voltage to be at that.

That being said, I've seen some people say that it need 2.1v to run at the SPD rated timings on that kit.

So that might be holding you back in addition to the PCIE if you haven't locked it at 100mhz.

[Shelnutt2]

I was wrong, there is no F8 official yet. I would go with the F6, over the F7. Not much of a release besides the F6 doesn't have the gigabyte boot screen where F7 and later shows you a lovely gigabyte image during booting.

[SPL Tech]

I got it to boot now! I installed the latest BIOS and things work good now. So far I am at 317 FSB / 2.528 GHz. and I havent touched a single voltage setting. :)

[jph1589]

I got it to boot now! I installed the latest BIOS and things work good now. So far I am at 317 FSB / 2.528 GHz. and I havent touched a single voltage setting. :)
What was the issue, if I may ask?

[/\\/3|2o]

What was the issue, if I may ask?

Wondering the same thing. Did you only change the BIOS to fix the problem or did you do something else as well?

[[SC]Ceasar]

I think he only updated the bios since he said: "I installed the latest BIOS and things work good now."

O well, good to hear that its going good now. :D

[(Clanger)(DOA)]

well i talked with him on Aim and the board came with F3 :S. He updated it to F6 and like magic it worked.

[Stratcat]

well i talked with him on Aim and the board came with F3 :S. He updated it to F6 and like magic it worked. Oh, absolutely!

A magic BIOS will nearly always work better than the non-magic versions! :shrug: :p

</end jk'ing>

~ Strat ~

[(Clanger)(DOA)]

HEY i like Magic BIOS's. They are trippy.:bday:

[SPL Tech]

I just updated the BIOS and it worked. I have the PCI-e locked at 100 MHz. the ram at 2.0 to keep a 1:1 devider and at the moment I am rollin in da hood at 345 fsb with stock voltages. :)

[greenmaji]

IDK.. it was pre-F3's that were the problem, maybe the Vdimm was defalt set too low with the F3's (IIRC that was still a problem with that ver.)
good to hear it fixed the problem, its just nice to know why ;)

[/\\/3|2o]

I just updated the BIOS and it worked. I have the PCI-e locked at 100 MHz. the ram at 2.0 to keep a 1:1 devider and at the moment I am rollin in da hood at 345 fsb with stock voltages. :)

Awesome. Im getting the same setup for christmas so its good to know these things.