Wondering if anyone has encountered this before. Our lab has been using STARs for years but this issue is suddenly cropping up. Run Control will close without warning and the method will stop in its tracks. Windows Event Viewer shows an error for HxRun.exe. Previously, we have been told to make sure we have the latest version of Windows Visual C++ distributable, which we do. I’d appreciate any experiences or insight!
Hi Tony,
Would you be able to share the event logs you mentioned from the time of the last crash? There can be numerous reasons as to why an application crash would happen besides corrupted or missing MS Visual C++ redistributable components.
You can upload files to this link (password: Hamilton24)
Thanks.
-Nick
Hi @NickHealy_Hamilton, I hope you are doing well. We are dealing with a related issue on some of our Hamilton PCs. Could you share with me how the above error was resolved? I can provide you with additional information and follow up in email if that is easier. Thanks!
I don’t believe we received any additional materials to try and troubleshoot so this thread has not been resolved.
I followed up with you separately - as Nick mentions, there can be many reasons to cause the crash so it’s best to focus on your specific setup.
Thank you,
Eric
1 Like
Hi @czimage we’ve had similar issues on one of our PC’s. I received a file from Hamilton to monitor certain crashes and then dump the memory to a file. In our example it turned out (untill now, because I haven’t found a true issue) that a full reinstall of Windows 11 Pro, including all drivers updated (Bios,GPU etc.) resolved the issue. My educated guess would be that a driver was corrupt or an issue with memory that we resolved somehow.
If you are able to run a program like Memtest86 you could check the health from your memory and rule that out as a factor.
Hey Folks,
we are encountering a similar issue where Venus 6.2 run control will crash with no error indicated.
This is especially painful when running methods with expensive consumables.
The method is shown as complete in the run control and as running in the trace viewer, whilst the robot (STARlet) is frozen.
I run Venus on a Virtual machine company laptop, but locally with no network connection.
Does anyone has an idea what could cause this behavior?
1 Like
Hi @Cem96,
There are a lot of potential causes for a Run Control crash: memory issues, graphics issues, file corruption, method-specific errors, etc. I suggest working with your IT group to check the Windows Event Viewer logs around the time of the crash to obtain more specific information as to what is going on.
Thank you,
Dan
1 Like
What do the firmware logs say? I’ve never seen this happen on a Hamilton but I’ve seen very similar occurrences on other equipment and sometimes the issue was the cable itself being excessively bent which causes the serial driver to weirdly hang forever while waiting for a response.
Powershell can give you a lot of ability to diagnose issues like this and figure out where in the call stack the problem is. I would guess it’s either a memory fault or a physical signal issue.
1 Like
Hey There,
thanks for the quick replies.
It was a cable issue, Heatershaker and The Starlet where connected to the PC via a usb Hub.
After removing it, everything runs reliable again.
Honesty I dont know how this worked all the years.
3 Likes