Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Can't read MEMORY.DMP file


22 Jul 2009   #1

Windows 7 x64
 
 
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 System SpecsSystem Spec
.

22 Jul 2009   #2

Win 8 Release candidate 8400
 
 
BSOD dumpfile

Quote   Quote: Originally Posted by wazoo View Post
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 System SpecsSystem Spec
22 Jul 2009   #3

Windows 7 x64
 
 

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


22 Jul 2009   #4

Win 8 Release candidate 8400
 
 
memory.dmp

Quote   Quote: Originally Posted by wazoo View Post
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 System SpecsSystem Spec
22 Jul 2009   #5

Mac OS X
 
 

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 System SpecsSystem Spec
22 Jul 2009   #6

Windows 7 x64
 
 

Quote   Quote: Originally Posted by zigzag3143 View Post
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 System SpecsSystem Spec
22 Jul 2009   #7

Windows 7 x64
 
 

Quote   Quote: Originally Posted by sonyman View Post
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 System SpecsSystem Spec
22 Jul 2009   #8

Mac OS X
 
 

Quote   Quote: Originally Posted by wazoo View Post
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 System SpecsSystem Spec
22 Jul 2009   #9

Windows 7 x64
 
 

Quote   Quote: Originally Posted by sonyman View Post
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 System SpecsSystem Spec
22 Jul 2009   #10

Mac OS X
 
 

Quote   Quote: Originally Posted by wazoo View Post
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 System SpecsSystem Spec
Reply

 Can't read MEMORY.DMP file




Thread Tools



Similar help and support threads for2: Can't read MEMORY.DMP file
Thread Forum
Solved Attempt to write read only memory (egldrv.sys) Drivers
Windows 7 does not read Sony Memory Stick Pro Duo Music, Pictures & Video
Help required creating batch file to read .csv file General Discussion
Can someone read my MEMORY.DMP and tell me what'is causing Blue Screen BSOD Help and Support
how to read virtual memory General Discussion
How to read memory.dmp file? BSOD Help and Support
Won't read memory card Hardware & Devices

Our Sites

Site Links

About Us

Find 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 03:07 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33