SecureCRT Application has stopped working

[enigma2060]

I recently installed ver 7.3.6 64 bit on WIndows 7 and when I enter a session to connect, the application crashes.
Details

Problem signature:
Problem Event Name: APPCRASH
Application Name: SecureCRT.exe
Application Version: 7.3.6.963
Application Timestamp: 564df049
Fault Module Name: dgapi64.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 53a9f98a
Exception Code: c0000005
Exception Offset: 00000000000fc2b9
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: b4f1
Additional Information 2: b4f1898947728297c6918d65049220d6
Additional Information 3: 70c9
Additional Information 4: 70c9a76771a174c6feba903ef653d14d


any ideas?

[rtb]

Hi enigma2060,

I am sorry to hear about the crash. At this point, there isn't enough information to draw any conclusions.

Please submit a bug report. When submitting the bug report, please include as many details about the issue as possible.

For example, what is the history of SecureCRT on this machine?

Are you using an old configuration folder?

What specific steps are you using to "enter a session to connect"?

[jdev]

After looking at this again, a bug report may not help. What's crashing is a DLL file that's been injected into the SecureCRT.exe process outside of our control. dgapi64.dll is not produced or distributed by VanDyke Software, and we have no control over its operation. It's is associated with Digital Guardian, which has been known to cause similar crashes in the past (see this forum post from 2014).

Originally Posted by enigma2060

Problem signature:
Problem Event Name: APPCRASH
Application Name: SecureCRT.exe
Application Version: 7.3.6.963
Application Timestamp: 564df049
Fault Module Name: dgapi64.dll <-- Not part of SecureCRT -- injected by Digital Guardian system software
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 53a9f98a
Exception Code: c0000005
Exception Offset: 00000000000fc2b9
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: b4f1
Additional Information 2: b4f1898947728297c6918d65049220d6
Additional Information 3: 70c9
Additional Information 4: 70c9a76771a174c6feba903ef653d14d

The best course of action at this time would be for you to report the crash/problem to Digital Guardian, and/or work with your IT team to enable an exception for SecureCRT within the Digital Guardian software.

Alternatively, it's been reported that if you use the 32-bit version of SecureCRT, the 32-bit DLL which Digital Guardian injects into SecureCRT does not seem to cause the crash.

--Jake