Alrighty,
Apparently I was bad so I'm getting an oddball problem. I have a system that is getting a few random lockups, looks like it is coming from Explorer.Exe. After running a few spyware/malware programs and removed a few other problem programs the issue persisted.
So, after a defrag I deceided it was time to hop into Recovery Console and see if there were any errors on the drive. Here's where I get a bit confused.
I boot into recovery console and when prompted to type in my administrator password I receive the error that it is invalid. No biggie, reboot and attempt to log onto the main administrator account with what I believe the password to be, and I can log on.
For my sanity sake I change the passwords over on all the administrator accounts on the system and reboot. I'm still receiving the error that the password is invalid...my first thought is that the SAM was corrupted but if that was the case I'd see other behavior.
Soooooooo, my only thought is that during its initial setup (wasn't done by myself) someone associated a different account as the system administrator default (which may have since been removed). Any thoughts on how to discover this? Or what else may be causing this issue?
Apparently I was bad so I'm getting an oddball problem. I have a system that is getting a few random lockups, looks like it is coming from Explorer.Exe. After running a few spyware/malware programs and removed a few other problem programs the issue persisted.
So, after a defrag I deceided it was time to hop into Recovery Console and see if there were any errors on the drive. Here's where I get a bit confused.
I boot into recovery console and when prompted to type in my administrator password I receive the error that it is invalid. No biggie, reboot and attempt to log onto the main administrator account with what I believe the password to be, and I can log on.
For my sanity sake I change the passwords over on all the administrator accounts on the system and reboot. I'm still receiving the error that the password is invalid...my first thought is that the SAM was corrupted but if that was the case I'd see other behavior.
Soooooooo, my only thought is that during its initial setup (wasn't done by myself) someone associated a different account as the system administrator default (which may have since been removed). Any thoughts on how to discover this? Or what else may be causing this issue?