Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
I have been working with OCing some of these new CPU's and I like to use SiSandra cpu arithmatic benchmark to compare where the OC is actually sitting at. I have done 3 E4300 cpu's and 1 E4400 cpu thus far and have a E6420 on the way from newegg right now.
After reading this thread I must say I am kinda disapointed in what I may receive. I would like to see your SiSandra scores in Arithmatic CPU Benchmark to see if the 4Meg cache makes any difference.
Here is an example of a OC I did on one of my E4300 CPU's.
E4300 C2D @ 3.331ghz 1.50vcore
E4400 C2D @ 3.500ghz 1.65vcore
EVGA 680i SLI 122-CK-NF68-T1
2 gigs OCZ SLI Ready 1066 mhz ram
1 EVGA 8800GTS 640 Meg ACS3
Thermaltake Armor Water cooled case
2 10,000 RPM Raptor 150gig HD
Dell 24" LCD 1920x1280 resolution
I've never seen a system that was 4hour+ stable on Orthos, that couldn't take a run through 3dMark.
On the other hand, I've been able to completely run through a full trial assault on 3dMark, and crash with Orthos in under an hour.
I think at some point, all of these requirements are overkill.
I can boot at almost 3600Mhz on air.
I can run Super Pi at 3540Mhz.
I can run 3dMark at 3500Mhz.
I can run Orthos 4+ hours at 3460Mhz.
I can run 24/7 at 3400Ghz.......
We can go on for days.
Stick with a simple, stress-testing method, and be done with it.
.
Mr. White: My cpu was loading around 64, 65 C when I did my 3.4ghz @ 1.5375v I think yours at 57C is not a temperature issue. Some chips just can't hack it at the higher FSB / voltage.
The rules for the overclock thread says at least 4 hours on orthos. So for the sake of being on the database, you should be ok. But would you really want to run it at that speed knowing it could crash on your under extended heavy load?
Well, I'll try with just a little more Voltage and see if it can do around 10 hours. Off course the question is really whether Orthos failed after 7 hours as it could just have failed after 1 hour? If so, I will certainly lower the FSB a little. However, I rarely (read never) use my computer for 7 hours in a row at full load.
Maybe it was not a CPU temp issue, but a NB temp problem. With my current room temp at 26-27°C the NB idles at 37°C and reaches around 41-42°C under load. Whats your opinion?
How are you guys reading NB temperatures? I'm running a DS3 rev 1.3 and using Everest Ultimate Edition - is it the "motherboard" sensor?
Just curious.![]()
That's completely up to you. Is it 'stable' enough to pass a 4 hour session of Orthos to enter into the 'stable' settings database? Sure.
Not too sure I would be happy with current settings if I knew my system 'could' crash as shown by your screenshot.
What's the matter, got a system that isn't completely stable when you throw more things at it to test it other than a 4 hour stability test?
FFS, how much harder is it after you have your Orthos run or even before your Orthos run to boot up another program to see if your system can make it through it? If your idea is to compile a load of settings that other people with similar systems can use as a benchmark and guide, would it not make sense to attempt to at least achieve complete system stability?
Any OC'er knows that you can run prime or orthos all day without touching anything else, boot up something 3D and there goes your system. But to each their own I guess.
You missed the part where I said it passes your suggested test and failed on the one recommended by the thread starter.
I'm not usually up for a pissing contest, but since I will be spending 64.2769 hours trying to fulfill the system test, stress, time-limit, program variations that you require in order to finally deem a system, "Stable"......I'll have a little extra time on my hands to get into it with you if that's what you prefer.![]()
I agree man. All this testing for stablilty is sometimes ridiculous. I don't have(nor want to spend) the time on running all these benchmarks just to prove stability. I'd much prefer spending my time encoding or playing a game then watching Orthos run for 10 hours. I didn't spend money to run benchmarks.
I know this sounds crazy but have you tried underclocking your ram to 400mhz using 1T instead of 2T and even lower timmings.
Yah the ram speed IMO doesnt make that much of a difference as far as performance its only a factor in where you want to OC at 1:1 etc. Some people say that sync the ram with the FSB gives best performance which I tend to agree with, however I have seen some VERY high OC's 5ghz+ where they have their ram at 400mhz lowest possible latency and 1T timing and they seem to swear by it.
I'm baaaaaackk....just posted this up in the Intel OC thread.
I'm taking back the E6420 crown...for now...moving to a D-Tek Fusion this week, went from P5B Deluxe to DS3 to push higher.
User Name: dnottis
Stability: 6 Hours Orthos
CPU: E6420
OC: 3680 Mhz
Stepping: 6 B2
Week: L709
Code: A171
Vcore: 1.550 (BIOS), 1.49v actual
Cooling: Water
Cooler brand/model: Thermochill PA120.2, Swiftech Apogee, D5 Pump, MCW60, 2x 75CFM 120s @ 12v
Motherboard: Gigabyte DS3 rev.1, C1 chipset
Bios Version: F11 Bios
Operating System: Vista x64, XP SP2
RAM brand: OCZ 2GB
RAM rated speed: 8500
RAM actual speed: 920Mhz
Latency: 5-5-5-15
![]()
Your only running 1.49v of actual vcore to hit 3680? If so, you should have no problem getting that thing 3700+++ stable.
I have to use about 1.58v after vdroop to get 3680 to be stable. Im curious to see what results you can get using about 1.55-1.58v.
Nice work!
If your load temps are 53C do you really think a different water block and tubes is going to make a difference? 65C I beleive is the Intel ceiling on the C2D although after all the CPU's I have done I am lead to beleive its 90C.
Why arent you guys going higher with your Core Voltage 1.6 vcore is pretty common when trying to find your ceiling for OCing shoot several of my CPUs were at 1.65 (With non-conductive liquid cooling).
C2D are really some mind boggling CPUs for OCing, cant wait to get back home this weekend and play with my new E6420 and contribute some real hands on knowledge about them.

