• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

E6300 Clcok Speed in CPU-Z

MolDog

MolDog

MolDog

Associate
Joined
4 Sep 2006
Posts
45
Hi

I've recently built a Core 2 Duo rig with a E6300 processor. I turned off speed step (which I believe is what my DS3 Motherboard identified as EIST in the BIOS) to check clock speeds etc in CPU-Z. When I did this however, CPU-Z said that it was running at 1600MHz on a multiplier of 6.0x, whereas windows was indicating it is running at its full stock speed of 1.8GHz in the main page of system properties everytime I open it.

Is this a problem between core 2 DUO and CPU-Z or could some other form of Clock/FSB control be running?

edit

By windows indicating this I mean the second clock speed indicated for the processor next to the RAM, not the bit that says E6300 @ 1.86GHz.
 
Last edited:
There are 2 things you need to disable in the BIOS C1E and Speedstep (EIST). Intel do like to save energy. It's a good habit they picked up in bad circumstances (trying to keep a 3.8GHz Prescott cool :D )
 
Same thing happened to me with my new e6600. CPU-Z would flick between 2.4 and 1.6. It was the C1E setting that I hadn't disabled :D
 
I did experience a problem with cpu-z version 1.39

With all my speedstep stuff off - no power saving on, it reported my clock running at x6 aswell. I wouldn't have thought it incorrect, but it was since I had been using cpu-z version 1.38 a minute before and it was reading my correct clock at x10.

I would bet that if you reinstalled version 1.38 of cpu-z that your readings will be correct! Unless 1.38 is messed up in some way lol.
 
Ah Thanks

Was looking at those and wondering if they made a difference but thought better not mess before I know what it does

Cheers for the help
 
Just an update - I installed 1.39 again just to determine what the problem was, and it turns out that I had a form of speedstep on, so it was reading the speed correctly. As soon as I put a workload on it, it just jumped up in speed.
 
You must log in or register to reply here.
Back
Top Bottom