Bsod with error code:  100000d1

By mainframer
May 2, 2008
  1. Hello everyone!

    I'm new to TeshSpot and hope that someone out there can help me! I found this site by Googling 100000D1 trying to find some assistance.

    I'm running a new PC (built Feb 2008) with Win XP Sp2 on it. It's been rock solid until Apr 16 when it started going BSOD on me.

    A typical Event Log entry looks like:

    Event Type: Error
    Event Source: System Error
    Event Category: (102)
    Event ID: 1003
    Date: 5/2/2008
    Time: 7:05:40 AM
    User: N/A
    Computer: TOGNETTI01
    Error code 1000008e, parameter1 c0000005, parameter2 0a1f0004, parameter3 ba9e7250, parameter4 00000000.

    For more information, see Help and Support Center at .

    0000: 53 79 73 74 65 6d 20 45 System E
    0008: 72 72 6f 72 20 20 45 72 rror Er
    0010: 72 6f 72 20 63 6f 64 65 ror code
    0018: 20 31 30 30 30 30 30 38 1000008
    0020: 65 20 20 50 61 72 61 6d e Param
    0028: 65 74 65 72 73 20 63 30 eters c0
    0030: 30 30 30 30 30 35 2c 20 000005,
    0038: 30 61 31 66 30 30 30 34 0a1f0004
    0040: 2c 20 62 61 39 65 37 32 , ba9e72
    0048: 35 30 2c 20 30 30 30 30 50, 0000
    0050: 30 30 30 30 0000

    Everything I've read seems like it could be anything from needing a BIOS update to a hardware problem, to a driver issue.

    I've seen other posts on where someone can analyze a minidump? I was wondering if someone could look at mine and see if a cause can be narrowed down. I'd like to find the real cause and fix it instead of stabbing in the dark.

    Even better would be somewhere or somehow to learn how to read these myself. Coming from a mainframe environment, I'm used to reading dumps if I can find where to start.

    Not sure how to upload the minidumps...I see I can have attachments. I'll attach the dumps there and hopefully you can get to them.

    I look forward to hearing from you!

    Thanks in advance!
  2. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    Your one error is an 0x4E which is a very good indication of bad RAM and your minidump in particular cited memory corruption. Corrupted memory can cause all kinds of headaches.

    I strongly suggest you go to the following website and download their free MemTest utility for eith floppy or CD. Then run MemTest on your RAM for a minimum of 7 passes. This takes a long time but well worth it.

    If you have any errors then you need to run the test for a each stick of RAM and replace the bad stick(s).

    Also, in your other minidumps a driver for Norton (Symantec) a dfirewall driver for Trendmicro firewall were cited. Tell us what security software you are running.
  3. Bobbye

    Bobbye Helper on the Fringe Posts: 16,335   +36

    Thank you for posting the Event Error. I can't open the dmp files, but here are the possiblilites based on the Event Error:

    1. The computer automatically restarts, you receive an error message or a Stop error message, or an event is logged in the system event log when you try to connect to a remote Microsoft Windows Server 2003-based computer by using a Terminal Services session;en-us;894061
    (This issue occurs because of the NULL pointer deference in win32k.sys._

    2. A Windows Server 2003-based computer crashes and then generates the following error message: "STOP: 0x0000008E":;en-us;907966
    (This is caused by a problem in the Win32k.sys file.)

    3. You may receive an error message on a Windows-based computer: "STOP 0x00000050" or "STOP 0x0000008e":;en-us;903251
    (This problem may occur if the computer is infected with a variant of the HaxDoor virus.)
Topic Status:
Not open for further replies.

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...