4 ms·

Yeah. You can actually change the behavior, so that the default is to just stay on the blue screen until the user manually reboots. Why someone ever thought aut

Yeah. You can actually change the behavior, so that the default is to just stay on the blue screen until the user manually reboots. Why someone ever thought automatic reboot was a good idea, or how they haven't bothered to change the default for 30 fucking years, is beyond me.

mrguyorama 4y ago
I thought the default was to reboot after dumping memory to disk as a dumpfile, which tended to give you ample time with slow hard drives. Somehow my system got itself into a state for a while where it had a registry key set to just not make dump files, and that key was not fixed even when using the normal control panel based settings panel that is meant to let you change those settings, OR the dedicated microsoft tool built to give administrators more control over BSODs. The correct way to troubleshoot a BSOD isn't on the BSOD screen anyway. You open up the dumpfile in windbg and click "analyze" so it can spit out some good details for you.
userbinator 4y ago
Why someone ever thought automatic reboot was a good idea For a server, which might only be accessible remotely, it is. For an interactive computer, I agree that it isn't. I believe this was a heritage from the NT series --- the 9x BSoDs just sat there and waited for you to reboot (except when things got so bad that it triple-faulted...)
Aeolun 4y ago
I think they’re probably preventing luddites from being stuck on that screen until they gather up the courage to press the reset button. For 99% of the people the error message is meaningless and the only thing they can do is restart, so it makes sense to do that automatically.
Beltalowda 4y ago
I don't recall Windows XP doing it back in the day. Or if it did, it didn't for boot errors like in Windows 10. I'm not sure because it's been a long time, but as I mentioned in my other comment, I had people come in with hand-written copies of all of the BSOD message, and you need some time for that (and fairly sure those folks didn't change some setting). Automatic reboot isn't so bad, but just change it to a minute, or 30 seconds, or "press a key to abort reboot". An intern can do this. Hell, I'd send a patch, let me just find the Windows repo on GitHub...
- jaclaz 4y ago
  Rest assured that not only XP, even 2000 did the same, and of course it did BSOD when booting, the most common being 0x0000007b "Inaccessible boot device". But automatic reboot is a setting in the Registry, the issue is just with the default being "reboot" (I believe this was changed in XP, 2K just stayed on the BSOD by default, if I recall correctly).

mrguyorama 4y ago

I thought the default was to reboot after dumping memory to disk as a dumpfile, which tended to give you ample time with slow hard drives. Somehow my system got itself into a state for a while where it had a registry key set to just not make dump files, and that key was not fixed even when using the normal control panel based settings panel that is meant to let you change those settings, OR the dedicated microsoft tool built to give administrators more control over BSODs. The correct way to troubleshoot a BSOD isn't on the BSOD screen anyway. You open up the dumpfile in windbg and click "analyze" so it can spit out some good details for you.

userbinator 4y ago

Why someone ever thought automatic reboot was a good idea For a server, which might only be accessible remotely, it is. For an interactive computer, I agree that it isn't. I believe this was a heritage from the NT series --- the 9x BSoDs just sat there and waited for you to reboot (except when things got so bad that it triple-faulted...)

Aeolun 4y ago

I think they’re probably preventing luddites from being stuck on that screen until they gather up the courage to press the reset button. For 99% of the people the error message is meaningless and the only thing they can do is restart, so it makes sense to do that automatically.

Beltalowda 4y ago

I don't recall Windows XP doing it back in the day. Or if it did, it didn't for boot errors like in Windows 10. I'm not sure because it's been a long time, but as I mentioned in my other comment, I had people come in with hand-written copies of all of the BSOD message, and you need some time for that (and fairly sure those folks didn't change some setting). Automatic reboot isn't so bad, but just change it to a minute, or 30 seconds, or "press a key to abort reboot". An intern can do this. Hell, I'd send a patch, let me just find the Windows repo on GitHub...

jaclaz 4y ago
Rest assured that not only XP, even 2000 did the same, and of course it did BSOD when booting, the most common being 0x0000007b "Inaccessible boot device". But automatic reboot is a setting in the Registry, the issue is just with the default being "reboot" (I believe this was changed in XP, 2K just stayed on the BSOD by default, if I recall correctly).