Discussion Locked

XP BSOD error

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

The classic IRQL_NOT_LESS_OR_EQUAL line is causing me a bit of a strain. How do I locate which driver is causing my BSOD upon closing XP?
0x.....A
(0x.....2DC, 0x.....FF, 0x.....0, 0x804E9D48)

Best regards
Christian Sparre

5 replies

by timwalsh

If you haven't already check out the following Knowledgebase article:
Troubleshooting a Stop 0x0000000A Error in Windows XP (Q314063).
Unless the Stop message is giving you some clue as to which driver (should reference a filename somewhere in theerror message), you are basically stuck with a process of elimination to find the offending driver. If you have installed anything new, that's usually the best place to start. Otherwise follow the procedures in the above KB article.
Good luck.

by maxwell edison

The IRQL_NOT_LESS_OR_EQUAL or Stop 0x0000000A errors are able to be generated by both software and hardware issues. The message indicates that a kernel mode process or driver attempted to access a memory address that it did not have access to.

This issue can be caused by any of the following possibilities:

Mcafee VirusScan for Windows NT issue
Windows upgrade
Service Pack
Driver issue
Hardware issue

See, "Troubleshoot Windows XP Professional"

http://www.microsoft.com/windowsxp/pro/using/howto/gettingstarted/guide/troubleshoot.asp

(REMOVE SPACES from the pasted URL.)

Maxwell

This discussion is closed to new replies.