Total Commander

Posted: **2021-02-14, 16:14 UTC**

Several times in the last few days I had crashes of TC on starting.
Next start-up is then ok.
Here some Windows error report example:

Code: Select all

Version=1
EventType=CLR20r3
EventTime=132577924927270736
ReportType=2
Consent=1
UploadTime=132577924929718204
ReportStatus=268435456
ReportIdentifier=8b4cd309-d99f-4dd7-9d22-8bddae9a53a8
IntegratorReportIdentifier=8700e77e-2670-4896-91bf-01a1cc59f899
Wow64Host=34404
NsAppName=totalcmd64.exe
OriginalFilename=totalcmd64.exe
AppSessionGuid=00004118-0003-0057-3b55-3297eb02d701
TargetAppId=W:000684be359d11a81312c3029212c38e92d200000904!00004daf8aa0294c9a1fad479757cdf7ac2cfbec0588!totalcmd64.exe
TargetAppVer=1970//01//01:00:00:00!8dbe55!totalcmd64.exe
BootId=4294967295
TargetAsId=3919
UserImpactVector=808452912
IsFatal=1
EtwNonCollectReason=1
Response.BucketId=a955bb2b6a93e211185377555974a824
Response.BucketTable=5
Response.LegacyBucketId=1752875888433997860
Response.type=4
Sig[0].Name=Problem Signature 01
Sig[0].Value=totalcmd64.exe
Sig[1].Name=Problem Signature 02
Sig[1].Value=9.5.1.0
Sig[2].Name=Problem Signature 03
Sig[2].Value=0
Sig[3].Name=Problem Signature 04
Sig[3].Value=mscorlib
Sig[4].Name=Problem Signature 05
Sig[4].Value=4.8.4300.0
Sig[5].Name=Problem Signature 06
Sig[5].Value=5f7e60da
Sig[6].Name=Problem Signature 07
Sig[6].Value=f21
Sig[7].Name=Problem Signature 08
Sig[7].Value=60
Sig[8].Name=Problem Signature 09
Sig[8].Value=System.AccessViolationException
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.19042.2.0.0.768.101
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=8192
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=941b
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=941bad0d8a599e876fc99a9ec7e1728d
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=84cf
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=84cf66820d4cc4131ed9c307acf07ebf
UI[2]=C:\Tools\Wincmd\totalcmd64.exe
LoadedModule[0]=C:\Tools\Wincmd\totalcmd64.exe
LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\WINDOWS\System32\KERNEL32.DLL
LoadedModule[3]=C:\WINDOWS\System32\KERNELBASE.dll
LoadedModule[4]=C:\WINDOWS\System32\advapi32.dll
LoadedModule[5]=C:\WINDOWS\System32\msvcrt.dll
LoadedModule[6]=C:\WINDOWS\System32\sechost.dll
LoadedModule[7]=C:\WINDOWS\System32\RPCRT4.dll
LoadedModule[8]=C:\WINDOWS\System32\comdlg32.dll
LoadedModule[9]=C:\WINDOWS\System32\combase.dll
LoadedModule[10]=C:\WINDOWS\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.19041.746_none_ca02b4b61b8320a4\comctl32.dll
LoadedModule[11]=C:\WINDOWS\System32\ucrtbase.dll
LoadedModule[12]=C:\WINDOWS\System32\GDI32.dll
LoadedModule[13]=C:\WINDOWS\System32\win32u.dll
LoadedModule[14]=C:\WINDOWS\System32\shcore.dll
LoadedModule[15]=C:\WINDOWS\System32\gdi32full.dll
LoadedModule[16]=C:\WINDOWS\System32\USER32.dll
LoadedModule[17]=C:\WINDOWS\System32\msvcp_win.dll
LoadedModule[18]=C:\WINDOWS\System32\SHLWAPI.dll
LoadedModule[19]=C:\WINDOWS\System32\SHELL32.dll
LoadedModule[20]=C:\WINDOWS\System32\ole32.dll
LoadedModule[21]=C:\WINDOWS\System32\oleaut32.dll
LoadedModule[22]=C:\WINDOWS\System32\IMM32.DLL
LoadedModule[23]=C:\WINDOWS\system32\uxtheme.dll
LoadedModule[24]=C:\WINDOWS\system32\winsta.dll
LoadedModule[25]=C:\WINDOWS\system32\sspicli.dll
LoadedModule[26]=C:\WINDOWS\system32\version.dll
LoadedModule[27]=C:\WINDOWS\system32\winmm.dll
LoadedModule[28]=C:\WINDOWS\system32\mpr.dll
LoadedModule[29]=C:\WINDOWS\system32\dwmapi.DLL
LoadedModule[30]=C:\WINDOWS\SYSTEM32\msimg32.dll
LoadedModule[31]=C:\WINDOWS\system32\winspool.drv
LoadedModule[32]=C:\WINDOWS\SYSTEM32\kernel.appcore.dll
LoadedModule[33]=C:\WINDOWS\System32\bcryptPrimitives.dll
LoadedModule[34]=C:\Program Files (x86)\1&1\1&1 Upload-Manager\SHNDLERS64.DLL
LoadedModule[35]=C:\WINDOWS\SYSTEM32\ntmarta.dll
LoadedModule[36]=C:\WINDOWS\SYSTEM32\windows.storage.dll
LoadedModule[37]=C:\WINDOWS\SYSTEM32\Wldp.dll
LoadedModule[38]=C:\WINDOWS\SYSTEM32\WindowsCodecs.dll
LoadedModule[39]=C:\WINDOWS\System32\bcrypt.dll
LoadedModule[40]=C:\WINDOWS\SYSTEM32\profapi.dll
LoadedModule[41]=C:\WINDOWS\SYSTEM32\PROPSYS.dll
LoadedModule[42]=C:\WINDOWS\System32\clbcatq.dll
LoadedModule[43]=C:\WINDOWS\System32\MSCTF.dll
LoadedModule[44]=C:\WINDOWS\SYSTEM32\Uiautomationcore.dll
LoadedModule[45]=C:\WINDOWS\SYSTEM32\TextShaping.dll
LoadedModule[46]=C:\Tools\Wincmd\PLUGINS\Autorun\autorun.wdx64
LoadedModule[47]=c:\Tools\Wincmd\PLUGINS\TCFS2\TCFS2Tools.dll64
LoadedModule[48]=C:\Tools\Wincmd\PLUGINS\TWinKey\TWinKey.wdx64
LoadedModule[49]=C:\WINDOWS\System32\SETUPAPI.dll
LoadedModule[50]=C:\WINDOWS\System32\cfgmgr32.dll
LoadedModule[51]=C:\WINDOWS\SYSTEM32\NETAPI32.dll
LoadedModule[52]=C:\WINDOWS\SYSTEM32\NETUTILS.DLL
LoadedModule[53]=C:\WINDOWS\SYSTEM32\WKSCLI.DLL
LoadedModule[54]=C:\WINDOWS\system32\wtsapi32.dll
LoadedModule[55]=C:\WINDOWS\system32\dataexchange.dll
LoadedModule[56]=C:\WINDOWS\system32\d3d11.dll
LoadedModule[57]=C:\WINDOWS\system32\dcomp.dll
LoadedModule[58]=C:\WINDOWS\system32\dxgi.dll
LoadedModule[59]=C:\WINDOWS\system32\twinapi.appcore.dll
LoadedModule[60]=C:\WINDOWS\SYSTEM32\mscms.dll
LoadedModule[61]=C:\WINDOWS\SYSTEM32\USERENV.dll
LoadedModule[62]=C:\WINDOWS\SYSTEM32\ColorAdapterClient.dll
LoadedModule[63]=C:\WINDOWS\System32\ui11np.dll
LoadedModule[64]=C:\WINDOWS\System32\drprov.dll
LoadedModule[65]=C:\WINDOWS\System32\ntlanman.dll
LoadedModule[66]=C:\WINDOWS\System32\davclnt.dll
LoadedModule[67]=C:\WINDOWS\System32\DAVHLPR.dll
LoadedModule[68]=C:\WINDOWS\SYSTEM32\cscapi.dll
LoadedModule[69]=C:\WINDOWS\System32\coml2.dll
LoadedModule[70]=C:\WINDOWS\SYSTEM32\apphelp.dll
LoadedModule[71]=C:\Windows\System32\dlnashext.dll
LoadedModule[72]=C:\Windows\System32\PlayToDevice.dll
LoadedModule[73]=C:\Windows\System32\DevDispItemProvider.dll
LoadedModule[74]=C:\WINDOWS\System32\MMDevApi.dll
LoadedModule[75]=C:\WINDOWS\System32\DEVOBJ.dll
LoadedModule[76]=C:\Windows\System32\PortableDeviceApi.dll
LoadedModule[77]=C:\WINDOWS\System32\WINTRUST.dll
LoadedModule[78]=C:\WINDOWS\System32\CRYPT32.dll
LoadedModule[79]=C:\WINDOWS\SYSTEM32\MSASN1.dll
LoadedModule[80]=C:\Windows\System32\EhStorAPI.dll
LoadedModule[81]=C:\WINDOWS\SYSTEM32\textinputframework.dll
LoadedModule[82]=C:\WINDOWS\System32\CoreUIComponents.dll
LoadedModule[83]=C:\WINDOWS\System32\CoreMessaging.dll
LoadedModule[84]=C:\WINDOWS\System32\WS2_32.dll
LoadedModule[85]=C:\WINDOWS\SYSTEM32\wintypes.dll
LoadedModule[86]=C:\Program Files\Listary\Hooks\ListaryHook64-6.1.8.0.dll
LoadedModule[87]=C:\WINDOWS\SYSTEM32\OLEACC.dll
LoadedModule[88]=C:\Program Files\Common Files\microsoft shared\ink\tiptsf.dll
LoadedModule[89]=C:\WINDOWS\system32\USP10.DLL
LoadedModule[90]=C:\Windows\System32\thumbcache.dll
LoadedModule[91]=C:\Windows\System32\Windows.FileExplorer.Common.dll
LoadedModule[92]=C:\Windows\System32\iertutil.dll
LoadedModule[93]=C:\WINDOWS\SYSTEM32\mscoree.dll
LoadedModule[94]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll
LoadedModule[95]=C:\WINDOWS\SYSTEM32\sxs.dll
LoadedModule[96]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
LoadedModule[97]=C:\WINDOWS\SYSTEM32\VCRUNTIME140_CLR0400.dll
LoadedModule[98]=C:\WINDOWS\SYSTEM32\ucrtbase_clr0400.dll
LoadedModule[99]=C:\WINDOWS\System32\psapi.dll
LoadedModule[100]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\mscorlib\ed4777cae83e1fc9087ac3dc82cf23ab\mscorlib.ni.dll
LoadedModule[101]=C:\WINDOWS\SYSTEM32\CRYPTSP.dll
LoadedModule[102]=C:\WINDOWS\system32\rsaenh.dll
LoadedModule[103]=C:\WINDOWS\SYSTEM32\CRYPTBASE.dll
LoadedModule[104]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System\5dd302cc18514670950e7f3fbebddb06\System.ni.dll
LoadedModule[105]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Drawing\f4b470d059025978bbe597afc6e60f7d\System.Drawing.ni.dll
LoadedModule[106]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clrjit.dll
LoadedModule[107]=C:\WINDOWS\System32\DriverStore\FileRepository\iastorpinningcomponent.inf_amd64_a41f71ab3b5175b6\iaStorAfsServiceApi.dll
LoadedModule[108]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Core\5b420a81d9bf78ed0945d8ac1ca932b4\System.Core.ni.dll
LoadedModule[109]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Configuration\43245d36d271e5e3abf3742885086b10\System.Configuration.ni.dll
LoadedModule[110]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Xml\131a023309990432765d7a97ec31d6a7\System.Xml.ni.dll
LoadedModule[111]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Compba577418#\a9770f77715f4b63f8a7d7b2bb219eee\System.ComponentModel.Composition.ni.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
OsInfo[0].Key=vermaj
OsInfo[0].Value=10
OsInfo[1].Key=vermin
OsInfo[1].Value=0
OsInfo[2].Key=verbld
OsInfo[2].Value=19042
OsInfo[3].Key=ubr
OsInfo[3].Value=804
OsInfo[4].Key=versp
OsInfo[4].Value=0
OsInfo[5].Key=arch
OsInfo[5].Value=9
OsInfo[6].Key=lcid
OsInfo[6].Value=1033
OsInfo[7].Key=geoid
OsInfo[7].Value=94
OsInfo[8].Key=sku
OsInfo[8].Value=101
OsInfo[9].Key=domain
OsInfo[9].Value=0
OsInfo[10].Key=prodsuite
OsInfo[10].Value=768
OsInfo[11].Key=ntprodtype
OsInfo[11].Value=1
OsInfo[12].Key=platid
OsInfo[12].Value=10
OsInfo[13].Key=sr
OsInfo[13].Value=0
OsInfo[14].Key=tmsi
OsInfo[14].Value=220960520
OsInfo[15].Key=osinsty
OsInfo[15].Value=1
OsInfo[16].Key=iever
OsInfo[16].Value=11.789.19041.0-11.0.1000
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=16211
OsInfo[19].Key=svolsz
OsInfo[19].Value=220
OsInfo[20].Key=wimbt
OsInfo[20].Value=0
OsInfo[21].Key=blddt
OsInfo[21].Value=191206
OsInfo[22].Key=bldtm
OsInfo[22].Value=1406
OsInfo[23].Key=bldbrch
OsInfo[23].Value=vb_release
OsInfo[24].Key=bldchk
OsInfo[24].Value=0
OsInfo[25].Key=wpvermaj
OsInfo[25].Value=0
OsInfo[26].Key=wpvermin
OsInfo[26].Value=0
OsInfo[27].Key=wpbuildmaj
OsInfo[27].Value=0
OsInfo[28].Key=wpbuildmin
OsInfo[28].Value=0
OsInfo[29].Key=osver
OsInfo[29].Value=10.0.19041.804.amd64fre.vb_release.191206-1406
OsInfo[30].Key=buildflightid
OsInfo[30].Value=5AFFFB9B-FB87-4242-B66A-4ECEEB1CF75F.1
OsInfo[31].Key=edition
OsInfo[31].Value=Core
OsInfo[32].Key=ring
OsInfo[32].Value=Retail
OsInfo[33].Key=expid
OsInfo[34].Key=fconid
OsInfo[35].Key=containerid
OsInfo[36].Key=containertype
OsInfo[37].Key=edu
OsInfo[37].Value=0
FriendlyEventName=Stopped working
ConsentKey=CLR20r3
AppName=Total Commander
AppPath=C:\Tools\Wincmd\totalcmd64.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=3D7532CF7667823EDE7FB424CAB1FE69
MetadataHash=-894169730

