Any way to recover/repair a text file corrupted by a BSOD?


  1. Posts : 112
    64-bit Windows 10 Pro 1909
       #1

    Any way to recover/repair a text file corrupted by a BSOD?


    I'm furious! I spent several hours adding and updating the code in a large GUI application I'm developing, saving the changes every minute or so like a good boy. Well, I'd just finished a save when I got some kind of kernel BSOD. I rebooted and went back to the code file I had been working on and found to my horror that the second half of the text file -- the very area I had added hundreds of lines of code to, was now completely gone!

    It's not as if I hadn't been saving the file very, very often. And I do have a backup copy I made yesterday, but that doesn't include the hundreds of lines I added today! I'd never had a BSOD rape me the one this one did, and who could have foreseen such a thing?

    I have already tried running two different data recovery tools (obviously not from the same drive), Runtime Software's "Get Data Back" (simple and NTFS paid versions) as well as MiniTool Power Data Recovery paid version, but neither one was apparently designed to recover partially corrupted files.

    So I came to ask you folks if any of you know if there are any other options I can try. I'm pessimistic, but I didn't want to just surrender without asking...

    Thanks.
      My Computers


  2. Posts : 112
    64-bit Windows 10 Pro 1909
    Thread Starter
       #2

    OMG, I did it! I can scarcely believe it, but I did it!

    Here's what I did. I used a disk editor to search the entire disk for some text that would only exist within a disk region that contained the new code I was working on, whether allocated to a file or not. And it actually found it -- after the last good line of text in the very same file. It turned out that the last half of that file was not actually gone, but rather the corruption merely moved the effective EOF much earlier than it should have been. So I used that disk editor to simply copy the "missing" part of the file (the part after the bogus EOF) to another text file, then I opened up the original file for editing and pasted the missing text back into the original file and saved it.

    Bingo -- now the file had all of my hard work back in place! Hooray!!
      My Computers


  3. Posts : 4,224
    Windows 10
       #3

    Nice save, Thenin! A knowledge of file structures and layouts did you right in this case. Good job.
    --Ed--
      My Computers


  4. Posts : 112
    64-bit Windows 10 Pro 1909
    Thread Starter
       #4

    EdTittel said:
    Nice save, Thenin! A knowledge of file structures and layouts did you right in this case. Good job.
    --Ed--
    Wow, thanks enormously, Wise Guru Sir! Coming from you, that's high praise indeed!
      My Computers


 

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

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




Windows 10 Forums