By: Roland

Roland — Fri, 28 May 2010 13:31:49 +0000

My memory.dmp file says access is denied. I have even taken ownership, tried to open it with windbg and it still says that. My BSODs are really random ranging from once a month to twice a day. If anybody has had this issue and knows how to gain access please reply. I could just zip the file and upload it to someone who can help me but it’s not what i want and i consider that the very last resort, so please don’t suggest that. Thank you.

By: Justin

Justin — Wed, 13 Jan 2010 09:56:11 +0000

Thanks alot, that really helped, Worked a treat!

By: Doug

Doug — Sun, 30 Aug 2009 16:10:42 +0000

Thanks. Found out it was google chrome and google updater as possible culprits. I turned them off. Will see how that works. At least I have something to go on. Hey! Wouldn’t it be great if MS just gave you some reasonable error reporting for the average user every time automaticly? Instead of going through all this?
Example: Bluescreen of death, reboot, when the computer comes back on dumpcheck.exe comes on in an easy to read format and says Google was on and caused an error, try this….reinstall, uninstall ect.

By: Mark

Mark — Mon, 18 May 2009 09:09:17 +0000

thanks for shared.

well done.

By: sunil

sunil — Fri, 02 Jan 2009 18:23:17 +0000

Thanks for your contribution… its really helpful

By: andrew

andrew — Fri, 24 Oct 2008 02:05:48 +0000

Someone showed me that for the symbol path you can just put following so you dont have to actually download them:

SRV*c:\symcache*http://msdl.microsoft.com/download/symbols

By: Carlos

Carlos — Thu, 04 Oct 2007 23:14:12 +0000

I follow all the procedures, but every time I try to run the “Open Crash Dump” I get is symbol path invalid.

I downloaded the Symbols for Win2K3 Sp1 and it contains 19 subfolders. I try to each one of the paths, but still got the same error.

Loading Dump File [M:\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 argument when starting the debugger. *
* using .sympath and .sympath *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe –
Windows Server 2003 Kernel Version 3790 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: Server, suite: Enterprise TerminalServer
Built by: 3790.srv03_sp1_gdr.070304-2232
Kernel base = 0×80800000 PsLoadedModuleList = 0×808af988
Debug session time: Thu Oct 4 17:00:21.523 2007 (GMT-5)
System Uptime: 8 days 1:12:24.765
*********************************************************************
* 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 argument when starting the debugger. *
* using .sympath and .sympath *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe –
Loading Kernel Symbols
……………………………………………………………………………………………………………….
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffd800c). Type “.hh dbgerr001″ for details
Loading unloaded module list
……………………………..
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck AB, {10, 7000, 0, 1}

***** 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 ***
*** ***
*************************************************************************
Probably caused by : ntkrnlmp.exe ( nt!RtlAreAllAccessesGranted 1c585 )

Followup: MachineOwner
———

By: Mauricio

Mauricio — Tue, 04 Sep 2007 19:51:50 +0000

Thanks a lot for your contribution, i found my server’s problem following your advice.

By: Mohamed

Mohamed — Fri, 10 Aug 2007 16:00:43 +0000

thanks

By: Gra

Gra — Tue, 08 May 2007 13:38:37 +0000

Cheers this was very useful info.

Comments on: Viewing a memory.dmp file after a bugcheck