Post your E4300 Overclock!

Page 19 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
vdrop is the delta between bios and idle, and what worries me is the extreme vdrop my board has. I'm worried it might randomly spike and send me up to the voltage it's supposed to be at and kill my cpu :?

At least from what you just said I can pretty much confirm it's a motherboard issue that my cpu can't hit 3ghz orthos stable

Since you have an AMD build I can say with all likelihood if anything it is a vdrop problem (ty for the explanation), I just don't remember seeing a vdroop on an AMD processor.

I see you concern and it is well placed, however the voltage is going to have to really shoot up to kill your CPU. Spikes in voltage, while not good, aren't likely to kill your CPU in an instant unless it is massive. I would stress it every way you know how and monitor the voltage, if it doesn't spike I would probably relax a bit.

That is a strange issue though. I wonder if my DFI board had that problem lol.
 
Unfortunately, I am new to overclocking and therefore not sure I did everything right, but my E4300 seems to need more than stock voltages to even reach 2.7 GHz.
Please tell your E4300 batch. Mine is Q649... mounted on a P5B Deluxe
I need 1.525 vcore in bios, idle real 1.5 and load 1.48 volts real to reach 340 FSB. There's about a 0.05 volts drop on load. I managed to decrease temperature up to 65° on cores with rseating my HSF, 4 times and changing the way I apply hermal compound.

Like said above, E4300 new batches look hot and voltage hungry. If I try once to remove the IHS from mine, maybe I can lower temperatures and voltages to reach the 3 GHz. My system is very stable on 16h Orthos session, so I won't care about volts / temperature unless system hangs up

Coretemp reports temperature ... 70°C

At that speed, and a so small vcore, you're too hot, even for a bad CPU batch. It looks definately like a cooling issue. Use coretemp 0.95 and not 0.94 (which underestimates the core temps by 15°). Either the thermal compound is not well applied or your IHS is really concave. An easy solution is to put a virtual layer of thermal compound on HSF and IHS surfaces and increase the amount in the center area of IHS (thin line in the middle of IHS, about 2/3rd of its large). This should compensate your concave IHS without voiding the warranty of CPU if you lapp it

Good luck, give us feedback. We need it all owners of these new bad E4300 batches
 
I don't think that would fry the mobo, otherwise how else would anyone ever use a multimeter to monitor the vcore?

Also, now I am getting a weird video error. I can't figure out if it is driver related or card related. I am leaning towards card related.

Randomly my screen blacks out for a second and then comes back. It does this on a literally random basis and just started recently (no idea why). At times the whole display locks up entirely and forces the machine to crash. When I turn it back on it gives me the "Windows has recovered from a serious error." It says it is driver related but I don't think believe that because I have been using the same drivers for nearly 8 months.

I really don't want to have to purchase a 8800GTS.... I was holding out for the 89 series.
 
Ok, thanks for your replies.

