Share via

IRQL_NOT_LESS_OR_EQUAL (0x0000000A)

Anonymous
2010-09-18T21:47:36+00:00

Last month I formatted my hard drives and reinstalled Windows.  At first, I had tons of problems getting Windows to install (very random BSODs), and after running Memtest86 on each of my 4 sticks of RAM, I found a bad stick.  So while I'm waiting for an RMA on that....I continued with the Windows install using 2 sticks of good RAM (I ran Memtest on each of them for about 2 hours).  Windows installed fine, and I've had pretty good luck getting all my software and external devices reinstalled.  However, I'm getting this error a few times a week:

IRQL_NOT_LESS_OR_EQUAL

0x0000000A (0x00000013, 0x0000001C, 0x00000001, 0x80502302)

The error is consistently the "0A" error, but I haven't been observant enough to see if the four trailing parameters are always the same.  Oftentimes, the BSOD hits during the night, when I'm not able to observe it, and the computer sometimes restarts on its own.  Other times, I have to manually restart it.  There's never any other identifying information (like a file specified), and there is NOTHING in my Event Viewer...EVER.  It basically tells me that the computer was restarted, because I can see all the services restarting and their time-stamps, but I can't find anything telling me that the restart was caused by an error.

Also, I've read on Microsoft's website that I should be able to submit a Windows Error Report after these errors -- but I'm never given that option.

I've downloaded and installed the BlueScreenView utility, but the only BSODs it's reporting are a couple from earlier this month related to my RAID controller (0x00008086, iaStor.sys).  That problem was solved during my first round of driver updates.  But these current problems are not registering in BlueScreenView.

I've updated all of my drivers with the most current ones available on the manufacturers' websites, so I don't know what more I can do on that front.

The only thing different about the setup from BEFORE I wiped out the hard drives is that I'm now just using the onboard audio, since I never saw any benefit to using the Turtle Beach Riviera card I was previously using.  So I just removed it to open up the space in the case and am quite happy with the onboard audio.  Those drivers are also current.  Nothing else is any different, so I'm hesitant to start pulling things out one-at-a-time since they worked fine before.

For what it's worth, my computer is home-built.  Abit IP35 Pro motherboard, 700W power supply, EVGA GeForce 8600 GT video, G.Skill DDR2 RAM (2 GB now, originally 4 GB; 1 GB being RMA'd, and I removed its "mate" from the system until I get the new stick).  I HAVEN'T updated the BIOS in a while -- my understanding is that flashing a BIOS without needing to is risky, and this system worked fine before with the current BIOS.  I'm not sure if there's a new one available or not.

What can I try next?

Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

23 answers

