Access Violation Exception 8.01
Moderators: Hacker, petermad, Stefan2, white
Access Violation Exception 8.01
I have some dumps here for c0000005 = Access Violation Exception. If there's some interest, I would find a possibility to upload them.
Roman.
Roman.
Last edited by Romaschka on 2013-05-28, 16:35 UTC, edited 2 times in total.
So, where's the bug?
Regards
Dalai
- What were you doing when you got what message?
- "Who" did show the message: a plugin or TC itself? A screenshot may be helpful, too.
- The access was denied to what/where?
- What OS are you using? From your report [EDIT]- not report but memory dump -[/EDIT], I can conclude that you use Windows Server 2008 R2 (x64) Datacenter inside VMware, is that correct? If so, which VMware product?
Regards
Dalai
Last edited by Dalai on 2013-05-28, 11:56 UTC, edited 1 time in total.
#101164 Personal licence
Ryzen 5 2600, 16 GiB RAM, ASUS Prime X370-A, Win7 x64
Plugins: Services2, Startups, CertificateInfo, SignatureInfo, LineBreakInfo - Download-Mirror
Ryzen 5 2600, 16 GiB RAM, ASUS Prime X370-A, Win7 x64
Plugins: Services2, Startups, CertificateInfo, SignatureInfo, LineBreakInfo - Download-Mirror
The bug is in the (process full memory) dump.
- There is no message, I've no idea, when it ocures. There is only WER, or Dr. Watson, who collects crash dumps and sends them to MS
- So there is also no message, I've got
- I don't think, it's a plugin problem, I haven't used them for the long time
- I guess it's a memory access denied, but I really don't know
- The information inside the dump is correct, we are using vSphere 5.1.0, 1021289 here... does it really matters?
Here ist the stack:
0:000> kb
*** Stack trace for last set context - .thread/.cxr resets it
RetAddr : Args to Child : Call Site
00000000`0070fd76 : 00000000`03454628 00000000`00b17dc0 00000000`00000000 00000000`00000000 : 0x0
00000000`03454628 : 00000000`00b17dc0 00000000`00000000 00000000`00000000 00000000`01c07010 : TOTALCMD64+0x30fd76
00000000`00b17dc0 : 00000000`00000000 00000000`00000000 00000000`01c07010 00000000`0070fd1a : 0x3454628
00000000`00000000 : 00000000`00000000 00000000`01c07010 00000000`0070fd1a 00000000`01c06de0 : TOTALCMD64+0x717dc0
If you have reasonable symbols you can get the place in code, where the problem occures, function names and parameters.
Next time I'll pay attention to what I've done.
Roman.
- There is no message, I've no idea, when it ocures. There is only WER, or Dr. Watson, who collects crash dumps and sends them to MS
- So there is also no message, I've got
- I don't think, it's a plugin problem, I haven't used them for the long time
- I guess it's a memory access denied, but I really don't know
- The information inside the dump is correct, we are using vSphere 5.1.0, 1021289 here... does it really matters?
Here ist the stack:
0:000> kb
*** Stack trace for last set context - .thread/.cxr resets it
RetAddr : Args to Child : Call Site
00000000`0070fd76 : 00000000`03454628 00000000`00b17dc0 00000000`00000000 00000000`00000000 : 0x0
00000000`03454628 : 00000000`00b17dc0 00000000`00000000 00000000`00000000 00000000`01c07010 : TOTALCMD64+0x30fd76
00000000`00b17dc0 : 00000000`00000000 00000000`00000000 00000000`01c07010 00000000`0070fd1a : 0x3454628
00000000`00000000 : 00000000`00000000 00000000`01c07010 00000000`0070fd1a 00000000`01c06de0 : TOTALCMD64+0x717dc0
If you have reasonable symbols you can get the place in code, where the problem occures, function names and parameters.
Next time I'll pay attention to what I've done.
Roman.
Yes, it does. I can remember a bug in Virtual PC regarding shared folders that caused TC to crash (see this thread). So, yes, it is important to know if TC runs on a native Windows or on a virtualized one.Romaschka wrote:- The information inside the dump is correct, we are using vSphere 5.1.0, 1021289 here... does it really matters?
So, there is a message. TC crashes and WER/Dr. Watson jumps in because of an uncaught exception. That's important information- There ist no message, I've no idea, when it ocures. There is only WER, or Dr. Watson, who collects crash dumps and sends them to MS

