Sign in with
Sign up | Sign in
Your question

OC Frustration - Can't get E4300 above 300MHz FSB

Last response: in Overclocking
Share
February 28, 2007 1:14:16 AM

Ok - I've followed wusy's guide. I've read a million threads. I've reseated my heatsink. But I can't OC my E4300 (on a P5B Deluxe with a Scythe Infinity) past 300MHz FSb. I'm currently running 20 deg C at idle. 45 deg C at 100% TAT load (60 deg C in TAT).

At 300MHz, I'm running 1.350 Vcore, all other voltages are auto. I've turned off C1E, etc. I bump it up to 333MHz (or even 315 MHz), and I get BSOD. I move my NB voltage to 1.55, Windowss doesn't even boot. I've relaxed my mem to 5-5-5-12 - Windows doesn't boot. I bump up my vCore to 1.375. Windows starts to boot then dies.

Any suggestions?
February 28, 2007 2:45:27 AM

Can you list out more settings. BIOS settings: RAM divider, vcores tried, vdimm, nb voltage, timing settings for RAM, etc.

I know you said your voltages were on auto.

You might try manually setting things as a start. I don't have alot of personal experience but I have done some good research, as I just ordered an E4300 not 3 days ago.
February 28, 2007 5:07:52 AM

I'm having a simmilar issue, except for me it's around 350.
(motherboard = asus p5n-e sli, which can supposedly hit 500, though all I want is 400 ;)  )

and I'm trying to lower the multiplier in order to get the fsb to 400 (1:1 mem ratio) but I can't, even though I can run the CPU at a higher clock speed with lower fsb higher mult.
Related resources
February 28, 2007 10:53:36 AM

If you need help please list out more specs than just your mobo. I need RAM model, voltages, CPU, the whole shebang. :wink:
February 28, 2007 11:32:48 AM

Quote:
I'm having a simmilar issue, except for me it's around 350.
(motherboard = asus p5n-e sli, which can supposedly hit 500, though all I want is 400 ;)  )

and I'm trying to lower the multiplier in order to get the fsb to 400 (1:1 mem ratio) but I can't, even though I can run the CPU at a higher clock speed with lower fsb higher mult.


Heard there is a wall with 350. If you try bumping right up to 400 from 350 you will run stable again.
February 28, 2007 11:34:07 AM

More information certainly helps. My hardware is listed in my sig - here goes:

1st attempt
FSB = 266MHz
vCore = Auto
vMCH (I assume this is the NB voltage) = Auto
SB Voltage = Auto
vDimm = 2.15V
Timings - 4-4-4-12 - It also works at Super Talent's rated 4-4-3-8
Result = Stable

2nd attempt
FSB = 300MHz
vCore = 1.350V
vMCH = Auto
SB Voltage = Auto
vDimm = 2.15V
Timings - 4-4-4-12
Result = Stable

3rd attempt
FSB = 315MHz
vCore = 1.350V
vMCH = Auto
SB Voltage = Auto
vDimm = 2.15V
Timings - 4-4-4-12
Result = BSOD after windows loads

4th attempt
FSB = 315MHz
vCore = 1.35V
vMCH = 1.55V
SB Voltage = 1.6V
vDimm = 2.15V
Timings - 4-4-4-12
Result = Windows begins to load, then PC reboots

5th attempt
FSB = 315MHz
vCore = 1.3625V
vMCH = 1.55V
SB Voltage = 1.6V
vDimm = 2.15V
Timings + 5-5-5-15
Result = Windows won't even load
February 28, 2007 1:32:44 PM

Put your PCI-E freq to 100-107
PCI freq to: 33
and lock it up (fixed)

while ocing put your ram to 5-5-5-12 and set ur Vmch to 1.5 and SB volt:1.6 and put your Vcore:1.35. then low down it too (if it enter windows and runs stable)
February 28, 2007 1:56:18 PM

Sorry - forgot to mention that I changed the PCI-E Freq to 105. PCI was changed to 33.3 MHz.

