I guess the BIOS is responsible for handling the conversion of some key sequences into extended ASCII, so plausible it could be buggy in this way (but not so plausible for the OP issue). The link doesn't seem to mention a BIOS update or acknowledge it as a known BIOS issue though?