IRQL_NOT_LESS_OR_EQUAL error message

[Teztaz]

I received this stop error on a blue screen:

A problem has been detected and windows has been shut down to prevent damage
to your computer.
IRQL_NOT_LESS_OR_EQUAL
Tech info at bottom reads:
STOP 0X0000000A (0XF891A100,0x00000002,0x00000001,0x804D9BBA)

After reading advice on this board, I enabled the Driver Verifier and the
error message changed to:
A problem has been detected and windows has been shut down to prevent damage
to your computer.
A device driver attempting to corrupt the system has been caught. The faulty
driver currently on the kernel stack must be replaced with a working version.
At the bottom:
STOP 0x000000C4 (0x00000030,0x00000016,0x0000002,0x00000000)

Please help me - what do I do next? I've been trying to fix this for ages
and I'm getting nowhere. I can only run in Safe Mode. I thought I'd
uninstalled the printer driver which probably started this problem (using
Add/Remove pgms), but the problem continues. I cannot reinstall and uninstall
the software (as suggested by HP) because the installation fails because the
Print Spooler is not enabled in Safe Mode. I cannot restore to an earlier
date because the System Restore option was OFF (darn it) - this is a
reburbished computer.

System Info:
MS Windows XP Profession V 5.1.2600 Service Pack 2 Build 2600
Dell Latitude D400 laptop
SMBIOS version 2.3

Thank you!!!!!!!!!!!!!!

 

[Mark L. Ferguson]

PStat could help you detect the driver on the stack. Have a read of this
excellent post on doing that:

<quote from Ron Martell MVP>
******
Identifying the cause of STOP errors using PSTAT & Excel

Many times when a STOP error occurs the information provided does not
specifically identify the application, device driver, or other
component file where the error occurred. However the 4 parameters
associated with the STOP (bugcheck) code will very often include one
that is the address where the error occurred. You first need to look
up the detailed information about the specific STOP code in order to
determine if the address is included and if so which of the 4
parameters has the address.

You can identify the meaning of each of the parameters for your
specific STOP code at:
http://msdn2.microsoft.com/en-us/library/ms789516.aspx

The second step in the procedure is to identify the addresses that
each active process is being loaded at. The PSTAT utility will
provide this information. On some systems the PSTAT utility may
already be present. Check this by opening a Command Prompt window
(Start - Run - CMD) and entering the following command:

PSTAT /?

If PSTAT is not on your computer you can download it free from
Microsoft. The download is called "Windows XP Service Pack 2 Support
Tools" and it is available from
http://www.microsoft.com/downloads/...76-9BB9-4126-9761-BA8011FABF38&displaylang=en
With PSTAT installed on your computer the next step is to open a
Command Prompt window again (Start - Run - CMD) and generate a report
with PSTAT. Because you need to copy part of the information from
this report (and only part) it is best to create the report as a text
file. In the Command Prompt window enter the following command:

PSTAT > C:\JUNK\PSTAT.TXT

You may change C:\JUNK\ to whatever drive and folder that you want to
save the report into.

Now open the saved file in Notepad. Start - Run - NOTEPAD
C:\JUNK\PSTAT.TXT

Scroll down the file, about 80% of the way to the end of the file and
you will find a head line:

ModuleName Load Addr Code Data Paged LinkDate

It is the information from this line to the end of the file that we
want to copy from this file and save as a separate file. Select the
block of text and copy it to the clipboard. Open a new notepad window
and paste the clipboard contents into it. Save this file under a
different name. I use PSTAT2.TXT and put it into the same C:\JUNK
folder.

Now launch Microsoft Excel and use File - Open to bring the PSTAT2.TXT
file into Excel. Excel will automatically parse the file into
columns. Once this is done use DATA - SORT to sort the entire
spreadsheet based on the value in Column B (Load Addr).

It is now a simple task to read down the addresses until you find the
highest value that is less than the address where the error occurred.
That module (name in column A) is the prime suspect for the cause of
your error.


Good luck

Ron Martell Duncan B.C. Canada
<end quote>
--
Was this helpful? Then click the Ratings button. Voting helps the web
interface.
http://www.microsoft.com/wn3/locales/help/help_en-us.htm#RateAPostAsAnswer
Mark L. Ferguson
..