Blue screen of death? What to do?  

First you have to use anti virus and delete all the virus which were scanned.Next restart the system and also delete some junk files while scanning the system.After restart make sure everything is intact.And don't worry about a blue screen but if you still get it then the only option is to upgrade the system or re install the operating system.

Answered by nishanth , an ibibo Specialist, at 10:01 PM on July 22, 2008

There are four basic sections that you should be aware of on a Blue Screen of Death:
•The first section lists the actual error message.
•The second section lists the Microsoft® Windows NT® modules that are already loaded into memory.
•The third section lists the modules that were about to be loaded had the error not occurred.
•The fourth section lists the current status of the Kernel Debugger.

In such a situation, your first instinct would probably be to tell them to reboot the server and let you go back to sleep. However, as you've probably already found out, rebooting isn't always the magic cure all. It can be a gut-wrenching feeling, staring at the incomprehensible blue screen with all its numbers and codes. However, this experience doesn't have to be so traumatic. The secret is to know how to read the Blue Screen of Death.

For more detail-
http://www.microsoft. com/t echnet/archive/winntas/tips/te chrep /bsod.mspx?mfr=true

Answered by Gyan Singh , an ibibo Master, at 7:13 PM on July 16, 2008

There are four basic sections that you should be aware of on a Blue Screen of Death:
•The first section lists the actual error message.
•The second section lists the Microsoft® Windows NT® modules that are already loaded into memory.
•The third section lists the modules that were about to be loaded had the error not occurred.
•The fourth section lists the current status of the Kernel Debugger.

In such a situation, your first instinct would probably be to tell them to reboot the server and let you go back to sleep. However, as you've probably already found out, rebooting isn't always the magic cure all. It can be a gut-wrenching feeling, staring at the incomprehensible blue screen with all its numbers and codes. However, this experience doesn't have to be so traumatic. The secret is to know how to read the Blue Screen of Death.

For more detail-
http://www.microsoft. com/t echnet/archive/winntas/tips/te chrep /bsod.mspx?mfr=true

Answered by Anju Singh , an ibibo Master, at 6:25 PM on July 16, 2008

well
There are four basic sections that you should be aware of on a Blue Screen of Death:
•The first section lists the actual error message.
•The second section lists the Microsoft® Windows NT® modules that are already loaded into memory.
•The third section lists the modules that were about to be loaded had the error not occurred.
•The fourth section lists the current status of the Kernel Debugger.

In such a situation, your first instinct would probably be to tell them to reboot the server and let you go back to sleep. However, as you've probably already found out, rebooting isn't always the magic cure all. It can be a gut-wrenching feeling, staring at the incomprehensible blue screen with all its numbers and codes. However, this experience doesn't have to be so traumatic. The secret is to know how to read the Blue Screen of Death.

For more detail-
http://www.microsoft. com/t echnet/archive/winntas/tips/te chrep /bsod.mspx?mfr=true

Answered by jaivir , an ibibo Master, at 6:30 PM on July 15, 2008

There are four basic sections that you should be aware of on a Blue Screen of Death:
•The first section lists the actual error message.
•The second section lists the Microsoft® Windows NT® modules that are already loaded into memory.
•The third section lists the modules that were about to be loaded had the error not occurred.
•The fourth section lists the current status of the Kernel Debugger.

In such a situation, your first instinct would probably be to tell them to reboot the server and let you go back to sleep. However, as you've probably already found out, rebooting isn't always the magic cure all. It can be a gut-wrenching feeling, staring at the incomprehensible blue screen with all its numbers and codes. However, this experience doesn't have to be so traumatic. The secret is to know how to read the Blue Screen of Death.

For more detail-
http://www.microsoft.com/t echnet/archive/winntas/tips/techrep /bsod.mspx?mfr=true

Answered by Nagendra , an ibibo Master, at 7:32 AM on July 09, 2008

