Solved Cannot Open Mini Dump Files

[richc46]

View attachment 184955

Followed instructions and problem is identical to before

 

[carwiz]

Looks like you're trying to run the zip file????

Right click the zip file and click on "Extract All". Choose where you want the files to go.
Start the debugger. Click on File in the header menu and select Open Crash Dump from the drop-down menu.
In the file selection screen, locate the dump file from the above extract.

I'm not sure what else to try. The above works for me.

 

[richc46]

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!

Personally, I felt that this would work. My symbols are on the c drive in symbols and I put -y SRV*c:\symbols. Was this part correct?

 

[carwiz]

The location is ok, but use the symbols from the server.

Your line would look like this: (including the http)

-y SRV*C:\symbols*http://msdl.microsoft.com/download/symbols

If you don't use the server, your symbols will probably be incomplete and outdated. If you still want to use your downloaded symbols, use the following. (Don't use "SRV" unless you specify the server URL.)

-y C:\symbols

And you can't open a .zip file. The dump needs to be extracted first.

 

[richc46]

Did it exactly the way that you mentioned and its the same thing. Im not using Zip since, I have been able to open for at least a year.

 

[carwiz]

I've been trying to figure out how you got to were you were in the screen display. I couldn't duplicate it. I did see that you have an older version. Get the latest version and follow the Open Crash Dump instructions I posted before.

 

[richc46]

Ken,
Regardless of how this all turns out, I sincerely thank you for your time. It is truly very kind of you and it is very, very appreciated. If we do get this fixed, I will be grateful everytime I help out with the BSODs. Ill report back.

 

[richc46]

View attachment 184996

Must have made an error on the target, but dont see where.

 

[carwiz]

You keep mixing the syntax for the location. Are you going to use the server for symbols?

If you are, copy and paste the following line after the last quote in the target of the desktop shortcut--EXACTLY. Include the space before the "-y" and the URL. Do NOT add or omit anything.

-y SRV*C:\symbols*http://msdl.microsoft.com/download/symbols

---------------------------------------------------------------

 

[richc46]

I went to my desktop
Windbg properties
I deleted everything that I had done before, but kept the orignal target that was present right after I made the desktop shortcut.
I copied and pasted, as you said and came up with the same as before

View attachment 185002

 

[richc46]

It is my thought that my debuger suffered some sort of corruption. I even reinstalled windows using easy transfer, which may have brought the corruption to the new install. I did a clean install with format. Since, everything worked fine when I first installed Seven, I could probably get it to work, by installing and not using easy transfer and just reinstalling everything from a back up. Although, I really want to get back to the BSODs, I dont think that I want to go through the process of starting from scratch with favorites, settings, and documents. Any other thoughts would be very much appreciated, but Im losing hope.

 

[carwiz]

I would un-install "Debugging Tools for Windows" and download/install the most current version. You're at least one major release behind and the functions may be different. At least we'll be on the same page. If you open Windows Explorer, can you see C:\Symbols?

 

[richc46]

Good idea, start from scratch so we are on the same page.
Why not give me the link that you used, to insure uniformity.
If I go to explorer, I do not see symbols.
I can only see it if I go to c drive. and then I can see the symbols folder.

 

[richc46]

This is the link that I used after I first experienced the problem. When used and I try to open a file, it uses media center. I had to go to associations to associate dmp with windbug.
Download and Install Debugging Tools for Windows

 

[carwiz]

I used this link. A rectangle surrounds the download link.

Debugging Tools for Windows 64-bit Version

 

[richc46]

I deleted everything that I had done previously, and downloaded from your site, everything seemed to go fine. I then took the information that your provided and copied and pasted, I left the space when I pasted. I went to desktop and opened Windbug. I then went to the Seven Forums and tried to read a dump report. It came out the same as the Screen Shot that I posted earlier. I know how to install the Debugger as I did it about a year ago, without any trouble. I really think that I have some sort of corruption that is creating the problem. I will try an SFC and see if any corruption is detected.

SFC was completed and no errors found.
I think that it is obvious at this point that my debugger is not installing correctly, due to some sort of corruption or other problem.

 

[carwiz]

Repost the shot of the error but drag the right side of the Command window so I can see the entire text.

I started to wonder about the file name and thought that could be the problem. I think I used all MS defaults during the install except I store data on my D-drive. But, I think Ken mentioned he used "Symbols". It shouldn't matter as long as you point to the directory. I also noticed my server symbols are in a different directory from the "installed" 32/64-bit symbols.

D:\
MS-Symbols - Contains 4,262 folders of symbol names. Each of these contain two folders of what appear to be GUIDs. Most likely 32-bit and 64-bit. Each of these have one .PDB file.
MS-WebSymbols - Contains 249 folders but its make-up is slightly different. It has PDB and SYS folders. I think the sys folders are public symbols (drivers) and they may contain many sub-entries.

Only the two (32-bit/64-bit) MS-Symbols were "installed" via a MSI and show up on the Add/Delete Programs list along with Debugging Tools for Windows(x64). So if you re-install the Debugger, I suspect the symbols must also be re-installed.

So I guess it would be a valid point, now that you re-installed Debugger, to un-install and re-install the two symbol downloads from Microsoft. At least, I'm thinking so. :banghead:

 

[carwiz]

Also, when you say "delete", I hope you mean Un-Install. ????

 

[Jonathan_King]

Rich-

Open a blank copy of Windbg (NOT opening a dump), go to File > Symbol File Path, and copy/paste:

[PLAIN]SRV*c:\symbols*http://msdl.microsoft.com/download/symbols[/PLAIN]

Exit Windbg, selecting Yes to "Save workspace information".

Also, open a command prompt as administrator and enter:

"c:\program files\debugging tools for windows (x64)\windbg.exe" -IA

The IA part is case sensitive.

 

[carwiz]

-IA Associates WinDbg with the file extensions .dmp, .mdmp, and .wew in the registry. After this action is attempted, a success or failure message is displayed. After this association is made, double-clicking a file with one of these extensions will start WinDbg. The -IA parameter must not be used with any other parameters. This command will not actually start WinDbg, although a WinDbg window may appear for a moment.

Good one Jonathan! I missed that. Wouldn't this have been done automatically on install?