1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Error Message [IRQ_NOT_LESS_OR_EQUAL]

Discussion in 'Windows XP' started by thesilfieszone, 2007/11/30.

  1. 2007/11/30
    thesilfieszone

    thesilfieszone Inactive Thread Starter

    Joined:
    2007/11/29
    Messages:
    7
    Likes Received:
    0
    First off HI! I found these forums yesterday and they have been most helpfully, I'm sure my windows experience has been changed forever!!! <3

    So yesterday, my computer was randomly re-starting. I looked around and was able to go to MY COMPUTER > ADVANCED > STARTUP & RECOVERY and unchecked "automatically restart" box.

    Now i received a blue screen of death....

    A problem has been detected and windows has been shut down to prevent damage to your computer.

    IRL_NOT_LESS_OR_EQUAL

    if this is the first time you have seen this stop error screen, restart your computer if this screen appears again follow these steps...

    1.) check to make sure any new hardware or software is properly installed. if this is a new installation ask your hardware or software manufacturer for any windows updates you might need.

    2.) if problems continue, disable or remove any newly installed hardware or software. disable BIOS memory options such as catching or shadowing if you need to use safe mode do so.

    Technical Information:

    ***STOP: 0x0000000A, 0xe21a9000, 0x0000002, 0x0000001, 0x805952ba

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


    ~~~~~~~~~~~~~~~~~~~~~~

    I recently installed a fax modem, and winfax. I'm sure it might be one of those problems.
     
  2. 2007/11/30
    surferdude2

    surferdude2 Inactive

    Joined:
    2004/07/04
    Messages:
    4,009
    Likes Received:
    23
    Welcome aboard!

    Try software first and then hardware...uninstall WinFax and test. If no joy, pull the newly installed modem and test. This sort of error is usually generated by a driver that is not appropriate for the system but can also be caused by incompatible hardware.
     

  3. to hide this advert.

  4. 2007/11/30
    thesilfieszone

    thesilfieszone Inactive Thread Starter

    Joined:
    2007/11/29
    Messages:
    7
    Likes Received:
    0
    thanks, i think it's the software. it's a shame because WINFAX was such a good program. now i need to find something else.

    thanks again!
     
  5. 2007/11/30
    Wildone_106

    Wildone_106 Inactive

    Joined:
    2002/10/10
    Messages:
    48
    Likes Received:
    0
    Wow..I was about to post the exact same problem on my wifes computer:
    http://img340.imageshack.us/img340/8166/erroryd1.jpg

    Only we hav'nt installed any new hardware or software that I can think of..but now it does this BSOD randomly..any other recourse's we can take?

    I did a virus scan & defragged, have 52gb harddrive space..very puzzling. I only posted here as the error is the same as the OP not trying to hijack the thread:)
     
  6. 2007/12/01
    mailman Lifetime Subscription

    mailman Geek Member

    Joined:
    2004/01/17
    Messages:
    1,901
    Likes Received:
    11
    Hi, Wildone. :)

    Microsoft KB314063: Troubleshooting a Stop 0x0000000A error in Windows XP

    aumha.org: TROUBLESHOOTING WINDOWS STOP MESSAGES

    ==========

    Perhaps a DebugWiz-generated BSOD dump log will help you determine the cause.

    Please carefully follow all the instructions in this link and then paste a few of your most recent DebugWiz-generated BSOD dump log analysis reports in a new thread (so you don't have to feel guilty about hijacking someone else's thread).

    The DebugWiz application should be run while connected to the Internet so your Windows Debugging Tools can retrieve the proper "symbols ". The additional information the DebugWiz-generated reports provide might help us narrow down the culprit more quickly.

    For critical program errors, the DUMP file will be found in \Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\user.dmp

    For "Blue Screen Of Death" (BSOD) system crashes, the DUMP file will be found at C:\WINDOWS\Minidump\MEMORY.DMP (mini-model setting) or be found for large model settings at C:\MEMORY.DMP

    ========

    After producing a DebugWiz-generated dump log, you might be able to determine the cause by reading this 4-page article, Network World: "How to solve Windows system crashes in minutes" (specifically the last paragraph of page 3 and all of page 4).
     
    Last edited: 2007/12/01
  7. 2007/12/03
    thesilfieszone

    thesilfieszone Inactive Thread Starter

    Joined:
    2007/11/29
    Messages:
    7
    Likes Received:
    0
    wow that's great advice! I was just HOPING it was the softwhere and the modem, but i sitll got the blue screen later!

    I LOVE THIS SITE!!!
     
  8. 2007/12/03
    mailman Lifetime Subscription

    mailman Geek Member

    Joined:
    2004/01/17
    Messages:
    1,901
    Likes Received:
    11
    Thanks for your compliments, thesilfieszone! :)

    I'm glad you're finding the information useful here at Windows BBS. There's a LOT of good information here. :)

    Please keep us posted on your progress and feel free to post a few dump logs in this thread if you find it necessary to seek further assistance with your current issue.

    Good luck!
     
  9. 2007/12/04
    thesilfieszone

    thesilfieszone Inactive Thread Starter

    Joined:
    2007/11/29
    Messages:
    7
    Likes Received:
    0
    i'll let you know how it goes today. I took out the old modem, because i read somewhere that the type of modem i purchased was cheep, and flawed. I purchased a Smartlink modem - but was told that it did not support the E0 command, this is a standard modem command but not supported by these modems.

    I also X'ed WINFAX, and am going to try SNAPPY FAX. Hopefully it won't crash again with a new modem and fax software. If not i'll start the debugging process.

    Thanks Again!
     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.