Here some example from the Eventlog:

Code: Select all

Faulting module name: KERNELBASE.dll, version: 10.0.19041.804, time stamp: 0x0e9c5eae
Exception code: 0xe0434352
Fault offset: 0x000000000002d759
Faulting process id: 0x4284
Faulting application start time: 0x01d702ebfd63b247
Faulting application path: C:\Tools\Wincmd\TOTALCMD64.EXE
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 455f4943-36ee-4da6-af94-1dd6e6e1b9db
Faulting package full name: 
Faulting package-relative application ID: 

Data = TOTALCMD64.EXE
Data = 9.5.1.0
Data = 00000000
Data = KERNELBASE.dll
Data = 10.0.19041.804
Data = 0e9c5eae
Data = e0434352
Data = 000000000002d759
Data = 4284
Data = 01d702ebfd63b247
Data = C:\Tools\Wincmd\TOTALCMD64.EXE
Data = C:\WINDOWS\System32\KERNELBASE.dll
Data = 455f4943-36ee-4da6-af94-1dd6e6e1b9db

Posted: **2021-02-14, 17:12 UTC**

Looks like it crashes with "mscorlib" which is part of .NET runtime.
AFAIK TC does not use .NET runtime.
May a plugin crashed using .NET runtime?

Posted: **2021-02-14, 17:13 UTC**

