This really could be any number of things from HW going bad (MB, controller,
ram, etc) to drivers, applications, or services running on it, and is really
impossible to tell you like this.
If the server is set to auto reboot after a crash, you can change that so it
doesn't, and then get the "blue screen" infor off of the monitor before you
reboot it (ie, stop code, parameters, and description) which will ofter give
an idea if its a driver problem, hw, etc. However without having a debug on
the dump file it should generate, it is going to be almost impossible to
tell what the exact cause is, and you may need to open a ticket to have it
read.
some info that might help;
307973 HOW TO: Configure System Failure and Recovery Options in Windows
http://support.microsoft.com/?id=307973
254649 Windows Memory Dump File Options Overview
http://support.microsoft.com/?id=254649
303021 How to Generate a Memory Dump File When a Server Stops Responding
(Hangs)
http://support.microsoft.com/?id=303021
315263 Reading the Small Memory Dump Files That Windows Can Create for
Debugging
http://support.microsoft.com/?id=315263
--
David Brandt
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.