WinXP crash - detailed error message!

  1. #1
    jhiker is offline Newbie

    WinXP crash - detailed error message!

    Hi,
    First time on the forum....

    My daughter's Toshiba Satellite P10 laptop started behaving strangely yesterday. She hasn't installed any new hardware or software recently but Win XP HE continually shows a BSOD and reboots after about 10mins. As far as I know she has all the critical service updates. We disabled the auto reboot and here is the error message in as much detail as I can recall. She has a Toshiba 'Tools & Utilities' disk and a Windows 'Recovery Disk' - Win Xp came pre-installed on the laptop. I have my own copy of Win XP Home Edition if this is relevant to any repair procedure that might be recommended. She uses the laptop for coursework so I need to get this sorted asap. Any help would be much appreciated. The error message follows below in as much detail as I can recall - she's 200 miles away so this is being done over the phone!
    She has used system restore to roll back to a week ago when all was stable and run ad-aware and cleaned out three pieces of spyware. She has also run a virus check boot-up scan with Avast! - the problem persists.
    I have asked her to start in safe mode and see if it still happens - no reply yet.

    Problem detected...
    DRIVER_IRQL_NOT_LESS_OR_EQUAL
    If this is the first time, restart, etc...... (then the usual note about checking recently installed hardware/software)... it goes on..
    Technical information...
    First, there's what look like three 'stars' then it goes on (the same line)
    STOP:0X000000D1(0X950DD45C,0X0000000Q,0X00000001,0 XF710FEC4)
    next line goes like this..
    '3 stars again' then MA111nd5.sys-addressF710FEC4 base at F7102000,datestamp 403bfe87
    - beginning dump of physical memory
    - physical memory dump complete
    - contact system administrator...

    Hope someone can advise - many thanks.
    Jeff


  2. #2
    jephree is offline ¨*·.¸ «.·°·..·°·.» ¸.·*¨
    0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    (Click to consult the online Win XP Resource Kit article.)
    The system attempted to access pageable memory using a kernel process IRQL that was too high. The most typical cause is a bad device driver (one that uses improper addresses). It can also be caused by caused by faulty or mismatched RAM, or a damaged pagefile.

    http://aumha.org/win5/kbestop.htm

    MA111nd5.sys is a driver for Netgear wireless adapter.

    Is this new? Does she have drivers for it? An installation disk?

    Also view your Error Log via:
    [1] Start Menu
    [2] Help and Support
    [3] Pick a Task
    [4] Tools
    [5] Advanced System Information
    [6] View the Error Log

  3. #3
    jhiker is offline Newbie
    Thanks for that. The MA111 wireless adaptor isn't new, she's been using it for three or four months with no problem. The Netgear wireless configurator and drivers have been installed from the CD that came with it though I might see whether there are more recent ones on the Netgear website.
    Bizarrely, she called me 24hrs later to say the computer had been on for several hours with no problem. She turned it off and came back to it later and again no crashes over an extended period!
    All this despite crashing every 10mins the previous day despite closing the computer down and starting up again for a new session.
    Is it possible for an error like this to 'right itself' spontaneously like this, or can i expect it to happen again do you think.

    Your comments are much appreciated.

  4. #4
    jephree is offline ¨*·.¸ «.·°·..·°·.» ¸.·*¨
    Certainly a combination of processes could have been getting tangled up just at a temporary juncture.

    Especially if it was a Page File Error it could easily have been a temporary issue.

    Let us know if problems return.

+ Reply to Thread