Microsoft Windows Operating system are synonym with the term blue screen of death , or just blue screens. Most technician will prompt the user to format or reinstall microsoft windows xp when the user bring the computer for computer repair.

Sometimes blue screens will occur when computer crashes , and Microsoft Windows will self restart after blue screen appearing for some seconds. This is due to the default settings of Microsoft Windows operating system.

To diagnose blue screen, you must change the default setting of Microsoft Windows XP operating system in System Properties.

1. Right click on My Computer icon on the desktop, and click “Properties”.
2. Choose “Advanced” tab
3. Click on “Settings” in the “Startup and Recovery” section.
4. Go to “System Failure” section , and tick “Write an event to the system log” , untick “Send an administrative alert” , untick “Automatically restart.
5. Click OK.

Now Microsoft Windows XP will write a dump file containing information on blue screens and will not self restart itself everytime blue screens occured during computer crashes.

Everytime blue screens occur, it will display some information on error occured. This informatios are crucial when troubleshooting and computer repair. Most of the blue screens will display error code. You can use this error for a search on the net for troubleshooting and computer repair process.

For example, a blue screens display the error nv4.sys . A quick search on the will show that nv4.sys is a component of Nvidia driver file, so automatically you know that the blue screens is caused by incompatible nvidia driver which is causing a conflict with the Microsoft Windows operating system.

Most of the time, an update of the driver will solved the blue screens problem. This can be apply to most of Microsoft Windows XP blue screens error.

See also:

• Blue screen when installing Microsoft Windows XP (1)
• Why Computers Crash (0)
• The basic tips for computer troubleshooting and repair. (0)
• Random blue screen error message cause by faulty RAM (6)
• Blue screen with random error messages (1)

I was reading some forums, and I find this funny post by Dr. Suess.

If a packet hits a pocket on a socket on a port, and the bus is interrupted at a very last resort, and the access of the memory makes your floppy disk abort, then the socket packet pocket has an error to report.

If your cursor finds a menu item followed by a dash, and the double-clicking icon puts your window in the trash, and your data is corrupted ’cause the index doesn’t hash, then your situation’s hopeless and your system’s gonna crash!

If the label on the cable on the table at your house, says the network is connected to the button on your mouse, but your packets want to tunnel to another protocol, that’s repeatedly rejected by the printer down the hall……

And your screen is all distorted by the side effects of gauss, so your icons in the window are as wavy as a souse; then you may as well reboot and go out with a bang, ‘cuz sure as I’m a poet, the sucker’s gonna hang.

When the copy on your floppy’s getting sloppy in the disk, and the macro code instructions cause unwanted risk, then you’ll have to flash the BIOS and you’ll want to RAM your ROM, just quickly turn the darn thing off and run to tell your Mom!

Well, that certainly clears things up for me. How about you?

Funny, but true.

See also:

• The basic tips for computer troubleshooting and repair. (0)
• Diagnosing Microsoft Windows XP blue screen (1)
• Blue screen when installing Microsoft Windows XP (1)