blue screen

Did u installed any new hardware / software in recent time . Did u changed any setting of your OS? If that is the case then back it to its previous config & then check. Make sure there is no hardware conflict or malfunctioing hardware.

"Inside the Blue Screen" by Windows 2000 magazine:

http://www.winntmag.com/Articles/Index.cfm?IssueID=26&ArticleID=301

Microsoft's suggestions: "Blue Screen Preparation Before Contacting Microsoft (Q129845)"

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q129845

One more good link: http://windows.about.com/library/weekly/aa030599.htm

(REMOVE SPACES from the pasted URLs.)

Good luck,

Maxwell

At the top of the BSOD you will find a couple of lines telling you where the error occured. If you note the message in CAPS this should point towards the problem. on the same line there may be a driver name that raised the error. bearing in mind if the problem is a PCI card the error message can often point to the card fitted in the first MB slot.

Chris.

The memory dump should be saved to %systemroot%\memory.dmp, usually c:\winnt\memory.dmp. This dump file will usually reveal the driver that generated the stop code. A couple of resource kit utilities can help you find it. Executing "dumpchk.exe memory.dmp" will validate the dump file and spit out a lot of info. One line is ExceptionAddress. Remember this for later.

The utility pstat.exe will generate a rather long list of load modules and load addresses. You may want to redirect the output of pstat to a text file (pstat.exe >memaddr.txt). The module with an address equal to or just below the ExceptionAddress from the dump file will point to the failing driver.

The memory dump should be saved to %systemroot%\memory.dmp, usually c:\winnt\memory.dmp. This dump file will usually reveal the driver that generated the stop code. A couple of resource kit utilities can help you find it. Executing "dumpchk.exe memory.dmp" will validate the dump file and spit out a lot of info. One line is ExceptionAddress. Remember this for later.

The utility pstat.exe will generate a rather long list of load modules and load addresses. You may want to redirect the output of pstat to a text file (pstat.exe >memaddr.txt). The module with an address equal to or just below the ExceptionAddress from the dump file will point to the failing driver.

This question was auto closed due to inactivity