Win XP “Stop” errors
Some of you may remember from last year, about this same time actually, that I started having some problems with my workstation. The intermittent Blue Screen of Death (BSoD) type problems. The dreaded WinXP “Stop” messages.
This time it has been the usual Stop 8e along with a Stop 50. When the crashes first began, there was a reference to the video driver in the error message. Experience from my previous adventure led me to know that the initial indicator is most likely the problem. Subsequent crashes may have any number of related “Stop” messages and pointers to win32k.sys and other system drivers. Doesn’t necessarily mean anything.
Since I noticed my video adapter had been acting up while editing some of my photos, I was quite certain the adapter was having a near-death experience. Over the course of about 24 hours, it degraded enough to where the computer would not even boot.
I replaced the video card with a $50 Radeon and so far so good.
Whenever I get these BSoD errors, I always like to do a quick Google search to see if there is a quick answer. There never is but it is always fun. The tidal wave of BS that is out there in the guise of “free technical support” such as is available on tech sites is comical verging on ridiculous. The task of weeding through the BS and finding the pertinent information can be daunting for even a seasoned pro.
Here is one of the best I have ever seen that is both hilarious and indicative of the challenge Microsoft faces going in to the next five to ten years. A guy is responding to the desperate pleas for help from a XP user experiencing random BSoD Stop messages:
Random crashes like this sounds to be cpu related…whether bad cpu or cpu is overheating. Are you using thermal grease between the heatsink and the cpu? Try not to use the thermal pads, they’re not good at transferring heat.
The funniest thing is that the people needing the help are usually those who have went out to help “a friend” or “their uncle” sort out their WinXP problems. Never it is evident from the posts that the desperate person is actually billing someone for a technical support call. Now that the “support specialist” has consulted the poor WinXP user to buy a completely new computer one component at a time and the computer still crashes, they become crazy desperate. You can just tell from the sound in their voice as they make their desperate pleas for help.
Here are a few rules of thumb for the BSoD Stop errors in WinXP:
1. If the crashes started suddenly for no apparent reason and nothing has been changed on the PC, it is quite likely going to be a RAM memory failure of some sort. The failure may be the main RAM or video RAM or even cache. Look for any clues that might point to the video card.
2. If there has been a recent change to the PC, whether new software or new hardware was added, the crashes will usually be caused by a configuration problem, especially bad/outdated drivers.
3. The power supply. A weak P/S can be the cause of erratic behavior in every component on a system. If successive error messages seem to indicate everything is screwed up, then the P/S is probably weak and subsystems are not getting optimal levels of current.
All of these culprits can be tested without buying a single new part. All the other suggested measures regarding heat, hard drive partitions, swap files, front side bus (FSB) speed, over-clocking, and thermal grease are just plain idiotic in 99.9% of the cases. They are desperate measures taken by desperate people. I know, I’ve been there before.
What is sad is that people are continually falling in to the trap of replacing an entire system because it is too expensive to get theirs fixed. Computers are too cheap to spend several hundred dollars getting one fixed. Even sadder is that is shouldn’t have to be that way.
While the WinXP BSoD crashes can be mysterious and difficult to pin down, they are usually not that big a deal to correct. It just cost me $50 for a new video card.