Thanks again guys.

The salvage operation complete. I ran it using -f and -n parameters.

The weird aspect is that it hasn't found any errors. I am QUITE sure that I did correctly diagnose the hard drive as dysfunctional. Here's why:

1. Blue screens with KERNEL_DATA_INPAGE_ERROR with stop code 0x0000007a. Apparently one possible event when this message appears is when the system can't retrieve some data from page file. I had my page file on this drive so it seemed logical enough.
2. Immediately after these blue screens when I restarted usually the drive wasn't found during boot and didn't appear in my computer. I had to shut down completely and then boot, after which it was found correctly.
3. Running chkdsk test in read only mode didn't even complete because it ran into errors. It suggested doing the fix processes if I remember right.
4. The hard drive made this squeaking noise sometimes, as if the bearing was about to break.

I DID test my RAM too, just in case, and did encounter errors. I removed two of my sticks and didn't encounter errors after a quick test (~30 minutes), while before I got a few in the same time, so I figured it's good enough to run this salvage operation. I need to test around with the RAM some more once the copy process is finished. I know, I'll be careful. I know that bad RAM can corrupt data or worse. Anyway, this is the other possible explanation besides a faulty hard drive.


Anyway, back to the original question: if there are no errors in the ddrescue process, does it mean that it was able to read everything without a hitch? I suppose it can't check for file integrity? How can I check what data is corrupted and what isn't?