Total Commander crash while I delete the fils

Please report only one bug per message!

Moderators: sheep, Hacker, Stefan2, white

fhurta@gmail.com
Junior Member
Junior Member
Posts: 3
Joined: 2020-10-26, 11:36 UTC

Re: Total Commander crash while I delete the fils

Post by *fhurta@gmail.com »

I sent it yesterday, it might have ended up in spam.. Please let me know if you have received it. Thanks!
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 40083
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Re: Total Commander crash while I delete the fils

Post by *ghisler(Author) »

Yes, I have received it a few days ago. But apparently you haven't received my reply?
Here it is as a post:

The error occurs in the following file: COM_Sensor64.dll in function DGSetupSensor.

If you google for COM_Sensor64.dll, you will find that it belongs to a tool named
"Digital Guardian".

Maybe an update of this tool would help, or uninstalling and re-installing it.

Complete report:
=============================================================================
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\dn\TOTALCMD64.EXE_201026_123213.dmp]
User Mini Dump File with Full Memory: Only application data is available

WARNING: Minidump contains unknown stream type 0x15
WARNING: Minidump contains unknown stream type 0x16
Comment: '
*** "C:\Apps\bin\procdump64.exe" -accepteula -ma -j "c:\dumps" 26172 580 0000000009290000
*** Just-In-Time debugger. PID: 26172 Event Handle: 580 JIT Context: .jdinfo 0x9290000'
Symbol search path is: srv*D:\SYMBOLS*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Version 17763 MP (8 procs) Free x64
Product: WinNt, suite: SingleUserTS
Machine Name:
Debug session time: Mon Oct 26 12:32:14.000 2020 (UTC + 1:00)
System Uptime: 0 days 18:17:16.888
Process Uptime: 0 days 0:12: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.
(663c.431c): Access violation - code c0000005 (first/second chance not available)
ffffffff`ffffdeb8 ?? ???
0:023> !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
*** ERROR: Symbol file could not be found. Defaulted to export symbols for DgApi64.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for drivefsext.dll -
Failed calling InternetOpenUrl, GLE=12029

FAULTING_IP:
+3d5ec
ffffffff`ffffdeb8 ?? ???

EXCEPTION_RECORD: ffffffffffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: ffffffffffffdeb8
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000008
Parameter[1]: ffffffffffffdeb8
Attempt to execute non-executable address ffffffffffffdeb8

PROCESS_NAME: TOTALCMD64.EXE

ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%p verwies auf Arbeitsspeicher bei 0x%p. Der Vorgang %s konnte im Arbeitsspeicher nicht durchgef hrt werden.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%p verwies auf Arbeitsspeicher bei 0x%p. Der Vorgang %s konnte im Arbeitsspeicher nicht durchgef hrt werden.

EXCEPTION_PARAMETER1: 0000000000000008

EXCEPTION_PARAMETER2: ffffffffffffdeb8

WRITE_ADDRESS: ffffffffffffdeb8

FOLLOWUP_IP:
COM_Sensor64!DGSetupSensor+3d5ec
00007ffb`5d03d92c 90 nop

FAILED_INSTRUCTION_ADDRESS:
+3d5ec
ffffffff`ffffdeb8 ?? ???

MOD_LIST: <ANALYSIS/>

NTGLOBALFLAG: 0

APPLICATION_VERIFIER_FLAGS: 0

IP_ON_HEAP: ffffffffffffdeb8
The fault address in not in any loaded module, please check your build's rebase
log at <releasedir>\bin\build_logs\timebuild\ntrebase.log for module which may
contain the address if it were loaded.

FAULTING_THREAD: 000000000000431c

BUGCHECK_STR: APPLICATION_FAULT_SOFTWARE_NX_FAULT_INVALID

PRIMARY_PROBLEM_CLASS: SOFTWARE_NX_FAULT_INVALID

DEFAULT_BUCKET_ID: SOFTWARE_NX_FAULT_INVALID

