I was referring to the Scarebus 350, actually and the offending rollover was about 150 days... but coming from the Avionics world such things don't surprise me regardless of model of a/c. (And Boing and Scarebus buy avionics from many common suppliers re-using tons of code modified for each model and variant...).
As to resetting, fuel load is usually less than, say, 24 hours worth. So based on various conditions that indicate the aircraft is safely on the ground (squat switches, airspeed_trend, groundspeed, parking_brake_set, etc. and so on) it would be easy enough (though not trivial) to implement resets of certain counters (etc.) after x hours and while state=parked_at_gate. Of course that becomes a requirement which becomes a testable item which becomes ... or simply when the offending parameter(s) exceed(s) a threshold (and state=parked_at_gate) then run the reset procedure(s). Depending on the criticality level of the box, the costs of such could be quite high.
Easier to force that box to re-boot (while safely at the gate, of course).
Depending on what bus(es) a box is connected to, it can "listen" for various parameters even if it is not usually a user of a given parameter. Otherwise other boxes would have to be programmed to provide the offending box with the reset command (when, ... you know).
(I don't know if it is actually done that way, but that is a way it could be done).