Just a curious observation (unrelated to the problem; as sqa_wizard already mentioned, some .NET code is involved in causing the issue, see also the event type CLR20r3 indicating the problem originating in the .NET CLR)

The timestamp in

Code: Select all

TargetAppVer=1970//01//01:00:00:00!8dbe55!totalcmd64.exe

looks quite odd (it's the POSIX epoch time; it's neither the Windows NT epoch time nor a timestamp i would associate with anything related to totalcmd.64).

EDIT: Regarding your additional event log, the exception code 0xe0434352 is also indicating some unhandled .NET exception occuring...

Posted: **2021-02-14, 18:20 UTC**

Horst.Epp,
Not confirmed. Check your shell extensions.

Roman

Posted: **2021-02-14, 21:22 UTC**

I suggest to try with a clean wincmd.ini and/or to disable Autorun plugin since that's loaded by TC in your case.

Regards
Dalai

Posted: **2021-02-15, 08:38 UTC**

Dalai wrote: ↑2021-02-14, 21:22 UTC I suggest to try with a clean wincmd.ini and/or to disable Autorun plugin since that's loaded by TC in your case.

Regards
Dalai

I may try this but unfortunately the crash happens one in about 100 start-ups and never while I'm working with it.
So I'll live some time with the problem and see if any upcoming patch resolves it.