LAST_CONTROL_TRANSFER: from 00007ffb5d03d92c to ffffffffffffdeb8

STACK_TEXT:
00000000`6ba7d058 00007ffb`5d03d92c : 00000000`000036b7 00000000`00000008 00000000`00000003 00007ffb`a24a7960 : 0xffffffff`ffffdeb8
00000000`6ba7d060 00007ffb`a1fbbcfb : 00000000`000036b7 00000000`0f216eb0 00000000`6ba7d400 00007ffb`a1fbbce0 : COM_Sensor64!DGSetupSensor+0x3d5ec
00000000`6ba7d0c0 00007ffb`a1f8ff98 : 00000000`0919ea50 00000000`6ba70000 ffffffff`fffffffe 00000000`0919ee30 : windows_storage!CFileOperation::_NotifyStartOperationsCallback+0x1b
00000000`6ba7d0f0 00007ffb`a1f4b6e1 : 00000000`0919ea50 00000000`6ba7d220 00000000`8007000e 00000000`0f1c7880 : windows_storage!DPA_EnumCallback+0x48
00000000`6ba7d120 00007ffb`a1f43135 : 00000000`00000000 00007ffb`5e2fe664 00007ffb`a1f43080 00000000`00000000 : windows_storage!CFileOperation::StartOperations+0x1b5
00000000`6ba7d5f0 00007ffb`5d03bfc9 : 0000c18f`00000001 00007ffb`a1f43080 00000000`00000000 00000000`0919ea60 : windows_storage!CFileOperation::PerformOperations+0xb5
00000000`6ba7d650 00000000`005deea8 : 00000000`00000001 00000000`0000431c 00000000`00000000 00000000`00000000 : COM_Sensor64!DGSetupSensor+0x3bc89
00000000`6ba7d700 00000000`00000001 : 00000000`0000431c 00000000`00000000 00000000`00000000 00000000`6ba7fd20 : TOTALCMD64+0x1deea8
00000000`6ba7d708 00000000`0000431c : 00000000`00000000 00000000`00000000 00000000`6ba7fd20 00000000`00000000 : 0x1
00000000`6ba7d710 00000000`00000000 : 00000000`00000000 00000000`6ba7fd20 00000000`00000000 00000000`00000000 : 0x431c


SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: com_sensor64!DGSetupSensor+3d5ec

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: COM_Sensor64

IMAGE_NAME: COM_Sensor64.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 5e308c85

STACK_COMMAND: ~23s; .ecxr ; kb

FAILURE_BUCKET_ID: SOFTWARE_NX_FAULT_INVALID_c0000005_COM_Sensor64.dll!DGSetupSensor

BUCKET_ID: X64_APPLICATION_FAULT_SOFTWARE_NX_FAULT_INVALID_BAD_IP_com_sensor64!DGSetupSensor+3d5ec

WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/TOTALCMD64_EXE/9_5_1_0/_______0/unknown/0_0_0_0/bbbbbbb4/c0000005/ffffdeb8.htm?Retriage=1

Followup: MachineOwner
---------
Author of Total Commander
http://www.ghisler.com
fhurta@gmail.com
Junior Member
Junior Member
Posts: 3
Joined: 2020-10-26, 11:36 UTC

Re: Total Commander crash while I delete the fils

Post by *fhurta@gmail.com »

Hello Christian,
Thank you very much for this thorough analysis.

Digital Guardian is installed on my computer. It is not very old (latest update 4 month ago). It is part of the corporate network security suite and I can't manage it at all.

At least I learned from your post on analysis of dump files. It was very helpful, thank you again.
Now I need to figure out how/if I can resolve it in the corporate.

Best regards
Filip
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 40083
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Re: Total Commander crash while I delete the fils

Post by *ghisler(Author) »

Your company should try to report the bug to the developers of Digital Guardian. You probably have some kind of maintenance contract.
Author of Total Commander
http://www.ghisler.com
Post Reply