Windows 1.0 BSOD (Incorrect DOS Version)

The first version of Windows had a BSOD that could occur if you booted the OS on the wrong DOS version, such as MS-DOS 6.0 or above. It also includes multiple BIOS beeping sounds.

SOCIAL MEDIA LINKS:

[JudgeDeadd]

Tech support: "Okay, read the error message to me"
You: "..."

[HalfLifeonSteamPLZ]

Didn’t know that Windows 1.0 can display enchantment table language

[EpicBanana]

0:07 wow, i like it, it explains the BSOD

[zoomosis]

This bug is particular to Windows 1.0 and is due to an incorrectly written DOS version check. There's a good explanation of the bug on Stack Exchange: "Why does Windows 1.01 crash at the splash screen?"

[kevinsconcepts]

Windows 95 and above bsod: show information of the pc

Windows 1 to 3: Ukm ok lemme show some symbols and uhh.. and happy faces w/hearts to show my love to the user :D

[karmatical]

Technically, this is not a windows Bsod.
The B.S.O.D is a fancy name for a Kernel Panic, which is a critical error occuring inside the operating system kernel (core).
But windows 1.0 probally didn't even had something such as a kernel, because it was a program and not an proper operating system yet.
Any DOS program can show this error screen, if you ever played with Assembly and made a mistake, you probally have seen this exact screen.
Its basically Machine code (Compiled Assembly), being printed on the screen and probally being treated as Sound Output as well (this explains the long beep).
As the machine code is not supposed to be text, nothing there makes sense, it will print a bunch of weird characters related to numbers that most of the time are not even related to an regular ascii char.

[Moviesxp]

BSOD:shows symbols
Me:he be speaking enchanted table

[EpicevanXD]

Bsods are error messages that display when windows realized something broke. This is the entire os failing to open and performing the computer equivalent of screaming for help

[lucssa]

Windows 1.01: Here's some certain language, hope you enjoy reading it!
Notch: *Hmmm.... Interesting.... *

[BigNate_.]

The random characters do have meaning. As someone else in this comment section said, it’s machine code being displayed on screen instead of actually being used by the machine, but the characters themselves are part of ASCII, which is the standard character set used on every American PC today, but you’d usually never see these characters themselves. You CAN see them if you set your computer to a language that ASCII doesn’t support (which is any language that isn’t English apparently). It’s also possible to see them when you open up a .bin file in a non-binary-code program like Notepad.

So essentially this is just binary being shown on screen, which ends up being random nonsense when put through ASCII.

[igor-kot]

It's beeping just because of typing ASCII BEL character 0x07 to console

[Fiku_]

The thing that makes me laugh is the lil shmali faces that pop up every now and then

[joshuamccutcheon]

Nobody:
My brain in literally any situation that requires thinking:

[Contryballs_anti-emoji-cat]

If your are scared, the correct version is ms-dos 1.00-2.00-3.00

[shortyoutuber]

well, the gibberish characters are likely enchantment table characters.

[SarthakDoesMidisAndWindowsAndY]

"Incorrect DOS version"


This means you have MS-DOS 3.30 or higher, perhaps MS-DOS 6.22. Windows can boot with MS-DOS 6.22 and with Windows 2.0 etc. Until NT versions come up.

[neon]

0:07 average comments made by 3 year olds:

[mexicoandmorealt]

Old blue screen: encantamient table language

New bluescreen: :(

[thatonecommenter.]

"Incorrect DOS version"
*starts speaking enchanting table*

[TheOfficialKillaGrinds]

Tech support: what is wrong with your pc?

Me: its speaking enchanting table