Stop errors are a common error in windows XP. There are a quite a few Stop errors listed in win XP. Stop errors are nothing but a precautionary note from winxp before a major breakdown. These Stop errors appear only in the NT based operating systems like Win NT, 2K, XP etc. Stop errors can come up due to various reasons. But most have been found to be hardware issues.

Stop errors are identified by an 8 digit hexadecimal number. The word minidump is closely associated with Stop errors. But the fact is we all know that if there is a STOP error then there is a problem and the error code will help in determining the solution.

How to Troubleshoot Windows Stop Errors? Let me explain some errors in short and possible troubleshooting to fix it. If you can’t resolve the issue, you can talk to computer services provider for tech support.

1: Stop 0x0000000A or IRQL_NOT_LESS_OR_EQUAL- This code indicates that there is some error in the kernel mode process itself. A kernel mode process can access other processes that have an IRQ which is less than or equal to its own.

Resolution: This error may happen after installing a faulty driver or a firmware. In case the stop error lists a driver name or a service, list it and see if it can be disabled. This can clear the error. Then a possible update of that driver is required.

It might also happen due to a faulty hardware too.In case this error comes while updating OS then it could be a possibility that there is a faulty driver too.

2: Stop 0x0000001E or KMODE_EXCEPTION_NOT_HANDLED – This error shows again that there is a kernel level error. This one shows an unknown processor instruction.

Resolution: This error may happen after installing a faulty driver or a firmware. In case the stop error lists a driver name or a service, list it and see if it can be disabled. This can clear the error. Then a possible update of that driver is required.

Firmware incompatibilities also can cause this error.It could also happen because of memory leak i.e. an application or service is not releasing memory correctly.

This was a few resolutions for a few STOP error codes. But in general most STOP error codes have general troubleshooting steps:

1.Examine the “System” and “Application” logs in Event Viewer for other recent errors that might give further clues. To do this, launch EventVwr.msc from a Run box; or open “Administrative Tools” in the Control Panel then launch Event Viewer.
2.If you’ve recently added new hardware, remove it and retest.
3.Run hardware diagnostics supplied by the manufacturer.
4.Make sure device drivers and system BIOS are up-to-date.
5.However, if you’ve installed new drivers just before the problem appeared, try rolling them back to the older ones.
6.Open the box and make sure all hardware is correctly installed, well seated, and solidly connected.
7.Confirm that all of your hardware is on the Hardware Compatibility List.
8.Check for viruses.
9.Investigate recently added software.
10.Examine (and try disabling) BIOS memory options such as caching or shadowing.