Why in hell would my VCore be O/Ced when I boot up Windows XP ???

[DaMulder]

Hi Guys.
Yes you read the topic right. I replaced my 2100+ XP with an 2700+ FSB 333. The boars automatically set the FSB to 333 and everything seemed fine in the Bios. The Vcore was 1.66 V and nothing was O/Ced.
But then when I was in Windows XP I noticed that the CPU was running extremely hot for no reason as I have a descent cooler on that Athlon as well. Not that "in-a-box" cheap thingie that came with the CPU and I also know how to apply heatsink so that would not be the problem.
I figured out that Windows XP somehow changed the Vcore to 1.77 when I went to check everything in Sandra 2002. I don't know why it did this but when I actually open an OC programm and set the Vcore to 1.75 and then change it back to 1.65 then it would actually run in Windows XP at the standart Vcore. That's the only way to run the CPU without overheating though and apparently that is very annoying.

Basically what I wanna know is: What could be the problem? Did the 2100+ run at a Vcore of 1.75 and Windows did not notice the new CPU yet?
Or would reinstalling Windows XP help me in any way?

Did anyone experience this before?
Please help me!!!

Phil

 

[hitechjb1]

... I don't know why it did this but when I actually open an OC programm and set the Vcore to 1.75 and then change it back to 1.65 then it would actually run in Windows XP at the standart Vcore. That's the only way to run the CPU without overheating though and apparently that is very annoying.

...
Phil

Windows must now has an automatic utility program that does automatic overclocking. jk

What is that OC program that can set Vcore you are talking about?

Usually, we set Vcore in the bios manually.

 

[DaMulder]

bbb

I believe the programm is called "Easy Tune" or whatever... It's like FuzzyLogic on MSI boards but it came with an Gigabyte board. I don't remember the name cause it's my friends PC.

And why the hell would Windows XP have it's own overclocking utility that makes your CPU overheat from the start ??? That just does not make ANY sense.

 

[hitechjb1]

Re: bbb

I believe the programm is called "Easy Tune" or whatever... It's like FuzzyLogic on MSI boards but it came with an Gigabyte board. I don't remember the name cause it's my friends PC.

And why the hell would Windows XP have it's own overclocking utility that makes your CPU overheat from the start ??? That just does not make ANY sense.

I don't think windows does automatic oc for you.

May be just that Easy Tune uses some old setting. Can you disable it and try. Most ppl overclock by using bios setting. This way you know exactly what you are doing, than leave it to some programs to fool around with these important numbers.

 

[2500+RPM]

My friend has a p4 with gigabyte MB and that same lame prog came with it, its a joke.

 

[altec]

Disable the program like the other guys said, usually those things cause more problems than they do good. Also go into your BIOS after it is disabled, and make sure you set the vcore manually: it shouldn't change after that, and if it does, come back and see us.

 

[OC Detective]

Well first thing is your vcore for the XP2100 was 1.66V whereas default is 1.6V for tbred so it was already overvolted to a certain degree, maybe your bios allows overvolting by percentage? The default voltage of the XP2700 is 1.65V so the voltage will be higher anyway. I dont think windows is making your vcore higher.

 

[K_King]

If its a Palomino 2100 the default voltage is 1.75

I have a similar issue, my BIOS says 1.725 yet whever I go into windows (xp) I see that my voltage is about .50 higher than what I put in the BIOS. Doesnt make a difference I still think I am at 1.725.

 

[DaMulder]

No no...

I would not care if it was running at 1.65 insted of 1.60. But it runs at 1.75 in Windows, although BIOS sais it's set to 1.6.

AND this EasyTune thing is not the cause of the problem as it was never installed before. This problem occured only after changing the CPU and it causes serious heat without any extra performance.

Basically Windows XP starts up and the Vcore is 5% too high and the BIOS tells me everything is normal...

Any more ideas?

 

[DaMulder]

Solved!

You might find it interesting that a Bios Update just fixed it. The BIOS and Windows Vcore settings match now and the temps are much better now as well.

Thanks for trying to help anyway!

Phil