Button not response in Find Files dialog

Please report only one bug per message!

Moderators: white, sheep, Hacker, Stefan2

Post Reply
BeckYang
Junior Member
Junior Member
Posts: 29
Joined: 2006-04-02, 10:33 UTC

Button not response in Find Files dialog

Post by *BeckYang » 2016-07-04, 09:02 UTC

TC Version: 8.52 32bit (2015-08-26)

I open the Find Files dialog, click "Start search" and it works fine.
Then I switch to other program and do something.
After switch to TC, I cannot get response on clicking any button. I try to close the dialog, but it does not work too. The "Search for" text input still get inputed chars, but pressing enter key does not perform search.

Finally, I create a mini dump file and kill the process using process explorer.
https://drive.google.com/file/d/0B4KuWV7cJg0JMHM3S1FOaUpyUG8/view?usp=sharing

TC works fine after restarting it. Although the problem only happen several times, but I hope it can be fixed. Thanks.

I also create a full dump (51MB), I can offert the file if required.

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

Post by *ghisler(Author) » 2016-07-06, 16:41 UTC

Here is the analysis - looks rather unusual. Unfortunately there isn't any usable stack trace with our own code.

Code: Select all

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


Loading Dump File [E:\bugswcmd\BETA50\b - Button not response in Find Files dialog.DMP]
User Mini Dump File: Only registers, stack and portions of memory are available

Symbol search path is: srv*C:\SYMBOLS*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: SingleUserTS
Machine Name:
Debug session time: Mon Jul  4 10:23:34.000 2016 (UTC + 2:00)
System Uptime: not available
Process Uptime: 0 days 7:31:08.000
...........................WARNING: winspool overlaps mpr
................WARNING: propsys overlaps comctl32_73760000
....WARNING: WindowsCodecs overlaps propsys
.WARNING: apphelp overlaps WindowsCodecs
...WARNING: srvcli overlaps apphelp
...WARNING: mscms overlaps ntshrui
.....WARNING: wkscli overlaps netutils
.....
....WARNING: duser overlaps explorerframe
.WARNING: dui70 overlaps duser
WARNING: dui70 overlaps explorerframe
......................WARNING: secur32 overlaps ntshrui
.......WARNING: IMTCCORE overlaps IMTCTIP
.WARNING: IMTCCFG overlaps IMTCCORE
..............WARNING: d3d11 overlaps dxgi
..WARNING: msls31 overlaps tiptsf
.
Cannot read PEB32 from WOW64 TEB32 7efdd000 - Win32 error 0n30
wow64cpu!CpupSyscallStub+0x9:
00000000`71d02e09 c3              ret
0:000> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

*** WARNING: Unable to verify timestamp for TOTALCMD.EXE
*** ERROR: Module load completed but symbols could not be loaded for TOTALCMD.EXE
GetPageUrlData failed, server returned HTTP status 404
URL requested: http://watson.microsoft.com/StageOne/TOTALCMD_EXE/8_5_2_0/2a425e19/unknown/0_0_0_0/bbbbbbb4/80000003/00000000.htm?Retriage=1

FAULTING_IP: 
+a8b91f0
00000000`00000000 ??              ???

EXCEPTION_RECORD:  ffffffffffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 0000000000000000
   ExceptionCode: 80000003 (Break instruction exception)
  ExceptionFlags: 00000000
NumberParameters: 0

FAULTING_THREAD:  0000000000000ea8

DEFAULT_BUCKET_ID:  STATUS_BREAKPOINT

PROCESS_NAME:  TOTALCMD.EXE

OVERLAPPED_MODULE: Address regions for 'ntshrui' and 'secur32' overlap

ERROR_CODE: (NTSTATUS) 0x80000003 - {AUSNAHME}  Haltepunkt  Im Quellprogramm wurde ein Haltepunkt erreicht.

EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - Mindestens ein Argument ist ung ltig.

MOD_LIST: <ANALYSIS/>

NTGLOBALFLAG:  0

APPLICATION_VERIFIER_FLAGS:  0

PRIMARY_PROBLEM_CLASS:  STATUS_BREAKPOINT

BUGCHECK_STR:  APPLICATION_FAULT_STATUS_BREAKPOINT

LAST_CONTROL_TRANSFER:  from 0000000000000000 to 0000000071d02e09

STACK_TEXT:  
00000000`0008ec08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : wow64cpu!CpupSyscallStub+0x9


STACK_COMMAND:  ~0s; .ecxr ; kb

FOLLOWUP_IP: 
wow64cpu!CpupSyscallStub+9
00000000`71d02e09 c3              ret

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  wow64cpu!CpupSyscallStub+9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: wow64cpu

IMAGE_NAME:  wow64cpu.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  573a550a

FAILURE_BUCKET_ID:  STATUS_BREAKPOINT_80000003_wow64cpu.dll!CpupSyscallStub

BUCKET_ID:  X64_APPLICATION_FAULT_STATUS_BREAKPOINT_wow64cpu!CpupSyscallStub+9

WATSON_STAGEONE_URL:  http://watson.microsoft.com/StageOne/TOTALCMD_EXE/8_5_2_0/2a425e19/unknown/0_0_0_0/bbbbbbb4/80000003/00000000.htm?Retriage=1

Followup: MachineOwner
---------
Author of Total Commander
http://www.ghisler.com

Post Reply