This freaked me out so much when i came home from school and saw my dad on the 98se pc trying to fix the blue screen (I knew what it was because I was and still am an is nerd, and no, im not born 30 years ago, even then we considered the computer retro) which panicked me so much
1:37 We’ve all been there before. We all have those irrational frights and fears about BSODs (90's kids rejoice!) Sad Mac anyone? (Oh don’t even get me started on that…)
I think the reason why Windows 98 blue screened in that 1998 COMDEX demonstration, was likely because the guy next to Bill Gates moved the scanner while it was initializing the USB driver. Notice early on in that clip (the part where the guy jokingly said, "That's an everyday task.", shown between 4:00-4:06), he had trouble plugging in the USB cable to the computer, then after it blue screened, notice that the guy next to Bill Gates was holding the USB slot scanner (shown between 4:14-4:15) before he put it back down and said: "...Moving right along..." after the BSOD. Even with a slot scanner like the one used in that demonstration; any USB device should NEVER be moved while it's powered on and initializing. It's also possible that the USB cable might have not been fully connected and the USB connector slightly got "unplugged" during the initialization process after when the host (next to Bill Gates) put the slot scanner down. It's also possible that the USB driver may have been intended for Windows 95 B/C and may have not been compatible with Windows 98.
Windows 8 from memory in it's early development had a black screen placeholder for the new lighter colored blue screen with the frown icon. Some builds of Longhorn replaced a Blue Screen of Death with a Red Screen of Death. Windows Insider Preview builds starting sometime in the interin development builds of windows 10 feature updates changed the blue screen of death to the green screen of death for some reason. Windows 11's blue screen of death was a black screen of death for a while before quickly being reverted back to a blue screen, although a darker shade of blue. Windows 1.x and 2.x have an unreadable blue screen that was never officially declared as a blue screen of death. Instead, lines flashed on top of the operating environment to indicate a system crash.
Some time in 2003 or 2004, had gotten up early, maybe an hour or so before school to play a bit of Midtown Madness 2 on my PC which had Windows ME on it. Was going fine, but then it got a BSOD & gave me a good spook i'll say (only 10 years old at the time i was) and kind of ran back to my room even. Did say anything & whatnot, just saw that screen, PC shut off i think & yeah, that happened. That's the worst the good old blue screen had affected me, almost 20 long years ago now.
@@jacquelinedelossantos426 Sure gets a bad rap, but apart from that one issue i had almost 20 years ago, it's never done me wrong. Works just fine on the various older PC's i own, and hasn't randomly bluescreened on me at all, since i'd started using it now & again back in 2015
The GSOD for insider builds was introduced in Windows 10 Creators Update build 15002. However, if a BSOD occurs before the system is booted, it's still blue. Windows 11 would later revert to a (darker) blue in an update to the initial release. Not sure why it was black in Windows 11 to start. Windows 10 Fall Creators Update build 16170 introduced the ability to trigger a black screen bugcheck by holding the power button for 7 seconds. This only works on devices where the power button must be held for longer than 7 seconds to force shut down. I'm not sure why this feature was implemented, because if the system is frozen, you would never reach this screen and instead keep holding the button until it force shuts down. Luckily they fixed that uninstall updates BSOD from build 22543!
These are my answers and/or guesses for the bonus mini-game at 3:09: 3:11 Windows NT 3.1 (first NT version to feature a BSoD on release) 3:16 Windows 9x CD drive error (?) 3:22 Windows 98 ACPI RSoD 3:27 Windows 2000 build 1796 (first BSoD using BOOTVID.DLL with black screen bug) 3:30 Windows Me build 2419 Safe to Shutdown (replaced with standard 9x version in the final) 3:35 Windows 8 build 7880 (Hi-res Windows XP-7 BSoD using VBE2) 3:40 Windows 8 build 7899 Black Screen 3:46 Windows Server 2016 (also Windows 8/10 Japanese version) 3:50 Windows 8, 10, 11 Insider GSoD (Green Screen) 3:55 Windows 11 RTM 22000.194 Black Screen
Here are my notes from this video: there was a blue screen in Windows 1.0 and 2.0, but those are a result of a bug in the Windows logo code when installing an unsupported DOS version. Those systems will usually freeze and/or exit to DOS when they crashed. Additionally, Windows Server 2012 onwards and Japanese versions of Windows 8, 10, and 11 do not feature a sad emoticon. And oh man, gotta love that famous Windows 98 COMDEX BSoD moment! Fun times…
2:33 80×50 isn't pixels, it's characters in text-mode. The characters were 8×8 which means 640×400 pixels. They switched from 80×50 text-mode to 640×400 graphics mode.
I don't know why, but for a very long time, exiting OBS Studio on my Windows 10 machine always caused BSOD no matter what. I still don't know why it happened. Even if for a long time, updating OBS wouldn't fix that. But since updating OBS to a newer version, it has stopped BSOD'ing my PC, thank god.
What particular build was that first Windows 8 beta one? Looks like a higher-resolution version of the classic XP-7 BSOD with anti-aliased text; never seen that one before so I assume it was an earlier build from before the public Developer Preview.
0:59 "initially using a black background, the colour would be changed to blue starting in Windows 3.11 in 1992" Hang on doesnt Windows 1 not have a BSOD? If I remember correctly its a garbled mess.
It technically wasn't a blue screen, nor referred to as one at the time. The term "Blue Screen" has kinda been retroactively applied to it (as it has for the similar screen in Windows 2).
Good question! I don't think the reason is known. Maybe to make it a bit more arresting/to distinguish it at a glance from DOS or an ordinary DOS app, maybe? (Although, now that I've said this, I remember there were MANY blue DOS apps, lol.)
1st Windows NT 4.0 2nd Windows Me 3rt Menphis build 1351 4rt Windows Vista 5th Windows Me 6th Windows XP 7th unknown 8th Windows 10 9th Windows 11 10th Windows 11
3:07 VMware SVGA 3D driver used. Disabling it would result in the BSOD in native resolutions and Windows Insider BSOD in green instead of 640x480 blue.
I got BSOD On Windows 11 22H2 Because It froze And BSOD, and shrinked to 1366x768 for gpu issues and got uninstalled after BSOD. Also i needed to reinstall the driver
This freaked me out so much when i came home from school and saw my dad on the 98se pc trying to fix the blue screen (I knew what it was because I was and still am an is nerd, and no, im not born 30 years ago, even then we considered the computer retro) which panicked me so much
1:37 We’ve all been there before. We all have those irrational frights and fears about BSODs (90's kids rejoice!)
Sad Mac anyone? (Oh don’t even get me started on that…)
@@johnnycha well i never got a Mac and don't think I'm ever going to anyway lol
in the end did you find the cause of BSoD? maybe HDD fail?
I think the reason why Windows 98 blue screened in that 1998 COMDEX demonstration, was likely because the guy next to Bill Gates moved the scanner while it was initializing the USB driver. Notice early on in that clip (the part where the guy jokingly said, "That's an everyday task.", shown between 4:00-4:06), he had trouble plugging in the USB cable to the computer, then after it blue screened, notice that the guy next to Bill Gates was holding the USB slot scanner (shown between 4:14-4:15) before he put it back down and said: "...Moving right along..." after the BSOD.
Even with a slot scanner like the one used in that demonstration; any USB device should NEVER be moved while it's powered on and initializing. It's also possible that the USB cable might have not been fully connected and the USB connector slightly got "unplugged" during the initialization process after when the host (next to Bill Gates) put the slot scanner down. It's also possible that the USB driver may have been intended for Windows 95 B/C and may have not been compatible with Windows 98.
Windows 8 from memory in it's early development had a black screen placeholder for the new lighter colored blue screen with the frown icon. Some builds of Longhorn replaced a Blue Screen of Death with a Red Screen of Death. Windows Insider Preview builds starting sometime in the interin development builds of windows 10 feature updates changed the blue screen of death to the green screen of death for some reason. Windows 11's blue screen of death was a black screen of death for a while before quickly being reverted back to a blue screen, although a darker shade of blue. Windows 1.x and 2.x have an unreadable blue screen that was never officially declared as a blue screen of death. Instead, lines flashed on top of the operating environment to indicate a system crash.
Some time in 2003 or 2004, had gotten up early, maybe an hour or so before school to play a bit of Midtown Madness 2 on my PC which had Windows ME on it. Was going fine, but then it got a BSOD & gave me a good spook i'll say (only 10 years old at the time i was) and kind of ran back to my room even. Did say anything & whatnot, just saw that screen, PC shut off i think & yeah, that happened. That's the worst the good old blue screen had affected me, almost 20 long years ago now.
Windows ME is a bad OS. That's why you get a BSOD!
@@jacquelinedelossantos426 Sure gets a bad rap, but apart from that one issue i had almost 20 years ago, it's never done me wrong. Works just fine on the various older PC's i own, and hasn't randomly bluescreened on me at all, since i'd started using it now & again back in 2015
The GSOD for insider builds was introduced in Windows 10 Creators Update build 15002. However, if a BSOD occurs before the system is booted, it's still blue.
Windows 11 would later revert to a (darker) blue in an update to the initial release. Not sure why it was black in Windows 11 to start.
Windows 10 Fall Creators Update build 16170 introduced the ability to trigger a black screen bugcheck by holding the power button for 7 seconds. This only works on devices where the power button must be held for longer than 7 seconds to force shut down. I'm not sure why this feature was implemented, because if the system is frozen, you would never reach this screen and instead keep holding the button until it force shuts down.
Luckily they fixed that uninstall updates BSOD from build 22543!
Thanks for the info - I've clarified the reference to the Green Screen in the description!
Thanks for the clarify
These are my answers and/or guesses for the bonus mini-game at 3:09:
3:11 Windows NT 3.1 (first NT version to feature a BSoD on release)
3:16 Windows 9x CD drive error (?)
3:22 Windows 98 ACPI RSoD
3:27 Windows 2000 build 1796 (first BSoD using BOOTVID.DLL with black screen bug)
3:30 Windows Me build 2419 Safe to Shutdown (replaced with standard 9x version in the final)
3:35 Windows 8 build 7880 (Hi-res Windows XP-7 BSoD using VBE2)
3:40 Windows 8 build 7899 Black Screen
3:46 Windows Server 2016 (also Windows 8/10 Japanese version)
3:50 Windows 8, 10, 11 Insider GSoD (Green Screen)
3:55 Windows 11 RTM 22000.194 Black Screen
The GSOD wasn't introduced until Windows 10 Creators Update build 15002. All prior beta builds, and all public builds, aren't green.
@@techwithtyler20 Agreed, it probably was still blue in earlier Insider Preview builds of Windows 8 and 10
Here are my notes from this video: there was a blue screen in Windows 1.0 and 2.0, but those are a result of a bug in the Windows logo code when installing an unsupported DOS version. Those systems will usually freeze and/or exit to DOS when they crashed.
Additionally, Windows Server 2012 onwards and Japanese versions of Windows 8, 10, and 11 do not feature a sad emoticon.
And oh man, gotta love that famous Windows 98 COMDEX BSoD moment! Fun times…
I did manage to crash Windows 1 Alpha and got a screen similar to the boot crash screen except it was black
same applied to Server 2016 and onwards, but you can re-enable the face if you want
also you can disable it in consumer counterparts of them
2:33 80×50 isn't pixels, it's characters in text-mode. The characters were 8×8 which means 640×400 pixels. They switched from 80×50 text-mode to 640×400 graphics mode.
That advert at the end showing the Blue Screen of Death was amusing.
I don't know why, but for a very long time, exiting OBS Studio on my Windows 10 machine always caused BSOD no matter what. I still don't know why it happened. Even if for a long time, updating OBS wouldn't fix that. But since updating OBS to a newer version, it has stopped BSOD'ing my PC, thank god.
I forgot that you could return to Windows from a bsod. I don't think I've ever seen that work
Me neither. Used to have so much fun with the inevitable graphical glitches it caused, though, lol.
You can only do this in Windows 9x. Windows NT and later NT based Windows did not allow such activity.
What particular build was that first Windows 8 beta one? Looks like a higher-resolution version of the classic XP-7 BSOD with anti-aliased text; never seen that one before so I assume it was an earlier build from before the public Developer Preview.
7880, I believe.
0:59 "initially using a black background, the colour would be changed to blue starting in Windows 3.11 in 1992"
Hang on doesnt Windows 1 not have a BSOD? If I remember correctly its a garbled mess.
It technically wasn't a blue screen, nor referred to as one at the time. The term "Blue Screen" has kinda been retroactively applied to it (as it has for the similar screen in Windows 2).
@@WindowsOnWindows Ahh, makes sense.
Bless that demonstrators heart the amount of embaressment he must have felt in that moment in that clip at the end.
Windows 98SE (Systemic Ennui)... 😁 Cheers...
The Blue Screen Of Death Was Eerie!
I was terrified the first time I had a blue screen of death, I thought I killed the computer!
I wonder why they changed the bg color to blue. Cosmetic maybe?
Good question! I don't think the reason is known. Maybe to make it a bit more arresting/to distinguish it at a glance from DOS or an ordinary DOS app, maybe? (Although, now that I've said this, I remember there were MANY blue DOS apps, lol.)
Could you make a video about ctrl+alt+delete or Windows Security please ?
My laptop crashed a few times in September. It happened once in late October and November. Some crashes in September were buzzing as frack.
Insider builds of windows(beta) & window server 2022
1st Windows NT 4.0
2nd Windows Me
3rt Menphis build 1351
4rt Windows Vista
5th Windows Me
6th Windows XP
7th unknown
8th Windows 10
9th Windows 11
10th Windows 11
@Bcc timers and more because both 9th and 10th are from Windows 11
@Bcc timers and more 3 mistakes
3:07 VMware SVGA 3D driver used. Disabling it would result in the BSOD in native resolutions and Windows Insider BSOD in green instead of 640x480 blue.
I got BSOD On Windows 11 22H2 Because It froze And BSOD, and shrinked to 1366x768 for gpu issues and got uninstalled after BSOD. Also i needed to reinstall the driver
2:20 Exectuion???
Well spotted!
Good News: My mom buyed a new charger!
666 veiws man great you have called the devil