IRQL_NOT_LESS_OR_EQUAL

Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)

A few days ago, my WinXP Home edition started restarting spontaneously. I
turned off auto-restart and after a few more restarts, I finally got a blue
screen. Besides the "A problem has been detected..." the relevant bits are...

IRQL_NOT_LESS_OR_EQUAL

Technical information:
*** STOP: 0x0000000A (0x00556018, 0x0000001C, 0x00000000, 0x804E323B)

I gather from the article on this fault that it is a read fault, but I don't
know how to determine which application/driver/etc. is involved. I've tried
rolling back the restore by a month (the problem has only presented itself
for a few days) and closing all unnecessary apps.

I haven't been able to run a full virus, or AdAware scan, because the
computer hasn't run long enough between restarts.

Any advice?
--
Cheers,
Stephen

Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)

Update:
Another stop. This time, no "IRQL..." just...

*** STOP: 0X0000000B8 (0X00000000, 0X00000000, 0X00000000, 0X00000000,)
--
Cheers,
Stephen

Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)

I would also suggest going into Control Panel/Administrative Tools/Event
Viewer and taking a look at both the Application and System listings in the
left panel. Tapping on those will reveal "events" in the right pane where
you can look for error messages denoted by either a yellow triangle with an
exclamation point (advisory) or a red circle with a white X (warning, real
issue). Those can be right-clicked with a selection of Properties to see a
portion of the problem. It may lead you to a specific driver or hardware
which is causing the issue.

--
Michael

"stephmon" <stephmon@discussions.microsoft.com> wrote in message
news:E81FD8E4-1E50-4110-ABF6-DEA3B7CD06F1@microsoft.com...
>A few days ago, my WinXP Home edition started restarting spontaneously. I
> turned off auto-restart and after a few more restarts, I finally got a
> blue
> screen. Besides the "A problem has been detected..." the relevant bits
> are...
>
> IRQL_NOT_LESS_OR_EQUAL
>
> Technical information:
> *** STOP: 0x0000000A (0x00556018, 0x0000001C, 0x00000000, 0x804E323B)
>
> I gather from the article on this fault that it is a read fault, but I
> don't
> know how to determine which application/driver/etc. is involved. I've
> tried
> rolling back the restore by a month (the problem has only presented itself
> for a few days) and closing all unnecessary apps.
>
> I haven't been able to run a full virus, or AdAware scan, because the
> computer hasn't run long enough between restarts.
>
> Any advice?
> --
> Cheers,
> Stephen

Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)

Try all the following with existing dump files but you can also turn on the
Driver Verifier (type verifier in Start Run and follow the wizard). This is
strict checking of all drivers (so it makes computer slower). This may give
different error messages and pinpoint one driver that is not crashing but
causing another driver to crash. If you can't start after enabling verifier
choose Last Known Good Configuration at the Failed Boot menu (which will
start without verifier).

Get your XP CD and install Windows Support Tools.


Type in start run after installing and rebooting


pstat > "%userprofile%\desktop\driverl­ist.txt"


The last table in this file is a list of loaded drivers. Other things apart
from hardware uses drivers. Post the list of drivers (the last table only -
REPEAT THE LAST TABLE O N L Y ) or match the fault address to the driver.


If you have the XP SP2 Security Update CD (else see
http://www.microsoft.com/whdc/­de [...] pkg.m­spx
)


Install symbols from <CD Drive Letter>:\SUPPORT\SYMBOLS


Download
http://www.microsoft.com/whdc/­de [...] x86.­mspx


Load the crash dump file into windbg (File - Load Crash Dump and it's in
c:\windows\minidump) and READ WHAT IT SAYS (you may need to tell it where
the symbol files are), then
Type
!Analyze -v
into Windbg's command line.
(this will hopefully tell you the faulty component)

If a minidump doesn't help use a kernel dump, if that doesn't help create a
full dump.

You can look up specific details here
http://msdn.microsoft.com/library/ [...] dtools/hh/
ddtools/BCIntro_ea8b9fd0-2d81-4a04-a7ed-c1c6a80bd501.xml.asp

If it indicates faulty memory might be the cause you can get a memory tester
here
http://oca.microsoft.com/en/wi­ndiag.asp


If it mentions a core windows system file, meaning it a MS fix is required,
upload a minidump to

http://oca.microsoft.com

Also try typing the main error code in Help while online (ie,
Stop 0x50
and also try in the 8 digit form
stop 0x00000050)
and if there are too many hits use a filename if available. Generally memory
addresses are different for each computer (as each computer has a different
mix of drivers) so parameters aren't that useful for searching.




--
--------------------------------------------------------------------------------------------------
http://webdiary.smh.com.au/archive [...] 01075.html
=================================================
"stephmon" <stephmon@discussions.microsoft.com> wrote in message news:E81FD8E4-1E50-4110-ABF6-DEA3B7CD06F1@microsoft.com...
> A few days ago, my WinXP Home edition started restarting spontaneously. I
> turned off auto-restart and after a few more restarts, I finally got a blue
> screen. Besides the "A problem has been detected..." the relevant bits are...
>
> IRQL_NOT_LESS_OR_EQUAL
>
> Technical information:
> *** STOP: 0x0000000A (0x00556018, 0x0000001C, 0x00000000, 0x804E323B)
>
> I gather from the article on this fault that it is a read fault, but I don't
> know how to determine which application/driver/etc. is involved. I've tried
> rolling back the restore by a month (the problem has only presented itself
> for a few days) and closing all unnecessary apps.
>
> I haven't been able to run a full virus, or AdAware scan, because the
> computer hasn't run long enough between restarts.
>
> Any advice?
> --
> Cheers,
> Stephen

Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)

Thanks to everyone for the feedback, it's all been tremendous. I'm not sure
when I'll have a chance to tackle all of this, since I'm preparing to move to
California soon. Hopefully, I'll be back with good news in a few weeks.

Thanks again to all!
--
Cheers,
Stephen