TechSpot

Please help with reading a minidump file

By Nick88
Mar 2, 2010
  1. I have got a problem (obviously)..

    I have played a game (Football Manager 2010) for a couple of moths without any problems. Now, since a couple weeks, it always crashes when loading to start a match. After searching the internet, I found out that i could find out about the origins of these crashes in Minidump files and read them in Windbg. Onfortunately, i know nothing about these kind of technicalities and how to interprete these Minidump files. Can someone please help me figuring out what my problem is and more important: how to fix it! I will copy the Minidump file from Windbg below.


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


    Loading Dump File [C:\WINDOWS\Minidump\Mini030210-02.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 Personal
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
    Debug session time: Tue Mar 2 14:14:11.500 2010 (GMT+1)
    System Uptime: 0 days 1:44:36.076
    *********************************************************************
    * 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
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {80000004, 806eaad1, a72f86c4, 0}

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

    *** WARNING: Unable to verify timestamp for pci.sys
    *** ERROR: Module load completed but symbols could not be loaded for pci.sys
    *** WARNING: Unable to verify timestamp for VIDEOPRT.SYS
    *** ERROR: Module load completed but symbols could not be loaded for VIDEOPRT.SYS
    *** WARNING: Unable to verify timestamp for igxpmp32.sys
    *** ERROR: Module load completed but symbols could not be loaded for igxpmp32.sys
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    *** WARNING: Unable to verify timestamp for dxg.sys
    *** ERROR: Module load completed but symbols could not be loaded for dxg.sys
    *************************************************************************
    *** ***
    *** ***
    *** 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 ***
    *** ***
    *************************************************************************
     
  2. Nick88

    Nick88 TS Rookie Topic Starter

    Here is the rest of de Minidump file. Sorry for the double post, but otherwise i would have used to much characters...

    *************************************************************************
    *** ***
    *** ***
    *** 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 ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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 ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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 : pci.sys ( pci+ae0 )

    Followup: MachineOwner
    ---------
     
  3. Archean

    Archean TechSpot Paladin Posts: 5,682   +86

    Please post your minidumps here for analysis and advice accordingly.
     
  4. Nick88

    Nick88 TS Rookie Topic Starter

    This is the most recent Minidump file.
     

    Attached Files:

  5. Archean

    Archean TechSpot Paladin Posts: 5,682   +86

    0x8E, KERNEL_MODE_EXCEPTION_NOT_HANDLED, is probably being caused by a faulty device driver. For now, I'll advise you to check whether upgraded drivers are available for various hardware items i.e. graphic card/sound/motherboard etc.

    Another option can be see whether there is an available upgrade for your motherboard's BIOS.

    To find which driver may be causing it, please follow these guidelines:

    a) Windows Key + R (or Click on Start, then on Run...)
    b) Type in 'verifier' and hit enter
    c) Make sure 'Create Standard Setting' is selected and hit next
    d) Click on 'Select all drivers installed on this computer' and hit Finish
    e) Reboot

    There is a possibility that your computer will crash on reboot. If this occurs hit F8 when rebooting just before the windows logo screen and select the safe mode boot option. Follow the same steps above but on step 4 choose 'Select driver names from a list'; hit next; check the box next to any driver where the provider is not Microsoft; hit Finish; reboot.

    This will slow the performance of you computer a little while enabled but will hopefully catch the driver causing corruption. Next time you crash the blue screen will hopefully say something like "DRIVER_VERIFIER_DETECTED_VIOLATION". When this occurs please repost your minidump.
     
  6. Nick88

    Nick88 TS Rookie Topic Starter

    I have tried all your suggestions, but none of them seemed to have worked so far. But nontheless, thanks very much for your effect. Do you have any other suggestions or maybe someone else? I will also now upload the latest minidump file.
     

    Attached Files:

  7. Archean

    Archean TechSpot Paladin Posts: 5,682   +86

    Same error as earlier dumps.

    Well, if the above suggestions hasn't worked then we need to consider whether there is some hardware issues, first thing to check would be RAM. Please download memtest, and run it atleast for 8 passes; if you have multiple RAM Modules in your system I would suggest to use this procedure one by one on each module.

    Also please provide me with your system's specifications/OS etc.
     
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...