BetaArchive Logo
Navigation Home Screenshots Image Uploader Server Info FTP Servers Wiki Forum RSS Feed Rules Please Donate
UP: 28d, 23h, 13m | CPU: 24% | MEM: 5803MB of 10703MB used
{The community for beta collectors}

Post new topic Reply to topic  [ 16 posts ] 
Author Message
 PostPost subject: BSODs and DMP files        Posted: Mon Apr 13, 2009 11:45 pm 
Reply with quote
Staff
User avatar
Offline

Joined
Mon Jun 23, 2008 6:34 pm

Posts
692

Location
NY, USA

Favourite OS
Win 10 64-bit
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


Top  Profile
 PostPost subject: Re: BSODs and DMP files        Posted: Mon Apr 13, 2009 11:47 pm 
Reply with quote
Staff
User avatar
Offline

Joined
Sun Apr 12, 2009 11:22 pm

Posts
703

Location
/dev/urandom

Favourite OS
W7x64, OSX
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.

_________________
Web developer, part-time moderator, full-time CSS wizard.


Top  Profile
 PostPost subject: Re: BSODs and DMP files        Posted: Mon Apr 13, 2009 11:52 pm 
Reply with quote
Staff
User avatar
Offline

Joined
Mon Jun 23, 2008 6:34 pm

Posts
692

Location
NY, USA

Favourite OS
Win 10 64-bit
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?


Top  Profile
 PostPost subject: Re: BSODs and DMP files        Posted: Mon Apr 13, 2009 11:55 pm 
Reply with quote
Donator
User avatar
Offline

Joined
Wed Aug 27, 2008 12:52 am

Posts
890

Location
United States

Favourite OS
Windows Server 2008 Standard
Try this: http://www.youtube.com/watch?v=D2xVRh-7 ... annel_page

_________________
Image


Top  Profile
 PostPost subject: Re: BSODs and DMP files        Posted: Mon Apr 13, 2009 11:57 pm 
Reply with quote
Staff
User avatar
Offline

Joined
Sun Apr 12, 2009 11:22 pm

Posts
703

Location
/dev/urandom

Favourite OS
W7x64, OSX
Sorry, I forgot you are using 7. Try this.

_________________
Web developer, part-time moderator, full-time CSS wizard.


Top  Profile
 PostPost subject: Re: BSODs and DMP files        Posted: Mon Apr 13, 2009 11:58 pm 
Reply with quote
Staff
User avatar
Offline

Joined
Mon Jun 23, 2008 6:34 pm

Posts
692

Location
NY, USA

Favourite OS
Win 10 64-bit
Thlump wrote:

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


Top  Profile
 PostPost subject: Re: BSODs and DMP files        Posted: Mon Apr 13, 2009 11:59 pm 
Reply with quote
Donator
Offline

Joined
Sun May 13, 2007 12:42 am

Posts
2406
You can use WinDbg to open it. :wink:


Top  Profile
 PostPost subject: Re: BSODs and DMP files        Posted: Tue Apr 14, 2009 12:00 am 
Reply with quote
Staff
User avatar
Offline

Joined
Mon Jun 23, 2008 6:34 pm

Posts
692

Location
NY, USA

Favourite OS
Win 10 64-bit
Alpha-Critik wrote:
Sorry, I forgot you are using 7. Try this.

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


Top  Profile
 PostPost subject: Re: BSODs and DMP files        Posted: Tue Apr 14, 2009 12:02 am 
Reply with quote
Staff
User avatar
Offline

Joined
Mon Jun 23, 2008 6:34 pm

Posts
692

Location
NY, USA

Favourite OS
Win 10 64-bit
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!


Top  Profile
 PostPost subject: Re: BSODs and DMP files        Posted: Tue Apr 14, 2009 12:09 am 
Reply with quote
Staff
User avatar
Offline

Joined
Sun Apr 12, 2009 11:22 pm

Posts
703

Location
/dev/urandom

Favourite OS
W7x64, OSX
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...

_________________
Web developer, part-time moderator, full-time CSS wizard.


Top  Profile
 PostPost subject: Re: BSODs and DMP files        Posted: Tue Apr 14, 2009 12:29 am 
Reply with quote
Staff
User avatar
Offline

Joined
Mon Jun 23, 2008 6:34 pm

Posts
692

Location
NY, USA

Favourite OS
Win 10 64-bit
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?


Top  Profile
 PostPost subject: Re: BSODs and DMP files        Posted: Tue Apr 14, 2009 12:37 am 
Reply with quote
Staff
User avatar
Offline

Joined
Sun Apr 12, 2009 11:22 pm

Posts
703

Location
/dev/urandom

Favourite OS
W7x64, OSX
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.

_________________
Web developer, part-time moderator, full-time CSS wizard.


Last edited by Alpha-Critik on Tue Apr 14, 2009 12:44 am, edited 2 times in total.

Top  Profile
 PostPost subject: Re: BSODs and DMP files        Posted: Tue Apr 14, 2009 12:40 am 
Reply with quote
Staff
User avatar
Offline

Joined
Mon Jun 23, 2008 6:34 pm

Posts
692

Location
NY, USA

Favourite OS
Win 10 64-bit
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....


Top  Profile
 PostPost subject: Re: BSODs and DMP files        Posted: Tue Apr 14, 2009 4:24 am 
Reply with quote
Staff
User avatar
Offline

Joined
Thu Oct 23, 2008 3:25 am

Posts
2688

Location
Earth.

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

_________________
Visit my BLOG!
Wanna play a fun browser based game that plays while you're away? Click here.


Top  Profile  WWW  YIM
 PostPost subject: Re: BSODs and DMP files        Posted: Tue Apr 14, 2009 10:13 am 
Reply with quote
Staff
User avatar
Offline

Joined
Mon Jun 23, 2008 6:34 pm

Posts
692

Location
NY, USA

Favourite OS
Win 10 64-bit
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.


Top  Profile
 PostPost subject: Re: BSODs and DMP files        Posted: Tue Apr 14, 2009 1:30 pm 
Reply with quote
Donator
Offline

Joined
Sun May 13, 2007 12:42 am

Posts
2406
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.


Top  Profile
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 16 posts ] 




Who is online

Users browsing this forum: No registered users and 4 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
Jump to:  

All views expressed in these forums are those of the author and do not necessarily represent the views of the BetaArchive site owner.

Powered by phpBB® Forum Software © phpBB Group

Copyright © 2006-2018

 

Sitemap | XML | RSS