Windows 2003 server restarting continuously. I can see error code 6008 only. This is the 4th time today the server get restarted. Please help.Suneesh

Hi, Please check if there are any *.dmp file in the %systemroot%/minidump folder. If there is a minidump file you can analyze it to finde the source of the problem. http://support.microsoft.com/kb/315263

Hi Suneesh,Windows by default doesnt exhibit this behavior, there should be either of the following reasons a) applicaiton calling shutdown.exe b) virus / malware attackc) improper tweaking of registry under user profile / HKLM. Please let us know in detail when do you see this behavior is that a) after immediattely logging on to machine ( after authenticaiton has been completed) b) after launching any of the applications ?You can also check the same behavior in safe mode which gives us an idea about the 3rd party applications installed.sainath !analyze

HiPlease analyse the Memory dump /mini dump error through windows Debugging toolshave you checked and seen any eventviewer related error?Thanks...Deva --Self-trust is the first secret of success.

Error 6008 = The previous system shutdown at <time> on <date> was unexpected.Look for error 1001 source SaveDump for the stop code. The computer has rebooted from a bugcheck.If no BSOD's occur (Event ID: 1001 Source: SaveDump), then it may be a power problem. I would look at a possible faulty (or undersized) pc power supply, UPS, bad battery, or the circuit feeding the outlet that the pc is plugged into. Regards, Dave Patrick .... Microsoft Certified Professional Microsoft MVP [Windows]

Hi Dave, Thanks for the info, i had seen the above issue earlier with the faulty battery and i replaced it which eventually resolved my problem and other problem was the power outlet which was causing the problem. I hooked the laptop power to another socket and eventually it got resolved the problem. @Deva : Configuring dumps is not the viable solution in this scenario the reason is that when operating system dumps the data , its should dump the entire memory block i mean the current stack which OS is executing , with windbg or softice ( best debugger i have used earlier ) would not provide the stack in the memory during the problem . So analyzing the previously held threads in the stack and analyzing the TEB would not provide you much info. sainath !analyze