Bryan Lynch - NM7C
I had it happen again just now.
I've been on FT8 all day trying to catch this happening again with more attention paid to the actual steps taken.
I had a QSO with one other "/" call today with no issue (W4ID/6) just before this attempt
Steps to WSJT-X Crash:
RX: AI7MH/P calling CQ
TX: (Several Attempts) AI7MH/P NM7C [report]
Change: NM7C changed split TX Freq as AI7MH/P was in active QSO (Hold Tx Freq function in WSJT-X)
TX: AI7MH/P NM7C [report]
RX: NM7C AI7MH/P [report]
CRASH and program exit.
To be clear again, the crash happened within 1-2 seconds of decoding "NM7C AI7MH/P". No buttons were pressed to make this occur.
Got the message about an orphaned JT9 process upon attempted re-launch of WSJT-X
Killed the process manually.
Launched WSJT-X again, back to normal ops.
Radio is Kenwood TS-2000
Interface is Signalink USB
WSJT-X Version: 2.5.3
Operating System: Windows 10 Pro
CAT Interface: Ham Radio Deluxe 220.127.116.111
Logging: HRD Logbook 18.104.22.1681
Windows Event Viewer crash data:
Faulting application name: wsjtx.exe, version: 22.214.171.124, time stamp: 0x61b0e1e7
Faulting module name: ntdll.dll, version: 10.0.19041.1288, time stamp: 0xa280d1d6
Exception code: 0xc0000374
Fault offset: 0x00000000000ff199
Faulting process id: 0x3048
Faulting application start time: 0x01d7f2c175779c6f
Faulting application path: C:\WSJT\wsjtx\bin\wsjtx.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 8064184e-f48e-495a-8c86-25c0d7181db5
Faulting package full name:
Faulting package-relative application ID:
I hope this helps with troubleshooting efforts.
I've never had a WSJT-X crash in years of using it until this issue.