Windows 2003 hanging on login/applying computer settings

One of my Windows Server 2003 machines has suddenly stopped working. There have been no changes to its configuration or GPO. If I boot up the machine normally, it generally will get as far as "Applying Computer Settings." The machine will then freeze completely. The mouse and keyboard will cease to work, the machine will not respond to pings, and it'll just hang there on that same screen.

I've attempted to boot the machine in safe mode but it still doesn't work. In safe mode I can get as far as the login screen (with a few brief exceptions). Once I enter the login information, the machine freezes again. A couple of times it actually started the login process but then froze up.

Obviously I'm unable to access event logs, but according to a monitoring system I have set up on our network, this server first became unresponsive on Saturday evening. The only thing this server is running is Trend Micro Office Scan, which it's been running for a little over a year now. We have never had any issues like this with it before.

Any ideas?
LVL 1
elorcAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Darius GhassemCommented:
Run a chkdsk /r on the system. You could be having a hardware problem with one of the drives.

Run a repair on OS as well.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
kevin_uk05Commented:
This potentially could be a hardware issue or maybe just an issue with the OS.

One thing to check is that you have no USB devices connected to the server on boot up.

If you cannot gain access to the server or event logs then i am not sure what you are going to do, other than restore the boot volume from a backup or re-build the volume.

0
uescompCommented:
Did you perhaps try logging into the local system and not the network, also try logging in as a different profile, this will narrow it down from it being something other than the OS or hardware.  Also run a memory test to be sure it not your ram.
0
Introducing the "443 Security Simplified" Podcast

This new podcast puts you inside the minds of leading white-hat hackers and security researchers. Hosts Marc Laliberte and Corey Nachreiner turn complex security concepts into easily understood and actionable insights on the latest cyber security headlines and trends.

Aj8787Commented:
Well as you are struck at login screen so it is most probably OS issue as if  hardware had issuesthe system would have given some beeps and died..

You can run a OS repair using windows 2003 media

I hope it fixes the problem
0
Shreedhar EtteCommented:
Have you tried to boot the server into Last Known Good configuration?

What is the role of the server?
0
elorcAuthor Commented:
Well, it looks like it's a memory issue. I wasn't sure about it at first but when I tried to run the Windows repair it died about halfway through with a memory error. I swapped out memory and was able to log into (and use) Windows without further issue.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Anti-Virus Apps

From novice to tech pro — start learning today.