TCC startup crash in Windows 8 Pro x64

  • This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.
Dec 19, 2012
3
0
#1
Fresh install of Windows 8 Pro x64 with all updates. Fresh install of TCMD 14.03.53. No INI files, no tcstart or tcexit files. Can't start either TCMD or TCC. All I get is "TCC has stopped working" dialog. Here are problem details from that dialog:


Code:
Problem signature:
  Problem Event Name:    BEX64
  Application Name:    tcc.exe
  Application Version:    14.0.3.53
  Application Timestamp:    50c7e649
  Fault Module Name:    StackHash_4e5d
  Fault Module Version:    0.0.0.0
  Fault Module Timestamp:    00000000
  Exception Offset:    PCH_E7_FROM_ntdll+0x000000000002336E
  Exception Code:    c0000005
  Exception Data:    0000000000000008
  OS Version:    6.2.9200.2.0.0.256.48
  Locale ID:    1033
  Additional Information 1:    4e5d
  Additional Information 2:    4e5d5dc6aabf76cc679d707f73217047
  Additional Information 3:    c3f4
  Additional Information 4:    c3f4f21ff0efa95302412e4fece51da2

Tried to run as administrator. Same result. No GPF file generated. Attached content of Windows Error Reporting directory from crash.
 

Attachments

Mar 16, 2013
6
0
#2
Fresh install of Windows 8 Pro x64 with all updates. Fresh install of TCMD 14.03.53. No INI files, no tcstart or tcexit files. Can't start either TCMD or TCC. All I get is "TCC has stopped working" dialog. Here are problem details from that dialog:
.
I'm also getting this issue, is there any resolution to it? I just got a new laptop (asus g55v) and TCC won't run on it period. I've tried my licensed v11 copy, then tried to install v14 and v15. They all crash on start-up. Very little software has been installed on this laptop. I'd upgrade/buy new lic if I could get TCC working on this laptop.
 
Mar 16, 2013
6
0
#3
Faulting application name: TCC.EXE, version: 15.0.0.18, time stamp: 0x513e8012
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000007fd00040000
Faulting process id: 0x113c
Faulting application start time: 0x01ce21fb1e13b59d
Faulting application path: C:\Program Files\JPSoft\TCMD15x64\TCC.EXE
Faulting module path: unknown
Report Id: 5be40541-8dee-11e2-be7c-dc85de92066e
Faulting package full name:
Faulting package-relative application ID:

This laptop is running windows 8 pro 64 bit, and all windows updates. I've been using this program since it was 4dos, can someone please help?

Who can I email the core dump to?
 

rconn

Administrator
Staff member
May 14, 2008
10,096
85
#4
Send the dump to support@jpsoft.com. Also, you should have a *.GPF file that TCC creates; that is usually in your c:\users\(yourname)\appdata\local\jpsoft" directory. That is more valuable than the one that Windows creates, so please send that.

I've been running Windows 8 x64 here for several months; I've never seen a crash. The crash address is *not* inside the TCC code, so it's either crashing in a Windows dll or an injected dll. I need the stack trace to determine the calling TCC code.
 
Mar 16, 2013
6
0
#5
one other thing i noticed, the wrapper (not sure what its called) around the shell window appears to be working but the shell itself isn't, the wrapper shows the cpu and I can see it updating behind the windows crash box, the menus work etc. tried to use the cmd shell its not responding.

emailed, let me know if I can assist further..
 
Mar 16, 2013
6
0
#7
Yes correct. Here it is loading into windbg, access violation on one of the dlls:

