Can't read MEMORY.DMP file

Page 1 of 2 12 LastLast

  1. Posts : 8
    Windows 7 x64
       #1

    Can't read MEMORY.DMP file


    So.... I downloaded and installed both the Debugging tools from MS as well as the Symbols package.

    I run WinDbg and set the Symbol File Path to c:\Symbols; where I installed the Symbols download to.

    I then Open Crash Dump and load in my MEMORY.DMP file that was created when I got a BSOD while playing Left4Dead (I have a feeling my Creative X-fi XTreme is the problem... but I'm not sure).

    However, I get no usefull information because the debugger tells me:

    *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -

    And what follow sis just a few pages of "Debugger is not using the correct symbols."

    I got this message BEFORE I downloaded the Symbols install... and then installed Symbols thinking that would solve it.

    No such luck.

    What am I doing wrong here??

    Thanks!
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    BSOD dumpfile


    wazoo said:
    So.... I downloaded and installed both the Debugging tools from MS as well as the Symbols package.

    I run WinDbg and set the Symbol File Path to c:\Symbols; where I installed the Symbols download to.

    I then Open Crash Dump and load in my MEMORY.DMP file that was created when I got a BSOD while playing Left4Dead (I have a feeling my Creative X-fi XTreme is the problem... but I'm not sure).

    However, I get no usefull information because the debugger tells me:

    *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -

    And what follow sis just a few pages of "Debugger is not using the correct symbols."

    I got this message BEFORE I downloaded the Symbols install... and then installed Symbols thinking that would solve it.

    No such luck.

    What am I doing wrong here??

    Thanks!
    Hi and welcome to sevenforums

    Please check device manager to see if the vid driver and audio drivers are installed and working "properly" as I said in the PM.

    Thanks

    Ken
      My Computer


  3. Posts : 8
    Windows 7 x64
    Thread Starter
       #3

    That was the first thing I checked.
    Yes... both drivers are installed and functioning properly.
      My Computer


  4. Posts : 28,845
    Win 8 Release candidate 8400
       #4

    memory.dmp


    wazoo said:
    That was the first thing I checked.
    Yes... both drivers are installed and functioning properly.
    how abt system specs. make model, ram, etc. OS (32 or 64). usb stuff like flash drives, card readers, bluetooth, anything device related.

    Ken
      My Computer


  5. Posts : 30
    Mac OS X
       #5

    Chances are that if you don't know how to read a memory dump, you don't need to be in the first place. I don't mean that in a bad way either. Chances are good that the BSOD itself or the event log contains all the information you need.
      My Computer


  6. Posts : 8
    Windows 7 x64
    Thread Starter
       #6

    zigzag3143 said:
    how abt system specs. make model, ram, etc. OS (32 or 64). usb stuff like flash drives, card readers, bluetooth, anything device related.

    Ken
    I've updated the system specs in the forum CP... so that should have all the pertinent info.

    Thanks.
      My Computer


  7. Posts : 8
    Windows 7 x64
    Thread Starter
       #7

    sonyman said:
    Chances are that if you don't know how to read a memory dump, you don't need to be in the first place. I don't mean that in a bad way either. Chances are good that the BSOD itself or the event log contains all the information you need.
    I'm not *entirely* sure I understand your response. I know how to *interpret* a memory.dmp file... the problem I am having is I am unable to get Windbg to give me an analysis due to the bad symbol errors I am getting.

    The event log can no useful info.... and the BSOD, unfortunately, was set to auto-reboot at the time so I did not get a chance to analyze it.
      My Computer


  8. Posts : 30
    Mac OS X
       #8

    wazoo said:
    I'm not *entirely* sure I understand your response. I know how to *interpret* a memory.dmp file... the problem I am having is I am unable to get Windbg to give me an analysis due to the bad symbol errors I am getting.

    The event log can no useful info.... and the BSOD, unfortunately, was set to auto-reboot at the time so I did not get a chance to analyze it.
    Disable automatic restart upon system failure and wait for the BSOD to occur again in that case, although the BSOD should have been logged. What I meant in my earlier post is that it probably won't help you figure out what the problem is any better than the BSOD itself, which should have contained all pertinent information.
      My Computer


  9. Posts : 8
    Windows 7 x64
    Thread Starter
       #9

    sonyman said:
    Disable automatic restart upon system failure and wait for the BSOD to occur again in that case, although the BSOD should have been logged. What I meant in my earlier post is that it probably won't help you figure out what the problem is any better than the BSOD itself, which should have contained all pertinent information.
    Unless I am mistaken, isn't the BSOD info in the Memory.dmp file? So if I can read the original dum file, won't the BSOD info be in it?

    The BSOD's have been rare. Unfortunately, problems with the games have not. For example, I've had both WoW and Left4Dead lock, sound loop, and then CTD. Unfortunately, what caused them to CTD has not be identifiable. The Left4Dead BSOD I mentioned above followed an earlier freeze, sound loop and CTD for L4Dead. So I'm hopeful that the BSOD memory dump will confirm that it is, in fact, my sound card causing the problem (what I suspect).
      My Computer


  10. Posts : 30
    Mac OS X
       #10

    wazoo said:
    Unless I am mistaken, isn't the BSOD info in the Memory.dmp file? So if I can read the original dum file, won't the BSOD info be in it?

    The BSOD's have been rare. Unfortunately, problems with the games have not. For example, I've had both WoW and Left4Dead lock, sound loop, and then CTD. Unfortunately, what caused them to CTD has not be identifiable. The Left4Dead BSOD I mentioned above followed an earlier freeze, sound loop and CTD for L4Dead. So I'm hopeful that the BSOD memory dump will confirm that it is, in fact, my sound card causing the problem (what I suspect).
    I believe that it is, so at this point it may be worth a shot.
      My Computer


 
Page 1 of 2 12 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 10:29.
Find Us