W2k reboots. help reqst with minidumps.

Hi,

I have a W2k server that started to reboot itself a couple of months ago.

I have never been in front of it at the exact moment when it happened, but when I noticed it and went to the server room it would have a black screen (not a blue BSOD) with a message about memory being dumped (it is configured to do a full memory dump).

I have tried everything software related I could think of (downgraded AV, disabled services, patched, etc.).
The only thing I didn´t do is updating drivers such as video card, the system was working fine with these since it was installed, about a year ago.

I have also checked temperatures and changed the PSU.

Because of minidump results, I disabled the onboard nic and placed a new PCI one.

I have also opened the minidumps, and most of them seem to reffer to tcpip.sys or win32k.sys, but there are several others mentioned.


When this started, it would reboot every 7 to 9 days aprox, but yesterday it did it twice within 17 hours.

I have been asking managment to get a backup server for 3 months, that is still on hold because of budget, and I am getting close to panic.

If anyone has a hunch, or better yet, the time an will to check the minidumps and maybe understand them better than me, I would be SO grateful.

Thanks in advance.

Cloack Ed.

EDIT to add:

- nothing is overcloacked
- I ran memtest and it passed (I know it could be faulty and still pass)
- there is a single memory stick
- I moved it to another mem slot
- The only PCI/agp card is the Nic I installed after the problem appeared.

 

Hi,

Usually system crash at tcpip.sys is related to faulty RAM and system crash at win32k.sys is related faulty ram or video ram. You had better use kd to analysis the stack trace in order to confirm the culprit.


Install Windows Debugging Tools
1) Create folder c:\symbols
2) Download and install the http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
3) Locate your latest memory.dmp file- C:\WINNT\memory.dmp
4) open a CMD prompt and cd\program files\debugging tools for windows\
5) type the following stuff:

Code:
c:\program files\debugging tools>kd -z C:\WINNT\memory.dmp
kd> .logopen c:\debuglog.txt
kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
kd> .reload;!analyze -v;r;kv;lmnt;.logclose;q

You now have a debuglog.txt in c:\, open it in notepad and post the content to this thread.