I suspect this gets pushback internally because the descriptive error message baked into the OS is often wrong or misleading. Having a code you can look up can provide a lot more context.

The forums usually take a while and a while and a lot of back and forth to arrive at a solution that works for maybe 80% of people under most circumstances, but is usually more of a workaround than a proper fix. (And there isn't necessarily just one cause of the error code, or one solution. The console doesn't know which is which without situational judgment)

The error codes are sort of a self service mechanism for advanced users who want to try unofficial troubleshooting. They're not a substitute for a real patch fixing the root issue.

Sometimes it can - the only time I've had this work, I had a bluescreen, on next startup Windows told me it was because I needed a driver update.

I think there's some path where driver devs can publish updates and link them to BSOD stacks which lets Windows tell users if they hit a bug that is fixed by a driver.

This was like 10+ years ago and I've never hit the same flow again, despite encountering bluescreens every once in awhile, which I guess goes to show how difficult this problem is.

You are assuming that this is not the first instance of this error code showing, this is the only error affecting the device, the device has internet access.