Spread the love! TechSpot Tech Gift Shortlist 2017

Computer restarts randomly(minidumps attached)

By cabby2
Jun 20, 2006
  1. Hi,

    My computer seems to randomly restart and I get errors in the event viewer when it does.

    I think it's driver related because I used google and the only similar error I could find was a corrupt driver, but I don't know how to read minidumps to make sure.

    These are the errors I got the last 2 times it restarted

    Error to go with mini dump 2:
    Error code 100000d1, parameter1 01000014, parameter2 00000002, parameter3 00000000, parameter4 baf87777.

    Error to go with mini dump1:
    Error code 1000008e, parameter1 c0000005, parameter2 baf785c8, parameter3 b7b5b8bc, parameter4 00000000.
  2. Tedster

    Tedster Techspot old timer..... Posts: 6,000   +15

    you need to use windows debug (download from M$) to analyze minidumps.
  3. cabby2

    cabby2 TS Rookie Topic Starter


    I used the program you mentioned.

    From oldest to latest minidumps, the program you suggested the error was 'probably caused by'










    nltdi seems to be the most common listed, but not the only one.

    The program also gave me strange errors, I don't know if they just parts of the analysis or errors with the actual debug program.

    They are like "Symbol search path is: *** Invalid ***"

    "Symbol search path is: *** Invalid ***
    * Symbol loading may be unreliable without a symbol search path. *
    * Use .symfix to have the debugger choose a symbol path. *
    * After setting your symbol path, use .reload to refresh symbol locations. *"

    "* Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *

    "*** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
    Debug session time: Tue Jun 20 12:29:38.812 2006 (GMT+2)
    System Uptime: 4 days 5:39:11.376

    "Unable to load image tcpip.sys, Win32 error 2
    *** WARNING: Unable to verify timestamp for tcpip.sys

    "***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *** WARNING: Unable to verify timestamp for nltdi.sys
    *** ERROR: Module load completed but symbols could not be loaded for nltdi.sys
    *** WARNING: Unable to verify timestamp for afd.sys
    *** ERROR: Module load completed but symbols could not be loaded for afd.sys"

    Now I see tcpip.sys in there and I recall I made a change to that file a while ago with a patch to increase the number of allowed connections because the default windows cap of 10 made the internet completly unusuable for me(I had to restart every 2 hours to 'free up' the connections, even if I closed the programs that were using them previously.

    I don't know if thats a part of the problem or what the mentioned files at the top of my post are used for.

    thanks if anyone can help
  4. howard_hopkinso

    howard_hopkinso TS Rookie Posts: 24,177   +19

    Hello and welcome to Techspot.

    nltdi.sys is the driver for the Netlimiter programme and is a known issue.

    Uninstalling Netlimiter will probably fix your problem.

    Regards Howard :wave: :wave:
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...