thats really nice, it crashed in orthos after 2hrs so gotta tweak it more when i get time. I cant wait to get my ram back from OCZ and see what my superpi is at 3-3-3-8-1T timmings. They have been out of stock for a week and unable to replace it waiting on their RM Manager to call me back im hoping I can get him to give me 2 gigs of their Flex water cooled DDR2 which would be really nice.
Dnott what are all your voltage's at I set my ram and core volts and let the system auto the rest I have a feeling thats where I need tweak it to get it stable because my Temps are VERY low compared to the E4400 and E4300 at 1.65+ Vcore at full load i hit up to 80C with them and only hit 65C with the E6420.
thats really nice, it crashed in orthos after 2hrs so gotta tweak it more when i get time. I cant wait to get my ram back from OCZ and see what my superpi is at 3-3-3-8-1T timmings. They have been out of stock for a week and unable to replace it waiting on their RM Manager to call me back im hoping I can get him to give me 2 gigs of their Flex water cooled DDR2 which would be really nice.
Dnott what are all your voltage's at I set my ram and core volts and let the system auto the rest I have a feeling thats where I need tweak it to get it stable because my Temps are VERY low compared to the E4400 and E4300 at 1.65+ Vcore at full load i hit up to 80C with them and only hit 65C with the E6420.
Updated entry.
I now have 2 entries, if that's allowed.
The first one was the uber-RAM speed version, this one is just for a nice, solid, stable overclocked CPU speed.
User Name: Evoic
Stability: 5+ hours - Small FFTs Orthos Beta
CPU: E6420 (Model L651B325)
OC: 3500Mhz
Stepping: 6 B2
Week: L651
Code: B325
Vcore: 1.53v (in BIOS) 1.49v (Actual)
Cooling: Air
Cooler brand/model: Scythe Mine Rev. B
Motherboard: eVGA 680i LT
Bios Version: P04
Operating System: XP Pro 32
RAM brand: PNY Value Ram
RAM rated speed: PC-2 5300 / 667Mhz
RAM actual speed: 673Mhz
Latency: 4-4-4-12
CPUZ Validation