1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Version 19.00.23 Crashes

Discussion in 'Support' started by cgunhouse, Dec 8, 2015.

  1. cgunhouse

    Joined:
    Dec 2, 2008
    Messages:
    209
    Likes Received:
    2
    After Build 23, TCMD crashes after about 5 minutes of running, even if TCMD is minimized.

    I have background TCC Windows running they have never been a problem before.

    I may have to back out and go back to Build 22.

    Craig
     
  2. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,855
    Likes Received:
    83
    Define "TCMD crashes".

    I need your error log before I can look at this.
     
  3. cgunhouse

    Joined:
    Dec 2, 2008
    Messages:
    209
    Likes Received:
    2
    Which error logs are you referring to, the Windows Event log?

    I have crash dumps produced using SysInternals' ProcDump.

    One produced using "C:\Program Files\SysInternals\procdump" -o -n 1 -e -64 -mp 9528 TCMD.dmp" (Large) and the other "C:\Program Files\SysInternals\procdump" -o -n 1 -e -64 3280 TCMD.dmp" (Smaller)
     
  4. Charles G

    Joined:
    Apr 2, 2011
    Messages:
    1,018
    Likes Received:
    0
    I think Rex is referring to the TCMD and TCC exception log files in the install folder. Usually (for x64):

    C:\Program Files\JPSoft\TCMD19_x64\tcc.exception.log
    C:\Program Files\JPSoft\TCMD19_x64\tcmd.exception.log
     
  5. cgunhouse

    Joined:
    Dec 2, 2008
    Messages:
    209
    Likes Received:
    2
    Both files are empty, that why I asked, I was hoping there were other files with something in them, I sent a mini-dump to support@jpsoft.com
     
  6. TimButterfield

    Joined:
    May 20, 2008
    Messages:
    401
    Likes Received:
    2
    I had the same crash issue with 23 right after setting up and starting to run it on Win7x86. The log files were empty also. I did capture this from Windows:
    Code:
    Problem signature:
      Problem Event Name:    APPCRASH
      Application Name:    tcmd.exe
      Application Version:    19.0.23.0
      Application Timestamp:    56664608
      Fault Module Name:    tcmd.exe
      Fault Module Version:    19.0.23.0
      Fault Module Timestamp:    56664608
      Exception Code:    c0000005
      Exception Offset:    000531ca
      OS Version:    6.1.7601.2.1.0.256.4
      Locale ID:    1033
      Additional Information 1:    0a9e
      Additional Information 2:    0a9e372d3b4ad19135b953a78882e789
      Additional Information 3:    0a9e
      Additional Information 4:    0a9e372d3b4ad19135b953a78882e789
     
  7. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,855
    Likes Received:
    83
    If the log files are empty, then the crash wasn't in TCMD (or TCC) code. It either happened in a Windows DLL that had its own exception handler, or a third-party app that injected itself into TCMD (or TCC).
     
  8. cgunhouse

    Joined:
    Dec 2, 2008
    Messages:
    209
    Likes Received:
    2
    Tried backing out to 19.00.22, it works fine, 19.00.23 does not work. I also loaded the debugger after the crash to see what the Call Stack showed:

    Call-Stack.png
     
  9. Charles G

    Joined:
    Apr 2, 2011
    Messages:
    1,018
    Likes Received:
    0
    @Rex,

    How would you suggest debugging this occurrence if this happens to someone not in the know, please?
     
  10. cgunhouse

    Joined:
    Dec 2, 2008
    Messages:
    209
    Likes Received:
    2
    And if 19.00.22 works and 19.00.23 doesn't work, what changed? My system didn't change, sure the error may be coming from a Windows DLL or injected code (why doesn't it inject itself into 19.00.22 and cause a crash) but the only thing that could of changed is how they were called from TCMD.
     
  11. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,855
    Likes Received:
    83
    The only thing that changed was using the new(er) embedded Windows file explorer instead of the old separate tree (folder) and list view controls.
     
  12. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,855
    Likes Received:
    83
    There is no way for a user to debug this, other than to disable apps that might be injecting code and see if the behavior changes.
     
  13. cgunhouse

    Joined:
    Dec 2, 2008
    Messages:
    209
    Likes Received:
    2
    I followed TCMD with Process Monitor and got:

    tcmd1.png
    The previous 11 events were "Thread Exit" events
    The "Thread Exit" events info is as follows:
    tcmd2.png tcmd3.png

    The "IRP_MJ_DIRECTORY_CONTROL" events info is as follows:
    tcmd4.png tcmd5.png

    Continued next comment (image upload limit)
     
  14. Alpengreis

    Joined:
    Jan 12, 2014
    Messages:
    229
    Likes Received:
    6
  15. cgunhouse

    Joined:
    Dec 2, 2008
    Messages:
    209
    Likes Received:
    2
    And finally "IRP_MJ_QUERY_INFORMATION" events info is as follows:
    tcmd6.png tcmd7.png

    The process tab is attach, it is a CSV (excel)

    TCMD seems to crash when something change on the network drive.
     

    Attached Files:

    #15 cgunhouse, Dec 10, 2015
    Last edited: Dec 10, 2015
  16. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,855
    Likes Received:
    83
    Try it with build 24 and let me know if it behaves any differently.
     
  17. cgunhouse

    Joined:
    Dec 2, 2008
    Messages:
    209
    Likes Received:
    2
    So far 19.0.25 has not crashed.

    I believe the correction you made fixed the problem!

    Thanks
     

Share This Page