Solved Cannot Open Mini Dump Files

[richc46]

Whenever I try to open or look at a mini dump file, the symbol for the file looks like the media center symbol. When I click on the symbol, media center opens. I have uninstalled my debugger (reads the mini dumps) to no avail. Any help?
Moderators, please, do not move this post since the advice of the BSOD people is needed.

 

[zigzag3143]

Hate having to ask but have you associated "DMP" files with Windbg in cpanel?

 

[carwiz]

"WinDbg"

 

[richc46]

Hate having to ask but have you associated "DMP" files with Windb in cpanel?

Yes, I did Ken and it solved the media center problem, but still cannot open the files.

 

[zigzag3143]

Figured

what happens? do you get an error?

What has changed from when it did work till now?

 

[richc46]

Nothing has changed. I wanted to do a BSOD in Vista. I noticed right away that the minidump icons on the reports submitted by the OP was different, it looked like the icon for media center. I clicked on it and media center openend. I went to Associations and noticed that .dmp was openend by media center. I changed the association. Now, the media center icon is gone, but replaced by an icon that I do not recognized. When I click on it the .dmp and begins to open, but then it says that it is not a legal 32 procedure. I have 64 bit Seven. Will you be kind enough to give me the links to install Windbg? I tried to reinstall, but to no avail. Perhaps, if I used different links.

 

[zigzag3143]

Nothing has changed. I wanted to do a BSOD in Vista. I noticed right away that the minidump icons on the reports submitted by the OP was different, it looked like the icon for media center. I clicked on it and media center openend. I went to Associations and noticed that .dmp was openend by media center. I changed the association. Now, the media center icon is gone, but replaced by an icon that I do not recognized. When I click on it the .dmp and begins to open, but then it says that it is not a legal 32 procedure. I have 64 bit Seven. Will you be kind enough to give me the links to install Windbg? I tried to reinstall, but to no avail. Perhaps, if I used different links.

Sorry Rich here it one. Debugging Tools for Windows 64-bit Version

Also that error is generated sometimes on mine as well when the symbol directory and the app directory aren't in path.

 

[richc46]

Thanks Ken, but tried that one already and did not work.

 

[carwiz]

Where did you install the Debugger? Did you let it defaut to Program Files?
What happens when you double-click WinDbg.exe? Does it start?

 

[richc46]

It does begin to start bug very quickly I see a notice that this is not a permitted action.

 

[carwiz]

Run as Administrator.

 

[richc46]

This is one that run as administrator will not help. Thanks for trying.

 

[zigzag3143]

Had a similar problem and the only workaround I found was to install the symbols and windb in a different location.

It would not run when symbols were installed under the windows directory, nor if the symbols were not in path so I had to add C:\symbols to path and install windb in c:\program files (x86)\debugger1.


I doubt that will fix it but its easy enough to try.

 

[richc46]

I truly appreciate your efforts, Ken. I know that you know how I feel. I see BSODS and just want to examine those files and am not able. Rep for all your efforts.

 

[carwiz]

Ok, let me get this straight. You can open the debugger then you get an error when trying to open a dump file?

Have you tried a different dump file?

I'm curios of your procedure.
Did you download any of the symbols or are you using the MS server?

Did you set the path for the dump and symbol files in debugger or use an execution parameter?

 

[richc46]

About 6 months after installing Windows 7, I used these links to download
?msdl.microsoft.com/download/symbols/debuggers/dbg_amd64_6.11.1404

?ownload.microsoft.com/download/7/F/B/7FBF7E6A-D0DE-442A-A683-4F9885A96FC9/Windows_Win7.7600.16385.090713-1255.X86FRE.Symbols

?ownload.microsoft.com/download/F/1/1/F11206A1-C532-4C9E-86FF-1261A693AA53/Windows_Win7.7600.16385.090713-1255.X64CHK.Symbol

I downloaded in the order shown. Although not the most current they worked on my computer for a couple of years. Now, these and the most current run into problems.

I have changed the first few letters of the downloads, so they will not execute, per forum rules.

I have tried vista forums bsods, seven bsods from several posters and always the same results.
Even the minidump symbol that I see when I go into the file are a bit different.

As soon as I click on the mini dump file, it seems to be opening, but very quickly I receive a notice that it is not permitted.
I have uninstalled, reinstalled, tried 32 bit and 64 bit (my computer is 64 bit). Just dont know.

My above links go right to the download, for your information and safety.

I am trying the same as I did in the past, I just download and it goes to the default location

 

[carwiz]

The x64 debugger version is for running on a 64-bit machine and will debug x86 and x64 dumps.

Create a desktop shortcut for WinDbg.exe. (Right click the .exe and chose Send to Desktop). Right click on the shortcut then click Properties.
On the Shortcut tab, add the following to Target but substitute your location for the symbol files. (bold) The one shown is the location on MY D: drive. Click apply, then OK.

-y SRV*d:\ms-websymbols*http://msdl.microsoft.com/download/symbols

The entire Target line should look like this:
"C:\Program Files\Debugging Tools for Windows (x64)\windbg.exe" -y SRV*d:\ms-websymbols*http://msdl.microsoft.com/download/symbols

Double clicking on a dump file will not work since the debugger doesn't know where the symbols are by default. Use the desktop shortcut to open the debugger then open the dump file. The default location of the dump files is C:\Windows\Minidump but you can choose from where to load the dump. After the dump is open, debugger will start downloading symbol files. Let it load--You'll see the status at the bottom of the screen. After the first time, it will download only those that are needed or updated.

Debug away!

 

[carwiz]

Hmmmmmm. Couldn't figure out how to NOT show the MS server as a link. Don't click on it--It's a server. Just highlight and copy the line from the start.

 

[richc46]

In the process of trying, will get back to you asap with the results. Thanks for all the help. I miss doing the BSODs. Cannot give rep, got the dreaded must spread it around notice.

 

[carwiz]

Cannot give rep, got the dreaded must spread it around notice.

Don't worry about that. Let's get you grinnin' again.