Windoze Update Sabotges XP: *possible* "Conspiracy"
by DRxDON - 7/30/09 1:32 PM
This is a LONG message but a VERY peculiar and interesting one... so PLEASE stick with me.
For a system on its last legs(or LEG) of support, Microsoft is still kicking out the updates for XP. I just discovered(to my horror and surprise) that one of their latest "must have" Critical Updates somehow changes my BIOS settings, overclocking my CPU till it's as hot as a stove! How is this possible? I have no onboard software that can change BIOS settings. I'm running an ancient FIC MB and a just as ancient AMD xp CPU.
Microsoft also seems to be at its same old dirty tricks, ignoring my setting NOT to automatically install updates. I usually keep my computer on for several days to a week at a time and rarely ever turn it off from my Administrators log-on name. A few days ago I shut down from my Administrator ID and noticed Windows installing about six updates. When I turned my machine back on, I noticed apps running very jerky and freezing; so was the mouse. So I restored my system to a date a few days before the updates were installed. When I rebooted, everything was fine. Then a storm was approaching so I had to shut down. I noticed the same updates being automatically installed again. As soon as the storm passed, I rebooted and again the same system freeze occurred. This time, I couldn't restore because the system froze completely. I manually turned the computer off.
When I tried to reboot, it would freeze on the BIOS setup screen. After a few tries I was able to get in and load default settings, but it would still get stuck. I pressed the file hot key so I could see what was going on and it stopped and said my CPU was overclocked. I felt the heat sink and it was red hot. However, the BIOS settings said that the clock speed was where it should be along with the core voltage.
I let it cool down and UNDER clocked the CPU and managed to boot and start windows. I just managed to start system restore and, almost toward the end, the system started to get jerky but the restore went through. After resetting the BIOS I was able to reboot and Windows worked fine.
I decided to live dangerously just to prove that it was the update that was REALLY causing the problem. I shut down again and let the damn updates install themselves(even though I kept making sure that I had this option turned off). Sure enough, before Windows even got to the log-on splash screen, the system froze again. Had to kill the machine manually; rebooting *SAID* that the CPU was overclocked but the settings were normal. When I under clocked the CPU, it jumped up as soon as Windows began its start-up routine and I had to shut down again. I had NO idea if was EVER going to get back in!
Luckily, I managed to keep the CPU at a .5 underclock multiplier without Windows noticing that it wasn't at it's *normal* setting and so wouldn't overclock it when it started up. This time I went to one of my several registry repair apps and quickly kicked in an old good registry before the big "W" could overclock my CPU again and freeze me out.
SUCCESS! I made sure the BIOS was set to optimum and got into Windows with no problem. Now I have Windows update shut down COMPLETELY and can turn my system on and off with no problem.
Now, WHAT THE HECK IS GOING ON HERE??? If I was a conspiracy theorist,... HEY! I AM a conspiracy theorist! ... I would say that Microsoft was trying to stealthily sabotage XP by messing with CPU clock speeds and core voltages, without the BIOS displaying this. In newer machines with newer motherboards and faster more flexible CPUs, this "trickery" may only cause slight instability, convincing people that they need to upgrade to the BIG 7. In older machines like mine, tech-savvy people wouldn't probably even notice the update connection and just think that the BIOS or MB was shot. Hell, most tech-savvy people wouldn't even have such an old machine like mine.
So, who's on board with my "conspiracy theory"? When Microsoft is concerned, I don't think that such "business tactics" are too far-fetched to be considered!