Which error logs are you referring to, the Windows Event log?
I have crash dumps produced using SysInternals' ProcDump.
One produced using "C:\Program Files\SysInternals\procdump" -o -n 1 -e -64 -mp 9528 TCMD.dmp" (Large) and the other "C:\Program Files\SysInternals\procdump" -o -n 1 -e -64 3280 TCMD.dmp" (Smaller)
I had the same crash issue with 23 right after setting up and starting to run it on Win7x86. The log files were empty also. I did capture this from Windows:
Code:
Problem signature:
Problem Event Name: APPCRASH
Application Name: tcmd.exe
Application Version: 19.0.23.0
Application Timestamp: 56664608
Fault Module Name: tcmd.exe
Fault Module Version: 19.0.23.0
Fault Module Timestamp: 56664608
Exception Code: c0000005
Exception Offset: 000531ca
OS Version: 6.1.7601.2.1.0.256.4
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
If the log files are empty, then the crash wasn't in TCMD (or TCC) code. It either happened in a Windows DLL that had its own exception handler, or a third-party app that injected itself into TCMD (or TCC).
If the log files are empty, then the crash wasn't in TCMD (or TCC) code. It either happened in a Windows DLL that had its own exception handler, or a third-party app that injected itself into TCMD (or TCC).
And if 19.00.22 works and 19.00.23 doesn't work, what changed? My system didn't change, sure the error may be coming from a Windows DLL or injected code (why doesn't it inject itself into 19.00.22 and cause a crash) but the only thing that could of changed is how they were called from TCMD.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.