As you suggested I reapplied the thermal compound and the cooler (yes, it's the intel box cooler). Now it is definitely running cooler. I hit 70 C easily after just a few seconds with 2.4 GHz before, it's now in the mid 60s (61-66C) while running orthos for 10 minutes.

I had the RAM multi set to 2.5 only at 266 MHz FSB. When I tried 333 MHz it was set to 2.0. Currently it's set to 2.0 (1:1).

I have run into 2 little problems with the c2d-guide, though.
First, I cannot find the RAM timing settings. There is a so-called "High Speed DRAM DLL Settings" option, but I can only choose between option 1 and 2. And I cannot find a way to see what these options exactly do. The manual just says that these option set the RAM timings.

The second problem is about the voltage settings. The guide says I should set vMCH and vFSB to 1.55 V and 1.4 V. The problem is that I can only set "Normal" and some "+0.xx V" values. So which value is "Normal"?

Furthermore I cannot find the PCI frequency settings. PCIe is set to AUTO.

vCore is currently set to 1.375 V @ 266 MHz FSB (not optimized, just to be save). While running orthos CPU-Z says vCore is 1.328 V.

My PSU is nothing special. Bought it 2 or 3 years ago in a local store.

As I cleaned the CPU I could read Q644 written on it. What exactly does it mean?

I hope that answers all the questions. Thanks for your help.
 
I have run into 2 little problems with the c2d-guide, though.First, I cannot find the RAM timing settings. There is a so-called "High Speed DRAM DLL Settings" option, but I can only choose between option 1 and 2. And I cannot find a way to see what these options exactly do. The manual just says that these option set the RAM timings.

You may have to change the configuration from "by SPD" to "Manual"

The second problem is about the voltage settings. The guide says I should set vMCH and vFSB to 1.55 V and 1.4 V. The problem is that I can only set "Normal" and some "+0.xx V" values. So which value is "Normal"?

vFSB stock voltage is 1.2v

VMCH stock voltage is 1.3v

Furthermore I cannot find the PCI frequency settings. PCIe is set to AUTO.

You need to lock down PCIe, change it to 100. PCI I think is already locked, I don't have the option on my board either.

vCore is currently set to 1.375 V @ 266 MHz FSB (not optimized, just to be save). While running orthos CPU-Z says vCore is 1.328 V.

It seems like your MOSFETs are getting a bit hot causing excessive vdroop (.05v is abit much)

As I cleaned the CPU I could read Q644 written on it. What exactly does it mean?

Means it was manufactured during week 44 of 2006.
 
Thanks for the info.
What can I do about the vdroop?

As I cleaned the CPU I could read Q644 written on it. What exactly does it mean?

Means it was manufactured during week 44 of 2006.

I read that the E4300 was manufactured differently depending on the date. Is this date good or bad?
 
That is a good point. I really don't know... we need an electrician. hehe

I updated the drivers to the May 31 Forceware... the problem hasn't gone away but time will tell.
 
Thanks.

I found the RAM timings: have to press CTRL + F1 in the BIOS menu. That activates the advanced mode.

Now I have set the FSB to 333 MHz, vMCH and vFSB to +0.2 V and vCore to 1.4 V. While running orthos both cores go slightly over 70 C, but after 2 minutes it throws an error. According to CPU-Z the vCore is idle 1.376 V and load 1.344 V.
I am not sure whether I should up the vCore even more. I want to use that CPU for approximately the next 3 years, so it should at least survive that time. I read somewhere that it is not save to set it higher than 1.4 V.

Before I used FSB333 I set it to 300 MHz @ 1.375 V and vMCH/vFSB = +0.1V. No error occured in orthos (at least till I stopped it after 15 minutes) and the temps were around 69 C. How save are these values?

Any help appreciated.
 
Figured out something about my video crashes. It seems they are driver related and progressive. nvlddmkm is the file that goes nuts in Vista and it screws with your video display and eventually migrates back into XP some how some way, I am not really versed on it, I just skimmed some posts. What hasn't seem to be figured out is if it can truly be solved or if it has any ill effects on the card itself.... makes me want a X2900XT...
 
Thanks.
I am not sure whether I should up the vCore even more. I want to use that CPU for approximately the next 3 years, so it should at least survive that time. I read somewhere that it is not save to set it higher than 1.4 V.

Before I used FSB333 I set it to 300 MHz @ 1.375 V and vMCH/vFSB = +0.1V. No error occured in orthos (at least till I stopped it after 15 minutes) and the temps were around 69 C. How save are these values?

Well, looks like, your E4300, is like of most of new E4300 chipsets.
Anyway, the answer is simple:
At these settings, you don't need to increase you vFSB/vNB/vSB/vICH, it just wastes power

If you want more power, vcore is your only way. I could get stable at a nice speed: 326x9= 2930MHz and a vcore 1.45. It is a good compromise between speed/vcore/safety
You would need less vcore if your mb has lower vdrop than mine (0.05v). With a vMod, I would fix my vcore to 1.48v and it will get me a nice 3.06GHz speed...

Also, once you find a setting that lasts Orthos a while, stability must be checked for a 16h run. 4h run is good, 8h is excellent, 16-24h run is rock solid
 
wait for the r650 or r670, I hear the r670 is the dual gpu version of the hd 2950xtx

I am trying. The monitor started cutting out so much it damn near gave me a siezure. I still have a lingering headache. I really want to hold out until Yorkfield/G90 but my guess is I will succumb and buy a Q6600 and a R650/G81.

From what I understand it is a driver conflict from a dual boot scenario so I am formatting my entire system except my data drive. I am doing long formats because I don't want a single file to exist. We shall see what this gets us.
 
set your PCIe freq to 102 and PCI voltage to +.1 (some people report this helps stabilize voltages on the board and also resolves the issue of OC settings disappearing on some boards with f10 and f11 bios) Also try 334 for your FSB. For some reason the DS3 likes 334 more than 333. Im running the same week chip as you (see sig) and its been awesome.
Check your box that the CPU came in and it will give you a full batch number. Does it fully match mine?
 
Formatted everything and installed only Vista.... and that F'in error came back. If develop epilepsy I am suing nVidia. lol

Now I reformatted, yet again, and I am just installing XP this time.

Pax: Q644A744 is my spare E4300, I may switch it out to see if I can break 3.4GHz because my current E4300 requires 1.4375 (1.4v load) for 3150 MHz. Though I have seen Q644's top out at 3375... oh choices to be made.
 
I tried an orthos run last night. When I woke up it had been running for 9h 15min without any errors or warnings.
FSB = 300 MHz, CPU Multi = 9, vCore = 1.35 V, other voltages at default, temps ~ 68 C.

It is just insane that the extra 33 MHz (FSB) for reaching 3 GHz are so unstable - even at 1.4 V.

Well since I just want my RAM to run at its max specs, I tried another configuration: FSB = 337 MHz, CPU Multi = 8, RAM Multi = 2, vCore = 1.325 V (that's stock if I am not mistaken), other voltages at default. That's 2.7 GHz and my RAM runs at 674 Mhz with 4-4-4-12 timings.

I have run some benchmarks with this setup and orthos for 30 minutes and so far no errors occured. Will run orthos next night to see how stable it really is.
Maybe I will lower the vCore a little bit more, if possible.

I am more or less happy with the power of the PC. I paid ~ 100 Euro for the CPU. Now, it is slightly better than a E6700 (stock), which costs ~ 260 Euro (atm). I think this is ok.

Edit:
Well, it's Q644 A472. And I don't have a 965P-DS3, but a P35-DS3R. But I will definitely test these settings later.

Thank you for all your help.
 
Well, at first I wanted to buy an E6420, but after reading some articles and posts in this forum (especially this thread) I decided to get an E4300, because everyone said, that this CPU is very good, considering it's overclocking capabilities, although I stopped reading after page 5.
I never thought it would turn out to be that much of a difference when buying a newer model. Maybe I should have kept reading, than I had probably tried to get an older model.

And the board, well, I want to be up-to-date with my hardware (at least the time I buy it). Additionally the socket might still be used in 2 or 3 years and with this board I have support for 45 nm CPUs. This way I do not have to buy a new board in case I want do upgrade my CPU.
 
I updated my overclock
Really wanted real time DivX encoding at good quality
New overclock and voltages, see my signature
I'm hi on the vcore, but maybe I'm lucky: my chip isn't concave, I had to change my rear case FAN for an Antec TriCool 120mm FAN (up to 79 CFM), and a Scythe Kama Bay 5" with a silent 120mm fan for front case intake. I also moved the 3 HD so that some more space between them.
That way, I lowered my incase temp to near ambiant (5 °C decrease). It gave me more room for this overclock at 1.58 vcore, and Orthos load at 69-73°C on TAT

Maybe it's high, but as no one really knows how these temps are true, I will live with it. I'll give feed back if I see any deterioration overtime in overclock stability
 
Okay heres my 1st Overclock.

DS 3 rev 3.3 F 11 / E 4300 Conroe

Case ; Silverstone LC 17 S Flat HTPC case 1x 90 mm front, 2 x 80mm back
PS has 120 mm fan
Cooling ;
AC 7 Pro
NB Cooler TT Extreme Spirit II


CPU Core Speed – 2720
FSB 340
CPU Multiplier x 8
CPU-FSB Divider 1:1
Memory timing 5-5-5-15

MCH OverVolt +.1
VDIMM OverVolt +.1
Pcie Freq 102
PCI OverVolt + .1
Vcore stock 1.325
Other Voltages Stock/ Auto

Passed 8 Hrs of Orthos.

TAT and Core Temp Readings
Idle 45
Load 57

I was told by using 8 x multiplier instead of 9 x, CPU uses less Power for V Core thus lower Temp. True ?

My memory is rated DDR 2 800 and I want to take advantage of it.

How far can I raise FSB on these E 4300 ?

Your suggestions to push it further welcome.
 
orthos4hr3.jpg


e4300@3.2Ghz 1.55 vore w/Thermaltake p120 EXtreme AS5
eVGA 680i SLi MB
4GB G. Skill DDR2800 55515@2.0v and 44412 ( only 2 atm, I loaned 2 to a friend)
Xfx 8800GTS 320 MB Vid (10700 3dMark06@ 626/969)

This will not even boot to bios @400x8 but is fine at 355x9

SuperPi is 18.5 for 1M
 
hey just to keep updated, I raised FSB to 356 x 8 = 2.8xxx now.
45 C idle and Load (Orthos) 60.
V core at 1.375.

I like to lower V Core, but it wasnt stable earlier.

So, what V Core are you guys running at ?

P-S ; I want to keep this PC for a couple of years :lol: before the chips die from overheating.

thanks