Strange Error affecting All CMMs: Critical Error

From your description I would definitely try just running the programs normally without all of your custom addons/software/reporting. I have gotten similar errors using other CMM software. It can be very hard to figure out exactly what is causing the error but generally its due to long nested loops with lots of variables being written to and read from repeatedly. It is trying to write to an available memory space it thinks is empty but is not. Basically your program is too complicated which is what I would expect running big programs from custom in-house spaghetti coded software. It doesn't actually have anything to do with the amount of RAM.

From your description I would definitely try just running the programs normally without all of your custom addons/software/reporting. I have gotten similar errors using other CMM software. It can be very hard to figure out exactly what is causing the error but generally its due to long nested loops with lots of variables being written to and read from repeatedly. It is trying to write to an available memory space it thinks is empty but is not. Basically your program is too complicated which is what I would expect running big programs from custom in-house spaghetti coded software. It doesn't actually have anything to do with the amount of RAM.

"spaghetti coded software"

Unfortunetly, I can't run any programs without that software in the long term. We are measuring many parts per day, and without it, the programs can easily get confused, leading to crashes when the wrong program is selected for a part. It, in general, is used for program management in many other ways too, that would be a hard sell to get rid of. I could, though, contact the original creator of the software. Is this error more likely caused by the launching software do you think? or just the overall complexity of the program?

I'd bet money on it being the launching software. It would have to be a really complicated CMM program otherwise. and nobody really makes those kinds of programs which is why everyone in this thread is just speculating as to what is causing your issue. Given what you've said your only real option is to rewrite that software pretty much entirely. Which is not actually as big of a task as it sounds. I guarantee that code is a regular dumpster fire if one person made it.

Further, it's happening on every machine and and presumably when running different part numbers. Think diagnostically, there is really only one common thread between all of these crashes.

Maybe a memory leak someplace due to time being a factor, its not every time, its not every program, but only happens after a length of time? 
Restarting the PC clears the memory and they just start it all over again? 

IDK, I just make the machine go beep beep beep all day. 

that's why they call you.....

Indeed. So they tell me anyways.... 

Sounds like your facility might be able to skip the monthly fire alarm test... Beep Beep...

Time to go home...

Haha! We just had that today. Its more of a whooping sound though. The only one we really care about is the tornado alarm, pretty sure we will all know if the building is on fire, but tornados are hard to see through the metal walls