???? Well, I guess you are proud to be an uneducated redneck. Just because it is useless to *you*, doesn't mean it is useless to everybody. To some of us, it is essential that the exception code be easily available. If it doesn't appear on the last screen the machine can put up before coming to a complete halt, where would you suggest it go? To a log file, when the file system might not be working? *sheesh*. Really, I'd like to hear where else you think it could be recorded in a manner that is both 100% reliable and easily accessible without specialized diagnostic equipment.
BTW -- 99% of the blue screens were 0E exceptions -- "invalid page fault". In other words, a page fault in the kernel. Page faults are only valid from user space code. In 99% of *those* cases, the cause was a driver bug where an I/O driver should have wired down a page so that it would not get swapped out while it was the I/O source or destination. Microsoft got tired of getting blamed for shitty third party drivers, thus we now have signed driver code.
Let me tell you, if you don't get an error code at a machine halt, the next step is to start hanging logic analyzer probes. Then when your bench tech is done hanging probes you get to come back and spend the next several hours staring at logic analyzer traces. Been there. Done that. Got the tee-shirt -- literally.