#Xscreensaver timestamp install#
#Xscreensaver timestamp drivers#

The bluescreen is so well known now that it has become a '(color) Screen Of Death' meme. This thing is highly authentic- it even simulates a reboot- and quite scary when you're not expecting it.

#Xscreensaver timestamp install#

Why wasn't it always this way - after all, what the heck else are you going to do after getting a BSoD? Have a party?ДЄfter rebooting, you could celebrate by buying a BSoD T-Shirt:ДЄnd for a few laughs, you can install the BSoD screensaver on a coworker's computer when they're not around. You may not see the BSoD much in Windows XP or Windows Server 2003 because the latest versions of Windows are configured to reboot automatically after a BSoD is encountered. If you're like most of us, you just cross your fingers and reboot. If you're a glutton for punishment, you can attempt to decipher all that technical jibba-jabba on the BSoD or perform BSoD troubleshooting. Microsoft catches a lot of flak for the Blue Screen of Death, but as frequently noted throughout the BSoD documentation, most BSoDs are due to faulty third-party hardware drivers. Here's a chronological pictorial, starting with Win9x and going up to WinXP: The BSoD is analogous to a Kernel Panic in the UNIX world, and it became a standard fixture in all subsequent versions of Windows. The driver information is in three columns the first lists the base address of the driver, the second lists the driver's creation date (as a Unix timestamp), and the third lists the name of the driver.

#Xscreensaver timestamp drivers#

Under Windows NT and 2000, the second and third sections of the screen contain information on all loaded drivers and a stack dump, respectively. Depending on the error code, it may display the address where the problem occurred, along with the driver which is loaded at that address. 0x0000001E, KMODE_EXCEPTION_NOT_HANDLED) along with four error-dependent values in parentheses. The 'Stop' message contains the error code and its symbolic name (e.g. The only action the user can take in this situation is to restart the computer, which results in possible data loss due to Windows not properly shutting down.Д«lue screens are known as 'Stop errors' in the Windows NT/2000/XP documentation, and are also sometimes referred to as 'bugchecks'. This is usually caused by a driver that throws an unhandled exception or performs an illegal operation. As I recall, the Blue Screen of Death was introduced with Windows NT 3.1 circa 1993:ДЄ blue screen of death occurs when the kernel, or a driver running in kernel mode, encounters an error from which it cannot recover.