Overclocking a E7200

[TridenT]

Asus Rampage Formula X48
Intel Core 2 Duo E7200
Crucial Ballistix Tracer DDR2 800 4x1GB ram

What do you suggest I put this thing at? I need detailed information because I swear, whenever I just put this thing off by .000001V it fails. It does minor overclocks great but it just can't get anywhere past 3.4GHz and that makes me really pissed off. My E6300 did better and it had a lower multiplier! So I am curious as to what you think I should do...

Also, I get a lot of different temperatures according to different programs.

2849MHz, about seven minutes into Orthos Blend stress. Real Temp 2.60 says Core Temp 50C. Core Temp 0.99.1 says Core #0 and #1 59-61C(TJ Max 105??? What?!) Asus PC Probe II says 49-50C. It seems that Core Temp 0.99.1 is wrong or both asus pc probe and real temp are wrong. What do you think?

Does upgrading my BIOS actually fix anything? (Seems it doesn't... I mean, I have used both 207 and 403... I had to flash back to 207 because I got boot sector errors on the actual BIOS themselves)

 

[nyker96]

btw, what's your distance to tjmax on ortho load just to get that outta way. you can see that in real temp. what's you current FSB at? I think running FSB 400 is easy one here with a little bit more juice. You need to give a bit more info here on your OC settings/volt/FSB/mem ratio etc etc.

 

[Extelleron]

The difference between the temp programs is just the TJ Max value. Realtemp and your ASUS program set the TJ Max for these 45nm CPUs @ 95, meanwhile CoreTemp sets it at 105. That is why CoreTemp will show a value 10C higher than the two other programs. When it comes to temps, there is no definitive authority, but I'd trust realtemp over coretemp for 45nm CPUs.

Are you having trouble with high FSBs or the chip itself? If your E6300 did 3.4GHz+ I'm assuming FSB is not the problem because that would require 500MHz or so. Meanwhile the E7200 should require <400MHz FSB to hit those speeds.

Are you saying that you cannot raise the CPU vcore at all?

Just make sure you have your RAM at 1:1 to eliminate that as a factor and raise the CPU voltage when needed... that is all that you really need to do, unless you run into an FSB bottleneck or something is weird with your setup. In terms of voltage you are clear up to around 1.35V and absolutely nothing above 1.4V.

 

[TridenT]

Here is a picture of the stuff. I did not set everything in this picture, a lot of it was on AUTO in the BIOS.
http://img236.imageshack.us/img236/3763/problemsgp4.jpg

I am unsure of what to exactly set the stuff to in the BIOS.

EDIT: Also it is running at 9.5x400MHz. It is just that throttle down thing that the CPU does in CPU-Z shows up.

 

[aigomorla]

Originally posted by: TridenTBoy3555
AUTO in the BIOS.

this is your problem

 

[Drsignguy]

Originally posted by: TridenTBoy3555
Here is a picture of the stuff. I did not set everything in this picture, a lot of it was on AUTO in the BIOS.
http://img236.imageshack.us/img236/3763/problemsgp4.jpg

I am unsure of what to exactly set the stuff to in the BIOS.

EDIT: Also it is running at 9.5x400MHz. It is just that throttle down thing that the CPU does in CPU-Z shows up.

The Bold part I edited is because you haven't disabled C1E and EIST in bios. You can disable it for now and later on you can enable it once you gain stability. Aigo is right about your AUTO settings. My E7200 as we speak is set at 9.5 x 379 = 3600 with cpu-z reporting voltage @ 1.232 @ full load. To me, I think your voltage setting to the cpu isn't causing instability, it's your ram timings, Ram voltage or NB holding you back.

 

[error8]

I need 1,37 V ( V core) in bios to be 3,8 ghz stable and 1,41 V ( in bios ) to be 3,9 ghz stable. Of course there are chips that can hit even 4 ghz on 1,3 V, but it seems that maybe yours is not.
Also, you are a bit on the high side with those temperatures. Change the cooler or something, since it seems unable to keep your temperatures down. 67 C in Real Temp with 1.3 V looks like a lot. I have 61 C with an aftermarket cooler at 1,38 V full load.
Loose the ram timings a bit.

Also, up the VTT voltage slightly, to 1,3 V or around that, but don't get over 1,4 V since you can burn it.

Your north bridge voltage seems quite good at 1,45 V and I don't see that it would help you getting it higher. Also, try upping the SB voltage a bit, maybe it will help. The thing is , I think that your chip clocks higher but with higher voltage. This seems to be the "problem".

 

[TridenT]

Alright, last night I had it at a very minor OC of 9.5x333... >_< I had it 1:1 ratio with my ram at DDR2 667, somewhere around 2.05--2.15V I think. About 2 and half hours in it gives me an error. I found this out when I woke up this morning. So I got, damnit! Then I go off to do another thing for ten minutes.. Come back and it has rebooted AND is at the fucking error screen. Where it bullshits about there being a bios corruption error or boot sector block problem. Something like that and it's a fucking piece of shit. You know why? Turn the damn thing off for a few minutes and power it back on, and it works perfectly again like nothing happened. It's complete BS!

 

[error8]

Maybe the ram is broken. Take a memtest and see if it gives you errors. Very weird situation there.

 

[TridenT]

Gaahhhh. CPU won't stay stable. I have to amp voltage to 1.4V for it to stay anywhere stable at 3800MHz.. But now the temp is just soaring. >_< What's really frustrating is the heatsink doesn't even feel warm at all. Makes me suspicious if I put enough thermal paste on or not or if the heatsink is making enough contact. I made sure the heatsink was making a lot of contact though and put a decent amount of paste on there.

 

[toadeater]

I got boot sector errors on the actual BIOS themselves)

