win2k error during sp3 setup
Results 1 to 3 of 3

Thread: win2k error during sp3 setup

  1. #1
    Registered User
    Join Date
    Nov 2002
    Posts
    100

    win2k error during sp3 setup

    I work as an IS Technician for a City in Minnesota. After the Windows 2000 Service Pack 3 installation completed, I checked the "Do not reboot now" checkbox to finish up deleting the *.tmp files on the system. I was unable to delete *.tmp, so I decided to reboot and then do it. During the shutdown process a Dr. Watson error came up for winlogon.exe. Upon reboot, the system would cycle up and down erroring on winlogon.exe. This would occur during Normal and Safe mode. I removed the drive and put it into a known good system and replaced the 173kb winlogon.exe with a 175kb file from a system already running the SP3 update. After that, the system would boot to the logon box, but after logging in would error on lsass.exe "code 128" and shutdown the system every 1 minute. Running the Windows 2000 repair did nothing, reinstalling to a new dir would not complete, etc. The system that I had installed the drive into to copy the winlogon.exe file upon rebooting now came up with an error stating that I had no pagefile, when in fact I did have one prior to installing the hard drive in question. Does anyone have any ideas? I am currently reinstalling Win2k Pro completely, but I have never EVER had this happen in the past.

  2. #2
    Driver Terrier NooNoo's Avatar
    Join Date
    Dec 2000
    Location
    UK
    Posts
    31,824
    From the lsass.exe error code, it seems you have borked your users and logins... probably by replacing the winlogon.exe from another machine.

  3. #3
    Registered User
    Join Date
    Nov 2002
    Posts
    100
    I fixed it...bad 256mb Micron DIMM. It gave me a run for my money though. We rarely have memory issues in this place and we have over 100 nodes. I actually checked the WD hard disk with DataLifeGuard, no errors. Reran Win2k setup, repair install found no system errors, file copy errors in DOS portion, would not load GUI portion, etc. So when in doubt, try RAM. I just wasn't picking that as my first choice, this system has been in place for 3 months, pretty much running 24x5 with no reboots during the week. Micron PC w/ Micron RAM...


    Good day to all...

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •