There are some interesting precedents for these types of problems that came to light back in 1999/2000 when US federal government and military commanders were auditing their systems for potential issues with the Y2K or 'Millenium Bug'
The later arose from incorrect date stamps being generated in older software, compounded by many programmers who failed to realise that the year 2000 was in fact a Leap Year under Gregorian calendar rules (divisible by 400).
One report from NORAD's control center in Cheyenne Mountain Colorado said:
NORAD was responsible for conducting test to determine what would happen to their computers in the event of a warning or nuclear attack on January 1, 2000. As a result, everything froze. The screens that monitored early warning satellites, radar, and other communications systems all locked up at the stroke of midnight. Without these computers functioning as normal, mission-critical systems were halted and the military could not proceed with missions as scheduled.
"Y2K Problems In Military Software" (Austin.Grant.Pham.Samuel.Stewart) - University of Phoenix March 2002.
Another report on the US spy satellite system reported:
United States spy satellites transmitted unreadable data for three crucial days. The bug was caused by a patch which was supposed to fix a Y2K bug, but caused the satellites to mangle data transmissions back to Earth. The complications came at an uneasy time, as there were serious fears of terrorist attacks in the first few days of the millennium.