Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

My computer got bluescreen, and saved all info to a memory file before restart. I have memory.dmp, and i have some very important files that i didnt save.

All the files I need to recover were txt files, which i opened notepad and I didnt save them, once my computer crashed, I lost them. All were plain text.

I have looked to programs like windbg but couldnt find a proper solution. I start to think that memory.dmp file doesnt have the raw data, it just have logs in it?

Please show me a way to recover my unsaved files from Memory.dmp

I am using windows vista.

share|improve this question
add comment

4 Answers

First, you're going to spend 10x longer than it would take to re-type them trying to recover whatever files you were working on.

Second, the "files" in question will not exist as "files" in memory. It will simply exist as allocated blocks of memory (probably fragmented into several locations), and may not even slightly resemble the end-result you remember looking at.

Third, the memory.dmp file typically only contains the memory allocated to the faulting thread. If it wasn't your editor that crashed, then the memory.dmp probably doesn't contain anything useful to you. It's highly unlikely that "notepad" was the thread that crashed... and even if it was, you would only recover that one instance of notepad.

I wish I didn't sound like a jerk for saying this... but that is EXACTLY why you should save frequently.

share|improve this answer
    
I really believe that the file contains all the necessary files i need to recover. Since the file size is near to my memory capacity. Also, i consume the memory (generally 90%) . And i am sure that the file is not notepad that crashed my computer. So which editor i should use or how i can be sure that those files are not in my hdd? I am sure what i have written into txt files are somehow in plaintext. So I might search the ram? (After i convert some plaintext i remember to hex data) –  met.in Apr 13 '11 at 21:22
add comment

The problem is that the memory dump doesn't contain the needed data in one single place. This is because of how applications works. They allocate memory partially, not the complete block on one time, this is why the data stored in RAM can be in different places of RAM, not in one chunk as it saves it on hard drive.

So, for restoring files you should probably check the whole files and taking by parts the lost data... Rewriting it from scratch can be a lot easier.

share|improve this answer
    
Yes i know it is seperated chunk by chunk. And the addressing is not linear. I would need a way to restore those data. Any recommendations? –  met.in Apr 13 '11 at 21:19
1  
As the other answerer (TheCompWiz) stated, there is a chance that the file doesn't contain the needed data (if it contains, it should be the same size as your used RAM when BSoD happened). If it is a full RAM dump, still, there is no "system" on how the data is stored - in the worst case each character is in their own place. Try to search some words which you remember were inside the file - maybe you will be lucky enough to restore parts of the text. –  Evengard Apr 13 '11 at 21:23
    
The size of the file is exactly same as my ram. Which tool do you recommend me to search a 2gb file? –  met.in Apr 13 '11 at 21:40
    
Try some kind of hex editor, for example notepad++ with hex plugin, or far, or whatever (google them). Try both ascii and unicode search. –  Evengard Apr 13 '11 at 21:45
    
notepad++ didnt work out as the file size is huge. i tried to open with wordpad and it really didnt load since hte file is exaclty same with my ram. Any solution ? –  met.in Apr 15 '11 at 6:33
show 1 more comment

Use LTFViewr and search through the .dmp file. I don't know if it can find anything.

But at least it can search through the whole file. It will take a while.

share|improve this answer
add comment

Well. This is an interesting exercise. If I were you, probably I would read byte by byte (not the whole file) of the memory dump and encode them to ASCII.

This for sure is not the "elegant" solution you would expect and it is going to take some time to go over that output, but you should be able to recognize parts of your texts, and with a little of luck, put them together again.

Best of luck...

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.