There's no boot sector in your BIOS. That is your HD giving you errors for one reason or another.

 

[TridenT]

Originally posted by: toadeater

I got boot sector errors on the actual BIOS themselves)

There's no boot sector in your BIOS. That is your HD giving you errors for one reason or another.

Nope, it's the BIOS. Because I can't even press DEL to get into the BIOS. -_- believe me, I know if it is the HDD or not because those errors come AFTER I post. This comes before I can POST even or even access anything else. I can't do anything except insert a CD ROM with FORMULA.ROM or a USB Device with that. >_< It ends up loading the oldest BIOS known to man.

 

[Drsignguy]

Originally posted by: TridenTBoy3555
Gaahhhh. CPU won't stay stable. I have to amp voltage to 1.4V for it to stay anywhere stable at 3800MHz.. But now the temp is just soaring. >_< What's really frustrating is the heatsink doesn't even feel warm at all. Makes me suspicious if I put enough thermal paste on or not or if the heatsink is making enough contact. I made sure the heatsink was making a lot of contact though and put a decent amount of paste on there.[/q]











Just so you know, to much TIM can cause problems just as much....What was your last Stable OC? Maybe, 3.8 is pushing your chip and other hardware...Why dont you post your last stable OC settings and lets see where you can go from there.

 

[Drsignguy]

Originally posted by: Drsignguy

Originally posted by: TridenTBoy3555
Gaahhhh. CPU won't stay stable. I have to amp voltage to 1.4V for it to stay anywhere stable at 3800MHz.. But now the temp is just soaring. >_< What's really frustrating is the heatsink doesn't even feel warm at all. Makes me suspicious if I put enough thermal paste on or not or if the heatsink is making enough contact. I made sure the heatsink was making a lot of contact though and put a decent amount of paste on there.[/q]

Just so you know, to much TIM can cause problems just as much....What was your last Stable OC? Maybe, 3.8 is pushing your chip and other hardware...Why dont you post your last stable OC settings and lets see where you can go from there.

 

[TridenT]

Most stable OC of now is 333x9.5 at around 1.3V. (It may be higher, I can't remember) It hits pretty high on the temperature at full-load. Around 65C it peaks at.
I haven't crashed once from this OC and no errors.

I didn't put too much TIM, I put the right amount.