That's silly. I think, as long as the BSOD gives a clear message, it's good enough. What really needs work is Microsoft application errors. Windows Update, Windows Mail, etc. 0x80###### error codes are so vague, explain nothing, point to answers.microsoft.com (which is beyond useless) and many of them have no known solutions other than to reinstall the OS because Microsoft doesn't provide an option to reinstall the broken program. They even point to "FixIt" tools that more often than not don't fix it.

If Microsoft wants to help on the BSOD front, the first thing they should do is disable the default to automatically restart. People don't even realize something is wrong when they don't see the BSOD in the first place. They should also remove all of the generic crap on the BSOD and only include the information that is useful for fixing it. It should be something as simple as:

HARDWARE FAULT:
0x0000000A IRQL_NOT_LESS_OR_EQUAL
IRQL # (DEVICE NAME)
READ

Advisement:
-Run hardware diagnostics (especially memory)
-If memory was recently added, remove it.
-Reseat memory.

You know...something that's actually meaningful and useful.

99% in my case of blue-screen of death is hardware issue

FordGT90ConceptThat's silly. I think, as long as the BSOD gives a clear message, it's good enough. What really needs work is Microsoft application errors. Windows Update, Windows Mail, etc. 0x80###### error codes are so vague, explain nothing, point to answers.microsoft.com (which is beyond useless) and many of them have no known solutions other than to reinstall the OS because Microsoft doesn't provide an option to reinstall the broken program. They even point to "FixIt" tools that more often than not don't fix it.

If Microsoft wants to help on the BSOD front, the first thing they should do is disable the default to automatically restart. People don't even realize something is wrong when they don't see the BSOD in the first place. They should also remove all of the generic crap on the BSOD and only include the information that is useful for fixing it. It should be something as simple as:

You know...something that's actually meaningful and useful.

M$ helping computer repair technicians to earn their bread and butter.:p

FordGT90ConceptThat's silly. I think, as long as the BSOD gives a clear message, it's good enough. What really needs work is Microsoft application errors. Windows Update, Windows Mail, etc. 0x80###### error codes are so vague, explain nothing, point to answers.microsoft.com (which is beyond useless) and many of them have no known solutions other than to reinstall the OS because Microsoft doesn't provide an option to reinstall the broken program. They even point to "FixIt" tools that more often than not don't fix it.

If Microsoft wants to help on the BSOD front, the first thing they should do is disable the default to automatically restart. People don't even realize something is wrong when they don't see the BSOD in the first place. They should also remove all of the generic crap on the BSOD and only include the information that is useful for fixing it. It should be something as simple as:

You know...something that's actually meaningful and useful.

You can dig deeper with debug tools and eventually you might find something clear cut, but yes it is a lot more cumbersome than it should be. But I know to little about the inner workings of things to say how a simpler system would work. And to be fair there is a massive amount of things in a computer that can be faulty.

I had issues with a system I thought was first memory related, then GPU, and then PSU with vauge error codes and event logs not saying much, but using a debugger I found a statement actually saying that the problem was ... I think it said either corrupt registers in the CPU or some communications in the motherboard. That the error, not shown in any error log apart from what I found with a debugger, was due one of two things. And seeing how CPU's are bulletproof it was obvious the motherboard was at fault, and it was. But the interesting part is that that useful error messege didn't really exist anywhere accesible.

FordGT90Concept
a slight edit

Windows 10 has detected
HARDWARE FAULT:
0x0001001A Old Hardware

READ

Advisement:
-Run hardware diagnostics (especially memory)
-If memory was recently added, remove it.
-Reseat memory.
Upgrade to Skylake System

FrickYou can dig deeper with debug tools and eventually you might find something clear cut, but yes it is a lot more cumbersome than it should be. But I know to little about the inner workings of things to say how a simpler system would work. And to be fair there is a massive amount of things in a computer that can be faulty.

I'm of the belief that computers have so much RAM these days, BSOD messages should always be loaded into the system memory for immediate access. When the fault occurs, it should be able to dump all of the important diagnostic assets to the display instantly. There's also no reason why it shouldn't be able to ask for a USB stick to dump everything on to. Using the USB stick as a buffer (because the operating system volume can't be written to for data integrity sake), it could even self-diagnose using it and narrow it down as you've described.

It shouldn't require internet access on any device to diagnose; QR codes are a step in the wrong direction as far as I'm concerned.

matar99% of blue-screen of death is hardware issue

How do you figure? Almost all of the blue screens I've encountered have been device drivers.

matar99% of blue-screen of death is hardware issue

I have seen more software issues (corrupt os/bad drivers) than anything else. It is rare to see a BSOD for hardware that I have seen.

cdawallI have seen more software issues (corrupt os/bad drivers) than anything else. It is rare to see a BSOD for hardware that I have seen.

I my case it was always hardware issues.

matarI my case it was always hardware issues.

You're around way too much defective hardware LOL

Locating individuals running W10 OS will be much easier...