TC has crashed

simon.m · Post by *simon.m » 2017-05-10, 18:14 UTC

Hello. After many years of using your great program it's first time that TC has crashed. It happened a few times in last week or so. It happened again a minutes ago and I clicked to debug in Visual Studio and only information I was able to get was this message that I guess it comes from TCM.

========
The following error was encountered: TF400813: Resource not available for anonymous access. Client authentication required.
========

I had connection to NAS and FTP active, program was minimized. I'm using windows 10 with latests updates.

simon.m · Post by *simon.m » 2017-05-10, 18:15 UTC

PS: for some reason I was able to enter my email as username. Could someone please just change it to to something else as option is disabled.

gdpr deleted 6 · Post by *gdpr deleted 6 » 2017-05-11, 09:32 UTC

FYI: the error message you have given here has nothing to do with Total Commander. It is an error message from Visual Studio Team Services (VSTS), telling you that VSTS (or some other part of VS) has some problem accessing a resource (just take a little time googling for the error code, if you want to know more details about this error)

Post by *ghisler(Author) » 2017-05-11, 09:35 UTC

OK, I have changed your user name to "simon.m".

I need some kind of stack trace. Could you use the tool Procdump to create one for me, please:
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 Alt+Shift+F5, e.g. procdump.lnk
3. Change 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.
8. Send me the dump from c:\dumps.

simon.m · Post by *simon.m » 2017-05-11, 15:59 UTC

Thank you. I ran the command and waiting for crash to happen. Hope it won't go murphy now

simon.m · Post by *simon.m » 2017-05-12, 11:45 UTC

Hi, it crashed now and file is 172MB big. It happened when I opened and pressed play on Google Play Music in google chrome

How can I send you this file?

gdpr deleted 6 · Post by *gdpr deleted 6 » 2017-05-12, 17:43 UTC

simon.m wrote:Hi, it crashed now and file is 172MB big. It happened when I opened and pressed play on Google Play Music in google chrome How can I send you this file?

I don't think Christian is interested in crash dumps of the Chrome webbrowser -- why should he, he isn't working for Google

(Or did i misunderstand your post...?)

simon.m · Post by *simon.m » 2017-05-12, 20:06 UTC

Yes, you missunderstood a bit. TCM crashed and it happened at the time when I opened opened https://play.google.com/music/listen and pressed play, if that would help him to investigate. Dump is TCM related.

MVV · Post by *MVV » 2017-05-12, 20:18 UTC

I can't imagine that file manager can crash when you do something in a web browser... Maybe you have some specific TC plugin installed?

simon.m · Post by *simon.m » 2017-05-12, 21:25 UTC

I understand. I don't have any plugin installed.

simon.m · Post by *simon.m » 2017-05-15, 09:34 UTC

Hi, it crashed again. This time I was connected to NAS on wifi network, enabled wired connection and disabled wifi network.
Dump is again 330MB in size.

Post by *ghisler(Author) » 2017-05-15, 14:01 UTC

It would be best if you could analyze the file yourself with windbg. It's easy:
1. Get windbg from here:
https://developer.microsoft.com/en-us/windows/hardware/download-windbg
2. Create new folder c:\Symbols
3. Run windbg.exe
4. Open menu File - Symbol file path
5. Set it to:
srv*C:\SYMBOLS*http://msdl.microsoft.com/download/symbols
6. Open menu File - Open crash dump
7. Pick the crash dump
8. In the command line at the bottom, write:
!analyze -v
including the ! at the start, and press ENTER

It will take a while initially to download all the symbol files to c:\Symbols. Once the result is there, select it all and copy+paste it to the forum.

Otherwise I can analyze it for you if you put the file in a dropbox or onedrive account or so and share the link with me. I just need one crash dump.

simon.m · Post by *simon.m » 2017-05-25, 20:09 UTC

Hi

I've collected 8 .dmp files now and here is analyze of one of them (337MB in size)

Does that help?

Code: Select all

Microsoft (R) Windows Debugger Version 10.0.15063.400 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\dumps\TOTALCMD64.EXE_170515_113245.dmp]
User Mini Dump File with Full Memory: Only application data is available

