- The first thing I recommend doing is to try to reproduce the error. If
the error happens consistently every time you try to perform a specific
task, the problem is likely software related. If the error is
inconsistent, the problem is likely to be hardware related.
- It's also a good idea to check your computer's event logs. Review the
System log and any application-specific logs to see if any strange
errors or warnings occurred just prior to the blue screen error. If such
errors or warnings exist, they can be useful in diagnosing the problem.
- Every blue screen error contains an error message (usually the first or
second line of text that is displayed). Even though these messages are
often cryptic, they can point you to the cause of the error. Searching
the Web for the error message will help you determine some possible
causes of the error.
- If the blue screen error is occurring on a computer whose history you
are not completely familiar with try checking the Reliability Monitor.
The Reliability Monitor is a tool that is included in Windows 7 and
Windows 8 that allows you to track a system's stability over a period of
time. The Reliability Monitor reports on things such as application
installations, system updates, and hardware upgrades. Any of these
factors could potentially contribute to a blue screen error. The key is
to determine whether any major changes were made to the system just
prior to when the blue screen error started occurring.
- I never cease to be amazed by all of the strange things that can happen
when a computer overheats. If you suddenly start getting blue screen
errors for no apparent reason, check to make sure that the computer is
not overheating. While you're at it, take the time to verify that all
the fans (internal and external) are working and that none of the case
vents are clogged or blocked.
- The vast majority of the blue screen errors I have encountered over the
years have been related to faulty memory, so it can be helpful to run a
memory diagnostic. Windows 7 and 8 include a memory diagnostic utility,
and there are free third-party tools you can use, such as Memtest X86.
- If you suspect that the blue screen errors you are receiving are related
to a specific application, try running that application on another
computer to see whether the blue screen occurs there as well. If the
blue screen errors follow you from computer to computer, the application
is either poorly written or the problem is related to software or a
configuration setting that is present on both machines. If the problem
does not follow you, the blue screen error is unique to a single
computer.
- As I mentioned earlier, the vast majority of blue screen errors I have
encountered have been related to faulty memory. Unfortunately, memory
diagnostic tools do not always detect memory problems because such
errors can be intermittent. That being the case, you might consider
replacing the memory in a computer that is experiencing a stubborn blue
screen error. Often times, this will correct the problem, even if there
was no obvious indication of faulty memory.
- Blue screen errors can sometimes be triggered by malware (especially on
Windows XP). About 10 years ago, I saw someone in Redmond demonstrate a
proof-of-concept virus that caused a blue screen error by forcibly
shutting down a critical system service. Since that time, the same
concept has been used on a number of viruses in the wild.
- One last trick worth trying is to power down and unplug the computer and
then reseat hardware components such as memory and PCI cards. As
strange as it may sound, I have run into several instances over the
years (especially on older hardware) in which components were slightly
loose and reseating them resolved the blue screen error.
If this article does not help you then i suggest you take your computer to a technician.
No comments:
Write comments