BetaArchive
https://www.betaarchive.com/forum/

BSODs and DMP files
https://www.betaarchive.com/forum/viewtopic.php?f=62&t=7710
Page 1 of 1

Author:  mattarnster [ Mon Apr 13, 2009 11:45 pm ]
Post subject:  BSODs and DMP files

I have recently suffered a number of BSODs, I think it might be due to a firewall problem, it didn't install correctly... It dumped the memory onto the hard-drive in the folder called Minidump... It has 2 files in it with names as dates that correspond to the BSODs happening... However I cannot open them. I don't know what program to use. I tried notepad but it simply kept saying that Access was Denied... I also tried taking ownership of the whole Minidump folder but that didn't work either...

If someone could help I would be very grateful...

Thanks
Matthew Arnold

Author:  Alpha-Critik [ Mon Apr 13, 2009 11:47 pm ]
Post subject:  Re: BSODs and DMP files

I can help!

1. Open an elevated command prompt. (Right-click, run as admin)

2. In the elevated command prompt, type takeown /f (full path of file) and press Enter.
NOTE: Substitute (full path of file) with your file's full path. For example,takeown /f C:\Windows\Minidump

3. A message will be displayed that this completed successfully. This will give you ownership of the file.

4. In the same elevated command prompt, type icacls (full path of file) /grant Matt:F and press Enter.
NOTE: Substitute (full path of file) with the full path of the file and (user name) with your user name.
For example, icacls C:\Windows\Minidump /grant Brink:F

Let me know if this works or not.

Author:  mattarnster [ Mon Apr 13, 2009 11:52 pm ]
Post subject:  Re: BSODs and DMP files

Alpha-Critik wrote:
I can help!

1. Open an elevated command prompt. (Right-click, run as admin)

2. In the elevated command prompt, type takeown /f (full path of file) and press Enter.
NOTE: Substitute (full path of file) with your file's full path. For example,takeown /f C:\Windows\Minidump

3. A message will be displayed that this completed successfully. This will give you ownership of the file.

4. In the same elevated command prompt, type icacls (full path of file) /grant Matt:F and press Enter.
NOTE: Substitute (full path of file) with the full path of the file and (user name) with your user name.
For example, icacls C:\Windows\Minidump /grant Brink:F

Let me know if this works or not.


It didn't work I'm afraid...
Maybe there is a program that specializes in opening these type of files?

Author:  Thlump [ Mon Apr 13, 2009 11:55 pm ]
Post subject:  Re: BSODs and DMP files

Try this: http://www.youtube.com/watch?v=D2xVRh-7 ... annel_page

Author:  Alpha-Critik [ Mon Apr 13, 2009 11:57 pm ]
Post subject:  Re: BSODs and DMP files

Sorry, I forgot you are using 7. Try this.

Author:  mattarnster [ Mon Apr 13, 2009 11:58 pm ]
Post subject:  Re: BSODs and DMP files

Thlump wrote:

Nope, No program to open .dmp extension...

Author:  Kenneth [ Mon Apr 13, 2009 11:59 pm ]
Post subject:  Re: BSODs and DMP files

You can use WinDbg to open it. :wink:

Author:  mattarnster [ Tue Apr 14, 2009 12:00 am ]
Post subject:  Re: BSODs and DMP files

Alpha-Critik wrote:
Sorry, I forgot you are using 7. Try this.

Nope, still "Access is denied". Good try though...

Author:  mattarnster [ Tue Apr 14, 2009 12:02 am ]
Post subject:  Re: BSODs and DMP files

Windows OCManage wrote:
You can use WinDbg to open it. :wink:

I'll have a go!

EDIT: Sorry for double post, they keep on coming too fast!

Author:  Alpha-Critik [ Tue Apr 14, 2009 12:09 am ]
Post subject:  Re: BSODs and DMP files

mattarnster wrote:
Alpha-Critik wrote:
Sorry, I forgot you are using 7. Try this.

Nope, still "Access is denied". Good try though...


Damn! I'm really stumped then. It works for Vista...

Author:  mattarnster [ Tue Apr 14, 2009 12:29 am ]
Post subject:  Re: BSODs and DMP files

The Windbg didn't work, when I opened the file, it just simply came out with a load of symbols like when you open an executable within Notepad...

Any other suggestions?

Author:  Alpha-Critik [ Tue Apr 14, 2009 12:37 am ]
Post subject:  Re: BSODs and DMP files

mattarnster wrote:
The Windbg didn't work, when I opened the file, it just simply came out with a load of symbols like when you open an executable within Notepad...


Symbols? Hmm... This must be something to do with the filetype, then.

Author:  mattarnster [ Tue Apr 14, 2009 12:40 am ]
Post subject:  Re: BSODs and DMP files

Alpha-Critik wrote:
mattarnster wrote:
The Windbg didn't work, when I opened the file, it just simply came out with a load of symbols like when you open an executable within Notepad...


Symbols? Hmm... This must be something to do with the filetype, then.


The extension (.dmp) doesn't have an associated program for opening it....

Author:  pizzaboy192 [ Tue Apr 14, 2009 4:24 am ]
Post subject:  Re: BSODs and DMP files

i found this, mebbe it helps
http://stackoverflow.com/questions/1585 ... s-dmp-file

Author:  mattarnster [ Tue Apr 14, 2009 10:13 am ]
Post subject:  Re: BSODs and DMP files

I opened it again, this time using Windbg, (how stupid am I, it had a "Open Crash Dump file..." in the menu...) Ok, this time when I opened it, it made more sense...


Code:
Loading Dump File [W:\Windows\Minidump\041309-25630-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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7057 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x8284e000 PsLoadedModuleList = 0x8299b750
Debug session time: Mon Apr 13 23:10:33.946 2009 (GMT+1)
System Uptime: 0 days 0:00:25.069
*********************************************************************
* 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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
....


I really can't make out what this means but thats what it displayed.

Author:  Kenneth [ Tue Apr 14, 2009 1:30 pm ]
Post subject:  Re: BSODs and DMP files

Nothing after that? It just looks like it's trying to find Win7 Build 7057 Symbols and it's trying to load the exports from ntdll.dll.

Page 1 of 1 All times are UTC [ DST ]
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group
http://www.phpbb.com/