cRio VI Stops Executing after exactly 80 min

[NatineInsula]

On my two cRIO controllers (both NI cDAQ 9171 + NI 9403) working almost flawlessly during 8 years, on the last weeks, both VIs now stop working after exactly 80 minutes. One started failing within weeks of difference.

I have inspected these logs /var/log, /var/volatile/log, /var/local/natinst/log/, /var/local/natinst/tracelogs, and I have been unable to find any valuable insight about the problem.

So we do not have any clue about the error, since it happens after a successful operation, and now it behaves so smoothly stopping after 80 minutes each time after remote reboot.

Since we don't have easy direct physical access, we cannot do physical procedures into it (such as recompile the VIs) and update everything.

How can I know which error is causing this problem?

[wiebe@CARYA]

How exactly 80 min? 80.0? 80.00? Or 71.6 (2^32 = 4,294,967,296 ms)?

Are there any watchdogs in place? One that stopped being whacked?

[NatineInsula]

The system turned into a 4810 s period clock (?!).

No, there is, and never during these years any watchdog timer or any auxiliar program has been placed. I suspect some NI manufacturer condition (which one?) has been activated for some reason.