NEED HELP
Friday, August 27, 2004 by SilentEagle | Discussion: WinCustomize Talk
IRQL_Not_Less_Or_Equal
stop: 0x0000000A (0x805e61e6, 0x00000002, 0x00000000, 0x805e61e6)
So I try to boot using "Previous Known Working Settings". Still I get the critial stop screen. So then I try to boot into safe mode. This time I get the critial stop screen but with different info:
RDR_FILE_SYSTEM
STOP: 0x00000027 (0xBAAD009C, 0xF97104E0, OxF97101E0, 0xF93029C6)
CDR4_xp.sys - Address F93029C6 base at F9301000, Datestamp 3c228bb1
I'm using Windows XP Home Edition
Pentium Celeron 1.2 Gigs
256 MB RAM
Can anyone help me with this error. I believe either BootSkin or LogOnSkin is causing this error. I really need to get back on my computer.
~SilentEagle
Reply #2 Friday, August 27, 2004 1:25 PM

Reply #4 Friday, August 27, 2004 4:17 PM

Reply #5 Friday, August 27, 2004 5:09 PM
Thanks for any help.
~SilentEagle
Reply #6 Friday, August 27, 2004 5:29 PM
Reply #7 Friday, August 27, 2004 6:03 PM
Reply #9 Saturday, August 28, 2004 12:02 AM
Quote from Pirates of the Carribean Curse of the Black Pearl
Elizabeth : That's it, then? That's the secret, grand adventure of the infamous Jack Sparrow. You spent three days lying on a beach drinking rum.
Jack Sparrow : Welcome to the Caribbean, luv.
Actually that irq_less than issue is what prompted me to by a new laptop.
I have that problem with a 2Ghz celeron Box, and I have done everything to try and resolve it. I think it is how windows assembles the OS Kernel on Install, and if something gets out of whack the least tiny bit, then you're Fux0r3d!
I have a problem on that box with lockups, and freezes. for some reason the connectors for the Hard Drives want to loosen, everynow and then from heat, and I have a PCI ATA card that does the same thing. I get that IRQ Crash and the machine starts freezing up, and I just shut it down, push all the cables, connectors and stuff, back snugg and it goes back to working alright. But after wifey watched me loose 50Gb of Mp3's to Drive crashes Several times and blaming, POS Machine..I got to get a new Laptop.
[Message Edited]
Reply #10 Saturday, August 28, 2004 12:28 AM
It sounds like you may have a hardware error which couldn't have been caused by BootDisk or Logon Studio. You may have to wipe your hard drive and try a new OS install. But, if you don't have the original WinXP OS disk, this option is impossible. But, this way, if the OS installation fails, you will definitely know that the problem is hardware related. Good Luck.
Reply #11 Saturday, August 28, 2004 12:30 AM
Reply #12 Saturday, August 28, 2004 12:48 AM
Reply #13 Saturday, August 28, 2004 12:48 AM
Reply #14 Saturday, August 28, 2004 8:30 PM
~SilentEagle
Please login to comment and/or vote for this skin.
Welcome Guest! Please take the time to register with us.
There are many great features available to you once you register, including:
- Richer content, access to many features that are disabled for guests like commenting on the forums and downloading skins.
- Access to a great community, with a massive database of many, many areas of interest.
- Access to contests & subscription offers like exclusive emails.
- It's simple, and FREE!








Reply #1 Friday, August 27, 2004 1:23 PM
The Stop 0xA message indicates that a kernel-mode process or driver attempted to access a memory location to which it did not have permission, or at a kernel interrupt request level (IRQL) that was too high. A kernel-mode process can access only other processes that have an IRQL lower than, or equal to, its own. This Stop message is typically due to faulty or incompatible hardware or software.
Interpreting the Message
This Stop message has four parameters:
Memory address that was improperly referenced.
IRQL that was required to access the memory.
Type of access (0x00000000 = read operation, 0x00000001 = write operation).
Address of the instruction that attempted to reference memory specified in parameter 1.
If the last parameter is within the address range of a device driver used on your system, you can determine which device driver was running when the memory access occurred. You can typically determine the driver name by reading the line that begins with:
**Address 0xZZZZZZZZ has base at -
If the third parameter is the same as the first parameter, a special condition exists in which a system worker routine, carried out by a worker thread to handle background tasks known as work items, returned at a higher IRQL. In that case, some of the four parameters take on new meanings:
Address of the worker routine.
Kernel interrupt request level (IRQL).
Address of the worker routine.
Address of the work item.
Resolving the Problem
The following suggestions are specific to Stop 0xA errors. For additional troubleshooting suggestions that apply to all Stop errors, see "Stop Message Checklist" later in this appendix.
A Stop 0xA message might occur after installing a faulty device driver, system service, or firmware. If a Stop message lists a driver by name, disable, remove, or roll back the driver to correct the problem. If disabling or removing drivers resolves the issues, contact the manufacturer about a possible update. Using updated software is especially important for multimedia applications, antivirus scanners, and CD mastering tools.
A Stop 0xA message might also be due to failing or defective hardware. If a Stop message points to a category of devices (video or disk adapters, for example), try removing or replacing the hardware to determine if it is causing the problem.
If you encounter a Stop 0xA message while upgrading to Windows XP Professional, the problem might be due to an incompatible driver, system service, virus scanner, or backup. To avoid problems while upgrading, simplify your hardware configuration and remove all third-party device drivers and system services (including virus scanners) prior to running setup. After you have successfully installed Windows XP Professional, contact the hardware manufacturer to obtain compatible updates. For more information about simplifying your system for troubleshooting purposes, see " Troubleshooting Concepts and Strategies" and "Troubleshooting Startup" in this book.
For more information about Stop 0xA messages, see the Microsoft Knowledge Base link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources. Search using keywords winnt, 0x0000000A, and 0xA.