I'm not sure what is causing it, but since it happens after several hours it sounds like it might be a "memory leak" where an array allocation or something of that nature is growing, not being properly deallocated, and eventually hitting a memory boundary. Could you give us a little more detail what you are doing, also there are somethings that have caused that type of problems in the past. A search of previous posting, etc. for memory leak produces a number of threads. Also to look for this one might start the program and note the amount of memory LabVIEW is taking using the "Task Manager" in Windows. Then looking at the numbers a while later (an hour or so) should tell you pretty quickly if this is an issue.
PutnamCertified LabVIEW Developer
Senior Test Engineer North Shore Technology, Inc.
Currently using LV 2012-LabVIEW 2018, RT8.5

LabVIEW Champion