Slashdot Mirror
Microsoft's BSOD Is Getting More Descriptive With QR Codes (cio.com)
itwbennett writes: Reddit user javelinnl posted a picture last week showing a new dreaded Blue Screen of Death (BSOD) featuring a QR code and a link that may appear in a future version of Windows 10. "Right now, the code and the link take users to a webpage that discusses generic fixes for errors that might cause a crash," writes Blair Frank from CIO. "In the future, though, Microsoft could provide a QR code that leads to more specific information about what caused the computer freeze up." As of this writing, Microsoft had not responded to Frank's request for comment, but when he forced a Blue Screen of Death on his Surface Pro 3, he was unable to get a QR code to appear, though a link to the help page did. The QR code shown in the image simply points to a generic resource page for "troubleshooting blue screen errors."
Like, I don't know, say, a system log that would store messages from drivers and system components like dmesg?
How about a memory dump before crashing that can be inspected later?
What makes you think that Windows does not store messages and does not create a dump (hint: it does. Stop errors are logged in the system log, and default is to create a dump file upon a stop error. Space is even reserved for the dump file on the system drive to guarantee that a dump can be created even if disk is full).
But hey, why don't you make your own assumptions and go by them to diss on something that you obviously don't know anything about?
When you restart your computer, Windows will recognize the dump file and will offer you to upload it to Microsoft. In case of device driver crashes (the most common cause along with hw fails) Microsoft will even notify the vendor if they have registered for crash information.
https://tech.slashdot.org/stor...
Reading slashdot one-liner: (irm http://rss.slashdot.org/Slashdot/slashdot).rdf.item | fl title,desc*
Like, I don't know, say, a system log that would store messages from drivers and system components like dmesg?
You mean like the windows event log which captures the cause of the BSOD and stores it for looking at later?
How about a memory dump before crashing that can be inspected later?
You mean the file c:\windows\minidump.dmp that is created when a BSOD?
Whatever happened to human readable error messages even?
Sure, care to name an example of an OS that provides a human readable error message for a complex issue that was able to cause the kernel itself to croak?
Stop reinventing the goddamn wheel, it's not gonna work if it's square.
The wheel hasn't changed. Only the shape of the check engine light is changing, and quite frankly that was always useless and broken.