We need the following to further assist you with the problem:FILE INVOLVED or COMMON VERBAL NAME
Common Verbal Name
Start at the top, below the error description and suspect file. The following is the abbreviated verbal message.
This abbreviated description serves as a common verbal name for the error described by the blue screen.
the STOP CODE?
In the next section down labeled “Technical information,” the first piece of information is a bug code, or “stop code,” you can use to reference the error. The stop code consists of five strings of alphanumeric characters. The stop code from the example is:
The first string outside the parentheses serves as a label for the error and is often abbreviated to the first two characters (0x) and the last two characters (50), so the code in the example is referred to as 0x50. The strings of characters inside the parentheses provide further details about the error.
[b]What is the DRIVER OR LIBRARY INVOLVED:
Driver or Library Involved
The next piece of technical information names the driver or library file that was running when the system crashed. This information can help eliminate unrelated causes and possibly resolve the issue. If a driver or library file has become corrupt, and there’s no physical memory problem, then replacing the damaged file with an intact copy may alleviate the problem.
example : nv4_disp.dll
The memory address where the fault occurred and time at which it happened are also listed. It’s possible, though unlikely, that physical components where vital data is stored are damaged or failing. Remember, the majority of blue screen errors are caused by faulty drivers or software incompatibility. Identify and repair the driver before you decide to dispatch and replace hardware.
These are the informations we need to know if you have a blue screen error.
Edited by wytboy55, 13 February 2008 - 04:10 PM.