DRIVER_IRQL_NOT_LESS_OR_EQUAL...???

[BiggyRat]

yo again, mates...!!!

my old machine...running XP Pro...that I sold to my friend...got a 'blue screen of death stop error' message...but the stop #'s read differently from other errors of the same type I searched out on the web.

his reads: DRIVER_IRQL_NOT_LESS_OR_EQUAL. STOP...0x488422ecd (bear in mind...it goes to a blank screen after the blue screen really quick...there's 4 or 5 stop # sequences in the chain, I think...but I only had time to scribble down one.

when I searched this sequence at the knowledge base...microsoft hadn't even heard of it.

(nothin' comes up in a google search, either)

they (microsoft) say that it reads (on an XP-based computer): DRIVER_IRQL_NOT_LESS_OR_EQUAL. STOP: 0x000000D1 (0x00000000, 0x00000002, 0x00000000, 0x00000000)...

& have a fix package #'d: 916595...which I downloaded...transfered to a thumb drive...& will attempt to install on his machine in safe mode tommorrow.

but I'm pretty certain I got that stop number copied down correctly.

this is weird...it bothers me that the stop chain reads differently on his box.

any thoughts or ideas...???

thanks,


BiggyRat

 

[John Lewis]

About the only thing that I could guarantee you at this point is you are not seeing the 0xD1 error resolved by the hotfix you have located. The numbers after the stop are important in determining the cause of the error.

I would suggest you take a picture. Camera phones usually will do the trick. Set the resolution as high as possible, black and white if that option is available. Snap a pic when the error pops up. You will then be able to get the correct numbers and the error text so you can reasonably begin troubleshooting.

 

[linney]

To get further information about the error look in your Event viewer. (From Safe Mode if you have to, but being in Safe Mode will automatically generate some false errors which you can disregard).

Look in the System or Application folder. You can get to the Event Viewer via right click My Computer icon and select Manage.

Any errors logged in the Event Viewer can be expanded by double clicking on the error line.

Take any event error I.D. number and search for it on this site.

http://www.eventid.net/events.asp

Also check any "Information" line that mentions "savedump" and you should find reference to "recovered from a bug check". This is the Stop Error that caused your problem.

You can also turn off "automatically restart after an error" so it will just halt at the fault and display the full Stop Error and blue screen. The same option is available via the Safe Mode screen but it only lasts for one reboot at a time.

Right-click My Computer, and then click Properties .
On the Advanced tab, click Settings under Startup and Recovery .
Click to clear the Automatically restart check box under System failure , and then click OK . The error message on a blue screen should remain on the screen so you can record the error information.



If the error occurred after installing a device driver or application, try using Safe Mode and removing the driver or program.


The above routines should at least allow you to double check (and then report here) the full error message.

 

[BiggyRat]

mhkwood & linney...

1) I had the numbers wrong, I believe. I looked at it again today; & the number sequence looks very much like the one found in the typical BSOD shown in a screen shot for a utility I found today; BlueScreenView:

http://www.nirsoft.net/utils/blue_screen_view.html

2) his system wont restart after the crash anyway. about 20 seconds after the BSOD, the monitor display turns a funny lavender color; & then goes black. Short of waiting around for god knows how long afterward...I can only restart his pc in safe mode.

what I need to figure out now is...can I install BlueScreenView in safe mode...???...& will it also run & give me the offending driver in it's list, in safe mode.

thanks much,


BR

 

[linney]

In your example there is the info down at the bottom under "Technical Information" if you can get that piece of information from your own BSOD then you are well on your way to identifying the problem driver.

That BlueScreenView program seems like it might install via Safe Mode with the only action required by you being double-clicking on the .exe to get it running.

When you find out which driver is causing the crash you can use the Recovery Console to Disable that driver from starting. You do this via the Disable command, you may also need to run the Listsvc command to identify the exact name of the driver you wish to disable.

How to install and use the Recovery Console in Windows XP

http://support.microsoft.com/default.aspx?scid=kb;en-us;307654&FR=1&PA=1&SD=HSCH

Things like pretty lavender colored screens might be pointing at a Video Card driver problem?

 

[Freestone]

Just as an FYI for the future, if you want to see the BSOD in all its infamous glory, turn off automatic restart, which by default is on.

Right-click My Computer, Properties, Advanced tab, in Startup and Recovery section click on the Settings button, then in the System failure section uncheck Automatically restart. After doing this the BSOD stays on screen until the PC is restarted.

 

[BiggyRat]

ok...

UPDATE:

BlueScreenView showed me the following:

STOP: 0x100000d1 (0x48422ecd, 0x00000002, 0x00000000, 0x86203c88)
NDIS.sys -Address 0xf7698b6c base at 0xf7692000

In the main view, where it highlights problem drivers, it highlighted the following:

NDIS.sys
ntoskrnl.exe

any ideas...??? (& I'm also searching myself)

thanks again,


BR

 

[linney]

818326 - STOP 0x0000001D or STOP 0x000000A Stop Error Occurs in Ndis.sys

http://support.microsoft.com/default.aspx?scid=kb;en-us;818326&FR=1&PA=1&SD=HSCH

829120 - You Receive a "Stop 0xD1" Error Message When You Try to Establish a TCP/IP Session

http://support.microsoft.com/default.aspx?scid=kb;en-us;829120&FR=1&PA=1&SD=HSCH

This lengthy post mentions NDIS.sys, which turned out to be a faulty Network Card.

If you get desperate you could try repairing windows by running it over itself. You will lose all your windows updates but your files will be untouched.

How to Perform an In-Place Upgrade (Reinstallation) of Windows XP (Q315341)

http://support.microsoft.com/kb/315341/en-us

WINDOWS XP - IRQL_NOT_LESS_OR_EQUAL
thread779-429616

Is this machine been kept updated? What Service Pack version is it running?

 

[BiggyRat]

linney...

thanks much.

I also grabbed the broadcom nic diagnostic utility AND the latest driver, from Dell.

maybe that'll do it...as an easy 1st try.

thanks again,


br

 

[linney]

I hope so, all the best.