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.

Resolved Irql_not_less_or-equal_to

Discussion in 'Windows XP' started by Clive RH, 2010/10/14.

  1. 2010/10/14
    Clive RH

    Clive RH Inactive Thread Starter

    Joined:
    2007/05/31
    Messages:
    19
    Likes Received:
    1
    My (Asus) laptop continually crashes and displays the error code above.
    I'm using Windows XP.
    Have tried uninstalling wireless driver as the most likely culprit but error continues.
    Many colleagues have the identical problem.
    Help please.
    Thanks,
    Clive.
     
  2. 2010/10/14
    markmadras

    markmadras Banned

    Joined:
    2010/08/23
    Messages:
    1,529
    Likes Received:
    105
    Have you installed any new programs or hardware just before this problem occured. And when the crashes occur does it concide with any particular activity.

    If you can look through your event logs this might give some clues as to the culprit. To see the Event Viewer logs, click Start, Settings, Control Panel, Administrative Tools, Event Viewer.

    You will need to look for an error event which coincides with your most recent crash time and date. Copy and paste at least 50 lines of it and post it back here.

    Have you tried running in safe mode to see if the problem continues.
     
    Last edited: 2010/10/14

  3. to hide this advert.

  4. 2010/10/14
    Clive RH

    Clive RH Inactive Thread Starter

    Joined:
    2007/05/31
    Messages:
    19
    Likes Received:
    1
    Hi,
    Thanks for the suggestion.
    Nothing new installed. The 'crash' problem occurred quite spontaneously, but rather suspiciously, following numerous Windows multiple updates. (the laptop hadn't been used for about four months). My computer specialist is also concerned about this as numerous other laptop users (different machines) have been experiencing similar problems. Disabling the wireless driver fixes the fault (but I need the wireless connection). Deleting the wireless driver and reinstalling , then swapping to an alternative driver doesn't fix the problem. The ndis.sys has been checked and is OK, virus scan is OK, checked with driver version held with one in 'container' - OK, Intel Pro Wireless update checked 22000BG checked and running version 810.12.2000. New version Driver is: 904.39
    Part of the error message when crashing refers to ndis
    I hope that some of this info is helpful.
    There are a lot of folks out there with laptops crashing to blue-screen all down to some difficulty with the wireless driver - and all it seems after a Windows Update of a few weeks ago.
    Help would really be appreciated.
    Thanks,
    Clive.
     
  5. 2010/10/14
    markmadras

    markmadras Banned

    Joined:
    2010/08/23
    Messages:
    1,529
    Likes Received:
    105
    Can you post the complete error message in full including any numbers.

    I sounds as if this is a problem with a windows update causing a conflict with your wireless driver. I can think of a few possible remedies, first check if there is an update available for the wireless driver to see if that works, next, do a system restore to a time before the MS updates were installed. If that all fails use your windows XP disc to run a Repair install (that's assuming you have a disc or you can borrow one of the same version of XP that is on your machine)

    Lets see how these remedies work out and then let me know how you get on.

    If the problem remains have a look in the event viewer logs and post the last 50 lines here, it may help.
     
  6. 2010/10/14
    Clive RH

    Clive RH Inactive Thread Starter

    Joined:
    2007/05/31
    Messages:
    19
    Likes Received:
    1
    Hello again,

    Thanks for your continued help.
    I contacted my computer specialist and he tells me that the only 'error' in the log is:irql_not_less_or_equal_to
    All drivers for the wireless comms are very latest - uploaded today.
    Thanks for your continued advice.
    Cheers,
    Clive.
     
  7. 2010/10/14
    Clive RH

    Clive RH Inactive Thread Starter

    Joined:
    2007/05/31
    Messages:
    19
    Likes Received:
    1
    Hello again,
    Further to my previous e-mail, the only message that appears relevant in the Error Log is this one:
    Event Type: Information
    Event Source: gupdate
    Event Category: None
    Event ID: 0
    Date: 14/10/2010
    Time: 10:53:50
    User: N/A
    Computer: LAPTOP
    Description:
    The description for Event ID ( 0 ) in Source ( gupdate ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Service stopped.

    Swapping to Safe Mode works OK as the wireless driver is disabled (and that's the apparent source of the problem).

    I hope this helps.
    Cheers,
    Clive.
     
  8. 2010/10/14
    markmadras

    markmadras Banned

    Joined:
    2010/08/23
    Messages:
    1,529
    Likes Received:
    105
    I think we can now be fairly sure that this problem is being caused by a conflict with a recent MS update and your wireless driver. Who do you blame:confused:

    One possible fix I have seen for the wireless driver is to uninstall it and then reboot to see if windows will use its own standard drivers without causing further BSOD's. That is a shot in the dark but may be worth a try. You could even try rolling back to an older driver version.

    The other solution is to go into control panel > Add or Remove Programs > check the 'Show updates' box and delete all the recent MS updates. You could (if you have the time and patience) delete one at a time and keep retesting until you find the one that is causing the problem. Then contact the provider of the wireless driver and ask if they have a solution.

    Good luck and if you find something conclusive please report back to this thread.
     
    Last edited: 2010/10/14
  9. 2010/10/14
    Clive RH

    Clive RH Inactive Thread Starter

    Joined:
    2007/05/31
    Messages:
    19
    Likes Received:
    1
    Hi,
    Thanks for confirming our suspicions - the question remains, what can I do about it and apparently the many thousands of others 'out there' with the same error message. Just in my small circle, I know of at least ten people with the same difficulty all arising from around the same period. My computer specialist reports several of his clients all with this problem.

    Ideas welcome.
    Thanks.
    Clive.
     
  10. 2010/10/14
    markmadras

    markmadras Banned

    Joined:
    2010/08/23
    Messages:
    1,529
    Likes Received:
    105
    I took a long time to edit my last post so they crossed over.
     
  11. 2010/10/14
    Clive RH

    Clive RH Inactive Thread Starter

    Joined:
    2007/05/31
    Messages:
    19
    Likes Received:
    1
    Hi Markmadras,
    Thanks for all your input on this.
    I'm much obliged.
    You may receive a few more queries about this from other equally baffled people.
    With all best wishes.
    Cheers,
    Clive.
     
  12. 2010/10/14
    markmadras

    markmadras Banned

    Joined:
    2010/08/23
    Messages:
    1,529
    Likes Received:
    105
    Your welcome.
     
  13. 2010/10/18
    Clive RH

    Clive RH Inactive Thread Starter

    Joined:
    2007/05/31
    Messages:
    19
    Likes Received:
    1
    Hi Markmadras,
    My computer specialist has fixed the problem.
    He informs me that there's a problem with the Intel Driver (latest download doesn't cure the glitch).
    He deleted the Intel wireless driver and used the 'zero config' one as the default.
    The laptop has been running trouble free now for several days.
    I hope this info may benefit others.
    Many thanks once again.
    Cheers,
    Clive.
     
  14. 2010/10/18
    markmadras

    markmadras Banned

    Joined:
    2010/08/23
    Messages:
    1,529
    Likes Received:
    105
    Just as I suggested in post 7, I'll remember that solution if it occurs again, thank you for letting me know.
     
  15. 2010/10/18
    Admin.

    Admin. Administrator Administrator Staff

    Joined:
    2001/12/30
    Messages:
    6,687
    Likes Received:
    107
    Please mark your thread as 'Resolved'.

     
    Clive RH likes this.
  16. 2010/10/18
    Clive RH

    Clive RH Inactive Thread Starter

    Joined:
    2007/05/31
    Messages:
    19
    Likes Received:
    1
    Thanks,
    I've now 'marked' the thread as 'Resolved' by clicking on the 'Thread Tools' option.
    Cheers,
    Clive.
     

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.