I've always understood that technical details cause technical problems in technical products/applications.

If you can isolate the problem down to one airport [in your specific case you already have] then that automatically eliminates a number of impossible answers to the problem.

Garmin has an list of current radio frequencies that cause problems with the 496. This could be a source of the problem, given some of the uniqueness in frequencies at various airports, if one or more of those frequencies are utilized in your aircraft on or around this particular airport.

The error message itself is not necessarily indicative of the source of the problem - especially with type 1 errors that come from human generated code.

But, if all you want to know is if other pilots are having the same or similar problem and you don't care to fix it, this probably won't help much either. Good luck with that.