My hypothesis is that the software update was done prior to the problem (e.g. off-hours) but that location triggered the bug. This could be as simple as a map update that confused the s/w.