ModLoad: 00000000`00400000 00000000`00468000 tcc.exe
ModLoad: 000007fc`ce5c0000 000007fc`ce77e000 ntdll.dll
ModLoad: 00000000`00150000 00000000`00286000 C:\Windows\system32\KERNEL32.DLL
ModLoad: 00000000`00290000 00000000`00383000 C:\Windows\system32\KERNELBASE.dll
ModLoad: 00000000`01810000 00000000`01973000 C:\Windows\SYSTEM32\dbghelp.dll
ModLoad: 00000000`10000000 00000000`102a9000 C:\Program Files\JPSoft\TCMD15x64\TakeCmd.dll
ModLoad: 00000000`01980000 00000000`01b6e000 C:\Program Files\JPSoft\TCMD15x64\ipworks9.dll
ModLoad: 00000000`01b70000 00000000`01cbc000 C:\Windows\system32\USER32.dll
ModLoad: 00000000`01cc0000 00000000`01d9e000 C:\Windows\system32\ADVAPI32.dll
ModLoad: 00000000`01da0000 00000000`03088000 C:\Windows\system32\SHELL32.dll
ModLoad: 00000000`03090000 00000000`0320e000 C:\Windows\system32\ole32.dll
ModLoad: 00000000`03210000 00000000`032d3000 C:\Windows\system32\OLEAUT32.dll
ModLoad: 00000000`032e0000 00000000`03385000 C:\Windows\system32\msvcrt.dll
ModLoad: 00000000`00080000 00000000`000a0000 C:\Windows\SYSTEM32\WINMM.dll
ModLoad: 00000000`03390000 00000000`035f9000 C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9200.16384_none_418c2a697189c07f\COMCTL32.dll
ModLoad: 00000000`000a0000 00000000`000a9000 C:\Windows\SYSTEM32\WSOCK32.dll
ModLoad: 00000000`03600000 00000000`037f7000 C:\Program Files\JPSoft\TCMD15x64\ipworksssl9.dll
ModLoad: 00000000`03800000 00000000`038dc000 C:\Program Files\JPSoft\TCMD15x64\ipworksssh9.dll
ModLoad: 00000000`038e0000 00000000`03a3e000 C:\Program Files\JPSoft\TCMD15x64\ipworkszip9.dll
ModLoad: 00000000`00390000 00000000`003e0000 C:\Windows\system32\SHLWAPI.dll
ModLoad: 00000000`000b0000 00000000`000b7000 C:\Windows\system32\PSAPI.DLL
ModLoad: 00000000`69bb0000 00000000`69c05000 C:\Program Files\JPSoft\TCMD15x64\onig.dll
ModLoad: 00000000`69b90000 00000000`69bae000 C:\Program Files\JPSoft\TCMD15x64\Everything.dll
ModLoad: 00000000`03a40000 00000000`03b80000 C:\Windows\system32\GDI32.dll
ModLoad: 00000000`03b80000 00000000`03bfd000 C:\Windows\SYSTEM32\WINSPOOL.DRV
ModLoad: 00000000`03c00000 00000000`03ca1000 C:\Windows\system32\COMDLG32.dll
ModLoad: 00000000`03cb0000 00000000`03d08000 C:\Windows\system32\WS2_32.dll
ModLoad: 00000000`03d10000 00000000`03d58000 C:\Windows\SYSTEM32\sechost.dll
ModLoad: 00000000`03d60000 00000000`03ea0000 C:\Windows\system32\RPCRT4.dll
ModLoad: 00000000`03ea0000 00000000`04050000 C:\Windows\SYSTEM32\combase.dll
ModLoad: 00000000`04050000 00000000`04082000 C:\Windows\SYSTEM32\WINMMBASE.dll
ModLoad: 00000000`04090000 00000000`04126000 C:\Windows\SYSTEM32\SHCORE.DLL
ModLoad: 00000000`003e0000 00000000`003e9000 C:\Windows\system32\NSI.dll
ModLoad: 00000000`04130000 00000000`04169000 C:\Windows\system32\IMM32.DLL
ModLoad: 00000000`04320000 00000000`04435000 C:\Windows\system32\MSCTF.dll
ModLoad: 00000000`059d0000 00000000`059d8000 C:\PROGRA~2\NVIDIA~1\3DVISI~1\NVSTIN~1.DLL
ModLoad: 00000000`6ad30000 00000000`6add3000 C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6871_none_08e717a5a83adddf\MSVCR90.dll
ModLoad: 00000000`05a10000 00000000`05a25000 C:\Windows\SYSTEM32\netapi32.dll
ModLoad: 00000000`059f0000 00000000`059fe000 C:\Windows\SYSTEM32\netutils.dll
ModLoad: 00000000`05a60000 00000000`05a84000 C:\Windows\SYSTEM32\srvcli.dll
ModLoad: 00000000`05a30000 00000000`05a45000 C:\Windows\SYSTEM32\wkscli.dll
ModLoad: 00000000`05a90000 00000000`05ac4000 C:\Windows\SYSTEM32\LOGONCLI.DLL
ModLoad: 00000000`05e80000 00000000`06057000 C:\Windows\system32\crypt32.dll
ModLoad: 00000000`05ad0000 00000000`05ae6000 C:\Windows\system32\MSASN1.dll
ModLoad: 00000000`05af0000 00000000`05b37000 C:\Windows\SYSTEM32\qwave.dll
ModLoad: 00000000`05b40000 00000000`05b4e000 C:\Windows\SYSTEM32\TRAFFIC.dll
ModLoad: 00000000`05b50000 00000000`05b53000 C:\Windows\SYSTEM32\WMI.dll
ModLoad: 00000000`05b60000 00000000`05b8a000 C:\Windows\SYSTEM32\IPHLPAPI.DLL
ModLoad: 00000000`06060000 00000000`0606a000 C:\Windows\SYSTEM32\WINNSI.DLL
ModLoad: 00000000`06090000 00000000`0609b000 C:\Windows\SYSTEM32\secur32.dll
ModLoad: 00000000`060a0000 00000000`060cc000 C:\Windows\SYSTEM32\SSPICLI.DLL
ModLoad: 00000000`060d0000 00000000`060d3000 C:\Windows\SYSTEM32\icmp.dll
ModLoad: 00000000`062e0000 00000000`0650e000 C:\Windows\system32\wininet.dll
ModLoad: 00000000`06510000 00000000`06726000 C:\Windows\system32\iertutil.dll
ModLoad: 00000000`06730000 00000000`06813000 C:\Windows\system32\uxtheme.dll
ModLoad: 00000000`060f0000 00000000`06111000 C:\Windows\SYSTEM32\dwmapi.dll
(1248.1be4): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
000007fd`00040000 ?? ???
 
Mar 16, 2013
6
0
#8
callstack window:

Child-SP RetAddr : Args to Child : Call Site
00000000`0178fa38 000007fc`ce5e336e : 00000000`0178fb00 000007fc`ce5f4647 00000000`00000000 00000000`7fffc000 : 0x000007fd`00040000
00000000`0178fa40 000007fc`ce5e32ae : 00000000`0178fb00 00000000`00000000 00000000`7fffc000 00000000`00000000 : ntdll!LdrpInitialize+0xb2
00000000`0178fab0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!LdrInitializeThunk+0xe
 

rconn

Administrator
Staff member
May 14, 2008
10,096
85
#10
callstack window:

Child-SP RetAddr : Args to Child : Call Site
00000000`0178fa38 000007fc`ce5e336e : 00000000`0178fb00 000007fc`ce5f4647 00000000`00000000 00000000`7fffc000 : 0x000007fd`00040000
00000000`0178fa40 000007fc`ce5e32ae : 00000000`0178fb00 00000000`00000000 00000000`7fffc000 00000000`00000000 : ntdll!LdrpInitialize+0xb2
00000000`0178fab0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!LdrInitializeThunk+0xe
That's Windows loader; the TCC code isn't being called yet.
 
Mar 16, 2013
6
0
#11
Sure, dwmapi just happens to be the last file loaded prior to the crash, I'm just sending as much information as possible. :) The crash address is the same in event viewer and debugger. What about the DLL list itself, are there any differences between your window 8 and mine?
 
Apr 30, 2009
17
0
#12
I'm getting the same behavior and no GPF file is created. This is with 15.00.34 and using msconfig to pare the starting services down to the bare minimum.
 
Apr 30, 2009
17
0
#13
I tried 15.00.36 and TCC is still crashing when loading with no GPF file created. Any thoughts on how I might get more information to help resolve this.
 
Apr 30, 2009
17
0
#15
The first time TCMD 32-bit starts I get a popup window that states "The handle is invalid. "Attache Console". Dismissing the dialogue box closes TCMD.

Starting TCMD 32-bit a second time, and subsequent times, it comes up without error and seems to work fine. Progress!
 
Dec 19, 2012
3
0
#16
Just to chime in. Nothing changed with v15. I'm still getting same error. No GPF file created either. Very frustrating.

Windows Debugger dump looks slightly different then posted above

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

CommandLine: "C:\Program Files\JP Software\Take Command x64 15.0\tcc.exe"
Symbol search path is: SRV*D:\SymbolCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
ModLoad: 00000000`00400000 00000000`00426000 tcc.exe
ModLoad: 000007fe`799e0000 000007fe`79b9e000 ntdll.dll
ModLoad: 00000000`00140000 00000000`00276000 C:\Windows\system32\KERNEL32.DLL
ModLoad: 00000000`00280000 00000000`00373000 C:\Windows\system32\KERNELBASE.dll
ModLoad: 00000000`01750000 00000000`017ef000 C:\Windows\system32\apphelp.dll
SHIMVIEW: ShimInfo(Complete)
ModLoad: 00000000`017f0000 00000000`01953000 C:\Windows\SYSTEM32\dbghelp.dll
ModLoad: 00000000`10000000 00000000`10229000 C:\Program Files\JP Software\Take Command x64 15.0\TakeCmd.dll
ModLoad: 00000000`01960000 00000000`01b50000 C:\Program Files\JP Software\Take Command x64 15.0\ipworks9.dll
ModLoad: 00000000`01b50000 00000000`01c9c000 C:\Windows\system32\USER32.dll
ModLoad: 00000000`01ca0000 00000000`01d7e000 C:\Windows\system32\ADVAPI32.dll
ModLoad: 00000000`01d80000 00000000`0305e000 C:\Windows\system32\SHELL32.dll
ModLoad: 00000000`03060000 00000000`031de000 C:\Windows\system32\ole32.dll
ModLoad: 00000000`031e0000 00000000`032a3000 C:\Windows\system32\OLEAUT32.dll
ModLoad: 00000000`032b0000 00000000`03357000 C:\Windows\SYSTEM32\MSVCP110.dll
ModLoad: 00000000`03360000 00000000`03434000 C:\Windows\SYSTEM32\MSVCR110.dll
ModLoad: 00000000`03440000 00000000`034e5000 C:\Windows\system32\msvcrt.dll
ModLoad: 00000000`00080000 00000000`000a0000 C:\Windows\SYSTEM32\WINMM.dll
ModLoad: 00000000`034f0000 00000000`03759000 C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9200.16384_none_418c2a697189c07f\COMCTL32.dll
ModLoad: 00000000`000a0000 00000000`000a9000 C:\Windows\SYSTEM32\WSOCK32.dll
ModLoad: 00000000`03760000 00000000`03957000 C:\Program Files\JP Software\Take Command x64 15.0\ipworksssl9.dll
ModLoad: 00000000`03960000 00000000`03a3c000 C:\Program Files\JP Software\Take Command x64 15.0\ipworksssh9.dll
ModLoad: 00000000`03a40000 00000000`03b9e000 C:\Program Files\JP Software\Take Command x64 15.0\ipworkszip9.dll
ModLoad: 00000000`03ba0000 00000000`03bf0000 C:\Windows\system32\SHLWAPI.dll
ModLoad: 00000000`000b0000 00000000`000b7000 C:\Windows\system32\PSAPI.DLL
ModLoad: 00000000`5acf0000 00000000`5ad45000 C:\Program Files\JP Software\Take Command x64 15.0\onig.dll
ModLoad: 00000000`5ace0000 00000000`5acea000 C:\Program Files\JP Software\Take Command x64 15.0\Everything.dll
ModLoad: 00000000`03bf0000 00000000`03d30000 C:\Windows\system32\GDI32.dll
ModLoad: 00000000`03d30000 00000000`03dad000 C:\Windows\SYSTEM32\WINSPOOL.DRV
ModLoad: 00000000`03db0000 00000000`03e51000 C:\Windows\system32\COMDLG32.dll
ModLoad: 00000000`03e60000 00000000`03eb8000 C:\Windows\system32\WS2_32.dll
ModLoad: 00000000`03ec0000 00000000`03f08000 C:\Windows\SYSTEM32\sechost.dll
ModLoad: 00000000`03f10000 00000000`04050000 C:\Windows\system32\RPCRT4.dll
ModLoad: 00000000`04050000 00000000`04200000 C:\Windows\SYSTEM32\combase.dll
ModLoad: 00000000`04200000 00000000`04232000 C:\Windows\SYSTEM32\WINMMBASE.dll
ModLoad: 00000000`04250000 00000000`042e6000 C:\Windows\SYSTEM32\SHCORE.DLL
ModLoad: 00000000`042f0000 00000000`042f9000 C:\Windows\system32\NSI.dll
(1270.140c): Break instruction exception - code 80000003 (first chance)
ntdll!LdrpDoDebuggerBreak+0x30:
000007fe`79a9ada0 cc int 3
 
Oct 15, 2011
8
0
#17
I get the "the handle is invalid", "AttachConsole", all the time now. I can no longer use 15.x tcmd.exe, on my Windows 8 PC. It used to happen once or twice, then the third time it ran no problem.

No problems with 12.x and 13.2, on the Windows 7 pcs.
 
Oct 29, 2012
11
0
#18
A work around may be deleting or renaming the registry key
Code:
HKEY_CURRENT_USER\Software\JP Software\Take Command 16.0\Settings\NormalLayout\CommandBars\CommandBars