Bugs in 64-bit version, crashes during deep scan near/at end of process

Recuva
1

Hello,

I started Recuva to try to recover file son a fiber SAN. I launched Recuva via a drive on another server. I set it to do a deep scan. After running for 3 days, I was disappointed to see it crashed and I lost all the time invested in the thing running. While it's running it doesn't report any status as to files that are found, only a percent complete which is a big drawback considering a user may want to recover a file when the job is only say 5% complete but they're forced to wait out the entire process because it never shows you what files are available.

This was the error reported:

Problem signature:

Problem Event Name: APPCRASH

Application Name: Recuva64.exe

Application Version: 1.42.0.544

Application Timestamp: 4ed76412

Fault Module Name: ntdll.dll

Fault Module Version: 6.1.7601.17514

Fault Module Timestamp: 4ce7c8f9

Exception Code: c0000006

Exception Offset: 0000000000029c12

OS Version: 6.1.7601.2.1.0.274.10

Locale ID: 1033

Additional Information 1: abcc

Additional Information 2: abcc8f7853b48d9807d6d51eb1fa5df9

Additional Information 3: abcc

Additional Information 4: abcc8f7853b48d9807d6d51eb1fa5df9

Read our privacy statement online:

http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:

C:\Windows\system32\en-US\erofflps.txt

I've only tried program a few times and it's crashed 2 out of 3 times. Seems to be major stability problems, any guidance would be appreciated.

Thanks,

UST

2

Please run recuva in Debug mode

  1. From the Windows desktop, click Start and then click Run.
  2. In the Run dialog box, type <path to Recuva> /debug. Typically, this will be: 
    "C:\Program Files\Recuva\Recuva.exe" /debug
  3. Click OK. Recuva starts in debug mode. You will see the word [debug] next to the version number at the top of the Recuva window.
  4. Once you have finished using Recuva and have quit the program, use Windows Explorer to navigate to the installation path (the same path you typed in Step 2). The log file will be in this folder in the format Recuva_log[date].txt.

the " marks are required

replace Program files\recuva with the location of your recuva program

replace recuva.exe with Recuva64.exe

force it to crash

attach the log to this thread, hold on to the dmp (also in the recuva folder) file as the developers may ask for it.

3

What's the capacity of your SAN? I know no more about them than I can flick through on Wikipedia, but aren't they huge?