TechSpot

Need help with reading minidump

By myuji
Feb 4, 2009
  1. Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\WINDOWS\Minidump\Mini012009-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    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. *
    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * 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+ *
    *********************************************************************
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** 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) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
    Debug session time: Tue Jan 20 19:13:00.437 2009 (GMT+8)
    System Uptime: 0 days 10:09:10.136
    *********************************************************************
    * 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+ *
    *********************************************************************
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    ...............................................................
    .......................................................
    Loading User Symbols
    Loading unloaded module list
    .......................
    *** WARNING: Unable to verify timestamp for hal.dll
    *** ERROR: Module load completed but symbols could not be loaded for hal.dll
    Unable to load image i8042prt.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for i8042prt.sys
    *** ERROR: Module load completed but symbols could not be loaded for i8042prt.sys
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {80000004, 806eaa4b, aa9dfc90, 0}

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

    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *********************************************************************
    * 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+ *
    *********************************************************************
    *********************************************************************
    * 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+ *
    *********************************************************************
    Probably caused by : i8042prt.sys ( i8042prt+7dc6 )

    Followup: MachineOwner
    ---------

    This is the minidump,and my computer reboots often.Can anyone help me?
     
  2. Route44

    Route44 TechSpot Ambassador Posts: 12,167   +37

    Your dump cites the i8042 Port Driver which belongs to the software i8042 Keyboard and PS/2 Mouse Port Driver and is part of your Windows OS.

    Your error code is 0x8E and these are caused by hardware issues. It could be your issue lies with your keyboard and mouse.

    However, do the following diagnostics first before going out and buying a new mouse and keyboard.

    A. Run Memtest on your RAM:

    1. Go to www.memtest.org and download the latest ISO version. It is free and perfectly safe.

    2. Burn to a CD.

    3. Place CD in your drive and reboot with CD in drive. The test will take over.

    4. Let it run for a LONG time. The rule is a minimum of 7 Passes. There are 8 individual tests per Pass. Many people will start this test before going to bed and check it the next day.

    5. If you have errors you have corrupted memory and it needs to be replaced.

    6. Also, with errors you need to run this test per stick of RAM. Take out one and run the test. Then take that one out and put the other in and run the test.


    B. Type ChkDsk in your Run box and hit Okay.


    C. Run a full harddrive diagnostics by using the free utility provided by your harddrive manufacturer.


    *** Get back to us with the results.
     
  3. myuji

    myuji TS Rookie Topic Starter

    Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\WINDOWS\Minidump\Mini020409-09.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    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. *
    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * 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+ *
    *********************************************************************
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** 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) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
    Debug session time: Wed Feb 4 17:11:55.437 2009 (GMT+8)
    System Uptime: 0 days 0:05:20.125
    *********************************************************************
    * 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+ *
    *********************************************************************
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    ...............................................................
    ........................................................
    Loading User Symbols
    Loading unloaded module list
    ...........
    Unable to load image rt2500usb.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for rt2500usb.sys
    *** ERROR: Module load completed but symbols could not be loaded for rt2500usb.sys
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000007E, {c0000005, a9a48c19, a9f79b70, a9f7986c}

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

    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *********************************************************************
    * 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+ *
    *********************************************************************
    *********************************************************************
    * 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+ *
    *********************************************************************
    Probably caused by : rt2500usb.sys ( rt2500usb+ec19 )

    Followup: MachineOwner
    ---------

    Erm,my computer has an error too..which's rt2500usb.sys.As my computer crashed another time today,i decided to use Debugging Tools for Windows to check it out.I did a google search on rt2500usb.sys,and discovered that it's a problem with network adapter.I wonder if this problem needs to be solved too?

    And,i'll do those checks and tell you about the results.Thanks and sorry to trouble you.
     
  4. Route44

    Route44 TechSpot Ambassador Posts: 12,167   +37

    Hey, no trouble at all. That is what we are here for. :) That rt2500usb.sys driver belongs to Linksys and it could be your NIC card is bad.
     
  5. myuji

    myuji TS Rookie Topic Starter

    I use Linksys Wireless Adapter..Been using it for a few years,but had no problems until recently.I've been seeing problems to fix this,and haven't tried though...Looks kinda risky.I dun want to reformat computer,lol.Wonder if there's any solution to fix this.

    Anyway,i'll do the memtest tomorrow.Thanks alot!
     
  6. Route44

    Route44 TechSpot Ambassador Posts: 12,167   +37

    Reformating is the last resort. You may want to try to uninstall and reinstall drivers for your NIC card. If is bad you'll need to replace it.
     
  7. myuji

    myuji TS Rookie Topic Starter

    B. Type ChkDsk in your Run box and hit Okay.


    C. Run a full harddrive diagnostics by using the free utility provided by your harddrive manufacturer.

    For the ChkDsk,i did it and it seems to me that there're no problems.After the 3 scans,the Command Prompt window just closed down.

    As for Part C,what do u mean by run a full harddrive diagnostics by using the free utility provided by your harddrive manufacturer?
     
  8. Route44

    Route44 TechSpot Ambassador Posts: 12,167   +37

    Your harddrive manufacturer will supply a free utility that you can use to diagnose your harddrive. It is totally free and a great tool to have. Go to your harddrive manufactuer's website, find it, and download and install to your computer. You may even be able to run it directly from your website.

    If you can't find who made your harddrive then you can use Seagate's Sea Tool utility that will run on many brands.

    ChkDsk as you descibed it worked correctly.
     
  9. myuji

    myuji TS Rookie Topic Starter

    I downloaded Seagate's Sea Tool utility as i'm not sure who made my harddrive,and i'm not sure as to what tests should i run on Seagate.Could you tell me,if possible?
     
  10. Route44

    Route44 TechSpot Ambassador Posts: 12,167   +37

    Run the Long DST. Let us know of the results.
     
  11. myuji

    myuji TS Rookie Topic Starter

    The Long DST passed..Except that it took kinda long to complete,though.
     
     
  12. Route44

    Route44 TechSpot Ambassador Posts: 12,167   +37

    Yes the Long DST takes, well, a long time. :D

    Have you done anything about your Linksys Wireless Adapter?
     
  13. myuji

    myuji TS Rookie Topic Starter

    Well,not yet...Haven't reinstalled it,but lately my computer seems okay..Except for random restarts sometimes though.Sometimes it's just fine the whole day o.o
     
Topic Status:
Not open for further replies.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.