Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

BSOD while booting w2k Prof


  • Please log in to reply

#1
martian63

martian63

    New Member

  • Member
  • Pip
  • 2 posts
Windows 2000 professional

Ran virtumondebegone and there was a microsoft autoupdate at the same time. Now when I try to reboot, I get the BSOD

STOP: c000021a {Fatal System Error}
The Windows Logon Process system process terminated unexpectedly with a status of 0xc0000080 (0x00000000 0x0000000)
The system has been shutdown.

I can't even boot in 'safe mode'. I can go to recover console.

Appreciate your help. :)
  • 0

Advertisements


#2
Ax238

Ax238

    Tech Staff

  • Technician
  • 1,323 posts
Hello martian63, welcome to GTG!

This is all to similar to a topic I read through over at eggheadcafe.com. Granted it deals with the Windows Malicious Software Removal tool, but it's worth a shot. No need to dig through it though, here is the relevant information to resolve the issue:

Just wanted to share my experience with this update that came out on
the 8th of this month that affects the Windows 2000 professional
computers rebooting just before login. After speaking with Microsoft,
it is actually the combination of the kb931768 update, along with a
malicious software removal update for May that came out at the same
time.

If you can boot into the recovery console and do the steps above as
noted by John John to uninstall the 931768 update (mine was named
$ntuninstallkb931768-IE6SP1-2007... (I forgot the rest of the path)),
and reboot after the uninstall, it would still reboot the machine just
before login screen appeared.

However, if you go into recovery console and go to c:\winnt\debug and
look at the log files there, you will see that the malicious software
removal tool actually tagged c:\winnt\system32\sfc.dll as a virus and
deleted the file at the next restart.

To fix this issue, uninstall the update 931768, then type the
following at the recovery console:

expand d:\i386\sfc.dl_ c:\winnt\system32\

After the sfc.dll file is restored, reboot the machine and everything
should come up just fine.


Regards,

Ax
  • 0

#3
martian63

martian63

    New Member

  • Topic Starter
  • Member
  • Pip
  • 2 posts

Hello martian63, welcome to GTG!

This is all to similar to a topic I read through over at eggheadcafe.com. Granted it deals with the Windows Malicious Software Removal tool, but it's worth a shot. No need to dig through it though, here is the relevant information to resolve the issue:

Just wanted to share my experience with this update that came out on
the 8th of this month that affects the Windows 2000 professional
computers rebooting just before login. After speaking with Microsoft,
it is actually the combination of the kb931768 update, along with a
malicious software removal update for May that came out at the same
time.

If you can boot into the recovery console and do the steps above as
noted by John John to uninstall the 931768 update (mine was named
$ntuninstallkb931768-IE6SP1-2007... (I forgot the rest of the path)),
and reboot after the uninstall, it would still reboot the machine just
before login screen appeared.

However, if you go into recovery console and go to c:\winnt\debug and
look at the log files there, you will see that the malicious software
removal tool actually tagged c:\winnt\system32\sfc.dll as a virus and
deleted the file at the next restart.

To fix this issue, uninstall the update 931768, then type the
following at the recovery console:

expand d:\i386\sfc.dl_ c:\winnt\system32\

After the sfc.dll file is restored, reboot the machine and everything
should come up just fine.


Regards,

Ax


Ax,

Thanks for the reply. I did all that and it still doesn't change anything. I uninstalled the updates. The date of sfc.dll was old which probably means it was never changed. However, I copied the file from debug folder (expand command didn't work).

Regards,
  • 0

#4
Ax238

Ax238

    Tech Staff

  • Technician
  • 1,323 posts
Try the following MS KB with hopefully better luck:
Error Message: STOP 0x00000001e KMODE_EXCEPTION_NOT_HANDLED in Win32k.sys

Regards,

Ax
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP