XP SP3 Why Me? - More Problems
(Page 4 of 4 )
Johansson has a section in his blog called “Other STOP Errors” that details the possible problems that could come up when installing SP3 on Intel-based computers. The most common error code that keeps coming up is 0x00000024. Again, the exact cause has not been identified, but Johansson points to possible faulty video drivers from ATI and nVidia. It may also mean that the system driver (ntfs.sys) has been corrupted. Either way, it's a good idea to check out that section to see if he can help you identify your problem.
Another major problem still causing a ruckus because no one is willing to take the blame has to do with the fact that some users can't connect to the Internet because the update to SP3 has emptied their Device Manager. Apparently, their network cards and previously-crafted connections disappeared.
After checking the Registry, users found that there were a number of corrupted entries in sections reserved for the settings of Symantec products, including Norton Internet Security and Norton 360. Symantec has denied that their product is the cause and essentially blamed Microsoft, referring to the other problems users have encountered so far.
I'm guessing that this article has dissuaded most readers from updating to SP3, if they haven't already. If they have and are experiencing any of these problems, they're probably ready to chuck their computer out the window by now. But before you do that, you many just want to remove SP3 from your computer and revert back to SP2, assuming you can regain control of your computer, of course.
Microsoft makes that very easy with this handy-dandy support document, so you're not completely stuck. I, for one, have learned to exhibit Zen-like patience when it comes to these updates, yet not when it comes to the new Indiana Jones movie. Where's the support document for that?
| DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware. |