Hi,
I've finally got some good news, for a change.
Yesterday and the day before that, two separate Microsoft support agents checked with the hardware team, and it turns out the issue isn't just known anymore, but it's known to be widespread and they have acknowledged that it is not a hardware issue, so they are working on a fix for it.