e6300 poor overclocking

Lupus

Lupus

Lupus

Associate
Joined
13 Aug 2003
Posts
100
Seems I got a lemon :(

I put it into a DS4 with the matched pair of 1Gb Geil PC6400 with a Scythe Ninja. Initially it was about 52 C idle. So I took the heatsink off and redid the paste (I'd initially put the paste on the cpu, not heatsink, when I removed the sink there was only a little paste on it ie. poor contact).

Anyway, afterwards the idle temp was about 34 C with load (prime95 running on each core) about 48 C.

I just started overclocking, following the Gigabyte board guide on this forum, but so far the results are awful. Upping the vcore to between 1.4 and 1.45 ends up with a load temp of 60-65 C. The computer has crashed on the higher clocks I've tried, such as 400x7, 350x7, 400x6.

Does anyone have any advice please? I was really hoping to get some decent overclocking from this (like almost everyone else has managed), but I'm not sure what to try now.

I bought all these components (and more) on Monday. Do you think I might be able to exchange it for another even though it's not broken?

I'd appreciate any advice (relevant to this issue; I already know about avoiding yellow snow) :)
 
I havent gone that high on the voltage just yet

ive got the ds3 instead of the ds4, but my sig says it all
it might be the ram not likeing the higher bus speeds, assuming x2 multipler on the ram

put 1.35v on the vcore
put 2v (+0.2v) on the DDR
put +0.1 on the MCH
then start at about 380x7 then slowly increase it

Im still a novice but thats what i did, and am happy with it. If someone can confirm my method
 
Last edited:
For reference

Originally Posted by WJA96
OK - I don't think this should be a problem.

I would definitely check out the CPU fan though as the last screenie shows it stopped. A stopped CPU fan probably isn't good.

Anyway - lets assume that your PC is just very cool and the motherboard has stopped the CPU fan all by itself (mine does).

Reboot the PC, press the DEL key to get into the BIOS.

Once in the BIOS, arrow over to 'LOAD OPTIMIZED DEFAULTS' and select that. It will ask if you are sure, confirm that you are the PC will reboot.

Use the DEL key to get back into the BIOS again.

Go to ADVANCED BIOS FEATURES and select that.

Set the following to Disable;

CPU Hyperthreading
CPU Enhanced Halt (C1E)
CPU EIST Function
Virtualization Technology

Press ESC to come out of that menu.

Go to the Motherboard Intelligent Tweaker (MIT) and select that.

Set CPU Host Clock Control to Enabled

You will now be able to change the CPU Host Frequency.

As you were already at 2.4GHz Set it to 333 to start with.

Now set the PCI Express Frequency to 100

Now select System Memory Multiplier

Set that to 2.00. Your memory will now happily overclock with the CPU up to FSB of 400, which is 2.8GHz. After that the memory will also be overclocked.

Depending on your Memory, you may need to adjust the DIMM overvoltage control by between 0.1 and 0.3V to give between 1.9V and 2.1V.

Leave all the memory options on AUTO for the moment. It's not optimal, but it's not going to slow you down much either.

Press F10 to save and restart. If that's nice and stable - use SuperPi 1M places as a quick test, then go up 5MHz.

That should be stable. The most common mistake I see is people over-clocking the RAM by increasing the System Memory Multiplier when they should be decreasing it.

Give that a go up to 400MHz FSB in 5 MHz steps and let us know how you get on.

If it goes too hard, the system will auto-reset and let back in at the last settings that worked, so don't worry.

PLEASE DON'T INCREASE THE VCORE VOLTAGE AT THIS POINT - IT'S NOT NECESSARY and it's the only way to damage you processor.
Click to expand...
 
Cheers.

Just tried those suggestions(there is no option about hyperthreading for me). I already updated the bios to F6 and installed the latest chipset drivers, which I forgot to mention before.

I've got it running at 340x7 (2380 MHz). I had to up the vcore a bit to get it to boot to windows with this (1.35v).
To get it to boot to windows at 350 required upping the vcore a few notches more, but wasn't stable, so I moved back down. Also tried going up to 400x6, but couldn't get it to boot to windows.

Not sure what else to try now, was really hoping to hit 2.8GHz (at the least; was aiming for 3GHz+) :(

Any thoughts?
 
Have you actually tried resetting the whole thing and starting over?

Also - your reported temperatures are very, very high for that cooler. Are you sure it's tightened down properly and evenly? BE CAREFUL - don't take a spanner to anything, please!

What is your case airflow like? I have found the DS4 can suffer from high chipset temperatures if the case cooling is bad.
 
I would also be concerned about the voltages you are using (they will contribute to the high heat load) as most people can do 400x7 without altering the vCore.

I definitely think that either the RAM divider is wrong or you have changed the RAM settings in some way. In either case try a full CMOS reset and start over. And do check that the BIOS changes have actually been saved as at least posting on these forums has indicated that the user thought they have changed something but the system had not saved it properly.
 
I've set the ram system multiplier to 2 and the ddr2 overvoltage to +0.3v. Set the MCH and FSB overvoltages to 0.1V (also tried OCing before upping them).

That's all I've done to change the ram settings.

Both cores are pretty much the same temperature, with a 1 C degree difference at most, both idling about 32 C stock idle and 43 C stock load. The heatsink seems to be on properly as I've tried pushing it down a bit while watching the temperatures and there was no change. Also tried it without the side of the case on and there was no noticable difference.

I set the bios to load optimized defaults before I'd started OCing again. Using a Lian Li PC7 with the 120mm fans that came with it (one in one out). The airflow is fine I think. Got the 120mm Ninja fan blowing through the heatsink towards the fan on the back of the case.

Each time I go to the bios, all the settings seem to have been saved correctly, couldn't spot any discrepancies. I'll try a CMOS reset and start again, hopefully that will help.
 
Can you post the FPO/Batch of your chip please (its written on the box). Least we'll have a rough idea of what sorta chip you're working with.

1.5v is a bit to much for 3ghz. Its FAR FAR to much for 2.6. If you're chip is that bad then I'd be really shocked. Most 6300's should do 3ghz on ~ stock voltage, maybe a touch over.

Work up slowly. Find a stable point on stock vcore first. That should give a decent idea of how well the chip clocks. Then, work on upping vCore and FSB from there. It's MUCH easier to find a stable overclock when you have a stable point to reference from.
Reset CMOS defaults, set the memory to whatever ratio gives you 1:1 running and manually set your ram to its rated timings. Probs worth giving it + 0.2v as well. With default vCore, start upping the FSB.
 
Did you load optimized defaults after you flashed the bios? If not, try that.

Also, have you set your ram timings manually? If not, hit ctrl+F1 on the main bios screen and then enter MIT, it should then allow you to set the ram timings (4-4-4-12). Also make sure you're PCI-E frequency is not on auto, but set to 101.
 
Just reset the CMOS (left the jumper on for over 10 mins) and loaded optimized defaults. Booted up, all was ok.

Then disabled the stuff previously mentioned, upped the voltages as said and set the ram timing to 4-4-4-12 with multiplier of 2. And changed the settings to those suggested in this thread.

At stock voltage the maximum I can get is 345MHz FBS (which I've got it at now). Going to 350 causes the comp to either not boot into windows, or to reset soon after. Upping the vcore a notch didn't help with that.

The code on the box the cpu came in (OEM) is *CP-135-IN

Been awhile since I've overclocked (barton 2500), but I had good results on my last system. So I'm not totally new to it :)

I'm open to other ideas.
 
Just a thought, take out one ram stick and try to overclock with only one stick installed. If you still have probs, try the other stick. A few ppl here, me included, have a few probs with the geil ram (I had to rma my first set). If still no joy, set the ram timings to 5-5-5-15, try that and post back.
 
Good call pieman.

I set the timings to 5-5-5-12 and ran memtest86, letting it run through all the tests, which resulted in 3 errors. Then removed one stick, tried 350 MHz and it rebooted again, so took that stick out. After gradually working my way up, I had it boot into windows at 490 MHz, so a bit of an improvement there :). But I've got it at 430x7 at the moment.

Unfortunately though, it seems the heatsink isn't sitting as snuggly as it was: the idle temps are now about 47-50 (vcore is still at stock) and pushing down on the heatsink will drop it a few degrees. Guess I'll have to reseat it again (sigh), which is difficult due to the size of the thing. Probably just take the whole mobo out again.

So it seems it was one stick of ram that was the problem, I'll see if I can get that exchanged.
 
are you sure all the clips are down properly?
I love the eclipse/mirage cases removable tray as you can fit the cooler and get all round it before putting it in the case!
 
Just put everything back in. I suspect I just pushed the clips in last time till they clicked, and didn't turn them to lock afterwards. My idle temp is now about 39 C and load is about 54 C. Still to do longer stability tests, but I'm feeling better about things now. If it proves stable here I'll see if I can push it further, since I've got more room experiment now.

Thanks for the help all, much appreciated :)
 
You must log in or register to reply here.
Back
Top Bottom