The best mechanism is to see "Event Log". From here u may get the whole story about windows 2003 server.
OR, u may download a small free tool called <a href="http://msdn.microsoft.com/en-us/windows/hardware/gg463009.aspx">WinDbg</a>, / Windows Debugger.
Notes: There is a way "Memory Dump" that is a snapshot of what the system had in memory when it crashed. There r 3 types of that, viz, Samll / mini dump; Kernel dump and Complete or Full dump.
Please look here for <a href="http://msdn.microsoft.com/en-us/library/ff551063(v=VS.85).aspx">More Utility Tools</a> for ur purpose....
Last Wiki Answer Submitted: April 12, 2011 8:48 am by Subhendu Sen22,035 pts.
All Answer Wiki Contributors: Subhendu Sen22,035 pts.
If you live outside the United States, by submitting your email address you consent to having your personal data transferred to and processed in the United States.
If you mean that it crashed (blue screened), then I would say that you need the Windows Debugger (WinDbg), available for free from Microsoft. It’s a bit of an odd creature for me to understand at times…but it *will* often allow you to analyze crash dumps to see what the offending process was.
If you mean that it crashed (blue screened), then I would say that you need the Windows Debugger (WinDbg), available for free from Microsoft. It’s a bit of an odd creature for me to understand at times…but it *will* often allow you to analyze crash dumps to see what the offending process was.
There are a few useful articles out there…try this one for starters and see if it helps:
http://www.networkworld.com/news/2005/041105-windows-crash.html
If there is a different issue you have in mind, then please update us as to the specifics!