Blue Screen

Go to the Microsoft support page and do a keyword search for Q275678 in the Knowledgebase. It will show an article for troublshooting that error code. Its pretty general but should lead you in the right direction.

It could be an error related to several applications. Since you didn't elaborate, we're not sure of your exact application. This error could occur with the following applications:

Microsoft Windows 2000 SP1 Advanced Server
Microsoft Windows 2000 Datacenter Server
Microsoft Windows 2000 SP1 Professional
Microsoft Windows 2000 SP1 Server
Microsoft Windows NT

That file (ntoskrnl.exe) and/or the registry could have become corrupt, and/or you may have been the victim os a virus (W32 FunLove virus).

That file should be located in this folder:

Windows\System or \WinNT\System32

You may need to change your boot log and/or copy the correct version of that file in the correct location. (Boot on floppy disk to do this.)

Try these links for specific information as to your particular situation:

http://www.jsiinc.com/SUBF/TIP2700/rh2745.htm

http://www.littlewhitedog.com/reviews_other_00021.asp

http://www.lehigh.edu/~rjm2/ntwntw.html

http://service1.symantec.com/sarc/sarc.nsf/html/W32.Funlove.4099.html

http://www.win2000mag.com/Articles/Index.cfm?ArticleID=2832

NOTE: REMOVE ANY SPACES that may have appeared in these URLs whild cut/paste.

Good luck,

Max

The first thing I'm going to suggest is article Q129845 on Microsoft's Knowledge Base as it describes the general approach to troubleshooting these types of problems.

If you have your system configured to write a memory dump file (memory.dmp) in the event of a blue screen, you can run dumpexam.exe against that file and it will give you a LOT more detail about the failure. My guess is that the problem here really isn't the NT kernel but rather a driver called by it.

The other strategy, and usually the more productive one, is to think about the server's recent history. What was the last thing done before the BSOD started? In particular, was any hardware or software upgraded, changed or installed? Also, it can be very important to know what OS and what Service Pack level you are running and on what hardware.

My experience with Stop 1E errors has been that the most common culprit is something like a video driver or some other driver that is fairly close to the hardware or BIOS and you can fix it by undoing whatever you did last, although that sometimes requires a parallel installation to permit the damaged file to be replaced.

paul

This question was closed by the author