Total Commander

Access violation at address 767EC1A5. Read of address 00000034.
Access violation at address 767EC1A5. Read at address 00000034
Windows 7 SP1 HomePremium 6.1 build (7601), base: 00400000

Please report the error to the Author, with a description
of what you were doing when this error occurred!

Windows exception: C0000005
Stack trace:
767EC1A5
00448B61 0044AB62 >00427706 0044A104 00427706 0044A05A
00427706 00434752 0044A104 00427706 0042CE8D 0042CF28

Raw:
0044A05A 00427706 0044AEDB 00434752 00448B61 0044AE31
0044A1CE 0044AB62 00427706 0044A104 00427706 0044A05A
00427706 0044AEDB 00434752 0044BAAE 00448B61 0044AE31
0044A1CE 0044AB62 00427706 0044A104 00427706 0042CE8D
0042CF28 0042D0E2
Press Ctrl-C to copy this report!


I am using TC 9.22a, 32-bit.

I normally go many weeks without seeing this error, but it happened three times today. Each time, I had pressed Shift-F6 so I could append characters to a filename, and the error occurred. Each time was with a different file. The renames always succeed after restarting TC. The filenames have been plain ASCII character names, so far. None are overly long names, almost always being under 60 characters.

Can you tell me when exactly you get the error? Directly after Shift+F6, or when trying to edit the name, or when you press ENTER?

I never got a chance to hit ENTER. Since the sequence I normally use is, Shift-F6, Left-arrow, Right-arrow, to un-select the name, before I start typing whatever I wish to append to the name. The error is after the Shift-F6, and before I get to actually append any characters. I notice the error as I'm moving my finger from the arrows to the character part of the keyboard. It appears to pop up as I'm hitting the arrows, but that could be a mirco-second before, or after, the arrows and it would be hard for me to reliably see the difference.

Unfortunately, it's never been repeatable. Choosing to exit, or to continue, TC after the error seems to make no difference. The same rename always works on the next attempt. I have not had any more errors since reporting the three that I had. That was the only time I can recall ever getting three of them in a day.