Starting with the classic Windows 9x Stop Error for kernel or driver failure, better known as... The Blue Screen.
You got this seemingly at random back in the day. The only predictive factors for a blue screen is everything else fucking up, or using Windows ME.
Here's the Windows NT version, which somehow managed to be even more inscrutable.
Beta builds of Windows Vista sported a red screen of death. Not the most reassuring color to help users through a fatal system crash.
![imageServlet[1].jpg](https://i.imgur.com/Z2NB781.jpg "imageServlet[1].jpg")
>>53639612
Like on Linux, tho.
Windows 8 and 10 decided to replace potentially useful crash dump information with a visual "fuck you".
>>53639694
>:(
>>53639694
>CRITICAL_PROCESS_DIED
Something happened.
Something happened.
>>53639694
The first 2/3rds of previous windows crashes were LOL DID U CAHGE A TING? UNDO DAT LOL XD
The remaining 1/3rd was a single useful line of technical info followed by generally useless trash..
Reducing all that shit to a friendly HEY FRIEND LETS FIX THIS FOR YOU followed by ALSO IF YOU'RE NOT A FUCKING RETARD, HERE'S THE ERROR CODE is a good idea.
If you think this is bad because its not a wall of gibberish and they threw in a :( you're beyond a fucking moron
>yfw crashing this live broadcast with no survivors
http://tv.rbc.ru/archive/tamancev/56f1743e9a7947ce38aa75c0
17m54s
>>53639874
>implying CRITICAL_PROCESS_DIED is a useful error code
It might as well be "SOMETHING_IS_WRONG_EXCEPTION as been raised, please do something"
>>53639635
literally never seen this in my life
>>53639635
All of the kernel panics I've ever seen are on a black screen.
They're so rare though. I've only seen 2 or so.
>Shitty Virtualbox drivers (promptly changed to qemu afterwards)
>Using kernel modules that weren't compiled on the same kernel install.
>>53639512
>You got this seemingly at random back in the day.
You usually got it when a program stopped working or access to a disk was not possible because you removed the CD/floppy. You usually just had to press a key to get back to windows.
>>53639512
>not ricing your win9x bluescreen
http://toastytech.com/files/bsod.html
>>53640278
Except CRITICAL_PROCESS_DIED is traditionally a bugcheck. So in this case it is useful, and usually points at the hardware abstraction layer...
>>53639882
>ataka na bryussel'
>he's more concerned about his fucking screen going blue
>>53639882
>>53640357
Except 99% of the time the screen would just *refresh* without returning to windows, and a restart was the only option.
>>53639882
Still better than this whole video:
https://youtu.be/TEO0B0lUHg8?t=125
Watch it to the end, they really broadcasted it this way
>>53639512
Have had constant shit like this from Windows 98. If it doesn't happen when safely removing a USB PC Card, it happens when attempting to use MIDI hardware in DOS games.
>>53640372
hehe.. win..wincuck..hehe
