Does Your Windows > Properties Show you the OC Speed?

bbasra

bbasra

bbasra

Associate
Joined
24 Feb 2008
Posts
74
Hi,

I have OC'ed to 3.4. Coretemp and CPU-Z show the OC speed but if you Right Click My Computer and Select Properties, mine show the Stock 2.4 Speed.

Is this normal?

TIA
 
This is a strange one, I just dropped my FSB to 200MHz and the multi from x9 to x8 and it is reporting that it is at 1.6GHz instead of the E2160's stock of 1.8GHz.

So for some reason that area in system info is reporting the multi correctly but not the FSB, if I load up dxdiag then its the same there. Very strange :confused:

I am on a Asus P5K-E by the way.
 
umm....8x200 = 1600Mhz....the 2160 has a multi of 9 so it is 1.8Ghz...of course it'll report 1.6Ghz if you have the multiplier set to 9
 
I think my post flew over your head mate ;)

People with the same problem as the OP are saying that the area in system properties doesn't update to give the overclocked speed. e.g if your stock is 1.8GHz then that's what it says the actual speed is regardless of if you have overclocked it or not.

I was just pointing out that it reads the multiplier correctly just not the FSB.
 
Mine shows 3.8, it doesnt read the actual multi (Which is x8, not x9), just the default for the chip. But it does show the actual speed.
 
Again gets asked every week and plenty of threads on it.

If you have an Intel CPU, most APP's inc Windows will read the DEFAULT MULTI, so if you lower/leave alone/raise Multi and OC the FSB it will still read the Default Multi X your FSB speed.

And if you overclock any CPU period in Windows using software, Windows will not see it, it will always be the boot up MHZ in the Sys Props.
 
Last edited:
helmutcheese said:
Again gets aked every week and plenty of threads on it.

If you have an Intel CPU, most APP's inc Windows will read the DEFAULT MULTI, so if you lower/leave alone/raise Multi and OC the FSB it will still read the Default Multi X your FSB speed.

And if you overclock any CPU period in Windows using software, Windows will not see it, it will always be the boot up MHZ in the Sys Props.
Click to expand...

Yeah but isn't it the other way round here though? I have my OC settings set in bios which load up fine but no matter what the fsb it still only reads 200FSB in that system properties window.

The Multi on the other hand I can switch between x8 and x9 and it is changing between 1600 and 1800 in that window. So its the other way round to what you said.

It doesn't really matter though, its just reading it wrong, no big deal. I just thought it was strange that both the OP and myself have the same motherboard. Worth pointing out as well that when I had XP installed it displayed it properly.
 
Agr3sive said:
Yeah but isn't it the other way round here though? I have my OC settings set in bios which load up fine but no matter what the fsb it still only reads 200FSB in that system properties window.

The Multi on the other hand I can switch between x8 and x9 and it is changing between 1600 and 1800 in that window. So its the other way round to what you said.

It doesn't really matter though, its just reading it wrong, no big deal. I just thought it was strange that both the OP and myself have the same motherboard. Worth pointing out as well that when I had XP installed it displayed it properly.
Click to expand...

Yours is indeed wonky, the APP's should see the FSB and Windows should give your CPU MHZ = DEFAULT Multi X any FSB.

So no idea whats wrong with your PC m8.
 
I think it has to be something to do with Vista, all latest versions of apps work fine, I get correct readings in...

CoreTemp
Asus Software
3D Mark Information Area
Cpuz

The two areas that report wrong are to do with Microsoft - system properties window and Direct X Diagnostics.

Its no big deal though, if someone comes up with a fix then great but I am not going to lose any sleep over it :p
 
You must log in or register to reply here.
Back
Top Bottom