Originally Posted by Talec
I would like a little help overclocking my Computer. I just Got a E7400 to replace my old Pentium D that died. I ended up replacing everything on my computer in order to figure out that it was my CPU that hit the crapper.
Here my Current Set up:
ATI X1950XT 512MB (Soon to be 4850HD 512MB)
4GB(2X2GB) OCZ 1066 DDR2
550W Thermaltake PS
3X 36GB Raptors
120GB Serial 7200RPM HD
Antec 900 Case
I would like some suggestions on how to get this up to set up to run at 3.4 to 3.6 GHz and run smoothly for 24/7.
Any help would be grateful. Thank You
Wow. You're awesome for providing these screenshots.
Based on what I see here, I say that before you do any overclocking, there are so-called "limiting" features in the BIOS that must be disabled. They are not overclocker-friendly. Disabling them will help you get the most out of your overclock.
- Spread Spectrum (disable anything that says it)
- Intel Speedstep, EIST, or Enhanced Intel Speedstep
- C1E Enhanced Halt State, or anything that says "C1E" or "C1" in the name.
- CPU Thermal Control, or anything that has options of "TM1", "TM2", and "TM1 & TM2".
After that, you can begin overclocking (and you can even find out your VID). But if you're using the stock CPU cooler, then I would venture to guess that 3.40GHz might be as high as you should go.
However, here are the tools that you need:
- Real Temp Some calibration may be necessary, so be sure to visit the Installation & Calibration Page for some awesome information/documentation).
- Orthos (for stress testing. It's Prime95, but with a better GUI and it lacks the features in Prime95 that overclockers don't use) Run the Small FFTs test for about 12 hours or so. Then when you're focusing on your memory, run the "Blend" test for like 6-12 hours (run these tests while you sleep, while you're at work/school, etc.)
- OCCT This is another stress testing tool. The "OCCT: CPU" test is very similar to Orthos. It has the Small Data Set test, which is the Small FFTs, the Medium Data Set, which is the "Blend" test, and the Large Data Set, which is the Large FFTs test. But most importantly, this program has a Linpack test. This stresses the CPU much, much more, and it also creates 10-15Â°C more heat. If your chip can pass like an hour or two of Linpack without overheating, then you know everything is good. But still do the other tests.
Beyond that, I say just do what FieryCoD and mtbiker003 suggested. And Broken Pixel has a good idea there too.
But in general, there are various ways to overclock. For example, I like to go straight to an overclock that somebody else is getting and then tweak from there. For example, I saw somebody getting 4.0GHz with 1.280V with their E8400, so I did the same thing. After some testing, I discovered that mine actually needs 1.320V to be truly
stable (and I mean stable with the Linpack test in OCCT. Otherwise, I only need 1.304V). Yeah, that saved me a ton of time.
Another method is to first find the lowest necessary core voltage to be stable at stock speeds. After that, gradually increase the FSB in tiny 10-20Mhz increments until it's unstable, and then increase the core voltage until it's stable again. And then start creeping the FSB speed up again until it's unstable, and then bump the core voltage up again, repeating this procedure until you're satisfied or something. And then when you're ready to call it a day, run a 12-hour Small FFTs test, then a 1-2 hour Linpack, and if it passes, then you're good. But the temps need to be watched too. But more on that later. Oh wait, before you call it a day, you should run like 30-minute Small FFT stress tests and like 15-minute Linpack tests to perform quick little checks after each tweak. And if you have nothing but time on your hands, than even a 1-hour Small FFTs test can be considered a "quick check" (as well as like a 30-minute Linpack test).
Another method is to crank the voltage to the highest "safe" voltage (such as 1.3625v), and then see how high of an overclock that will get you.
Either way, BSOD's and other failures are really good because they help you know when it's time to increase the core voltage, or back off the overclock a little.
Finally, I just want to say a few words about overclocking the memory: try to see if you can change the Command Rate (CR) from 2T to 1T
. You may have to increase the voltage from 1.8V, or you may have to increase the CAS# Latancy (CL) to 6. Either way, you'll feel a performance gain, and it's worth a try!!
That's as much as I can think of right now. As I said: more later.
But welcome to OCN, Talec. If you want your system in your signature like the rest of us, then just follow these simple instructions:
- Click on "User CP" on the black bar at the top (alternatively, click "Quick Links", then choose "User Control Panel" on the third dark bar down from the top of this little menu).
- Click "Edit System" that's located on the Left side in the User CP.
- Fill it in as thoroughly as possible. The more details you can provide, the better.
- If you have more than 1 system, then use "Add System".
- When you're finished, you can press Enter in almost ANY of the fields for the System (alternatively, click "Save Changes" at the bottom). Please note: there won't be a confirmation page. It'll just save it and bring you back to the top of the page.