BugCheck BSOD's

Software & Operating Systems

Software & Operating Systems
Microsoft, Linux, Productivity software, discussion

BugCheck BSOD's

  • Every few days now (usually unattended and off-line) there is a spontanious reboot and event viewer says "BugCheck" Reboot.
     
    Having now set it not to restart, this was the information on the BSOD:
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    IRQL_NOT_LESS_OR_EQUAL
     
    (the usual ...'if this is first time...")
     
    Technical information:
     
    *** STOP: 0x0000000A(0x00000054,0x00000002,0x00000001,0x804ECC86)
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     
    Six week old Dell D800, WinXPpro sp1 (had installed sp2 when first arrived and removed it due to BSOD's, only software installed at that time was NortonSystem 2003)
     
    Other than this very intermintant event, system seems fine.
     
    This has occured on/off D/Port Dock and on/off line and today, for first time, while in use.
     
    Art

    Message Edited by Art on 10-23-2004 12:43 PM

  • Stop 0x0000000A or IRQL_NOT_LESS_OR_EQUAL

    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.

    This issue can be caused by any of the following possibilities:

    1. Mcafee VirusScan for Windows issue
    2. Windows NT 3.51 upgrade from Windows NT 4.0
    3. Service Pack
    4. Driver issue
    5. Hardware issue

    Now what you need to do is think back to when this problem started , was it after installing some game/printer/digital camera/anti virus ?

    try a sfc /scannow , system restore , repair install

     What steps should I attempt to possibly avoid reinstalling Microsoft® Windows® XP?

    How do I perform a Repair Reinstall of Microsoft® Windows® XP?

    How do I use the System Restore utility in the Microsoft® Windows® XP operating system?

  • Thank you for posting such a resourceful response to my problem.  Let me address the possibilities:
     
    1.  McAfee has never been here, Norton System 2003 was the first install and immediately updated prior to visit to MS UpDate for sp2.
     
    3.  Service Pack sp2 was second install and then uninstalled after many BSODs in first seven days.  All other MS Updates were then installed and MS Firewalls enabled.  SpyBot and Ad-Aware are also up to date.
     
    4.  There are two (serenum, Prolific Technology) UnSigned Drivers, first is for a Holux usb 210 GPS and this is now going to be replaced with a Holux Bluetooth 230 GPS that I expect will need no driver.  Second one is for a FutureDial usb connection to cell phone, this is used with a SnapDial win-modem to dial out as well as SnapSync to address cell phone's addressbook.  Although system would often get confused about whether it was GPS or CellPhone that I wanted driven, neither one has ever been connected during this BSOD error.  Is it a safe assumption that since those drivers are not shown in Device Manager when they are not plugged in, that they could not be at the root of this problem?
     
    5.  No other external hardware (Dell D/Port, WxWorx XM Satellite weather receiver),  ethernet broadband or telephone modem connection are common to these events.  I would hope that a hardware failure within the D800 would become a lot less intermintant than 2-3 days between failures.  I recall a sign in the TV Repair Shop "not responsible for intermintant problems" and can only encourge this to become constant for troubleshooting purposes.  I would need to operate for several days on one of two 512MB RAMs (one from Crucial) to eliminate that before sending in for possible hardware repair.
     
    During the one week that sp2 was installed, there were five "Application Hang" freezes and five Cat (102) System Errors  in addition to the bugcheck crashes detailed below:

    Date:  9/11/2004
    Time:  7:33:09 PM
    Description:
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000c2 (0x00000040, 0x002a0000, 0x80000000, 0x00000000).
    Date:  9/14/2004
    Time:  6:23:51 PM
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x1000000a (0x00000000, 0x000000ff, 0x00000000, 0x806f2a71).
    Date:  9/14/2004
    Time:  8:58:19 PM
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000077 (0x00000001, 0xe235a008, 0x00000000, 0xb1ad095c).
     
    Only the middle one above looks like a "Stop 0xA" but after a history of two crashes a day, sp2 was removed.

    Date:  9/15/2004
    Time:  6:15:05 PM
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0x00000004, 0x00000002, 0x00000001, 0x804e3cd5).
    Date:  9/16/2004
    Time:  3:20:13 AM
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000004e (0x00000002, 0x00019ba5, 0x0003ffad, 0x00000001).
    Date:  9/18/2004
    Time:  1:52:20 PM
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000004e (0x00000099, 0x00000000, 0x00000000, 0x00000000).
     
    I believe that the five problems below were related to FutureDial's software and those went away after a download from FutureDial's website of a software program update on the evening of 9/29.

    Date:  9/25/2004
    Time:  1:45:48 AM
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000d1 (0x00000004, 0x00000002, 0x00000000, 0xf7a91c4e).
    Date:  9/25/2004
    Time:  9:07:48 PM
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000d1 (0x00000004, 0x00000002, 0x00000000, 0xf7ab1c4e).
    Date:  9/25/2004
    Time:  10:27:01 PM
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000d1 (0x00000008, 0x00000002, 0x00000000, 0xf7aba144).
    Date:  9/26/2004
    Time:  5:54:56 PM
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000d1 (0x00000060, 0x00000002, 0x00000000, 0xb21cbee7).
    Date:  9/29/2004
    Time:  12:50:58 AM
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000d1 (0xffbff30c, 0x00000002, 0x00000000, 0xf60136cf).
     
    The six events below, I can not associate with any install or other change to the system.

    Date:  10/2/2004
    Time:  12:46:58 AM
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0x00000004, 0x00000002, 0x00000000, 0x805135d8).
    Date:  10/11/2004
    Time:  8:17:45 AM
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0x96dbe7c8, 0x00000002, 0x00000001, 0x8051361f).
    Date:  10/12/2004
    Time:  12:09:47 AM
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x1000008e (0x80000004, 0x805315dc, 0xac9998f0, 0x00000000).
    Date:  10/19/2004
    Time:  1:36:01 PM
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000d1 (0x00000000, 0x00000002, 0x00000000, 0x00000000).
    Date:  10/21/2004
    Time:  2:34:25 PM
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000d1 (0x006f0075, 0x00000002, 0x00000000, 0xf123f144).
    Date:  10/23/2004
    Time:  10:10:57 AM
    This was the "0xA" that was detailed in post that you provided such excellent analysis of in your reply.
     
    The only freezes that have occurred since removing sp2, six weeks ago, were in the few hours that I had latest ALPS driver installed.  Unfortunately, all records of those were lost when I used GoBack to revert behind driver install point.
     
    After I post this message, I will be allowed to copy some of that 'code' and take it to some of the sites that you linked for me and search for answers.
     
    Art
     
     
    Edit:
     
    Just taking some of the above code to the first link that you provided (...XP/all/reskit...) I can see, will give a lot of insight as to what process may cause such an error.
     
    It is the 'hardware' aspect that I fear most, but it was Dell's hardware quality (and three year protection) that brought me back; in seven years of coffee drowns, three foot drop tests, overheat-to-freeze and operation of software way beyond its design capability, my Latitude LM has never had any 'hardware' failures.
     
    For the software conflicts, when you need the program and they say "never mind the 'driver-sign', we have tested it and its Ok" what can you do!


     

    Message Edited by Art on 10-24-2004 01:13 PM