Just a general question - windows crash on program crash

[Fractured]

Good morning folks! ? Just a general question. The "lovely" engineers here at work have written test software that tends to crash. Causing VISA errors, memory errors, etc. that then kills windows 10...explorer restarts, black screen, death.....

Is there away to write a proggie that can clear out the memory, clear the VISA errors/ports, and recover the environment without having to restart windows, which then takes 20 minutes to restart and not always fix the problems created without restarting again! 

Just a general query, no coding required at this time, just trying to get an idea of how to handle this multi time a day issue!!

 

Thanks!

[JLogan3o13]

It is not the right way to go about it. Trying to manually clear all the systems (memory, cache, etc.) that happens on reboot is just as likely to cause an issue as the buggy software you're dealing with (which you would then get the blame for rather than your engineering team). Best to document the issue heavily and keep on your management to make them resolve the issues they have introduced, rather than adding another layer of complexity to try and circumvent their mistakes.

[Fractured]

@JLogan3o13 Thats what we have been doing for about a year and a half. The problem is that Engineering is controlled by corporate, while we are constrained by the building manager. The issues are heavily documented but our corporate doesn't really care as long as it is not effecting their money too much. 

Your point is well taken though and I shall just keep slogging through. The problem is they use Labview to create all their test programs, which seems to be a major memory hog and very laggy. If there is the slightest deviation the program chokes hard and just crashes taking everything with it.. Hence hoping there was a way to write a mitigation program to keep it from nuking everything at one time!

Thanks!!

 

[JLogan3o13]

One thing I did, way back when I started in IT and encountered a similar issue, was learn the software they were using to create their homegrown app. Then, when I was able to start pointing out exactly where their coding mistakes were, I began sending "helpful" emails with suggestions on fixes in their code, ensuring I cc'd everyone I could think up the corporate ladder. Having a desktop engineer point out the developers' mistakes was not something anyone wanted to endure for long.

Of course, you might not choose to take the jackass route like I did 😃

[Fractured]

@JLogan3o13 Actually that is route is exactly up my alley!! hehe

Guess its time to learn Labview!