Recovering from SD card after blue screen

Recuva
1

Hello,

so here is my puzzle:

I was moving photos from sd card to hard drive (I'm using TeraCopy for copying) when I got a blue screen and computer restarted. After reboot I realized that the card was empty. Some photos were not copied, Recuva found all files (indeed, deep scan found photos more than year old :), but files that were not yet copied are in "very poor" state and the comment says: This file is overwritten with "(name of next file)", for instance for file _MGP4494.JPG comment says: "This file is overwritten with _MGP4495.JPG". Another thing I noticed is that path is just some number, actual path was /DCIM/100PENTX/, now it says /_311578/

Any thoughts on how to get those files back? They have not been overwritten, actually nothing was written to card since the reboot, I even put the little slider on SD card to read only. So data has to be there, right?

Thanks for the reply.

2

I think that Alan B has some experience of Teracopy, so he might chip in later.

If you look at Recuva's scan results in thumbnail mode then you'll see whether there is anything worth recovering. You can of course recover all the files you want and then go through them afterwards to see what's good and what's not.

I think that Recuva uses info from the file table to tell whether a file has been overwritten. Perhaps TC modified the table (although I can't see why) when the files were being copied. SSD's also do some funny file shuffling on their own, so maybe this has lost some info.

Are you running a deep scan? If not try it and look at the results in thumbnail mode. Look at all files, not just pictures, as some pics will have lost their extension and not be selected by the picture filter. I also run Recuva in Advanced mode, not the wizard, as this makes file selection so much easier.

3

I was moving photos from sd card to hard drive (I'm using TeraCopy for copying) when I got a blue screen and computer restarted. After reboot I realized that the card was empty.

You can use TeraCopy to either COPY or MOVE.

The correct result of "MOVING Photos" would include an empty card.

My experience of TeraCopy is that it computes a checksum for each file that is copied(moved),

after which it reads back all the copies and computes their checksums.

Only files with matching checksums are considered to be valid copies.

I am reasonable sure that TeraCopy would not proceed beyond COPY phase into the DELETE phase of a MOVE unless it has read back and validated the checksum.

It may be worth asking TeraCopy if there is anything different between their moving files from a SD card vs a HDD.

Support is available from

http://codesector.com/teracopy

If I was in your situation I would not trust my memory that I started the MOVE with more photos on the card than arrived on the HDD.

If I have hard evidence that my memory was correct then I would assume either :-

After the missing photo was sent to the HDD it suffered delays in either a Windows Disc Cache or the HDD Disc Cache,

and when TeraCopy read back the file it validated the contents of a cache that had not yet got onto the HDD;

or more probably

TeraCopy told Windows to delete each file that had been validated,

and then whilst Windows was deleting a file there was a "Windows Whoopsie" which zapped everything on the card and gave you a BSOD.

Fun Fact - Spell check does not like "Windows Whoopsie", so I Googled and came up with

http://www.multiclas...om_windows.html

Would you by any chance be using Microsoft "protection" ? :)