Comment: '
*** "D:\dumps\procdump.exe" -accepteula -ma -j "d:\dumps" 816 344 0000000001DB0000
*** Just-In-Time debugger. PID: 816 Event Handle: 344 JIT Context: .jdinfo 0x1db0000'
Symbol search path is: srv*
Executable search path is: 
Windows 10 Version 15063 MP (4 procs) Free x64
Product: WinNt, suite: SingleUserTS
15063.0.amd64fre.rs2_release.170317-1834
Machine Name:
Debug session time: Mon May 15 11:32:47.000 2017 (UTC + 2:00)
System Uptime: 3 days 13:07:12.122
Process Uptime: 2 days 21:49:09.000
................................................................
................................................................
....................................
Loading unloaded module list
................................................................
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(330.41c): Unknown exception - code e0435555 (first/second chance not available)
KERNELBASE!RaiseFailFastException+0x74:
00007ff9`776dfe24 803d5780190000  cmp     byte ptr [KERNELBASE!BasepIsSecureProcess (00007ff9`77877e82)],0 ds:00007ff9`77877e82=00
0:013> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

*** WARNING: Unable to verify timestamp for TOTALCMD64.EXE
*** ERROR: Module load completed but symbols could not be loaded for TOTALCMD64.EXE

DUMP_CLASS: 2

DUMP_QUALIFIER: 400

CONTEXT:  (.ecxr)
rax=0000000044e4ea40 rbx=0000000044e4efb0 rcx=0000000044e4ea40
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000044e4ea40
rip=00007ff9776dfe24 rsp=0000000044e4e960 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000006 r10=0000000000000000
r11=00007ff97a6cbf17 r12=000000000b57d0e8 r13=0000000003cdfbb0
r14=0000000003b04740 r15=0000000003ad99d0
iopl=0         nv up ei pl zr na po nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000244
KERNELBASE!RaiseFailFastException+0x74:
00007ff9`776dfe24 803d5780190000  cmp     byte ptr [KERNELBASE!BasepIsSecureProcess (00007ff9`77877e82)],0 ds:00007ff9`77877e82=00
Resetting default scope

FAULTING_IP: 
uiautomationcore.dll!Unloaded+103e28
00007ff9`4aa43e28 ??              ???

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 00007ff94aa43e28 (<Unloaded_uiautomationcore.dll>+0x0000000000103e28)
   ExceptionCode: e0435555
  ExceptionFlags: 00000001
NumberParameters: 0

DEFAULT_BUCKET_ID:  APPLICATION_FAULT

PROCESS_NAME:  TOTALCMD64.EXE

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

EXCEPTION_CODE: (NTSTATUS) 0xe0435555 - <Unable to get error code text>

EXCEPTION_CODE_STR:  e0435555

WATSON_BKT_PROCSTAMP:  0

WATSON_BKT_PROCVER:  9.0.1.0

PROCESS_VER_PRODUCT:  Total Commander

WATSON_BKT_MODULE:  unknown

WATSON_BKT_MODVER:  0.0.0.0

WATSON_BKT_MODOFFSET:  4aa43e28

BUILD_VERSION_STRING:  10.0.15063.296 (WinBuild.160101.0800)

MODLIST_WITH_TSCHKSUM_HASH:  9dd721ed1a3092b40c08057d4b4e23fa82b887f9

MODLIST_SHA1_HASH:  3bbc9a95107e28acc63bf6787361f0a6069506a6

NTGLOBALFLAG:  0

PROCESS_BAM_CURRENT_THROTTLED: 0

PROCESS_BAM_PREVIOUS_THROTTLED: 0

APPLICATION_VERIFIER_FLAGS:  0

PRODUCT_TYPE:  1

SUITE_MASK:  272

DUMP_FLAGS:  8000c07

DUMP_TYPE:  3

ANALYSIS_SESSION_HOST:  MMX-TP

ANALYSIS_SESSION_TIME:  05-25-2017 22:06:32.0187

ANALYSIS_VERSION: 10.0.15063.400 amd64fre

LAST_CONTROL_TRANSFER:  from 00007ff971d03a06 to 00007ff9776dfe24

THREAD_ATTRIBUTES: 
FAULTING_THREAD:  ffffffff

THREAD_SHA1_HASH_MOD_FUNC:  073924d75c1270084ebedce2205fff88cea45e08

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  f5ca82de5c674344bedaf80f3eff98a37d46cf40

OS_LOCALE:  ENG

PROBLEM_CLASSES: 

    ID:     [0n299]
    Type:   [APPLICATION_FAULT]
    Class:  Primary
    Scope:  DEFAULT_BUCKET_ID (Failure Bucket ID prefix)
            BUCKET_ID
    Name:   Add
    Data:   Omit
    PID:    [Unspecified]
    TID:    [Unspecified]
    Frame:  [0]

BUGCHECK_STR:  APPLICATION_FAULT

PRIMARY_PROBLEM_CLASS:  APPLICATION_FAULT

STACK_TEXT:  
00000000`44e4e960 00007ff9`776dfe24 KERNELBASE!RaiseFailFastException+0x74
00000000`44e4ef30 00007ff9`71d03a06 CoreUIComponents!Cn::FailFast::Do+0x82
00000000`44e4ef60 00007ff9`71d03983 CoreUIComponents!Cn::FailFast::Do+0xb
00000000`44e4ef90 00007ff9`71c78bd7 CoreUIComponents!CoreUIHost::OnInvalidCallback+0x47
00000000`44e4f070 00007ff9`71c31b9a CoreUIComponents!Cn::Com::NativeExit::Validate+0x3a
00000000`44e4f0a0 00007ff9`71c372f2 CoreUIComponents!Microsoft::CoreUI::ICallbackMessageListListener$X__CallbackAdapter::OnAdded+0x52
00000000`44e4f190 00007ff9`71c3d4d1 CoreUIComponents!Microsoft::CoreUI::Proxy::MessageProxyList::IRemoteMessageListListener__OnInsert+0x211
00000000`44e4f1e0 00007ff9`71c28be9 CoreUIComponents!Microsoft::CoreUI::Proxy::MessageProxy::Callback_OnMessage+0x3f9
00000000`44e4f590 00007ff9`71c4267f CoreUIComponents!Microsoft::CoreUI::MessagingInterop::MessageEndpoint$R::Delegate1+0x2f
00000000`44e4f5d0 00007ff9`71c2186a CoreUIComponents!Microsoft__CoreUI__MessagingInterop__EndpointHandler$ExportThunk+0x7a
00000000`44e4f680 00007ff9`7494c223 CoreMessaging!Microsoft__CoreUI__ExportEndpointHandler$CallbackThunk+0x1e3
00000000`44e4f710 00007ff9`74968f19 CoreMessaging!Microsoft::CoreUI::ExternalEndpoint::Callback_OnMessageCore+0x39
00000000`44e4f740 00007ff9`7496359e CoreMessaging!Microsoft::CoreUI::Messaging::MessageSession::Callback_DeliverMessage+0x1ae
00000000`44e4f800 00007ff9`749638c9 CoreMessaging!Microsoft::CoreUI::Messaging::MessageSession::Callback_DeliverMessageBatch+0xf9
00000000`44e4f8a0 00007ff9`7495fab1 CoreMessaging!Microsoft::CoreUI::Messaging::AlpcClientSender::Callback_ProcessBuffer+0x141
00000000`44e4f950 00007ff9`7495cdf4 CoreMessaging!Microsoft::CoreUI::Messaging::AlpcClientThunk::Callback_ProcessAsynchronousBuffer+0x24
00000000`44e4f990 00007ff9`7497a3dc CoreMessaging!AlpcConnection::Callback_DeliverBatchedBuffers+0x8c
00000000`44e4fa40 00007ff9`7497a99a CoreMessaging!AlpcConnection::Callback_HandleReceivedBuffer+0x18a
00000000`44e4faf0 00007ff9`7497aea6 CoreMessaging!AlpcConnection::Callback_ProcessIncoming+0x1a6
00000000`44e4fbb0 00007ff9`7495edae CoreMessaging!Microsoft::CoreUI::Messaging::AlpcClientSender$R::Delegate1+0x5e
00000000`44e4fc10 00007ff9`749606fb CoreMessaging!Microsoft::CoreUI::Dispatch::OffThreadReceiver::Callback_OnDispatch+0x18b
00000000`44e4fc80 00007ff9`749548a1 CoreMessaging!Microsoft::CoreUI::Dispatch::Dispatcher::Callback_DispatchLoop+0x251
00000000`44e4fd10 00007ff9`7495314e CoreMessaging!Microsoft::CoreUI::Dispatch::EventLoop::Callback_RunCoreLoop+0x3ce
00000000`44e4fde0 00007ff9`74953838 CoreMessaging!Microsoft::CoreUI::Dispatch::EventLoop::Callback_Run+0x9c
00000000`44e4fe50 00007ff9`749495b5 CoreMessaging!Microsoft::CoreUI::Messaging::MessageSession$R::Microsoft__CoreUI__IExportMessageSession_Impl::Run+0x35
00000000`44e4fe90 00007ff9`7495ab9b CoreMessaging!Microsoft::CoreUI::IExportMessageSession$X__ExportAdapter::Run+0x4b
00000000`44e4ff30 00007ff9`4a99bf7e uiautomationcore.dll!Unloaded+0x5bf7e
00000000`44e4ff38 00000000`0b586030 unknown!unknown+0x0
00000000`44e4ff40 00000000`0b569350 unknown!unknown+0x0
00000000`44e4ff48 00000000`0b57d0d0 unknown!unknown+0x0


STACK_COMMAND:  .ecxr ; kb ; dps 44e4e960 ; kb

THREAD_SHA1_HASH_MOD:  f349956d267c167ce27fec4aa9a76cdd51f12c81

FOLLOWUP_IP: 
CoreUIComponents!Cn::FailFast::Do+82
00007ff9`71d03a06 8324250000000000 and     dword ptr [0],0

FAULT_INSTR_CODE:  252483

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  CoreUIComponents!Cn::FailFast::Do+82

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: CoreUIComponents

IMAGE_NAME:  CoreUIComponents.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  3a99b3e0

BUCKET_ID:  APPLICATION_FAULT_CoreUIComponents!Cn::FailFast::Do+82

FAILURE_EXCEPTION_CODE:  e0435555

FAILURE_IMAGE_NAME:  CoreUIComponents.dll

BUCKET_ID_IMAGE_STR:  CoreUIComponents.dll

FAILURE_MODULE_NAME:  CoreUIComponents

BUCKET_ID_MODULE_STR:  CoreUIComponents

FAILURE_FUNCTION_NAME:  Cn::FailFast::Do

BUCKET_ID_FUNCTION_STR:  Cn::FailFast::Do

BUCKET_ID_OFFSET:  82

BUCKET_ID_MODTIMEDATESTAMP:  3a99b3e0

BUCKET_ID_MODCHECKSUM:  2de269

BUCKET_ID_MODVER_STR:  6.2.15063.296

BUCKET_ID_PREFIX_STR:  APPLICATION_FAULT_

FAILURE_PROBLEM_CLASS:  APPLICATION_FAULT

FAILURE_SYMBOL_NAME:  CoreUIComponents.dll!Cn::FailFast::Do

FAILURE_BUCKET_ID:  APPLICATION_FAULT_e0435555_CoreUIComponents.dll!Cn::FailFast::Do

TARGET_TIME:  2017-05-15T09:32:47.000Z

OSBUILD:  15063

OSSERVICEPACK:  296

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt SingleUserTS

USER_LCID:  0

OSBUILD_TIMESTAMP:  unknown_date

BUILDDATESTAMP_STR:  160101.0800

BUILDLAB_STR:  WinBuild

BUILDOSVER_STR:  10.0.15063.296

ANALYSIS_SESSION_ELAPSED_TIME:  ffa

ANALYSIS_SOURCE:  UM

FAILURE_ID_HASH_STRING:  um:application_fault_e0435555_coreuicomponents.dll!cn::failfast::do

FAILURE_ID_HASH:  {c5e82f46-f86c-49f9-7cd2-9239a9fe6280}

Followup:     MachineOwner
---------

Post by *ghisler(Author) » 2017-05-29, 14:17 UTC

Thanks for the dump. TOTALCMD64 doesn't even appear on the stack - the error seems to occur within uiautomationcore.dll.

Do you use a scripting tool to automate TC? If yes, which one?

I found a hotfix from Microsoft, but it's only for Windows 7 and 8:
https://support.microsoft.com/en-us/help/3005770/applications-crash-when-automated-by-a-ui-automation-client-app-in-windows

Post by *ghisler(Author) » 2017-09-25, 14:24 UTC

This is apparently the same bug as described here:
viewtopic.php?t=47959

So can anyone test the fix in TC 9.10 beta, please?