Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


BSOD Last Known Good Configuration or Messy Uninstall?

  • Please log in to reply
No replies to this topic

#1 fotafm


  • Members
  • 1 posts
  • Local time:06:31 AM

Posted 03 March 2013 - 11:37 AM

Compaq 5441 Rebuild:

I've been rebuilding a friend's OLD computer after a hard drive crash (Compaq Presario 5441, Win2K professional, GA-5SMM motherboard, 512MB SDRAM, AMD K6-2 475 MHz, 40 GB WD HDD, integrated video and sound).  To make this doorstop useful, I had to find an Antivirus program that would work in Win2K.  A six-month old version of AVAST worked (evidently AVAST is no longer support Win2K).  I had to apply several updates to Win2K and a hotfix before AVAST would install.  After AVAST installed the definition updates were not downloading.  I changed the settings in AVAST to "this system is always connected to the internet."  The definition updates would not download after the settings changed so I thought a reboot was in order.
After restart was selected, "BSOD."
I receive the following, ""systemroot\system32\drivers\aswSP.sys device driver could not locate the entry point SeTokenObjectType in driver ntoskrnl.exe"
I am wondering whether to try a potentially messy uninstall of AVAST in Safe Mode using pcdecrapifier or last known good configuration?
NOTE:  aswSP.sys is associated with AVAST.
I installed quite a few updates and some other programs that I did not not the installation order for or note if or when a restore point was created and I fear last known good configuration may be an equally messy alternative.
I do not suspect a root-kit virus but this is a remote possibility.  I cannot boot normally so attaching logs would not be very helpful.
Can someone assist me with potential alternatives?  The obvious is not desired, "an in place repair of Win2K."

BC AdBot (Login to Remove)


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users