@toadofsky @fatsam The Boeing 787 has had quite a few time-related problems.
In mid-2015, the FAA reported the generator control units (GCUs) would all simultaneously hang after about 248 days of uptime, causing a total outage of AC power to the aircraft. The workaround was to reboot all of the GCUs after no more than 120 days up. https://arstechnica.com/information-technology/2015/05/boeing-787-dreamliners-contain-a-potentially-catastrophic-software-bug/
Then in late 2016, they reported all three flight control computers could hang after 22 days up, leading to loss of flight control until they were rebooted. The workaround was to reboot them every week. https://www.seattletimes.com/business/boeing-aerospace/faa-orders-787-safety-fix-reboot-power-once-in-a-while/
In early 2020, there was another problem which could result in the control network crashing or in weeks-stale data from a wide variety of plane systems being shown to the pilots as if it were current. Again, the workaround was to reboot the whole plane every three weeks. https://www.theregister.com/2020/04/02/boeing_787_power_cycle_51_days_stale_data/
While these are all likely to be accumulators which overflowed, they all mean Boeing software is not developed particularly rigorously. I could definitely see a timestamp which the plane thinks is invalid causing flight control or engine control to go unresponsive. Particularly things tracked by rate—when the timestamp overflows, the rate will be wildly nonsensical until the full rate window is past the overflow.