Can't open crash dump file.

[aimeeandbeatles]

Okay, so in the middle of a game I got a blue screen, so I went to Windows/Minidump folder. There was one dump file there, went to open it in text editor and "Access is denied."

If I go File>>Open, it tells me I don't have permission to open it and to contact a system administrator (I AM THE SYSTEM ADMINISTRATOR YOU STUPID VISTA CURSE CURSE CURSE!!!!)

I've tried taking ownership but it didn't work. Any suggestions?

 

[Genocidicbunny]

Why are you trying to open it in a text editor anyways? AFAIK, you need Windows debugger viewer ( or something like that ) to view .dmp files.

Also, turn UAC the hell off, I havent had any file access problems since I did.

 

[aimeeandbeatles]

I downloaded a debugger viewer and turned off UAC. I got this:

Spoiler :

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is 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+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrpamp.exe -
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18226.x86fre.vistasp1_gdr.090302-1506
Machine Name:
Kernel base = 0x81a3e000 PsLoadedModuleList = 0x81b55c70
Debug session time: Fri Jun 26 18:46:19.778 2009 (GMT-3)
System Uptime: 2 days 3:10:11.093
*********************************************************************
* 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+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrpamp.exe -
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols

Loading unloaded module list
....
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {85a8d510, 8e013710, 0, 2}

***** 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 ***
*** ***
*************************************************************************
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.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 ***
*** ***
*************************************************************************
*********************************************************************
* 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 : nvlddmkm.sys ( nvlddmkm+e710 )

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

Um... what does it mean?

Edit: Seems nvlddmkm.sys is NVIDIA driver, correct?

 

[Genocidicbunny]

Yes, yes it is

 

[aimeeandbeatles]

Odd thing is, it's the first time anything like that's happened.

It's been really hot and humid in the area lately. Maybe overheating?

EDIT: Oh, and just before it happened, I noticed the menus/interface in the game (CivCity Rome) rapidly flickering off and on (at first I thought I pressed a key), and when I went esc to save, the menu backgrounds were transparent and flickering and I was lucky to get my game saved then it happened.

 

[Genocidicbunny]

Overheating, bad drivers, hardware problem. Eliminate the first by checking temps with RivaTuner and the second, with a driver reinstall. If that doesnt fix it, well, soz.

 

[Till]

You obviously should download the symbol information for the kernel and related libraries, if you are serious about using the debugger.

 

[aimeeandbeatles]

Where can I get the symbols?

Both SpeedFan and HWiNFO32 say my "normal" (not gaming) GPU temp is 66 C, which is normal for my card.

Will try downloading + installing latest drivers, for all I know Windows Update could have switched it behind my back.

Edit: More information from WhoCrashed:

On Fri 6/26/2009 9:47:32 PM your computer crashed
This was likely caused by the following module: nvlddmkm.sys
Bugcheck code: 0x116 (0x85A8D510, 0x8E013710, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Compatible Windows Vista Kernel Mode Driver, Version 182.50
company: NVIDIA Corporation
description: NVIDIA Compatible Windows Vista Kernel Mode Driver, Version 182.50

 

[Till]

Look here.

To use the Microsoft Symbol Server

1.Make sure you have installed the latest version of Debugging Tools for Windows.

2.Start a debugging session.

3.Decide where to store the downloaded symbols (the "downstream store"). This can be a local drive or a UNC path.

4.Set the debugger symbol path as follows, substituting your downstream store path for DownstreamStore.

SRV*DownstreamStore*http://msdl.microsoft.com/download/symbols

For example, to download symbols to c:\websymbols, you would add the following to your symbol path:
SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols

 

[aimeeandbeatles]

I didn't get that huge repeating thing, but I got this:

Module load completed but symbols could not be loaded for nvlddmkm.sys

hmmm...

 

[Till]

Well, these are just the symbols for various Windows components. I don't know if Nvidia provide debugging symbols for their drivers.

 

[aimeeandbeatles]

For the overheating thing -- Don't think that's it.

I opened up the game at the same settings, the GPU was at 69 C. Which is about 3 C above average.

 

[Genocidicbunny]

Try playing it for a little while. You also want to use a game that actually stresses the GPU. Something like crysis, company of heroes, supcom, etc should be good.

 

[aimeeandbeatles]

But I play mostly strategy games!

Or.... would the fancy 3D graphic that Folding@home generates work?

Edit: Tried fancy 3D graphic. Went up to 71 after a minute or so...

 

[Genocidicbunny]

Try the folding at home GPU client. If you have an nvidia 8xxx or later series card, it will work. The fancy graphic doesnt do much.