• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

How to Overclock Velocity Micro E2250???

jailben

n00b
Joined
Feb 4, 2009
Messages
10
Hello to All:

I am a newbie with a Velocity Micro E2250. Although the Intel Q9450 2.66 Quad processor is advertised as being overclocked to 3.2, CPU-Z analysis indicates that it is running at the stock 2.66MHz. I entered the BIOS, attempting to boost the FSB from 333 to 400, but I cannot locate the location in the BIOS to make the change. The mobo won't permit any increase in the multiplier beyond 8. Many reports indicate that this system should easily handle 3.2 stable. The cores currently run no hotter than 25C under load, and it is liquid cooled so cooling shouldn't be a problem. Any help would be appreciated.

Not bad for $700.00

Thanks in advance!
 
honestly if its running at stock id be calling and bitching about it.. what motherboard did it come with?
 
MOBO: ASUSTek model P5N-D
BIOS: Phoenix Version ASUS P5N-D 0403 dated 3/5/08

I don't know how to copy and paste a screenshot into this reply...
 
Zero82z:

Thank you so much. I am running well at 3200MHz. I am rendering video, using roughly 70-80% all 4 cores and my temps are in the upper 20'sC.

Very much appreciated. 3.2GHz is fast enough for me; When I get in AVCHD video editing (up from my current HDV) I'll need every ounce of processor.

I came to the right place...
 
Follow Up:

After two hours at 3.2GHz, (AI overclock at 20% increase) I got a BSOD.

Went back in and overclocked a 15% increase over the 2.66 stock, so it's been going ok for a while at 3.06GHz. Temps still in the 20's. Thanks again.
 
You might need to raise the voltage a bit to get it stable at 3.2GHz. And you should not use AI Overclock; it's always best to set everything manually.
 
Thanks, Zero,

If I knew all of the adjustments that must be made in tandem, one tweak at a time, I would consider it, but this is my first venture into the OC stuff, and I'm destined to mess something up...

I am probably better off leaving it, unless I understand all of the small changes needed to get that extra 200MHz.
 
dont use ai overlock. it also raises the ram speed in conjunction to the FSB.

just raise the fsb. it will show up as quad pumped in the bios so 1600 is what you want.
 
haadij404:

I went back and changed AI Overclock to "Manual" and modified the FSB to 1600. Did the previous AI Overclock change the RAM speed that hasn't changed back? CPU-Z shows the RAM at 480MHz. I'm not sure where it was before, but I believe it was less, likely 400MHz. Should I lower the RAM speed?

Cores 0 & 1 had errors on Prime95 after a few minutes, although the temperature of all cores was still in the 20's.

Thanks...
 
Yes, you should lower your RAM speed. It should be running at 400MHz. Also, you might want to raise your CPU voltage slightly. ~1.275V should be enough for your overclock. Prime95 should not show any errors when your overclock is stable, so don't leave it as-is until you've got that under control.

How are you monitoring your temperatures? You should use Real Temp 3.0.
 
Throttled back to 1566.6 FSB for a 3133.33MHz processor speed. Seems to be stable for 45 minutes on Prime 95. When I had it at 1600 PSB yielding 3.2GHz caused Prime 95 errors. Got Real Temp 3.0 ... Running around 59 - 60 degrees. Interestingly, when I set the TJ Max temp alarm at 71, which I believe is the spec limit of the Q9450, Real Temp reports the cores in the upper 20's (which must be wrong). I therefore did not set a max temp alarm.

So now I'm at a bus speed of 391.7 X8 = 3133.3MHz per CPU-Z. Although I set Vcore Voltage to 1.275, it's reported as 1.200 on CPU-Z.

Thanks for everyone's help; any further suggestions are always appreciated.
 
when I set the TJ Max temp alarm at 71, which I believe is the spec limit of the Q9450

The TCase spec for the Q9450 is around 71C. However, that is completely unrelated to the Tjmax, and you can't compare the TCase temperature to the core temperatures of your CPU.
 
So what maximum temperature should I be looking out for while processor is under a stress test as read by Real Temp???
 
Anything below the Tjmax point is fine for stress-testing. Basically, anything under 100C. For continuous use, my comfortable spot is 20C or more from Tjmax, so that would be 80C or lower for your CPU.
 
You have all been very helpful. Everybody starts out one day... Today is my turn..


If I keep running stable at 3.133GHz, this is where I leave it alone.
 
I have the same system above from Newegg. I had some problem with OCing and found this setting on another forum for 3.2GHz:

Vcpu: 1.25v
Vmem: 2.11v
HT: 1.4v
NB: 1.42v
SB: 1.52

I've run it stable with prime95 (no errors) for a few hours at 3.2GHz and Real Temp 3.0 has all cores no higher than 51C at any given time and usually at 49C.

My question is: should I see if I can get these voltages down any more? Is it worth the time and will it help with hardware longevity to work on lower voltages?

I know the Corsair DDR2 is recommended to go no higher than 2.1 and I am currently trying lower voltages to see if it stays stable.

Is Memtest useful to make sure I'm not frying my RAM here over time?

Lastly, I've also read elsewhere that these RAM are good OCers. Anyone know if this is true? When I first made the BIOS changes I neglected to unlink the RAM and it was running for those few hours stable at 480MHz. I moved in back to 400MHz due to what I read on this thread, but is it better (or harmful) to let it run at 480MHz if it is indeed stable?

I know, lots of Qs but I am new to this OCing (not happy the cpu from Newegg wasn't OC'd already).

Thank you
 
Update: I changed the memory voltage to 1.95 and we're still stable over the last few hours. One thing changed: CPU core temps now an average of 10 degrees lower. At this moment (with prime95 running for over an hour): 39 42 40 41.

Btw - I forgot to mention that I updated the Bios from the Velocity Micro support site. So it might be different from above system that this thread started with.
 
I've been trying to overclock the same system doing the same things you guys mentioned and it doesn't seem to be working. I know this is an older post but I figured somebody might stumble across it.

Funny thing is when I apply the settings you guys are mentioning, CPU-Z and every other program that can tell still reads the processer as 2.6ghz. Anybody have any idea why? And what should I do about it?

I tried getting in touch with Velocity Micro for help with it, and they were total jerks about it. Last time I ever buy one of their products. But since I'm stuck with this one, I figured I might as well make the best of it.
 
Even though it has already been stated.. but maybe not clearly for you.

Make sure you're not overclocking your ram way past its rated specs.
 
When I increase the FSB, I do it unlinked so the RAM isn't touched (I assume). By default the FSB for the CPU is 1333 and the RAM is 800. All I did was increase the CPU FSB to 1600. I didn't touch the RAM FSB.
 
Has this happened to anybody else? It's weird that the changes being made don't show up at all, except in the BIOS. It'd be one thing if I couldn't get it to run stable, but CPU-Z tells me its still running stock despite the settings in the BIOS.
 
Put the FSB to 1600 and ram to 800.

CPU Vcore to 1.3 (for the moment) and memory voltage to 1.80v.

What I'm assuming happens is that your overclock fails and the bios reverts back to the stock settings so that's what you see in cpuz.

If those above settings fail raise the northbridge voltage to 1.3. If everything is stable start backing down the CPU Vcore and testing. Rinse and repeat until it's at the lowest it can handle the 3.2ghz.
 
Back
Top