Application Error - 1000 TCMD30 WIndows 10

[Tom_SC]

This is the first version that has crashed on me. I do not have a crashlog in the programdata folder structure. All I see are these from Event Manager. I
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2023-06-06T14:13:23.4996370Z" />
<EventRecordID>780170</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>hiddenname</Computer>
<Security />
</System>
- <EventData>
<Data>tcmd.exe</Data>
<Data>30.0.18.0</Data>
<Data>646aa1b6</Data>
<Data>clr.dll</Data>
<Data>4.8.4614.0</Data>
<Data>63995bc5</Data>
<Data>80131506</Data>
<Data>000000000040050f</Data>
<Data>4f0c</Data>
<Data>01d9988103e2ba01</Data>
<Data>C:\Program Files\JPSoft\TCMD30\tcmd.exe</Data>
<Data>C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll</Data>
<Data>db3ef0d5-cb84-46c4-afb4-ec83eeacf5f0</Data>
<Data />
<Data />
</EventData>
</Event>

I do have windbg and see this when I look at the dbg file:

STACK_COMMAND: .ecxr ; kb ; ** Pseudo Context ** Pseudo ** Value: 1d ** ; kb

SYMBOL_NAME: clr!EEPolicy::HandleFatalError+79

MODULE_NAME: clr

IMAGE_NAME: clr.dll

FAILURE_BUCKET_ID: CLR_INTERNAL_ERROR_80131506_clr.dll!EEPolicy::HandleFatalError

BUCKET_ID_MODPRIVATE: 1

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

IMAGE_VERSION: 4.8.4614.0

FAILURE_ID_HASH: {449759d7-fc07-585f-23ff-be54379d60eb}

 

[Tom_SC]

Here is the exception record:

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ff8518b050f (clr!UnsafeJitFunction+0x00000000002464df)
ExceptionCode: 80131506
ExceptionFlags: 00000001
NumberParameters: 0

PROCESS_NAME: tcmd.exe

ERROR_CODE: (NTSTATUS) 0x80131506 - <Unable to get error code text>

EXCEPTION_CODE_STR: 80131506

FAULTING_THREAD: ffffffff

 

[rconn]

It's crashing at an address and in a dll (C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll) that isn't part of TCMD.

Somebody else is injecting clr.dll into TCMD. The usual suspects for that behavior are AV's and screen managers.

 

[Tom_SC]

In tcmd.exe.20236.dmp the assembly instruction at clr!UnsafeJitFunction+2464df in C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll from Microsoft Corporation has caused an unknown exception (0x80131506) on thread 13 So basically you are saying not your problem? These are not the droids you are looking for, move along?

 

[Tom_SC]

CLR (common language runtime) . So your application does not use .NET, is that what you are saying?

 

[rconn]

TCMD does not use .NET. It's native C++ code, with a dab of assembly.

 

[ohenryx]

TCMD does not use .NET. It's native C++ code, with a dab of assembly.

And a big thumbs up for that!