When you get the blue screen of death, write down the code that it is giving you and go to Google, type in all the number and Google will tell you what the problem is..........It may or may not be the sound card........The sound card is very easy to replace if that is what it is.............
"BSoD" redirects here. For other uses, see BSoD (disambiguation).
A public payphone that has failed and is displaying the Blue Screen of Death.The Blue Screen of Death (sometimes called "bluescreen", "stop error" or just abbreviated as "BSoD") is a popular name for the screen displayed by Microsoft's Windows operating system when it cannot recover from, or is in danger of being unable to recover from, a system error. There are two Windows error screens that are both referred to as the blue screen of death, with one (Windows NT 4/2000/XP) being significantly more serious than the other (Windows 9x). There are several causes of the blue screen popping up. It can be a poorly-written device driver, bad memory, damaged registry or usage of incompatible versions of DLLs (see more on the "Types of blue screens" section).
The blue screen of death in one form or another has been present in all Windows operating systems since Windows version 3.1. It is the successor of the less well-known black screen of death that occurs in OS/2 as well as MS-DOS[1]. In early builds of Windows Vista it was complemented with a red screen of death, used for boot loader errors.
The blue screen of death also occurs in Microsoft's home desktop operating systems Windows 95, 98, and Me. Here it is less serious, but more common. In these operating systems, the BSoD is the main way for virtual device drivers to report errors to the user. It is internally referred to by the name of "_VWIN32_FaultPopup". A Windows 9x/Me BSoD gives the user the option either to restart or continue. However, VxDs do not display BSoDs frivolously — they usually indicate a problem which cannot be fixed without restarting the computer, and hence after a BSoD is displayed the system is usually unstable or unresponsive.
The most common reason for BSoDs is that problems occur with incompatible versions of DLLs. This cause is sometimes referred to as DLL hell. Windows loads these DLLs into memory when they are needed by application programs; if versions are changed, the next time an application loads the DLL it may be different from what the application expects. These incompatibilities increase over time as more new software are installed, and is one of the main reasons why a freshly-installed copy of Windows is more stable than an "old" one.
In Windows 95 and 98, a BSoD occurred when the system attempted to access the file "c:\con\con" on the hard drive. This was often inserted on websites to crash users' machines. Microsoft has released a patch for this.[5]
The BSoD can appear if a user ejects a removable medium while it is being read on 9x/ME. This is particularly common while using Microsoft Office: if a user simply wants to view a document, he might eject a floppy disk before exiting the program. Since Microsoft Office always creates a temporary file in the same directory, it will trigger a BSoD upon exiting because it will attempt to delete the file on the disk that is no longer in the drive.
This type of blue screen is no longer seen in Windows NT, 2000, and XP. In the case of these less serious software errors, the program may still crash, but it will not take down the entire operating system with it due to better memory management and decreased legacy support. In these systems, the "true" BSoD is seen only in cases where the entire operating system crashes.
Good luck!