Cannot Open Mini Dump Files

Page 4 of 5 FirstFirst ... 2345 LastLast

  1. Posts : 17,796
    Windows 10, Home Clean Install
    Thread Starter
       #31

    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.
      My Computer


  2. Posts : 4,161
    Windows 7 Pro-x64
       #32

    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?
      My Computer


  3. Posts : 17,796
    Windows 10, Home Clean Install
    Thread Starter
       #33

    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.
      My Computer


  4. Posts : 17,796
    Windows 10, Home Clean Install
    Thread Starter
       #34

    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
      My Computer


  5. Posts : 4,161
    Windows 7 Pro-x64
       #35

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

    Debugging Tools for Windows 64-bit Version
      My Computer


  6. Posts : 17,796
    Windows 10, Home Clean Install
    Thread Starter
       #36

    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.
    Last edited by richc46; 23 Nov 2011 at 09:09.
      My Computer


  7. Posts : 4,161
    Windows 7 Pro-x64
       #37

    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.
      My Computer


  8. Posts : 4,161
    Windows 7 Pro-x64
       #38

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


  9. Posts : 13,354
    Windows 7 Professional x64
       #39

    Rich-

    Open a blank copy of Windbg (NOT opening a dump), go to File > Symbol File Path, and copy/paste:
    Code:
    SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Exit Windbg, selecting Yes to "Save workspace information".

    Also, open a command prompt as administrator and enter:
    Code:
    "c:\program files\debugging tools for windows (x64)\windbg.exe" -IA
    The IA part is case sensitive.
      My Computer


  10. Posts : 4,161
    Windows 7 Pro-x64
       #40

    -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?
      My Computer


 
Page 4 of 5 FirstFirst ... 2345 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 18:40.
Find Us