Official Core 2 Duo E7200 thread

[Xvys]

While the E7200 might be binned lower than E8000's, I'd be surprised if all these bad o/c's were due to crummy cpu's.

I find the most common roadblock to o/c, is the ram...or trying to run the ram at too tight of timings (4-4-4) with too low of voltage. Even if the ram is rated 4-4-4, I would set timings to 5-6-6-18 with 2.1v while testing. This should remove the ram as a o/c'ing roadblock, then you can concentrate on increasing the FSB and cpu voltage.

According to Intel documentation, the maximum recommended voltage for the Wolfdales is 1.3625v. Any voltage above that can lead to cpu degradation and shortened life. The maximum recommended FSB Termination (VTT) is 1.115v. 1.2v is overvolted, although some motherboards only go that low.

Most of the bios settings have little effect on successful o/c's to 4.0GHz or even 4.2GHz...other than, cpu voltage: 1.3625v max; ram voltage: 2.2v max (but I run mine at 2.0v and would not go above 2.1v); and depending on your m/b, the Northbridge voltage could be increased to 1.4v or even 1.55v for stability. You could also kick up the Southbridge voltage a notch if it suits your fancy. I enable Load Line Calibration (cpu voltage damper) to reduce vdrop and use the NB .61x ratio. I would keep most the remaining bios options in their default settings.

One trick to speed up your computer is to enable "Transaction Booster, or Performance Level", which at the "2" setting improves my memory latency by 30% (Performance Level 6 rather than the stock 12). Also changing to the 400MHz bootstrap improves my ram latency nearly 5% over 333 bootstrap at the same frequency.

[blizzisu]

Been running prime stable for an hour at 8.0x400(3.2ghz) using 1.392v after vdroop. Looks like uppping the voltage allowed me to get past the FSB wall of 370. My temps are at 82c though so i'm going to try dropping the vcore voltage down.

Currently testing for Prime stable at 9x400(3.6ghz) w/ a 1.368 vcore after vdroop. Temps w/ my original model Ultra 120 w/ a low db fan are maxing out at 78c.

[thehinge1]

Doh! I meant to type "1100".... my mobo adds 2MHZ no matter where you set it, then the same extra 2MHz disappears in windoze, cpu-z, etc.

Think bios is correct you cannot run 550FSB and 1000mhz it has to be at least 1:1 divider on ya mobo...

[Shrekogre]

Nice results. have you tried 7.5x533? for 4.0ghz?

can't get it stable on 500fsb. don't know if due to x48 or cpu

[blizzisu]

Been running prime stable for an hour at 8.0x400(3.2ghz) using 1.392v after vdroop. Looks like uppping the voltage allowed me to get past the FSB wall of 370. My temps are at 82c though so i'm going to try dropping the vcore voltage down.

Currently testing for Prime stable at 9x400(3.6ghz) w/ a 1.368 vcore after vdroop. Temps w/ my original model Ultra 120 w/ a low db fan are maxing out at 78c.

I like to keep my temps and voltage low, as this computer needs to last me at least 2-3 years so I am currently trying to find my max clock using 1.248 vcore after vdroop. Testing 8x400=3.2 ghz now.

[hawk999]

aw i'm still stuck at 3.4ghz

[Hazaro]

Purchased a E7200 for friend.

Q743B016
VID: ???

What I do know is that it clocks for crap.

This thing would not BUDGE over 3040 Mhz stable for ORTHOS on 1.3V load. Kept returning a rounding error. Temps were down, but this thing did NOT want to clock at all.

Pumping volts into it didn't help much either :/

[blizzisu]

Purchased a E7200 for friend.

Q743B016
VID: ???

What I do know is that it clocks for crap.

This thing would not BUDGE over 3040 Mhz stable for ORTHOS on 1.3V load. Kept returning a rounding error. Temps were down, but this thing did NOT want to clock at all.

Pumping volts into it didn't help much either :/

What motherboard are you using? With my P5Q Pro I was able to set everything to Auto and run at 9.5x333=3.17ghz. Have you tried that?

Currently I'm running it at 366x9.5=3.477ghz. I was able to do this with all auto settings as well. CPU-Z shows core voltage of 1.256v after vdroop when running full auto.

[Riggs]

Wow, that sucks.....

[4n70n]

Just purchased E7200 (Q744B016) SLAPC. And this is my quick test validation...i don't know stable or not. Bump the vcore to 1.4 :
Validation

[roadie]

From what I've seen, many chips with B in the middle of the batch number don't seem to be clocking too well.

[blizzisu]

Just purchased E7200 (Q744B016) SLAPC. And this is my quick test validation...i don't know stable or not. Bump the vcore to 1.4 :
Validation

I can boot into windows just fine at 4.0 ghz as well. It is when I try to validate that it's Prime stable for more than an hour that I start getting rounding errors.

