Windows Debug Unable to Open Image File

Hey guys,

I'm receiving a BSOD every time I exit a program (Civilization 5). It's got me perplexed since otherwise the system runs fine and this is the only time the error is received. Literrally as soon as I click the Exit button in the program or otherwise End Process this occurs. To complicate matters, it "only" happens about 75% of the time.

So curiosity has gotten the better of me and I want to try and figure out what exactly is causing the issue.

I've not used Windows Debugger before and am learning as I go. What I've managed so far is to download all symbols for *.DMP files using Symcheck.exe in the article in the Microsoft KB.

The issue I'm receiving now, is the Debugger says it can't find the Image files, which appear to be the Symbol files I've downloaded. I can't figure out how to point the program to look in the correct location for symbol files, and even if I copy all the symbol files to the directory it says it's trying to look at I still get the error.

I'm running Windows 7 x64 and the Windows Debug Utility as an Administrator (actually right clicking and selecting Run As Administrator...)

Attached is a single screenshot that shows various windows I thought would be pertinent. Below is what the debugger is posting.

Anyone have any idea what I'm missing? Some small setting somewhere?

Thx
-G


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

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: c:\symbols
Unable to load image \SystemRoot\system32\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 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`02c67000 PsLoadedModuleList = 0xfffff800`02eab670
Debug session time: Fri Sep 14 16:00:50.900 2012 (GMT+5)
System Uptime: 0 days 2:40:17.040
Unable to load image \SystemRoot\system32\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
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 0, fffff80002cec442}

***** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4FA390F35e8000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4FA390F35e8000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4FA390F35e8000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4FA390F35e8000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4FA390F35e8000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4FA390F35e8000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4FA390F35e8000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4FA390F35e8000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4FA390F35e8000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4FA390F35e8000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4FA390F35e8000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4FA390F35e8000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4FA390F35e8000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4FA390F35e8000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4FA390F35e8000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4FA390F35e8000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4FA390F35e8000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4FA390F35e8000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4FA390F35e8000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4FA390F35e8000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4FA390F35e8000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Debugging Tools for Windows (x86)\sym\ntoskrnl.exe\4FA390F35e8000\ntoskrnl.exe
The system cannot find the file specified.

*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+85442 )

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

 

Welcome to the MG forums!

It is very brave of you to want to learn to use the Windows debugger, but I am not sure if you will actually find what you are looking for.

I myself have not used the debugger for a few years, so I do not really remember in detail what to do.

However, before even of thinking of using a debugger, what is the BSOD error code? Do you find any additional information in the Event Viewer?

 

One important thing: save the Workspace in WinDbg once you've set the symbols location.

If you zip and upload the dump(s), I can look it over for you.