Windows 10 BSOD Getting QR Codes

HardOCP News

[H] News
Joined
Dec 31, 1969
Messages
0
I wasn't sure if the picture in this reddit thread was legit at first but, after some digging around, this is in fact the real deal. Apparently the upcoming free Anniversary Edition of Windows 10 will use QR codes in its BSOD screens to help you know why your system crashed.
 
The perfect thing for the many places where use of mobile phones is not allowed or not possible.
 
That's actually a really good idea. Too bad the actual errors will still be completely useless.
 
This seems like a great idea. Instead of trying to copy down arcane error codes, and making sure you got the right number of 0s and Xs, you can just scan the QR code. Now, of course this requires the resulting screen to actually MEAN something...
 
Makes sense and this is one of the few rare instances where they're helpful. The URLs would almost certainly be too long to type, so this covers that base.
 
Honestly love this idea. Quick way to get to the error code definition rather than typing the bugcheck code into Google and looking for the MSDN Bugcheck list.

Then I'd continue my normal troubleshooting procedure of pulling the Minidump file and analyzing it in WinDbg.
 
After scanning the QR code, Microsoft does a check on the device querying the info. If it's Android it's immediately converts it to a Windows Phone, if it's Apple it does the Inspector Gadget in a number of seconds this message will self destruct *boom*.

Magically your blue screen will be resolved followed by a traditional screening of All Ur Base.
 
Instead of trying to copy down arcane error codes, and making sure you got the right number of 0s and Xs.... Now, of course this requires the resulting screen to actually MEAN something...

Well, playing NES Punch Out, Metroid, and Faxandu, I'm a pro at that!! :)

Anyway, yes. I find some recent blue screens are kind of a 'shit happens' kind of thing (especially when the new QR BSOD just says "it's all good, we're fixing it and you'll be back in business in no time.." However, I remember getting a blue screen on Win NT and it meant you actually better fix some shit because something is totally wrecked.
 
Like damn. MS can actually innovate. It's a small but good idea, just wish this "feature" shipped with Windows 8 back when they ran out of ideas and decided to make all desktops into tablet UI.
 
So now I need to scan the QR code to get the overly general hexadecimal error code to not solve my problem? On the flipside, at least I don't have to type a 10 digit hexadecimal on my cell phone to find out my error is either because I set my system clock wrong or the extremely helpful "something else."
 
So now I need to scan the QR code to get the overly general hexadecimal error code to not solve my problem? On the flipside, at least I don't have to type a 10 digit hexadecimal on my cell phone to find out my error is either because I set my system clock wrong or the extremely helpful "something else."

It still tells you what the STOP code is, if you take a look at the screenshot that's linked to. Also, you only have to type in the "0x##" into google - all the extra 0's aren't necessary :p.

I feel like I'm the only one here that finds a use on the MSDN Bugcheck site to find out the cause of a BSOD...lol. I get more use out of that 80% of the time than random message board posts with "OMG MUH COMPUTER CRASHED HALP ME" and no resolution, and the post is 6 years old.
 
I don't know what you guys are doing but I normally can figure out the issue with the code, mini dump and/or google.
 
So what happens when your Windows 10 phone (the device you'd be scanning the QR code with) is the one that blue screens?
 
I ain't praising this one, a QR code is usually nothing but an easy way to 'type' a link.
Gotta love the irony of trouble shooting your windows computer with your android cellphone.... kind of like rescuing your windows PC with a bootable USB linux OS, so you can connect the internet, troubleshoot, download drivers and such.
So ironic its delicious.
 
Heh, might be a good idea if I kept my cell phone on once I got home.

I could make Windows 7 blue screen fairly easily by screwing up on the descriptor on a USB embedded device I was working on.
 
Sounds like the never helpful Windows Troubleshooter all over again.
 
If the QR codes would lead to prizes, I may finally have a reason to reinstall Geforce driver version 364.72!
 
So....they want us to scan a QR code, to read about the issue using our phones??? Really?How about once it gets back to windows, it just gives a me a link to click on?
 
I can't wait - my Win10 tablet BSOD's for no apparent reason at least twice a week. Yes, I've tried a full system restore, and I've tried a full hardware test.
 
So....they want us to scan a QR code, to read about the issue using our phones??? Really?How about once it gets back to windows, it just gives a me a link to click on?
I like that suggestion, but if you're having issues getting into windows (which can happen), then this is a nice way in and it's a bit easier than doing a manual web search.

Honestly, back when I got BSODs, I often took pictures of the BSOD page. This does it one better by opening a page with info on the issue.
 
I ain't praising this one, a QR code is usually nothing but an easy way to 'type' a link.
Gotta love the irony of trouble shooting your windows computer with your android cellphone.... kind of like rescuing your windows PC with a bootable USB linux OS, so you can connect the internet, troubleshoot, download drivers and such.
So ironic its delicious.

That point of view is rather dumb in my opinion. You use the tools you have available to you, who cares what it is as long as it works. :rolleyes: Of course, I suppose you will run away from a Windows computer to help fix a Linux machine? Or the irony. :D :wtf::facepalm::stop::yuck::dead::unsure: LOL ;)
 
Back
Top