Okay here's the scoop. I've been reading up on overclocking the last week or two and yesterday I decided to test my luck.

I tried overclocking my system, which is a:

Soyo K7VTAPRO 1.0 mobo (has multiplier dipswitch and everything)
Athlon XP 1.7GHz Processor
640MB PC133 SDRAM
nVidia Geforce2 Mx400 64MB Vid card

After doing some investigation I realized that the multiplier on my processor was locked so the only way I could over clock was by modifying the System bus (yes I know this is bad, but I had to try) through the bios. I decided on overclocking only 100Mhz higher because I was not trying to fry my processor. I just wanted a small boost.

I changed the System bus to 139Mhz (instead of 133Mhz) and instead of my system being 1.7GHz (1469) it's now running at 1.8GHz (1529MHz really), which was cool with me. I ran wcpuid and my H/W temp monitor and everything seemed fine. I wasn't to concern about overheating because I have a copper CPU, which is great at keeping components cool, but to be on the safe side I threw some more thermal paste on the die. I checked the temp and everything was running at a nice 48-50 degree Celsius temp.

Now, here's the problem. I go into Windows to System Info to check the speed of my processor and now I get some WMI Corruption error. I know noticed this WMI error has affected other areas such as advanced properites under network connections.

Alright so here's my question,

Should I up the Vcore on the processor? (It's currently only 1.79)

If WMI is corrupted, will other data on my system be corrupted because of overclocking and will more Vcore possibly help?

How in the hell do u fix the WMI corruption anyway (please don't send me that MS Support Link)?

Has anyone else run into this problem?

I am very tech savvy so I already investigated that MS fix and it of course it doesn't work like most of their support does that's why I'm posting my problem here, LOL.

So far that seems to be the only problem I've had with overclocking, but now I'm concerned that other data has become corrupted. I did notice a movie was corrupted after overclocking, but I'm not sure if that was because it was just a bad copy or because of overclocking.

Any assistance in this matter would be greatly appreciated.

Thank you

TECHZAPORT OUT!!!

download prime95 this will see if your cpu is stable thats all i can help you with myself.

Q-TEC 550 Watt PSU
MSI VIA KT4AV-L
2800+ Barton 512 DDR333
GeForce Fx5200 128Mb
Aero 7 Lite
80Gb Samsung ATA133 HDD
120Gb WD ATA100 HDD
LiteOn LDW-851S
LiteOn LTR-52246S

You're supposed to overclock via the FSB...the advantage of an unlocked multiplier is to lower it so that you can raise the FSB even higher! Having a faster CPU speed isn't as important as running at a higher FSB speed. 10 x 145 (1450mhz) is faster than 11 x 133 (1467mhz). Unfortunately, your multiplier is locked...but it can be easily unlocked, if you wanna mod your CPU

You can't burn out a CPU by seting the FSB too high...it will either become unstable, or it won't run at all, but it won't burn out. Too much voltage or allowing a CPU to overheat will cause it to fail, not too much FSB.

PC133 RAM is good to about 140-145mhz depending on quality. I'd try the CPU voltage at 1.85v (max safe voltage) & the FSB at 140mhz & see what happens. That will put your speed at 1540mhz. You can experiment from there, but your PC133 is gonna hold you back

...there is no spoon...

Jam, I had my system at 145MHz, but didn't want to mess up anything else. Plus I got that WMI error and was a lil scared so I pushed it back down to 139.

Should I be concerned with data corruption becuase of the FSB seting?

TECHZAPORT OUT!!!

I wouldn't worry about it, the worst that could probably happen is you getting that same error @ that bus speed.

I had a similar issue with IE, with my FSB @ 220, just dropped the FSB and am OK.

____________________________
The greatest risk is not taking one

Report Offensive Follow Up For Removal

I had my machine running at 1.9Ghz (1569) @145MHz system bus and WMI was working fine. The funniest thing is when I lowered it down to 139MHz that's when I got the error.

I assume if I just set it back to the original settings (1.7GHz @133 FSB) or 1.9GHz @145 FSB the WMI might correct itself.

What do you think?

I really don't want to do the System restore because I find MS restore to be garbage. I tired MS Support fix and of course it was futile.

Any info regarding that WMI error?

Thanks to everyone for their input regarding overclocking. I will definitely play around with it more when I get home.

TECHZAPORT OUT!!!

If you do not get the error @ 145FSB and your temps are OK, then go for it.

____________________________
The greatest risk is not taking one

Report Offensive Follow Up For Removal

Okay here are the results of my overclocking experience. Those WMI errors I received was definitely in result of overclocking my machine and seriously screwed up my Registry. In addition, I couldn't even do a system restore so of course I had to wipe out XP, which was no biggie since I tend to do it anyway about 3 times a year to clean up junk. I had all my data stored on a separate partition so I just blew bad boy away.

I was tempted to give up on overclocking, but being a techy I couldn't go down that easy. I played around with some settings and finally overclocked my machine to a point in which it was stable. Jam thanks for the suggestion to go to 140MHz because that is working just perfect for me. I didn't even have to up the voltage or anything. I knew I couldn't go to high because of my PC133 SDRAM and I noticed as soon as I went higher than 140MHz my machine began acting very weird. Even though it's a just lil overclock I still feel as it was a good accomplishment. I could unlock my processor and go with a higher multiplier, but I think I'm going to stay right where I am and not be greedy.

Here are my results I went from 1.7GHz (1469-I think) to 1.8GHz (1540). My temp is between 48-52 degrees with a simple copper CPU fan and generic thermal paste so I'm going to leave everything alone right now (because I don't feel like reinstalling anything for time being, LOL).

Thanks for everyone's input.

TECHZAPORT OUT!!!