IRQL error

I'm trying to track down an IRQL_NOT_LESS_OR_EQUAL blue screen.

Info: Win XP w/256 Meg ram

Complete error message is:
"A problem has been detected and windows has been shut down to prevent damage to your computer.

IRQL_NOT_LESS_OR_EQUAL

If this is the first time you've seen this stop error screen, restart your computer. If this screen appears again, follow these steps:

Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware or software manufacturere for any windows updates you might need.

If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching and shadowing. If you need to use safe mode to remove or disable components, restart your computer, press F8 to select Advanced startup options, and then select safe mode.

Technical Information
***STOP:0x0000000A (0x805B30FC, 0x00000002, 0x00000000, 0x805B2FD1)

Beginning dump of physical memory
Physical memory dump complete.
Contach your system administrator or technical support group for further assistance. "

If I'm reading this correctly it says that 0x805B30FC {reserved for system use} was improperly called on 0x00000002 {IRQ reserved for system use to cascade IRQs 8-15} for a read only 0x00000000 by 0x805B2FD1 {com port 2}

Could someone please tell me if I'm reading this correctly? I can't check the device manager for a conflict because the computer is my brother's and he's not within driving range. But if I am reading this correctly I could have him change the IRQ for COM2 to 3 and hopefully he will be able to get on line again.

Thanks in advance!!!!

 

As you may have already seen from Troubleshooting a Stop 0x0000000A Error in Windows XP and lots of other references, it is either a piece of hardware or a driver causing the stop.

But after that, it's pretty non-specific and I on't know of any way other than trial & error to pin-point the problem unless it just started after he added a device or updated one.

Best suggestion I can make is if there is a new device attached, check the HCL to make sure XP will deal with it and if so, try for a different driver.

If there isn't anything new, it might work to back up to a restore point from before the error started.

Moving this to the XP section.

 

Yes, I've check out that page and many more. He hasn't installed any new hardware or software. That's what is so confusing about it. It almost always happens when he tries to go on line {AOL}. He reinstalled AOL but did a restore before he checked to see if that stopped the error and the restore "un-did" the reinstall.

Any and all ideas are welcome!

 

I have seen screens like that when a memory stick has gone bad. Could you try swapping the memory out and see if that solves the problem? Good luck.

 

That is something I hadn't thought of since the system is almost new. But I'll check it out. That would probably explain why an almost new system is slower than the vintage {'95 era} Compaq he had. At least the Compaq is faster now that I've done a format and installed Win 98 on it.

Thanks for the idea...

 

Problem is alo known to be associated with adaptec cd burner software/drivers using the direct cd component. If this software is used it may need to be updated or uninstalled.

SEE:
IRQ_NOT_LESS_OR_EQUAL

To try to work around this issue: If Easy CD Creator is still installed, uninstall it, or uninstall only the DirectCD component.

Rename the Udfreadr.sys and Cdudf.sys files that are located in the %Systemroot%\System32\Drivers folder to Udfreadr.old and Cdudf.old. File properties: Udfreadr.sys, 23-Oct-01, 5.0.2.155 Cdudf.sys, 11-Jan-01, 5.0.2.155. NOTE : These files may have already been removed by the uninstaller program for Easy CD Creator.

Go to Start/Run/Regedit and Delete the following registry keys and then Rebooot:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\UdfReadr
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\cdudf

I haven't figured out how this would tie into an AOL conflict other than a possible resource or driver conflict but I thought it worth mentioning since it apparently has been a frequently reported known error and problem association.