Still having problems with TCMD randomly closing or crashing

[evensenm]

Various times I find that Take Command is no longer running when I never closed it, as if something crashed it. I haven't noticed any error logs (although I haven't checked Windows Event Viewer yet). My tabs are still open, now as console windows, but are hidden. I have to restart TCMD and then reattach those tabs to bring them back as tabbed windows in TCMD.

This all seemed to start when I got a new laptop running Windows 11 (Pro) Even prior versions of TCMD that never had this problem on my previous laptop (running Windows 10 Pro) started having this problem once I installed and started using on my new laptop. This is becoming a mystery to me.

TCC version.....

TCC 30.00.22 x64 Windows 11 [Version 10.0.22621.1848]
TCC Build 22 Windows 11 Build 22621
Registered to MARK7-WIN11

Mark E.

 

[evensenm]

Here are 2 application "error" events related to TCMD that I found in Windows Event Viewer. Hope someone can make sense of it.

Log Name: Application
Source: Application Error
Date: 7/13/2023 12:18:53 PM
Event ID: 1000
Task Category: Application Crashing Events
Level: Error
Keywords:
User: MARK7-WIN11\evens
Computer: MARK7-WIN11
Description:
Faulting application name: tcmd.exe, version: 30.0.22.0, time stamp: 0x649064cd
Faulting module name: tcmd.exe, version: 30.0.22.0, time stamp: 0x649064cd
Exception code: 0xc0000005
Fault offset: 0x0000000000035e54
Faulting process id: 0x0x4FD4
Faulting application start time: 0x0x1D9B5BD241F17CB
Faulting application path: C:\Program Files\JPSoft\TCMD30\tcmd.exe
Faulting module path: C:\Program Files\JPSoft\TCMD30\tcmd.exe
Report Id: 925fe8ea-9349-46df-a747-ca7ce5d7f683
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" />
<EventID>1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2023-07-13T19:18:53.9551642Z" />
<EventRecordID>62111</EventRecordID>
<Correlation />
<Execution ProcessID="29528" ThreadID="29532" />
<Channel>Application</Channel>
<Computer>MARK7-WIN11</Computer>
<Security UserID="S-1-5-21-241125996-2894727637-1114843912-1003" />
</System>
<EventData>
<Data Name="AppName">tcmd.exe</Data>
<Data Name="AppVersion">30.0.22.0</Data>
<Data Name="AppTimeStamp">649064cd</Data>
<Data Name="ModuleName">tcmd.exe</Data>
<Data Name="ModuleVersion">30.0.22.0</Data>
<Data Name="ModuleTimeStamp">649064cd</Data>
<Data Name="ExceptionCode">c0000005</Data>
<Data Name="FaultingOffset">0000000000035e54</Data>
<Data Name="ProcessId">0x4fd4</Data>
<Data Name="ProcessCreationTime">0x1d9b5bd241f17cb</Data>
<Data Name="AppPath">C:\Program Files\JPSoft\TCMD30\tcmd.exe</Data>
<Data Name="ModulePath">C:\Program Files\JPSoft\TCMD30\tcmd.exe</Data>
<Data Name="IntegratorReportId">925fe8ea-9349-46df-a747-ca7ce5d7f683</Data>
<Data Name="PackageFullName">
</Data>
<Data Name="PackageRelativeAppId">
</Data>
</EventData>
</Event>



Log Name: Application
Source: Application Error
Date: 7/13/2023 12:18:55 PM
Event ID: 1000
Task Category: Application Crashing Events
Level: Error
Keywords:
User: MARK7-WIN11\evens
Computer: MARK7-WIN11
Description:
Faulting application name: tcmd.exe, version: 30.0.22.0, time stamp: 0x649064cd
Faulting module name: tcmd.exe, version: 30.0.22.0, time stamp: 0x649064cd
Exception code: 0xc000041d
Fault offset: 0x0000000000035e54
Faulting process id: 0x0x4FD4
Faulting application start time: 0x0x1D9B5BD241F17CB
Faulting application path: C:\Program Files\JPSoft\TCMD30\tcmd.exe
Faulting module path: C:\Program Files\JPSoft\TCMD30\tcmd.exe
Report Id: e85dc402-b6cf-4e60-a2a8-538844856a7c
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" />
<EventID>1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2023-07-13T19:18:55.6323817Z" />
<EventRecordID>62112</EventRecordID>
<Correlation />
<Execution ProcessID="28768" ThreadID="5844" />
<Channel>Application</Channel>
<Computer>MARK7-WIN11</Computer>
<Security UserID="S-1-5-21-241125996-2894727637-1114843912-1003" />
</System>
<EventData>
<Data Name="AppName">tcmd.exe</Data>
<Data Name="AppVersion">30.0.22.0</Data>
<Data Name="AppTimeStamp">649064cd</Data>
<Data Name="ModuleName">tcmd.exe</Data>
<Data Name="ModuleVersion">30.0.22.0</Data>
<Data Name="ModuleTimeStamp">649064cd</Data>
<Data Name="ExceptionCode">c000041d</Data>
<Data Name="FaultingOffset">0000000000035e54</Data>
<Data Name="ProcessId">0x4fd4</Data>
<Data Name="ProcessCreationTime">0x1d9b5bd241f17cb</Data>
<Data Name="AppPath">C:\Program Files\JPSoft\TCMD30\tcmd.exe</Data>
<Data Name="ModulePath">C:\Program Files\JPSoft\TCMD30\tcmd.exe</Data>
<Data Name="IntegratorReportId">e85dc402-b6cf-4e60-a2a8-538844856a7c</Data>
<Data Name="PackageFullName">
</Data>
<Data Name="PackageRelativeAppId">
</Data>
</EventData>
</Event>




Mark E.

 

[rconn]

Not reproducible here.

That crash is in a Windows API (when Take Command is passing on Windows messages to other apps / dll's that have registered for it).

Are you running any new third-party apps that are hooking or injecting code (i.e., AV's, screen managers, etc.)?