Posted: **2021-02-15, 09:06 UTC**

Could you try to create a stack trace? You can use the tool Procdump to create one:
https://technet.microsoft.com/en-us/sysinternals/dd996900.aspx

1. Create new directory c:\dumps
2. Create a lnk file of procdump.exe or procdump64.exe (for 64-bit Windows)
with Ctrl+Shift+F5, e.g. procdump.lnk
3. Open the properties the lnk file with Alt+Enter
4. Change the command from c:\path\procdump.exe to
c:\path\procdump.exe -ma -i c:\dumps
5. Important: Click on "Advanced" and check option "As administrator"
6. Run procdump with this link file
7. Wait until the crash occurs.
8a. Send me the dump from c:\dumps.
or
8b. Analyze the dump yourself with Windbg as described below.

To analyze the dump yourself, please get windbg from here:
https://developer.microsoft.com/en-us/windows/hardware/download-windbg

Usage:
1. Create new directory c:\Symbols
2. Run Windbg
3. File - Symbol search path, add the following:
srv*C:\SYMBOLS*http://msdl.microsoft.com/download/symbols
4. File - Open crash dump - choose the dmp file
5. Enter the following in the command line (including the ! at the start):
!analyze -v
(including the exclamation mark!) and press ENTER.
6. Wait
7. When the result is there, select all, press Ctrl+C and paste
the result to the email body.

