Windows 8 started this. They decided to copy Apple's useless OS X kernel panic screen, and so only give you one word of useful information, no error code, no exception information, etc.
Unfortunately the QR code might be an improvement over Windows 8 and 8.1 if the QR code contains more detailed information. There are scenarios where you cannot get to the event viewer (or WinDbg) and need to diagnose a pre-boot BSOD. Windows 8 made this almost impossible without attaching a kernel debugger.
Windows 2000 had the best BSODs because they not only told you the details of the crash but also told you which module caused it. This often allowed you to immediately know what the issue was (e.g. if it was in Creative or Nvidia's drives you'd know just from the filename). You can still get the module via WinDbg but it would be useful to have it on the BSOD itself or even in the event log listing.
PS - I strongly suspect the reason Microsoft removed the module name in the Windows XP BSOD was because they were hurting third party hardware vendor's reputation.
> Unfortunately the QR code might be an improvement over Windows 8 and 8.1 if the QR code contains more detailed information.
The QR code shown in the example screenshot is just a link to http://windows.com/stopcode - hopefully they'll improve it to at least include the bug check code.
Unfortunately the QR code might be an improvement over Windows 8 and 8.1 if the QR code contains more detailed information. There are scenarios where you cannot get to the event viewer (or WinDbg) and need to diagnose a pre-boot BSOD. Windows 8 made this almost impossible without attaching a kernel debugger.
Windows 2000 had the best BSODs because they not only told you the details of the crash but also told you which module caused it. This often allowed you to immediately know what the issue was (e.g. if it was in Creative or Nvidia's drives you'd know just from the filename). You can still get the module via WinDbg but it would be useful to have it on the BSOD itself or even in the event log listing.
PS - I strongly suspect the reason Microsoft removed the module name in the Windows XP BSOD was because they were hurting third party hardware vendor's reputation.