Discussion Locked

NT Server 4.0 keeps crashing

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

I am getting ready to deploy a new server running NT 4.0 Server. The server is a brand new PIII 933MHZ running 256 MB Ram on a Asus VIA 694X-E MainBoard. I have installed all the latest drivers and Mainboard patches for the chipset it uses. However this system will crash at the oddest times. It gos to a blue screen and then does a memory dump and reboots it self. Also somtimes on bootup it fails to start alot of the applications so I reboot it and its fine for somtimes minutes and somtimeshours. I can not find any paticular thing that causes it to crash. It just does it at differnt times doing different things.

I am wondering with it being such new hardware if it has somthing to do with a compatibility issue with it being NT 4.0???

Any ideas or suggestions???

11 replies

by oskiller

Make sure your video is set to VGA on the server. There is no reason to load any kind of video driver other than the standard VGA on the server. Additionally, make sure you are not running any unncessary services. See if this makes any difference onthe server.

When it blue screens, are they similar blue screens?

by oskiller

If you can post some of the information from one or two of your blue screens (the first couple of lines or so), we can work with that as well to see if anything jumps out.

by nhoek

Yes the blue screens are the same, it gos to a blue screen and lists a bunch of memory address and then does its memory dump which counts to 100 and then it reboots.

by dark force

If you take down the first 3 or 4 lines of the blue screen, you can search Microsoft's KnowledgeBase with those numbers.
The numbers to get are:
Stop aXaaaaaaa, (aXaaaaaaa, aXaaaaaaa, aXaaaaaaa, aXaaaaaaa) Unhandled Kernel exception aXaaaaaaa fromaXaaaaaaa Address aXaaaaaaa has base at aXaaaaaaa - ntoskrnl.exe

If you search for first set of numbers after the Stop in MS's knowledgebase, Start with the first couple of addresses (omit the parentheses) and add more to narrow it down from there.
http://search.support.microsoft.com/kb/c.asp

Good Luck,
JR

by philando

The problem sounds hardware related or a compatibility issue. I am hoping that you already done this, but make sure you're using the latest service pack for NT (I think its 6a). Also if you're using any scsi controller for disk, make sure drivers and firmware is the latest. Definitely try the knowledgebase like one of your reponse suggested.
Its nice to have forums like this cause when you have a problem we (the community) feel your pain cause we've been there one way or the other. What did we do before the internet?
Good Luck.

This discussion is closed to new replies.