Unexpected Reboot
Some time I found my NT server restarted, events log id 6005 and 6009 appear in system log. Log full could be one of the reasons.
Are there other causes? I'd like to prevent such unexpected reboot events.
Thanks!
Windows Forum
Some time I found my NT server restarted, events log id 6005 and 6009 appear in system log. Log full could be one of the reasons.
Are there other causes? I'd like to prevent such unexpected reboot events.
Thanks!
by dklippert
6005
The Event log service was started.
6009
System startup.
Microsoft (R) Windows 2000 (R) 5.0 2195 Service Pack 1 Uniprocessor Free.
by yuemo
I'd like to know how can I prevent such unexpected reboot.
Thanks anyway.
by ann777
With WinNT you can set your Event Viewer logs to automatically "Overwrite events as needed" or "Overwrite events older than x days" or you also have the option of increasing your log file size.
Any one of the above three options should prevent the system from rebooting when the log file is full
by yuemo
Configure your system not to reboot automatically upon an error. Copy down the error message(s) you see and then post that data. From there we can investigate the causes behind your rebooting.
Go to start/control panel/system and set the startup options. Make sure reboot is not checked. Now when the system encounters the error which is causing the reboot, the server will sit there until you have a chance to see what is causing the problem. It will probably be a 0x00000050 error.
by yuemo
by yuemo
This discussion is closed to new replies.
Sort by Trending