I understand what you're saying, but in fact most of those errors require a couple of paragraphs to explain in a useful fashion, not "a few dozen characters". What you could say in one phrase would have to be so compact that it wouldn't mean much to most people and they'd have to google it anyway. When you google the code, you're going straight to it. Googling a phrase is far less precise.
If you ignore the fact that the error code happens to be hexadecimal and just think of it as a name, it actually is a very good way to get an explanation that is known to be correct. I know, that's not a particularly satisfying answer....
It’s like answering the question “Where do babies come from?”.
The answer given by microsoft is encrypted for a post-doc biologist, and even they aren’t expected to now the minutia inplied in the code word, they expect them to either nod and acknowledge microsoft’s vast intellectual superiority, or to look it up in a vast index and trace out all the chemical, hormonal and physical pathways.
Most users would like a an answer more like one you would give to an 11 year old, enough to give a general idea without burdening them with graphic details. - ‘Oh! The printer and the computer aren’t quite speaking the same language! I get it!’
They don’t want a gobbledygook answer with a bland suggestion that they go to the local university and look it up in an advanced biology text.