Rob I am running Version 220.127.116.11 which I believe is the latest free version. Honestly I doubt it is a software problem, more likely a hardware problem.
As I said I am not having any problems with JT65 crashing while the HRD logbook is up and running. I log every JT65 contact while I am actually making the contact.
Oh well Rick, you let the air out of that thought balloon!
There are interacting elements in the hardware, drivers, inter-process communication etc, so it could be a lot of things.
I don't claim to have much knowledge of HRD, but from memory it communicates between processes via TCP/IP ports.
Since this is a networking process, perhaps a lockup(or apparent lockup) could be due to his network processes being blocked for some reason intermittently.
I am not sure if HRD uses other inter-process comms methods such as shared memory or semaphores, but waiting on a network process can initiate a timeout period, which may suspend the process.
I am probably like the guy in plato's cave trying to guess reality from the shadows cast on the cave wall, but there is my input for what it is worth.
If I were doing it, I would have windows performance manager running, and see which processes are taking a lot of cpu time and memory usage in normal operation.
Then when the process hangs check it again and see if anything has drastically changed.
Another thing he could try is to do a netstat -a command in dos or cmd mode, and take a note of network connections being used by HRD/Logbook.
Then you could see if any are terminated or otherwise acting abnormally when the problem occurs.
The thing to do is to get a feel for the normal baseline conditions and then you can do some forensics when it goes belly up.
It could even be RF affecting the nomic interface, and that causing hanging - and HRD logbook may just be a co-incidence.
I know when my usb-signalink gets an RF overdose, it hangs my digimode program for a while.
Good luck and happy diagnosing.
73 - Rob