Dualcore 3GHz vs Quadcore 2.33GHz

[dIggl3r]

nah, you should be able to OC to 3Ghz with the stock fan. 3.0Ghz is essentially the same clock as the X6850, and as far as I know they used the same HSF with those. You just set your FSB to 333Mhz (aka 1333mhz), and you shouldn't even have to increase your vcore.

You're maybe right, but Core Temp still shows 60 to 63 at full load NOT overclocked. I'm reading everywhere temp should be lower, cpu shouldn't go over 60°, another saying no more than 65°. You're sayin o/c'ed to 3GHz shouldn't raise the temp at all? Guess I'll retry, was afraid...

And thanks for the suggestions, I like the prices hehe.

[dIggl3r]

NEWS UPDATE

Using this overclocking tutorial: http://forums.hexus.net/hexus-hardware/1...nners.html
I can overclock to 2.7GHz but @ 3GHz the system freezes on boot up. So unless I find a specific tutorial for my board (since the other is for an Asus board), I guess I'll just chill. :confused:

[gEd]

did you tweak the voltages at all?
there is quite a lot of info on the web related to overclocking with this mobo.

Overclocking can offer a good speed boost for either 0 cost, low cost or high cost depending on how far you want to go. It does require some investment of time to research and patience to take the overclocks up a little at a time and then test using a program such as intelburntest

http://www.xtremesystems.org/forums/show...p?t=197835

as I mentioned earlier, you could just throw some disk space at the problem - you can never have enough disk space in a HTPC rig.

[dIggl3r]

I got no need for extra hard drive (well, that's not true, everyone does eventually), BUT I indeed capture ALL the local hockey games here, and encode them (plus other local tv shows). I encode almost everyday, so I assure you I need more juice, not hdd in that regard.

The tutorial I linked says to let the voltages on AUTO, so I did. The "problem" with that tutorial, is that it wants us to manually change the way the bios recognize the cpu itself. But with my bios, it can't be changed. So...

I will check into your link. Thanks.

[Deusxmachina]

NEWS UPDATE

Using this overclocking tutorial: http://forums.hexus.net/hexus-hardware/1...nners.html
I can overclock to 2.7GHz but @ 3GHz the system freezes on boot up. So unless I find a specific tutorial for my board (since the other is for an Asus board), I guess I'll just chill. :confused:

I'd never leave the CPU voltage to auto. It can/will ramp up the CPU voltage when it "thinks" it should, not whether it needs it or not. The CPU could oc to a certain level fine, but now it's fried because the motherboard auto-upped the voltage too much.

If you mess with it more, I'd set the CPU voltage to whatever the default is that I can't think of offhand and you'd have to look up, and then play with the motherboard settings. Could be the memory needs a little more volts, or the north bridge, or maybe the cpu or mb or memory simply can't go any higher. My Core2Duos are limited by the current motherboards and memory more than they are limited by themselves. ymmv, of course.

[dIggl3r]

There's no north bridge configuration menu with my bios, that could be the problem. (the turorial has a whole page about this, while I can't change a thing about this)

[johnsonx42]

I can overclock to 2.7GHz but @ 3GHz the system freezes on boot up.

You probably need to tweak your memory ratio then. It depends on what your RAM can do of course; you can start at 1:1 (which means your RAM will run at the same speed as your FSB) if your RAM is at least PC-5300 (aka DDR2-667) then 1:1 will be perfectly safe up to 333Mhz.

[dIggl3r]

You probably need to tweak your memory ratio then. It depends on what your RAM can do of course; you can start at 1:1 (which means your RAM will run at the same speed as your FSB) if your RAM is at least PC-5300 (aka DDR2-667) then 1:1 will be perfectly safe up to 333Mhz.

I did just that (as the tutorial says), memory was @ 1:1. By the way, I suppose it's normal, after I change the FSB speed *up* and I save/reboot, the system shutdowns completly by itself, then reboots. When I raised from 266MHz to 300MHz, all went normal, no special noise or anything. When I raised to 333MHz (9x333 = 3GHz), I rebooted, heard my cpu fan running at max speed and system wouldn't load. I quickly shut it down! Resetted the bios...

So, right now, I'm @ 2.7GHz. I tested everything for severals hours, the temps are the SAME than @ 2.4GHz. I'm just sad that I can't go for 3GHz, everyone saying everywhere I should be able to do it EASY...

[johnsonx42]

So, right now, I'm @ 2.7GHz. I tested everything for severals hours, the temps are the SAME than @ 2.4GHz. I'm just sad that I can't go for 3GHz, everyone saying everywhere I should be able to do it EASY...

Yeah, I can see where that would be frustrating. I suppose it is possible you've got a rare E6600 that doesn't oc well. Still, getting stuck at a mere 12.5% overclock suggests something else is amiss. Don't worry about the fan coming on full when your OC attempt fails, that just means the BIOS isn't initializing to slow down the fan.

Perhaps a little extra vcore would help, say 100mv? Also make sure Spread Spectrum is disabled. Upgrading to the latest BIOS can help as well.