Waleed - from what I can tell, I've already tried your suggestion, to no avail.
February 28, 2007 2:18:21 PM

I've got the E4300 on a Gigabyte DS3, and I needed to use a much higher Vcore to make anything happen. I started at 1.45 and stepped it down. I needed about 1.40 to get a speed of 330. By simply leaving ALL the voltages on auto, I had the best success setting my comp up for a long term overclock, and not necessarily the highest possible speed.
February 28, 2007 3:29:09 PM

my freind gets e4300 at 400 fsb setting the multi at 8x at default voltage he uses s3 rev 3.3
February 28, 2007 6:28:06 PM

Thanks for the info. I'll try the higher voltage tonight and post back my results.
March 1, 2007 3:32:34 AM

What is your memory ratio? that is very important. Super Talent made the switch to Elpdia (or something close to that) for the RAM banks, in which case your RAM divider becomes very crucial.

Honestly, I think your vdimm is a bit low. It is just a hunch at this point and I have very little to support this honestly.

Get back to us with the results of your vcore hike and the mem ratio. :D 
March 1, 2007 12:28:22 PM

Still no luck. Not sure what I'm doing wrong :-(

The memory ratio is 1:1. SuperTalent rates their memory at 2.2V, but my Bios only has setting for 2.15 and 2.25V. I've been hesitant to go to the 2.25 setting. Memtest ran for 4 hours last night with no errors (that was at the manuf. rated 4-4-3-8 timings).

6th attempt
FSB = 333MHz
vCore = 1.45V
vMCH = 1.55V
SB Voltage = 1.6V
vDimm = 2.15V
Timings + 5-5-5-15
Result = BSOD

7th attempt
FSB = 333MHz
vCore = 1.475V
vMCH = 1.55V
SB Voltage = 1.6V
vDimm = 2.15V
Timings + 5-5-5-15
Result = BSOD
March 1, 2007 1:15:45 PM

I have my e4300 at 356FSB, 1436 QDR for 3204MHz at 1.49v. Although not a super-high, 4.0GHz overclock, it is a 78% overclock and that is above the average for Core 2 Duo CPUs. Check the actual numbers for Core 2 Duo ( agood data base is over at HardForum) and you'll see what the norms are.

I wanted 100% but she hit a wall at 3204 as far as Orthos stable. I can boot it at 3387MHz and run SuperPi to 1M but that's about it. At first I was disappointed but if you look at the numbers and consider what this chip is doing it really is phenomenal. The best overclocker I ever had was a AMD opte 165 that ran at 3006 MHz or a 68% overclock. Hand picked stepping and watercooling to get it there.

This e4300 is new silicon and is not handpicked as I have no idea on what stepping is worthwhile (and this one definitely is not the best stepping) at this time but it still pulled a 78% overclock. $179 CPU at 3204 MHz is pretty sweet when you really think about it.
March 1, 2007 1:17:18 PM

Bear in mind that some chips just won't OC well. It's rare, but it's more likely to happen with the Allendale than Conroe.

Try the suggestion made by GeminiReaper. There are rumors of some of the higer-end chips having OC "Holes" where they just won't operate. It would'nt surprise me if you find these holes in the Allendales as well. You might have hit a hile. Try skipping it over by bumping up your FSB and dropping your multi.

One more thing: drop your southbridge voltage back down a bit. This is the least affected chip in an OC, and is also the chip with the least amount of cooling.
March 1, 2007 2:02:24 PM

Yeah do remember that not all chips can his these speeds.
Nor all Mobos.
Nor all memory.
Some people get high OC's.
A lot do.
A lot don't though also.
I'm sort of sick of everyones.
ALL C2D will hit 4Ghz ez in air.
Because they won't.
March 1, 2007 2:49:03 PM

Thanks everyone for your suggestions and comments. If I can't hit a high OC, then the world isn't over. My system still screams for what I need it to do. If 300 is my wall, then so be it. I really can't complain about my 50% OC.

I'll be off work tomorrow so I'll be able to play around with things a bit more and see what happens. Thanks again!
March 1, 2007 2:53:20 PM

