Discussion Locked

Blue screen of death

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have proxy server 2.0 sitting on a NT4.0 platform with sp6a installed. Today I received a BSOD and after dumping the physical memory to disk, it will automatically restart.
I received this error message on the blue screen -

Beginning dump of physical memory
Dumping physical memory to disk.

I checked at the event viewer

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xc0000005, 0xf1b318a4, 0x00000000, 0x02f9fffe). Microsoft Windows NT [v15.1381]. A dump was saved in: C:\WINNT\MEMORY.DMP.

This is my first time receiving the error. Is there any advice on how I should maintain my server or any special tools? Is the event happening to our server is normal?

appreciate the help

5 replies

by mtnsqs

Look in the event log for any other errors or warmining messages - eg disk space or similar - this might help lead to the cause of the crash.

Check disk space on system - especially temporary space. You might need to keep an eye on this on a proxy server and clean it up .

One suggestion is to regularly reboot the system during an off time - Lots of programs have memoery leaks and a reboot is the only way to clean up the mess.

I reboot all my NT servers once a month, and since doing that find that BSOD's are rare and the systems seem to repsond better

by green lantern

No, BSOD's are not normal :-)
This is a very common bug check for a KMODE_EXCEPTION_NOT_HANDLED error. The x.c0000005 indicates an access violation error (IE not authorized). There should be a .SYS file following the hex numbers. This driver will usually be the system/driver causing the BSOD.
Without further data, cannot help more than this.
ralph

This discussion is closed to new replies.