The real reason for the old famous Microsoft Windows Blue Screen of Death — BSOD

There is an ongoing argument in the tech universe about the best operating system, and the definition of “the best OS” is yet another separate debate topic. I have had those arguments with two opposite sides: with Apple macOS as well as Linux users. Whenever we used to do any of those civil debates 😉 the well known blue screen of death (BSOD) must surface at the top of the discussion.

I think all PC users have suffered the BSOD in early Windows versions, the PC stops working all a sudden, and the user loses any unsaved work. If you haven’t, you are lucky! Please google “BSOD.”

Based on experience and research, the root causes of BSOD can be mainly traced to a hardware error. Unlike macOS that is designed to work only on a predefined set of hardware, Windows is designed to work on a broad list of hardware. Including old and new CPUs and memory and many more. So, any malfunctioned hardware or a poorly written device driver causes such error.

Also, the error in early Windows versions, 95,98 and ME, can be traced to memory management problems that were fixed in later versions. Microsoft has realized the rise of this issue and acted accordingly to minimize those external issues. Microsoft launched several tools to help hardware manufacturers test their drivers and reduce such errors detecting deadlock violations in Windows NT4.0 and Windows XP.

A deadlock is simply a state where two processes are waiting for a resource that is not currently available. “Process A” is waiting for a resource that is being used by “Process B,” and “Process B” is waiting for a resource that is being used by “Process A.”

In recent versions, when such errors occur, Windows dumps the memory on the hard drive, provides an error code, a QR code for the user to fix the error.


Personally, I don’t remember that last time I had a BSOD on any of my PCs, especially after Windows 7. Do you have any bad memories with the PC or BSOD? Feel free to share back yours.