Two more things (though they may be a stretch)

Would running Vista be my problem?

What about switching my memory to the other channel/banks?
March 1, 2007 3:07:07 PM

I have heard that Vista might be pickier about OC's.
That may be part of it.
I don't think switching banks would help.
So long as they're in correct ones now =P
March 1, 2007 3:15:52 PM

Nice setup you've got there. And damn you for your opty OC! I've only got to about 2750mhz and thereafter there be monsters.
March 1, 2007 3:33:51 PM

Quote:
Nice setup you've got there. And damn you for your opty OC! I've only got to about 2750mhz and thereafter there be monsters.


What stepping is your Opte? The CCBBE chips generally hit 3.0. I'll preface that with that is on water or some other higher end cooling. Air cooling usually limits the best Optes to 2850MHz to 2900MHz. You gotta go high end cooling to get to that magic 3.0 :D 

To Pink Caddy and Will14-
Are you cooling the chipsets actively? The chipsets on my P5N32-E SLI Plus run pretty hot but are on water now. Many are finding that active cooling of the chipsets is necessary to push past certain walls.
March 1, 2007 6:00:57 PM

My guess......and this is all it really is, a guess. 8)

Your NB needs some airflow to cool it off, although your NB voltage isn't terribly high.

Bump your ram up another notch and drop the timings back down to 4-4-3-8. The ram won't fry because of .05v. Alot of modules take an extra .2v and don't cry fowl (but some like lower voltages.... who knows).

The entire OC process is guess and check, plain and simple.

I'd try the hole theory. Try some random FSB settings, 320, 340, 350, 305 maybe you'll get luck and the worst thing that can happen is you lock up and have to reset the CMOS. HOWEVER, word of warning, OC's have been known to corrupt OS installs in rare instances, so be careful.
March 1, 2007 6:25:39 PM

Currently, I've got Asus' NB fan clipped on the the heat sinks (though I think I bent one of the fins in the process.

So here's a few things I'll try, given everyone's suggestions - 1 - Bump up vDimm to 2.25V. 2 - Try a different FSB speed (I'll go with 320 to start). 3 - drop my multiplier down to 8. 4 - scrap Vista (glad I didn't activate it yet) and put on XP w/ SP2.
March 1, 2007 6:30:45 PM

Sounds like a plan.

My E4300 came in today, so I will let it rip once I get home.
March 2, 2007 2:32:06 AM

So I went out of order - I've got XP installed now. As much as I liked the look and feel of Vista and that I had a new PC and that was a new OS, I think it's holding me back too much. I want to OC more than I want the same old games with a new look (and I've already mastered that cut rate Texas Hold 'Em game that came out as part of an "update" a couple of weeks ago).

Once I get my system built, I'm going to try my previous OC attempts again to see if Vista was the culprit.
March 2, 2007 12:19:59 PM

Good deal.

My E4300 came in, as I said, and I had nothing but problems last night but none really related to the CPU. First I erased the wrong hard drive so I erased my back up and my data.... yeah that was a sad moment, but nothing mission critical. Then I couldn't install XP because of hal.dll corruption issues on the hard drive... that took a few hours and 2 full low level formats to get rid of. Then I got into Windows, installed all my drivers, ClockGen, CPU-Z, CoreTemp, and Smart Guardian (came with the board) and guess what? SmarGuardian shows the cores at 40c and CoreTemps shows them at 24c idle.... explain that one.

I am inclined to believe CoreTemp.

As for OC'ing.... after taking 5 hours on the above, plus the actual build and lapping, I didn't get to OC really. Tonight will be a good deep dive into it along with much documentation.

Back to the topic... I hope vista was your issue... we shall see! 8)
March 2, 2007 12:28:31 PM

hey i have also seen that if NB gets too hot it does not let fsb to get high
March 2, 2007 1:21:17 PM

I had to take care of the 7 month old this morning, so I didn't stay up too late. I'm getting the system built now and will OC later today.
!