Keeping Flex-6500 up when PC crashes

Keith - KE4TH

Is there a way to keep my Flex-6500 running when my PC crashes?  Using SmartSDR version 1.11.12.  About 10 seconds after the PC crashes, the Flex-6500 freezes up - no more audio in headphones, stops transmitting when keyed, etc.  I appear to have a Windows 10 issue that causes 4 crashes per month.

Mike VE3CKO

Keith - KE4TH

Thanks Mike.  I have run the radio with my iPad, but it's not nearly as smooth as with the wired desktop.  Need to look closer at the Maestro.  Since the radio runs for about 10 seconds after losing its connection, maybe it is possible to extend this "mode".  No settings could be changed, but the radio operation would continue hopefully long enough to get the PC rebooted or connection restored.  This would make the radio/PC system more robust!

Martin AA6E

Larry _ NY8T

Your still using version 1.11.12, you very well may be able to solve your disconnect issue by using a newer version of smartsdr. Your current version is pushing on 5 years old.

WA2SQQ

Harold Rosee

Mike VE3CKO

Gene - K3GC

Keith - KE4TH

Thanks for the several comments and suggestions!  The PC symptom is that the PC reboots without any command or warning.  The PC is shut down each evening so it gets rebooted once per day.  I upgraded to Windows 10 from Windows 7 about 4 months ago, and did not have issues until late April.  The ASUS tower is over 5 years old now, so a hardware issue is possible.  The Windows 10 event log shows the reboots but I have not been able to learn much more from the logs.  I will do some digging!

Steve K9ZW

What is the full spec on your PC, as I had an issue where cumulative upgrades of system & other productivity software reduced the available memory of my system below what SmartSDR required.

SmartSDR "claims" the memory it needs both initially and then in increments until it arrives at a sable memory usage.

One of my PCs had enough to start SDR, but would then crash SmartSDR in a variable amount of time based on whatever else I was running.

As it was an older PC and was hardware limited to a certain amount of memory, I replaced it - actually pulling the RAM from the old machine to add to the new PC - and all is well.  

It was frustrating and I did open a support ticket wasting some of FRS's time in the process, as the older machine didn't crash instantly nor consistently.  

This may be different than your issue, but worth exploring as the "fix" is more available memory.

73

Steve
K9ZW

Keith - KE4TH

The PC has 8 GB of memory, 7.2 GB usable.  It is single-channel DDR3 at 800 MHz.  The processor is an AMD A10-6700 at 3.70 GHz.  I added an Intel SSD which is the main drive now.  Graphics are ATI AMD Radeon HD with 768MB of memory.  I can try running Task Manager and watch for declining memory.  While operating, typically FLDIGI is running as my logger, and Chrome (memory intensive from what I have read) is open to QRZ to check call signs.

Dudley WA5QPZ

Keith,

Check your CPU and powersupply fans,   I bet one or both are not spinning correctly,  has a bad bearing,  or clogged with dust bunnies..   If you have not cleaned the insides lately,  a can of compressed air can work wonders.. 

Dudley

Gene - K3GC

Keith - KE4TH

Thanks Dudley and Gene.  I checked the PS fan and CPU fan - both working ok but moderate dust on CPU heat sink. Cleaned up dust and both fans with can of Ultra Duster. Motherboard looked ok but I may not be able to spot issues there.  Downloaded AMD's Overdrive to monitor CPU temperature.  Gives "thermal margin" for each core i.e. difference between max T and current T.  Settled out at 37 C so it's will under the max temperature.  My guess now is a power supply issue - will keep using it until the issue happens again - it was ok today for two operating sessions total 5 CW contacts maybe 1.5 hrs of operating.  Thanks for your interest!

Keith - KE4TH

Steve,
I used Task Manager to monitor the memory during a series of 3 CW contacts.  It started at about 39% and settled out at 42%.  So I think the amount of memory is good.  At least in a shorter operating session, there did not appear to be any "memory leak".  Thanks for your comment - the symptoms sound just like what I am seeing.