Sign in with
Sign up | Sign in
Your question
Solved

I'm getting different clock speeds please help

Last response: in CPUs
Share
September 12, 2013 4:47:56 AM

First of all I BSEL modded my CPU (Q6600), to increase it's FSB to get it to 3.0ghz from 2.4ghz. it is a q6600. It showed 3.0Ghz in DxDiag, 2.99 ghz in computer properties and in task manager. now i was messing around and switched of multiple cores from my bios. But after i turned multiple cores on, Windows was still only detecting two cores so i flashed the lastest a22 bios for my dell optiplex 755. Now Windows detects 4 cores but @ 2.4ghz, bios also shows 2.4ghz, task manager, dxdiag and Properties also show 2.4ghz. But CPUZ and SetFSB shows 2.99 Ghz. I dont remember what bios showed when the mod was working before so i m not going with the bios. please tell me what's wrong and what should i do now. I m running Windows 8. I tried the previous bios but the same thing is still happening so i again switched to A22, i even tried A01 Bios. I really want the bsel mod back, PLEASE HELP. Is it 2.99/3.0Ghz or 2.4 Ghz.
You can see the picture over here: http://www.mediafire.com/view/z4gz8clcd434zjm/HELP_OMG....
Please help me guys.

More about : clock speeds

a b à CPUs
September 12, 2013 4:54:14 AM

double check your OC settings. try to benchmark, see if it reaches 3ghz
m
0
l
September 12, 2013 5:07:28 AM

Cons29 said:
double check your OC settings. try to benchmark, see if it reaches 3ghz


Dude, cant you see that there's a becnhmark, on 100% usage, cpuz is showing different results than task manager
m
0
l
Related resources
a b à CPUs
September 12, 2013 6:57:36 PM

sorry those sites are blocked here in the office so i cannot view the pics.

m
0
l

Best solution

October 6, 2013 8:34:24 AM

Cons29 said:
sorry those sites are blocked here in the office so i cannot view the pics.



Well, i cant upload the pic, i found the solution, i just had to turn off intel speed step, i m using the latest bios which runs my bsel mod and runs my processor on 3.0 ghz. The only problem was intel's speed stemp technology, thanks anyways
Share
October 10, 2013 7:39:57 AM

I found the problem, it was Intel Speed Step which was causing all the issue, I disabled it and everything went back to normal
m
0
l
!