Remember that not only Ghisler may be interested in the bug reports but other users, too. It's much easier for them to see if someone else reported a specific bug. Users can check if the environments (TC version, Virtualizer, Windows version and so on) match; makes it easier for Ghisler to locate the bug's cause and fix it or work around it.
Regards
Dalai
#101164 Personal licence
Ryzen 5 2600, 16 GiB RAM, ASUS Prime X370-A, Win7 x64
Plugins: Services2, Startups, CertificateInfo, SignatureInfo, LineBreakInfo - Download-Mirror
Ryzen 5 2600, 16 GiB RAM, ASUS Prime X370-A, Win7 x64
Plugins: Services2, Startups, CertificateInfo, SignatureInfo, LineBreakInfo - Download-Mirror
Ok,
here some more informations from Event Log:
Faulting application name: TOTALCMD64.EXE, version: 8.0.1.0, time stamp: 0x00000000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000000000
Faulting process id: 0x84
Faulting application start time: 0x01ce3aadc9fe8e03
Faulting application path: C:\Program Files\TotalCMD\TOTALCMD64.EXE
Faulting module path: unknown
Report Id: 52b9867e-acba-11e2-9a1f-005056956b21
Fault bucket 0, type 0
Event Name: BEX64
Response: Not available
Cab Id: 0
Problem signature:
P1: TOTALCMD64.EXE
P2: 8.0.1.0
P3: 00000000
P4: StackHash_22b1
P5: 0.0.0.0
P6: 00000000
P7: 0000000000000000
P8: c0000005
P9: 0000000000000008
P10:
BEX64 seems like Buffer Overflow?...
Here is one 5 mins earlier from Symantec AV:
Zeitüberschreitung bei Bewertungsprüfung während der Evaluierung nicht eindeutiger Dateien, wahrscheinlich aufgrund von Netzwerkverzögerungen.
Maybe it plays a role...
Roman.
here some more informations from Event Log:
Faulting application name: TOTALCMD64.EXE, version: 8.0.1.0, time stamp: 0x00000000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000000000
Faulting process id: 0x84
Faulting application start time: 0x01ce3aadc9fe8e03
Faulting application path: C:\Program Files\TotalCMD\TOTALCMD64.EXE
Faulting module path: unknown
Report Id: 52b9867e-acba-11e2-9a1f-005056956b21
Fault bucket 0, type 0
Event Name: BEX64
Response: Not available
Cab Id: 0
Problem signature:
P1: TOTALCMD64.EXE
P2: 8.0.1.0
P3: 00000000
P4: StackHash_22b1
P5: 0.0.0.0
P6: 00000000
P7: 0000000000000000
P8: c0000005
P9: 0000000000000008
P10:
BEX64 seems like Buffer Overflow?...
Here is one 5 mins earlier from Symantec AV:
Zeitüberschreitung bei Bewertungsprüfung während der Evaluierung nicht eindeutiger Dateien, wahrscheinlich aufgrund von Netzwerkverzögerungen.
Maybe it plays a role...
Roman.
- ghisler(Author)
- Site Admin
- Posts: 50386
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
Unfortunately the stack trace didn't reveal anything useful. Normally the built-in exception handler should catch all exceptions in TC. Therefore I guess that it's not in TC itself, but in some Explorer extension or plugin loaded by TC.
What are you doing in TC when you get this error?
What are you doing in TC when you get this error?
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com