Sort by: Most helpful
  1. Anonymous
    2010-09-18T23:38:00+00:00

    Sure - send it.  Sometimes folks can come up with 5 easily and want to send them all, but I think the last 5 are adequate!  If I don't look at it right away, somebody else will see it.

    12 hours is plenty of time to run MBAM and SAS too.

    Now that your BSOD knows you are looking for it, it may evade you.

    Describe your current antivirus and anti malware situation:  McAfee, Norton, Spybot, AVG, Avira!, MSE, Defender, ZoneAlarm, PC Tools, Comodo, etc.

    Since you mentioned audio, might as well check it out while we are waiting (and video info won't hurt):

    Please provide additional information about your system:

    Click Start, Run and in the box enter:

    msinfo32

    Click OK, and when the System Summary info appears, click Edit, Select All, Copy and then paste the information back here.

    For video driver information, expand the Components, click Display, click Edit, Select All, Copy and then paste the information back here.

    For audio information, expand the Components, click Sound Device, click Edit, Select All, 

    Copy and then paste the information back here. 

    There will be some personal information (like System Name and User Name), and whatever appears to be private information to you, just delete it from the pasted information.

    This will minimize back and forth Q&A and eliminate guesswork.


    Don't guess what the problem might be - figure it out and fix it. I need YOUR votes and points for helpful replies and Propose as Answers. I am saving up for a pony!

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2010-09-18T23:24:50+00:00

    Sorry -- yes, that other stuff (small memory dump, and the path to the minidumps) was already exactly as you specified.  Which leaves me puzzled as to why I don't have any dumps to look at right now.  But hopefully the next BSOD will generate one.

    The last two came about 12 hours apart (about 11:30 last night, after I went to bed, and about 11:45 this morning).  But, typically, it can go a day or two without happening.  Do you not want me to send the dump information the next time I get one (and wait until I get 5 of them)?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2010-09-18T23:05:27+00:00

    Good job.

    Did you set up the other stuff too (small dump, to the Minidump folder, etc.)?

    When you get some recent dumps, do this with your BSV:

    If you double click on of the dumps, you will get some information about it (including the Caused By Driver field) and you may be able to spot the problem right away - especially if you see a pattern in the dumps where the Caused by Driver field is the same (start with that driver).

    Select (highlight) one or more of the most recent dump files by clicking them and holding down the Ctrl key to select multiples files.  Try to select just the most recent ones that relate to your issue (maybe five or so dump files to get started).

    Click File, Save Selected Items and save the information from the dumps to a text file on your desktop called BSOD.txt.  Open BSOD.txt with a text editor, copy all the text and paste it into your next reply.

    Here is an example of the BSV report from a single BSOD that I initiated on purpose that shows the cause of the crash as the i8042prt.sys driver belonging to Microsoft Corporation:

    ==================================================

    Dump File         : Mini062110-01.dmp

    Crash Time        : 6/21/2010 11:51:31 AM

    Bug Check String  : MANUALLY_INITIATED_CRASH

    Bug Check Code    : 0x000000e2

    Parameter 1       : 0x00000000

    Parameter 2       : 0x00000000

    Parameter 3       : 0x00000000

    Parameter 4       : 0x00000000

    Caused By Driver  : i8042prt.sys

    Caused By Address : i8042prt.sys+27fb

    File Description  : i8042 Port Driver

    Product Name      : Microsoft® Windows® Operating System

    Company           : Microsoft Corporation

    File Version      : 5.1.2600.5512 (xpsp.080413-2108)

    Processor         : 32-bit

    Computer Name     : 

    Full Path         : C:\WINDOWS\minidump\Mini062110-01.dmp

    ==================================================

    Send the information from the last 5 memory dumps.


    Don't guess what the problem might be - figure it out and fix it. I need YOUR votes and points for helpful replies and Propose as Answers. I am saving up for a pony!

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2010-09-18T23:01:41+00:00

    The "Write an event to the system log" and "Send an administrative alert" boxes were already checked.  I did uncheck the "Automatically restart" box.

    NVIDIA reports that no driver updates are needed.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2010-09-18T22:08:06+00:00

    I would use BlueScreenView too, but perhaps your XP is not set up to log these events, create dump files or put the dump files where BSV expects to find them by default:

    XP is set up to automatically reboot on some system failures, so you need to disable that feature so the BSOD information will stay on the screen for you to see it.  You can also configure XP to log an event and create a memory dump file in a specified folder for each BSOD.

    Configure your system to not automatically restart on system failure (that is what it wants to do):

    Right click My Computer, Properties, Advanced, Startup and Recovery Settings.

    In the System failure section:

    Put a check mark in the "Write an event to the system log" box

    Put a check mark in the "Send an administrative alert" box

    Uncheck the "Automatically restart" box

    In the Write debugging information section, choose:

    Small memory dump (64 KB)

    Set the Small dump directory to:

    %SystemRoot%\Minidump

    Click OK, OK.

    Restart your computer and wait for the next BSOD (not very exciting, this waiting...).

    While you are waiting, you should also verify your NVIDIA drivers as follows:

    I would navigate to the NVIDIA website and let their online scanner take a look at your video card and see what it suggests for drivers and consider their analysis if they suggest a new driver.

    It is recommended to run the NVIDIA scan with Internet Explorer.

    Here is the address to the NVIDIA page:

    http://www.nvidia.com/Download/PreScan.aspx?lang=en-us

    Read the directions, then click the GRAPHICS DRIVERS button to start the scan.

    Optional, but recommended:

    Download, install, update and do a full scan with these free malware detection programs:

    Malwarebytes (MBAM):  http://malwarebytes.org/

    SUPERAntiSpyware: (SAS):  http://www.superantispyware.com/

    They can be uninstalled later if desired.


    Don't guess what the problem might be - figure it out and fix it. I need YOUR votes and points for helpful replies and Propose as Answers. I am saving up for a pony!

    Was this answer helpful?

    0 comments No comments