Posted: **2021-02-15, 09:47 UTC**

ghisler(Author) wrote: ↑2021-02-15, 09:06 UTC Could you try to create a stack trace? You can use the tool Procdump to create one:
https://technet.microsoft.com/en-us/sysinternals/dd996900.aspx

1. Create new directory c:\dumps
2. Create a lnk file of procdump.exe or procdump64.exe (for 64-bit Windows)
with Ctrl+Shift+F5, e.g. procdump.lnk
3. Open the properties the lnk file with Alt+Enter
4. Change the command from c:\path\procdump.exe to
c:\path\procdump.exe -ma -i c:\dumps
5. Important: Click on "Advanced" and check option "As administrator"
6. Run procdump with this link file
7. Wait until the crash occurs.
8a. Send me the dump from c:\dumps.
or
8b. Analyze the dump yourself with Windbg as described below.

To analyze the dump yourself, please get windbg from here:
https://developer.microsoft.com/en-us/windows/hardware/download-windbg

Usage:
1. Create new directory c:\Symbols
2. Run Windbg
3. File - Symbol search path, add the following:
srv*C:\SYMBOLS*http://msdl.microsoft.com/download/symbols
4. File - Open crash dump - choose the dmp file
5. Enter the following in the command line (including the ! at the start):
!analyze -v
(including the exclamation mark!) and press ENTER.
6. Wait
7. When the result is there, select all, press Ctrl+C and paste
the result to the email body.

Ok, the tool is wating and I will try on the next crash.
To what address I should send the dump ?

Posted: **2021-02-15, 12:31 UTC**

ghisler(Author) wrote: ↑2021-02-15, 09:06 UTC Could you try to create a stack trace? You can use the tool Procdump to create one:
https://technet.microsoft.com/en-us/sysinternals/dd996900.aspx

1. Create new directory c:\dumps
2. Create a lnk file of procdump.exe or procdump64.exe (for 64-bit Windows)
with Ctrl+Shift+F5, e.g. procdump.lnk
3. Open the properties the lnk file with Alt+Enter
4. Change the command from c:\path\procdump.exe to
c:\path\procdump.exe -ma -i c:\dumps
5. Important: Click on "Advanced" and check option "As administrator"
6. Run procdump with this link file
7. Wait until the crash occurs.
8a. Send me the dump from c:\dumps.
or
8b. Analyze the dump yourself with Windbg as described below.

To analyze the dump yourself, please get windbg from here:
https://developer.microsoft.com/en-us/windows/hardware/download-windbg

Usage:
1. Create new directory c:\Symbols
2. Run Windbg
3. File - Symbol search path, add the following:
srv*C:\SYMBOLS*http://msdl.microsoft.com/download/symbols
4. File - Open crash dump - choose the dmp file
5. Enter the following in the command line (including the ! at the start):
!analyze -v
(including the exclamation mark!) and press ENTER.
6. Wait
7. When the result is there, select all, press Ctrl+C and paste
the result to the email body.

Mail with dump is send.

Posted: **2021-02-17, 18:17 UTC**

I tried Christians suggestions
and it looks like TwinKey is responsible for my crashes on TC start-up.
Since I removed it from the configuration no more crashes

Now I have to use Virtual Panel for bookmarking files

Total Commander

TC crashes on start-up

TC crashes on start-up

Re: TC crashes on start-up

Re: TC crashes on start-up

Re: TC crashes on start-up

Re: TC crashes on start-up

Re: TC crashes on start-up

Re: TC crashes on start-up

Re: TC crashes on start-up

Re: TC crashes on start-up

Re: TC crashes on start-up