PDA

View Full Version : Error Access Violation ??


eklegein
24th January 2008, 19:02
I just purchased this and after 24 hours of running on a 400GB FAT32 drive, ZAR stopped with following error.

Access violation at 0x004DBA0A (tried to write to 0x040A0FF4), program terminated

What to do?

eklegein
24th January 2008, 19:27
I forgot to mention I am running WIndows XP. The drive is an IDE and it is plugged straight into the IDE port.

Running Version 8.3 Build 19

Alexey V. Gubin
25th January 2008, 06:25
Could you please locate the log file, C:\Program Files\ZAR\Logfile.txt,
and post last 50 or so lines of it here, so I can examine it.

eklegein
26th January 2008, 08:31
I have restarted ZAR in Safe mode. It has been running for 37 hours now and is 41% complete in Full Identifying. The window still shows that file format is unknown. I am going to let it run it's course and hopefully it actually finishes. If it doesn't, as it did not in all other attempts, I will then post the log file info as you are requesting. I am very surprised that this pass is taking so long as compared to the last one.

Alexey V. Gubin
26th January 2008, 11:07
I found it interesting actually. Safe vs. Normal mode may be different in drivers, or caching strategies, but typically there is no significant difference.

eklegein
27th January 2008, 08:06
Update: ZAR has been running for 60 hours now and is 81% complete in Full Identify mode running in XP Safe Mode. The machine has dual 1Ghz CPUs with a gig of RAM. It still indicates that the drive format is unknown. No bad sectors.

eklegein
27th January 2008, 20:19
000004A4: 70:54:54.656: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 70:54:54.656: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;
000004A4: 70:55:40.562: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 70:55:40.578: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;
000004A4: 70:56:26.484: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 70:56:26.500: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;
000004A4: 70:57:12.328: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 70:57:12.344: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;
000004A4: 70:57:58.156: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 70:57:58.156: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;
000004A4: 70:58:43.922: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 70:58:43.937: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;
000004A4: 70:59:29.844: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 70:59:29.859: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;
000004A4: 71:00:15.703: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 71:00:15.719: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;
000004A4: 71:01:01.531: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 71:01:01.547: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;
000004A4: 71:01:47.359: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 71:01:47.375: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;
000004A4: 71:02:33.140: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 71:02:33.156: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;
000004A4: 71:03:19.156: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 71:03:19.172: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;
000004A4: 71:04:05.015: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 71:04:05.031: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;
000004A4: 71:04:50.906: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 71:04:50.922: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;
000004A4: 71:05:36.750: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 71:05:36.750: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;
000004A4: 71:06:22.719: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 71:06:22.734: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;
000004A4: 71:07:08.562: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 71:07:08.562: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;
000004A4: 71:07:54.344: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 71:07:54.359: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;
000004A4: 71:08:40.109: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 71:08:40.125: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;
000004A4: 71:09:25.890: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 71:09:25.906: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;
000004A4: 71:10:11.765: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 71:10:11.781: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;
000004A4: 71:10:57.812: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 71:10:57.812: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;
000004A4: 71:11:43.672: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 71:11:43.672: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;
000004A4: 71:12:29.515: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 71:12:29.531: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;
000004A4: 71:13:15.375: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 71:13:15.390: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;
000004A4: 71:14:01.344: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 71:14:01.344: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;
000004A4: 71:14:47.219: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 71:14:47.219: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;
000004A4: 71:15:33.015: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 71:15:33.031: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;
000004A4: 71:16:18.828: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 71:16:18.844: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;
000004A4: 71:17:04.687: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 71:17:04.703: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;
000004A4: 71:17:50.656: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 71:17:50.672: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;
000004A4: 71:18:36.390: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 71:18:36.406: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;
000004A4: 71:19:22.187: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 71:19:22.187: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;
000004A4: 71:20:08.015: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 71:20:08.031: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;
000004A4: 71:20:53.781: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 71:20:53.781: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;
000004A4: 71:21:39.531: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 71:21:39.547: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;
000004A4: 71:22:25.500: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 71:22:25.515: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;
000004A4: 71:23:11.375: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 71:23:11.390: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;
000004A4: 71:23:57.203: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 71:23:57.219: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;
000004A4: 71:24:43.015: Local cache hit ratio: 0.0% cache hits of 2048 requests
000004A4: 71:24:43.031: MEMORY STATUS: Address space: 44800 KB; Alloc: 41629 KB; Free: 3013 KB; Small: 1843 KB; Big: 36112 B;


I would have thought that this recovery should have been simple. What ot do now?

Alexey V. Gubin
28th January 2008, 16:52
Honestly, I suggest you now go and check out what our competition has to offer, rather then wasting even more time while we try whatever troubleshooting options we have.

This case should be simple, but there are some which somehow turn out worse than expected. The competition, on the other hand, may have implemented something different and hence avoid the problem altogether.

eklegein
28th January 2008, 17:17
That is not fair. I have made numerous attempts that took weeks to execute. I followed your suggestions. I even purchased a license with anticipation that it would work and that you would stand behind the product. This drive did not crash and burn. It spins fine and I am sure it will format if need be. It was in a USB enclusre and the power supply was accidentally disconnected. I believe the FAT table was corrupted during an active transaction. The drive was removed from the USB enclosure and attached to a different computer directly to an IDE cable. Are you suggesting that you are abandoning me and not providing further support? My investment in this software is money thrown away if you cannot stand behind it. Is that fair? I just want to recover a few folders. The log file is 15.5MB in size and it has a lot of info in it. I noticed that even though the log file indicates that it recognized FAT32, the user interface never reflected this. And there are not bad sectors.

Alexey V. Gubin
29th January 2008, 03:24
I suggest that you try out someone elses' software because I think that will be most effective course of action. Pretty sure we will refund your money as the software did not work. Primary concern is that there is no way I can give the time you wasted back. So I have to suggest that to avoid wasting even more time.

eklegein
29th January 2008, 07:23
Your troubleshooting support has been invaluable. Your product is world-class. Please send me a full refund.

I have never, in my 35 years within this industry, have seen such stellar response standing behind a product while providing such thorough and in-depth customer support. Thanks for nothing.

I will be sure to have my young staff spread accurate reviews about ZAR all over the internet. They are very good at tuning up Google indices to ensure these upcoming reviews are highly visible in order help prevent others from becoming victimized, led along and ultimately left in the dark.

:mad:

eklegein
30th January 2008, 07:19
After having spent a couple weeks and several attempts in executing ZAR with hope that I could do a simple restore, I have taken your recommendation and tried your competition. :eek: :confused:

The first one that I installed last night has successfully recovered every single file on my 400GB drive and in just a matter of a few hours. :cool:

I hope you can fix your software soon. :rolleyes:


Now, what's it going to take to get you to

SEND ME A FULL REFUND IMMEDIATELY ? !!!!!!!!!

Alexey V. Gubin
30th January 2008, 09:34
Our typical practice is that refunds are completed in two days following the request. So I guess that's about it.

mckennis
20th February 2009, 21:38
The first one that I installed last night has successfully recovered every single file on my 400GB drive and in just a matter of a few hours.

So what software was it because I have wasted one 28 hour run and two 18 hour runs. They seem to be unable to fix this issue that has been reported for years.