If you ever have to kill its process, depending how far it got before it got stuck, a file named something like ONGOING-ISRUNNING-072713-194.TXT should be left behind in the Scripts folder.
If you haven't already deleted any of those files, could you please post the most recent one for me to look at?
It should contain a list of all the processes running at the time HG612_stats.exe started running.
Strictly speaking, if something goes wrong, HG612_stats.exe should record the problem in ONGOING_ERROR.LOG_file_ERROR.TXT & exit gracefully.
Could you please post that file for me to examine?
You may need to compress it first for it to fit within the forum's attachment file size limit.
My suspicion is that either some other program is blocking or causing HG612_stats.exe and/or HG612_Run.exe to hang or that something else is accessing the modem at the same time which would corrupt the modem's responses to HG612_stats.exe's stats data requests at an unexpected stage.
Whenever more than 1 instance of HG612_stats.exe attempt to run at the same time, possibly if the first instance has been slowed down by something else hogging all the PC's resources etc, one or both of the instances should be exited & a record of it logged in the EXIT_2_INSTANCES.LOG file.
Here are a couple of examples from when my resource hungry AV program (AVG 2015) slowed my PC down when running its daily scan:-
23/02/2015 4:09:08.66 - ONGOING-ISRUNNING-040900-398.TXT - ** Exiting as there are 2 instances of [HG612_stats.exe] running. Status = 1,
23/02/2015 4:09:08.66 - ONGOING-ISRUNNING-040800-587.TXT - ** Exiting as there are 2 instances of [HG612_stats.exe] running. Status = 1,
23/02/2015 4:09:08.71 - ONGOING-ISRUNNING-040800-587.TXT - ** ONGOING-ISRUNNING-040800-587.TXT DELETED - Status = 1,
23/02/2015 4:09:08.71 - ONGOING-ISRUNNING-040900-398.TXT - ** ONGOING-ISRUNNING-040900-398.TXT DELETED - Status = 1,
That tells me that the instance of HG612_stats.exe from 04:08 was still running at the time the 04:09 instance started.
Both instances needed to exit to avoid any of them hanging.
23/02/2015 4:33:28.83 - ONGOING-ISRUNNING-043300-298.TXT - ** Exiting as there are 2 instances of [HG612_stats.exe] running. Status = 1,
23/02/2015 4:33:28.90 - ONGOING-ISRUNNING-043300-298.TXT - ** ONGOING-ISRUNNING-043300-298.TXT DELETED - Status = 1,
That tells me that the instance from 04:32 must have still been running when the 04:33 instance started, but this time, only the instance from 04:33 needed to exit.
Could you also post your EXIT_2_INSTANCES.LOG file so I can see what was happening at around the problematic times?
Once we can confirm what causes the issue, I can build in some code to deal with it.
I see that your most recent upload to MDWS was timed at 05:59 this morning so it seems the problem is still present, unless you intentionally stopped the uploads or that you PC or ROUTER went into sleep mode etc.