You might have a hardware error. Especially if you say that you already tried restoring the computer with the restore disk. If a clean install does not work, then it must be hardware related.
There are some tools around that can help you test your hardware.
Most BSOD Errors are caused by faulty Memory.
There is a tool called "memtest" that can be download from the intertubes for free. It can run from a disk and will show you if your memory is defective. There are other programs for Disk and processor tests, but I can't remember any right now. Try Googling for Hardware Test Tool.

Answered by priyanka , an ibibo Specialist, at 10:10 PM on July 04, 2008

you Say its a Blue screen of death, READ the details. It will tell you what the problem is and what the technical code is. Re-ask the question with the code and info.

Answered by banish , an ibibo Specialist, at 6:56 PM on July 04, 2008

The "BSOD" means that a program has crashed and Windows is going to crash too.
The screen is all blue with white lettering. The error message will be different depending on what caused the computer to crash. It will inform you that you can press Ctrl-Alt-Delete to reboot the computer.
The best thing to do whenever you see this screen is to restart the computer. Even if the computer will successfully salvage the situation it doesn't usually work right until you reboot.
Consider yourself fortunate if you don't have to see this screen very often. That means that your computer isn't very crashy.
To resolve this, when your system booting, press F8 and when the boot option menu appears, select the Option "Last Known Good" configuration. Booting to the Last Known Good configuration allowed you to recover an unbootable system in most simple scenarios. If however, this doesn't work and you continue to see the BSOD, you will need to ascertain what the numbers mean. So an important factor is writing down the numbers which are displayed there. If there is any indication that your computer just stopped working because of a new piece of driver software you just installed, then a good starting point would be to roll back that driver:

Bring up the System Properties dialog. Click on the Hardware tab. Click on the Device Manager. Right-click on the problem device and select Properties. If the device is not working, it will likely appear with a red X in the middle of the icon. Click on the Driver tab and then click Roll Back Driver. Accept as appropriate and required.

You can also remove the "Auto Restart" option. In System Properties, click 'Advanced'. under 'Startup and recovery' click 'Settings'. Under 'System failure', remove/unselect the check mark against 'Automatically restart' option. If the BSOD problem persists, contact your system vendor/mechanic for further assistance.

Answered by shaista , an ibibo Master, at 10:59 AM on July 04, 2008

The Blue Screen of Death (BSOD) is a Stop Error that occurs in the Windows OSes and promptly halts the system, disallowing you to do anything more without a reboot. Most of these Stop Error messages will also include the name of the file or driver which caused the Stop Error to occur. If you can ascertain the file name, you ought to be able to browse your favorite search engine in order to find out what hardware or software caused the problem.

BSODS are usually caused by the following: (1) component has failed or degraded (for eg. Computer Chip Memory) (2) new drivers which have been added, or driver files which have become corrupted in the system for a number of reasons. (3) hardware which has been added or which has failed.

To resolve this, when your system booting, press F8 and when the boot option menu appears, select the Option "Last Known Good" configuration. Booting to the Last Known Good configuration allowed you to recover an unbootable system in most simple scenarios. If however, this doesn't work and you continue to see the BSOD, you will need to ascertain what the numbers mean. So an important factor is writing down the numbers which are displayed there. If there is any indication that your computer just stopped working because of a new piece of driver software you just installed, then a good starting point would be to roll back that driver:

Bring up the System Properties dialog. Click on the Hardware tab. Click on the Device Manager. Right-click on the problem device and select Properties. If the device is not working, it will likely appear with a red X in the middle of the icon. Click on the Driver tab and then click Roll Back Driver. Accept as appropriate and required.

You can also remove the "Auto Restart" option. In System Properties, click 'Advanced'. under 'Startup and recovery' click 'Settings'. Under 'System failure', remove/unselect the check mark against 'Automatically restart' option. If the BSOD problem persists, contact your system vendor/mechanic for further assistance.

Answered by A.R.Karthick , an ibibo Master, at 9:38 AM on July 04, 2008