Windows 2000 server constantly reboots...

I have a machine that acts as a DC and print server. It is constantly rebooting itself. I went to check the logs and when I got to the AppLog, it said that it was corrupt and unreadable. Could this be what is causing the machine to reboot?

If I log it into safe mode, everything is fine. So I'm thinking it's gonna be driver related or maybe something to do with this Applog. Any suggestions?

I tried to go in and rename the applog to something else so it would recreate the file, but I get an error saying that something else is using that process and the file can't be changed.

Help! Nobody can print!
LVL 1
Gabe_RiveraAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Computer101Connect With a Mentor Commented:
PAQed, with points refunded (500)

Computer101
E-E Admin
0
 
Debsyl99Commented:
Hopefully this will help,
How to Delete Corrupt Event Viewer Log Files
http://support.microsoft.com/?kbid=172156

Deb :))
0
 
RWrigleyCommented:
There is a GPO security setting that will cause a system to shut itself down if its unable to record security messages; your rebooting problem could be that.  Another possibility is bad drivers; this might also explain the event log corruption.
0
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
Gabe_RiveraAuthor Commented:
I checked the Domain Controller Security Policy and the reboot option is not enabled. Is there some place else that it could be enabled?

As far as bad drivers go, how do I start eliminating the driver issues? I uninstalled the video driver and it still rebooted. I disabled the NIC card and it still rebooted. There's not a whole lot else to this machine... it used an onboard IDE RAID controller, onboard sound, etc. There isn't much to it.
0
 
piddle61Commented:
How's your anti-virus, could be a Sasser virus!!! Stinger from www.nai.com will clean it and then get security patches from Microsoft update???
0
 
Jeb911Commented:
Click on start, then run and type in SFC /scannow make sure you have your appropriate windows cd available.
0
 
Gabe_RiveraAuthor Commented:
It was the power supply. Took me almost 12 hours of messing with it to figure it out. (*sigh*)
0
 
RWrigleyCommented:
Ah.  What wattage was the old one?
0
 
Gabe_RiveraAuthor Commented:
300W. System was built in June of 2002 and it's been turned on ever since...
0
 
Gabe_RiveraAuthor Commented:
This problem is resolved. It was a power supply that was flaking out.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.