Most Popular
| Top Stories | Commented | Featured |
TechSpot Blog: Disable Windows automatic check for solutions after a program crashes featured
Weekend Open Forum: Google Chrome OS and the future of cloud computing featured
Tech Tip of the Week: Unearth Region-Specific Windows 7 Themes featured
Sony: PlayStation 3 to be 3D-capable via firmware update
Radeon HD 5970 supplies dry up quick, not a big surprise
Xbox Live bans prompt class action lawsuit
Mozilla reveals 2008 revenue, rumors say Firefox coming to PS3
TS Community
| User Gallery | Recent Discussion |
 TECHSPOT for the Win by Psychodan |  Golden post by Fiziks |
 New os install by Sean |  Counter Strike by Akio |
TechSpot RSSInformation Technology
Third-party fix for XP SP3 reboots published
If you are one of the XP SP3 users that are plagued by the non-stop rebooting, you can breathe a sigh of relief today. A third-party, who is a formerly security manager for Microsoft, has released a tool that will be able to detect the problem and hopefully fix it.
The tool will prompt you to install the fix once you use it only if it detects a problem, and is a miniscule 16k VBScript file making it easy to acquire. The problem seems to be related to a driver intended for Intel devices which is attempting to load on AMD based machines. The tool is, of course, available for free. If you are suffering from this problem, it's definitely worth snagging it. It is unfortunate that once again a third party has had to step in, due to Microsoft being content with waiting weeks or even longer to fix these glaring issues.
The tool will prompt you to install the fix once you use it only if it detects a problem, and is a miniscule 16k VBScript file making it easy to acquire. The problem seems to be related to a driver intended for Intel devices which is attempting to load on AMD based machines. The tool is, of course, available for free. If you are suffering from this problem, it's definitely worth snagging it. It is unfortunate that once again a third party has had to step in, due to Microsoft being content with waiting weeks or even longer to fix these glaring issues.
Related Stories
