Recently, Robert M. Gary posted:

Neil Gould writes:
I don't think that's possible. There is no provision for the display
system to reboot the hardware; that just isn't done via software,
or even by physical switches located on the display unit(s). The
display
unit(s) can't turn on or off the individual modules either, so a
software
glitch of any kind -- or even total failure of the display -- isn't
able
to be the cause of a system-wide reboot.

A reboot of an individual display would not surprise me (although I've
never seen it happen). A reboot of both would surprise me.

Do you mean a display failure rather than a reboot? Anyway, as I
understand it, there is no facility for the display to reboot the
individual computers

However,
NW_pilot's issue was a software bug associated with the long range
tanks that were installed. I guess the computer failed working out the
fuel calculations. Since both sides run the same software, both sides
probably had the same fault.

That is my guess as well, based on the information from the seminar. As I
understand it, the G1000 would disable (red "X") the readout of any
component with an unresolvable conflict. Since the aux tank was
"refilling" the main fuel tanks via the overflow return, it wouldn't be
long before the flight computer data would be in conflict with the fuel
level sensor and therefore generate an unresolvable error. It should be
expected that both displays would show the same error condition.

Neil