Access Violation at 0x004DBA8A

[morganglines]

This product has worked very well and recovered quite a bit of data from hard disks on two other occasions with my previous computer (both of those were EIDE, not sure if that's here or there). Overall, I'm pretty pleased but for some reason one of the partitions on my SATA drive went belly-up and Zar isn't working for it.
Another 200gb FAT32 partition on the same physical drive (so far . . . *knocks on wood and preps to backup*) is working. My 500GB FAT32 partition is now showing as 'raw' formatted -- it worked fine for the last 8 months or so (formatted it with gparted live CD originally). Zar (8.3 build 26) works overnight then quits with the error "access violation at 0x004DBA8A (tried to write to 0x1640FF4), program terminated"

Logfile.txt only contains:
NT 5.1.2600 Service Pack 2; 2047 MB RAM (accurate)
TS: Stop validation
TS: Stopped validation
Logging - shut down

I'll try with the latest dev version (looks like 27 at this writing?) and enable advanced logging in the prefs then post back. I don't see any .zar file in the program folder.

[Alexey V. Gubin]

We are also working on this right now, although no promising result in sight (so far).

[morganglines]

Here's the last bit of the log (~4mb) when run on verbose (most of these 'tiffs' are .cr2 camera raw images -- I took out lines which were sequential since they often go on an on and it looks like the cap on posts is around 10k lines):

00000E44: Disk 0103, LBA 247631763 is TIFF image
00000E44: Disk 0103, LBA 247691315 is TIFF image
00000E44: Disk 0103, LBA 247710931 is TIFF image
00000E44: Disk 0103, LBA 247789363 is TIFF image
00000E44: Local cache hit ratio: 0.0% cache hits of 2048 requests
00000E44: MEMORY STATUS: Address space: 46080 KB; Alloc: 43765 KB; Free: 2198 KB; Small: 1174 KB; Big: 3024 B;
00000E44: Disk 0103, LBA 247808915 is TIFF image
00000E44: Disk 0103, LBA 247828467 is TIFF image
00000E44: Disk 0103, LBA 247848083 is TIFF image
00000E44: Disk 0103, LBA 247867827 is TIFF image
00000E44: Disk 0103, LBA 247887539 is TIFF image
00000E44: Disk 0103, LBA 247907251 is TIFF image
00000E44: Disk 0103, LBA 247927795 is TIFF image
... removed some lines here more TIFFs found. . .
00000E44: Disk 0103, LBA 248244536 is JPEG image
00000E44: Disk 0103, LBA 248336083 is FAT directory run
. . . sequential . . .
00000E44: Disk 0103, LBA 248336110 is FAT directory run
00000E44: Disk 0103, LBA 248336111 is FAT directory run
00000E44: Disk 0103, LBA 248336112 is FAT directory run
00000E44: Disk 0103, LBA 248336113 is FAT directory run
. . .
00000E44: Disk 0103, LBA 253994963 is TIFF image
00000E44: Local cache hit ratio: 0.0% cache hits of 2048 requests
00000E44: MEMORY STATUS: Address space: 46080 KB; Alloc: 44003 KB; Free: 1961 KB; Small: 1162 KB; Big: 3024 B;
00000E44: Disk 0103, LBA 254016531 is FAT directory run
. . . sequential . . .
00000E44: Disk 0103, LBA 254023294 is FAT directory run
00000E44: Disk 0103, LBA 254048796 is JPEG image
00000E44: Disk 0103, LBA 254148307 is Start of FAT directory
00000E44: Disk 0103, LBA 254148308 is FAT directory run
00000E44: Disk 0103, LBA 254148309 is FAT directory run
. . .
00000E44: Disk 0103, LBA 254148331 is FAT directory run
00000E44: Disk 0103, LBA 254148332 is FAT directory run
00000E44: Local cache hit ratio: 0.0% cache hits of 2048 requests
00000E44: MEMORY STATUS: Address space: 46080 KB; Alloc: 44199 KB; Free: 1764 KB; Small: 1159 KB; Big: 3024 B;
00000E44: Disk 0103, LBA 254267827 is FAT directory run
00000E44: Disk 0103, LBA 254267828 is FAT directory run
00000E44: Disk 0103, LBA 254267829 is FAT directory run
00000E44: Disk 0103, LBA 254267830 is FAT directory run
. . .
00000E44: Disk 0103, LBA 254825427 is CRW Canon raw image
00000E44: Disk 0103, LBA 254838419 is JPEG image
00000E44: Disk 0103, LBA 254838451 is CRW Canon raw image
00000E44: Disk 0103, LBA 254859059 is JPEG image
00000E44: Disk 0103, LBA 254862227 is FAT32 sector #0
00000E44: Disk 0103, LBA 254862228 is FAT32 sector #1
00000E44: Disk 0103, LBA 254862229 is FAT32 sector #2
00000E44: Disk 0103, LBA 254862230 is FAT32 sector #3
. . .removed 2,000 or so sequential lines . . .
00000E44: Disk 0103, LBA 254864287 is FAT32 sector #2060
00000E44: Disk 0103, LBA 254864288 is FAT32 sector #2061
00000E44: Disk 0103, LBA 254864289 is FAT32 sector #2062
00000E44: Disk 0103, LBA 254864290 is FAT32 sector #2063
00000E44: Disk 0103, LBA 254864291 is FAT32 sector #2064
00000E44: Disk 0103, LBA 254864292 is FAT32 sector #2065
00000E44: Disk 0103, LBA 254877779 is CRW Canon raw image
00000E44: Local cache hit ratio: 0.0% cache hits of 2048 requests
00000E44: MEMORY STATUS: Address space: 46080 KB; Alloc: 44520 KB; Free: 1443 KB; Small: 1223 KB; Big: 11264 B;
00000E44: Disk 0103, LBA 254892723 is JPEG image
00000E44: Disk 0103, LBA 254892755 is CRW Canon raw image
00000E44: Disk 0103, LBA 254905875 is JPEG image
00000E44: Disk 0103, LBA 254905907 is CRW Canon raw image
00000E44: Disk 0103, LBA 254918547 is JPEG image
00000E44: Disk 0103, LBA 254918579 is CRW Canon raw image
00000E44: Disk 0103, LBA 254933267 is JPEG image
00000E44: Disk 0103, LBA 254933299 is CRW Canon raw image
00000E44: Disk 0103, LBA 254948467 is JPEG image
00000E44: Disk 0103, LBA 254948499 is CRW Canon raw image
00000E44: Disk 0103, LBA 254962419 is JPEG image
00000E44: Disk 0103, LBA 254962451 is Start of FAT directory
00000E44: Disk 0103, LBA 254962452 is FAT directory run
00000E44: Disk 0103, LBA 254962483 is JPEG image
00000E44: Disk 0103, LBA 254962547 is Start of FAT directory
00000E44: Disk 0103, LBA 254962548 is FAT directory run
00000E44: Disk 0103, LBA 254962549 is FAT directory run
00000E44: Disk 0103, LBA 254962550 is FAT directory run
00000E44: Disk 0103, LBA 254962551 is FAT directory run
00000E44: Disk 0103, LBA 254962552 is FAT directory run
00000E44: Disk 0103, LBA 254962553 is FAT directory run
00000E44: Disk 0103, LBA 254962554 is FAT directory run
00000E44: Disk 0103, LBA 255002419 is Start of FAT directory
00000E44: Disk 0103, LBA 255002420 is FAT directory run
00000E44: Disk 0103, LBA 255002421 is FAT directory run
00000E44: Disk 0103, LBA 255002579 is JPEG image
00000E44: Disk 0103, LBA 255013107 is JPEG image
00000E44: Local cache hit ratio: 0.0% cache hits of 2048 requests
00000E44: MEMORY STATUS: Address space: 46080 KB; Alloc: 44617 KB; Free: 1345 KB; Small: 1222 KB; Big: 11264 B;
00000E44: Disk 0103, LBA 255051059 is JPEG image
00000E44: Local cache hit ratio: 0.0% cache hits of 2048 requests
. . . Hundreds of lines with this memory status message . . .
00000E44: Local cache hit ratio: 0.0% cache hits of 2048 requests
00000E44: MEMORY STATUS: Address space: 46080 KB; Alloc: 44617 KB; Free: 1345 KB; Small: 1222 KB; Big: 41264 B;
00000E44: Local cache hit ratio: 0.0% cache hits of 2048 requests
00000E44: MEMORY STATUS: Address space: 46080 KB; Alloc: 44617 KB; Free: 1345 KB; Small: 1222 KB; Big: 41264 B;
00000E44: Local cache hit ratio: 0.0% cache hits of 2048 requests
00000E44: MEMORY STATUS: Address space: 46080 KB; Alloc: 44617 KB; Free: 1345 KB; Small: 1222 KB; Big: 41264 B;
00000E44: Local cache hit ratio: 0.0% cache hits of 2048 requests
00000E44: MEMORY STATUS: Address space: 46080 KB; Alloc: 44617 KB; Free: 1345 KB; Small: 1222 KB; Big: 41264 B;
00000E44: Local cache hit ratio: 0.0% cache hits of 2048 requests
00000E44: MEMORY STATUS: Address space: 46080 KB; Alloc: 44617 KB; Free: 1345 KB; Small: 1222 KB; Big: 41264 B;
00000E44: Local cache hit ratio: 0.0% cache hits of 2048 requests
00000E44: MEMORY STATUS: Address space: 46080 KB; Alloc: 44617 KB; Free: 1345 KB; Small: 1222 KB; Big: 41264 B;
00000E44: Local cache hit ratio: 0.0% cache hits of 2048 requests
00000E44: MEMORY STATUS: Address space: 46080 KB; Alloc: 44617 KB; Free: 1345 KB; Small: 1222 KB; Big: 41264 B;
00000E44: Local cache hit ratio: 0.0% cache hits of 2048 requests
00000E44: MEMORY STATUS: Address space: 46080 KB; Alloc: 44617 KB; Free: 1345 KB; Small: 1222 KB; Big: 41264 B;

[Alexey V. Gubin]

Ok, one more thing you can try (since we are unable to reproduce the issue anyway) is to set "Quick scan mode" to "Disabled" in preferences under "Common filesystem analysis". And just retry with it disabled. I know this means a ten hours run at least, but this is the best idea we came up with.

This is what is known so far:

First is how the scanner part is supposed to work
1. Quick prescan
2. Quick scan
if it determines quick scan did not work, fallback occurs to
3. Full scan - the only method available prior to 8.3

All reported cases involve large FAT volumes. Quick scan only works for NTFS, and on FAT there is always a fallback/full scan. Quick scan itself works like charm with NTFS volumes. Full scan also works fine since it is not modified since 8.2. Looks like the fallback procedure is buggy. And it turns out we never tested it with a FAT32 >40GB volume; although we did not crash it as of yet by running on a 500GB volume, I suspect the fallback procedure might be faulty.
The idea is to disable quick scan and go straight to a full scan, thus bypassing a fallback routine.

Ah actually this is not exactly so as there is one report involving NTFS; however I suspect there was a fallback (it is possible to have a fallback to a full scan on an NTFS volume).

[morganglines]

Ok, thanks, I'll try that. I just got an external HDD to recover to and store newer pictures on so I can afford to be patient. :-)

[morganglines]

Left it to run overnight with QuickScan disabled -- it stops with
"UNABLE TO CONTINUE:
There seems to be no files on volume.
Unable to continue processing, program will now terminate.
Not a bug - data is probably beyond repair, or something is misconfigured."

In the background behind this dialog box ZAR shows "Located 68,872 files in 491 directories." The volume map appears about 1/4 done. There's now an auto-save sub folder in the Zar program files directory.

The log file is 126mb (picking up specific filenames now) ending with:

Frances_Scott_Superbowl42Tackle_20080203mmg3744.mi e
00000A9C: The object has been purged : Moon_I_Miss16Crop20080120mmg9828.mie
00000A9C: The object has been purged : Moon_I_Miss16Crop20080120mmg9852.mie
00000A9C: The object has been purged : NC3Q0011.MIE
00000A9C: The object has been purged : NC3Q0021.MIE
00000A9C: The object has been purged : NC3Q0056.MIE
00000A9C: The object has been purged : NC3Q0072.MIE
00000A9C: The object has been purged : Moon_20080120mmg0073.mie
00000A9C: The object has been purged : HDRPan_K_2_20080120mmg9932.mie
00000A9C: The object has been purged : HDRPan_O_4_20080120mmg9991.mie
00000A9C: The object has been purged : Moon_I_Miss16Crop20080120mmg9866.mie
00000A9C: The object has been purged : Moon_I_Miss16Crop20080120mmg9846.mie
00000A9C: The object has been purged : HDRPan_C_2_20080120mmg9843.mie
00000A9C: The object has been purged : HDRPan_O_4_20080120mmg9988.mie
00000A9C: The object has been purged : Rascal_HDR_F20080120mmg0159.mie
00000A9C: The object has been purged : OctoberNight20071015mmg5206.mie
00000A9C: The object has been purged : HDRPan_B_3_20080120mmg9832.mie
00000A9C: The object has been purged : HDRPan_C_4_20080120mmg9857.mie
00000A9C: The object has been purged : HDRPan_D_3_20080120mmg9876.mie
00000A9C: The object has been purged : HDRPan_F__20080120mmg9893.mie
00000A9C: The object has been purged : HDRPan_I__20080120mmg9915.mie
00000A9C: The object has been purged : HDRPan_K_2_20080120mmg9937.mie
00000A9C: The object has been purged : HDRPan_N__20080120mmg9961.mie
00000A9C: The object has been purged : Rascal_HDR_B20080120mmg0119.mie
00000A9C: The object has been purged : Rascal_HDR_E20080120mmg0149.mie
00000A9C: The object has been purged : Frances_Scott_Superbowl42Tackle_20080203mmg3742.jp g
00000A9C: The object has been purged : Frances_Scott_Superbowl42Tackle_20080203mmg3725.jp g
00000A9C: Performance: Ident data query (0 of 0) 0s
00000A9C: Performance: Ident data query (0 of 0) 0s
00000A9C: Performance: Ident data query (0 of 0) 0s
00000A9C: Performance: Ident data query (57549 of 57549) 0s
00000A9C: Performance: Ident data query (0 of 0) 0s
00000A9C: Performance: Ident data query (0 of 0) 0s
00000A9C: Performance: Ident data query (57549 of 57549) 0s
000006B8: UNABLE TO CONTINUE:
There seems to be no files on volume.
Unable to continue processing, program will now terminate.
Not a bug - data is probably beyond repair, or something is misconfigured.
000004D8: Performance: ValTime 0s

[Alexey V. Gubin]

if you zip the 126 MB log with maximum compression settings, how large it will be? If less than 15 MB (log compresses very well), email it to development@z-a-recovery.com

[morganglines]

An ~8mb zip file is on it's way. :-)

[Alexey V. Gubin]

Download and install http://www.z-a-recovery.com/zar-83-029.exe
Delete the log file (so we start clean in case it is needed).
Start ZAR, click "Advanced Configuration"
In there, under "Common filesystem analysis", clear both entries associated with filtering ("filter out") at the bottom of the window.
Click OK to close configuration.
Try to rescan.With this version, I just did a test run on a 500GB FAT32 volume in under six hours start-to-end.

[morganglines]

Cool, thanks, will try that now. :-)

[morganglines]

Took about 3 hours to analyze my 500gb partition, currently recovered around 1,600 of 68,000 files (still running as I type this . . .) It seems to have the file names too which will save me days working in Lightroom / Bridge. :-) Thanks again for your hard work!

[morganglines]

Completed successfully -- thanks again! :-)

[Alexey V. Gubin]

Okay, so we have it fixed finally, that's nice.