Wfview, faults then exits

Brief summary of problem (put in title as well): Wfview, faults then exits
Radio Model: 756pro2 and 706mk2G
Connectivity (USB/Ethernet/Wifi/Other): USB FTDI
Operating System: Win 10 64bit up to date
wfview version (press “About”): 1.64
Checked the wfview manual (Y/N): Y
Checked the wfview FAQ (Y/N): Y
Tried to google it (Y/N/NA): Y

What I did:
Configured and ran Wfview

Expected behavior:

Observed behavior:
Connect then exits
Have a 756pro2 and a 706MK2G connected to a Dell OptiPlex running Windows 10, they are connected via FTDI USB to serial converters.

They both run OK with the last “free” version of HRD.

Wfview will connect to either radio and brings up the frequency and then immediately exits. Looking at the Event Viewer shows a fault as below.

Faulting application name: wfview.exe, version: 0.0.0.0, time stamp: 0x64b3f16d
Faulting module name: wfview.exe, version: 0.0.0.0, time stamp: 0x64b3f16d
Exception code: 0xc0000005
Fault offset: 0x00000000000938d4
Faulting process id: 0x14b4
Faulting application start time: 0x01da10182184f6ee
Faulting application path: C:\Program Files\wfview\wfview.exe
Faulting module path: C:\Program Files\wfview\wfview.exe
Report Id: f39ffd59-83d0-4653-873d-ebc8157550df
Faulting package full name:
Faulting package-relative application ID:

With information as below.

Fault bucket 2060689043995788904, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: wfview.exe
P2: 0.0.0.0
P3: 64b3f16d
P4: wfview.exe
P5: 0.0.0.0
P6: 64b3f16d
P7: c0000005
P8: 00000000000938d4
P9:
P10:

Attached files:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6EF9.tmp.mdmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6FA6.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6FE6.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6FF5.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7006.tmp.txt

These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_wfview.exe_dfac9c97d45adaf57f96069c5901666cc394_ee3efcfb_773821cc-fbb3-40cd-a8ed-87cd66aa588a

Analysis symbol:
Rechecking for solution: 0
Report Id: f39ffd59-83d0-4653-873d-ebc8157550df
Report Status: 268435456
Hashed bucket: 82dea0d21ba3bf8e1c9909c47be88668
Cab Guid: 0

Many thanks for your help.

73s

David
G8JXA / N1OL

Hi David.

It’s worth trying the 32 bit version of wfview as some users have reported being unable to run the 64bit one. This is likely due to the 64bit version using QT6. I haven’t been able to reproduce this though.

Phil

Thanks for the fast response, confirm the 32bit version does work OK.
Is there anything I can do to help such as dump files etc.
Very best 73s.
David

Thanks David.

Yes a log file from the 64bit version would be useful (even better if you could do a debug log)

Full instructions are on Log file | wfview

73 Phil M0VSE

Phil, Hi!

I have a debug log and a Windows dmp file.

Where can I email them to?

Best 73s

David

~WRD0001.jpg

1 Like

Hi David, if you can send them to phil@m0vse.uk that will be great.

73
Phil