[mojado]

My 24/7 in testing....




http://valid.x86-secret.com/show_oc.php?id=406161

[Krelin]

Got mine E7200 today, too bad I have to wait at least a week for the PSU to complete my budget rig... Remember'd about the whole batch gambling-thing only when I already held the CPU in my hands. Got a Q814, afaik, that should be pretty ok, right?

[Jakalwarrior]

I made a seperate post but I guess I will add my results here for when people dig.

Vid 1.12 - Batch was SLAVN I "think". I was too excited to write it down but I tried to remember it.

3.8ghz @ 1.232, stock FSB, stock chipset, stock everything else. Posts past 4.0ghz but SATA craps out completely (think the PCIE lock on the board doesnt work right).

[thehinge1]

I just wanted to update that I finally got over my 'nothing more than 1.40vcore' knicker-twist and am over halfway thru a 1hr OCCT run at 1.4125 in bios, 1.34 under load with LLC disabled temps seem reasonable so hopefully it will make it thru more tests. Without tuning the ram to the new frequency it did 12.734 1M superpi with AV & everything else running on XP64.

I settled on a 1.30625vcore/LLC off/1.23v loaded 24/7 setup with 500fsb/DDR1200 at 7.5 multi at 3.750G.

I'm glad I did not keep that C0 stepping E8400, but an E0 is looking good for 4.5GHz+ so far

[hawk999]

i can't not go to 3.6ghz on low voltage

[Swatrecon_]

Alright, story time.

I went over to a friends house whose rig I directed (I told him what to buy) and another friend put it together. Well, when you want something done right, do it yourself. I rearranged the cables to improve air flow (what little there was). It's in a CoolerMaster RC690. The front fan wasn't plugged in, so no air flowing there. All the PSU cables were just shoved in front of it, in a big bunch. I ran them around the back. But the best part of all:

I attempted to overclock it, because that's what you do, right? Well, I ran coretemp and it came up with some crazy number like 102 degrees celcius!?!?! I was like "No, that can't be right." Well, it was. I opened up the case again and looked at the stock Intel Heatsink that was on and only one of the pins was even in. IT WAS JUST HANGING THERE!!!! So, I pushed all the pins back in and set everything back up and checked coretemp and it was around 60 degrees, a lot better. I didn't have time to reseat it plus I didn't have any thermal paste.

Anyway, he had been playing games like this and it never crashed once. That's pretty impressive. Apparently he played The Witcher for hours and it never skipped or stalled, anything. I was watching him playing it when I first got there and I can witness to that. It's crazy, I couldn't believe the toughness of this chip.

[oohms]

One reason these chips dont clock as well is because they aren't soldered to the IHS, resulting in worse contact. Mine was running linpack at 88 degrees, 3.6 ghz, 1.35v

I have taken off the IHS and im just prepping to install it again, with watercooling... hopefully this will see me get much better temps + overclocks

[carajean]

Ok quick update on my situation after my E7200 died.
I went out and got a tuniq tower 120 yesterday slapped it in my system. Instantly went to 3.8ghz pretty stable. Im running orthos now as I type this. Here is the KICKER though, my temps at full load are getting to a max of 67 degrees. I know that temp is a little high for this particular cooler. What should I do?? I have the fan facing the rear of the case also.

[hawk999]

Ok quick update on my situation after my E7200 died.
I went out and got a tuniq tower 120 yesterday slapped it in my system. Instantly went to 3.8ghz pretty stable. Im running orthos now as I type this. Here is the KICKER though, my temps at full load are getting to a max of 67 degrees. I know that temp is a little high for this particular cooler. What should I do?? I have the fan facing the rear of the case also.

hi there met what is ur voltage settings??

because i try to reach at 3.6ghz

it need 1.45vcore and 1.35v nb core and the temps are good idle is 30-34 load 50-55 degrees my board is Gigacrap aw it's gigabyte ep45-ds3r

tnx bro

one thing why did ur e7200 died?

[eternaljammer]

I can't wait to get my 7200 in! I hope I get a good one.

[hawk999]

I can't wait to get my 7200 in! I hope I get a good one.

hehehe i hope u get one..becuase my 7200 was so bad

[carajean]

1.34 voltage reading from cpu z
1.35 in bios
1.4-1.45 NB voltage

My proc died by a fluke accident if you read back a couple pages its all discussed there. ( sorry just got home from work kinda lazy right now)

[Frodin]

One reason these chips dont clock as well is because they aren't soldered to the IHS, resulting in worse contact. Mine was running linpack at 88 degrees, 3.6 ghz, 1.35v

I have taken off the IHS and im just prepping to install it again, with watercooling... hopefully this will see me get much better temps + overclocks

Please let us know how it goes! I have an E7200 that does 400x9,5 @ around 1,35v reaching 80C fully loaded on watercooling, been thinking of decapitating it too