Fatal Error and BSOD after uninstalling Superantispyware

By Remnis ·
Hello all! I am an IT tech doing free-lance work. Recently, after ridding a PC of viruses (nothing I removed was especially dangerous, just a bunch of MyWebSearch entries) I was cleaning up shop (i.e. uninstalling the various utilities and programs i had used). While uninstalling Superantispyware (a program I've used successfully hundreds of times) I received an error saying the uninstall had terminated unexpectedly. Subsequently, damage to the OS was rampant. I am now getting a BSOD at startup, and cannot boot the computer in Safe mode.
I must admit that i am completely mystified. The computer seemed entirely clean before this all happened, and I haven't found any record of this sort of problem on the internet...

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -


by Jacky Howe In reply to Fatal Error and BSOD afte ...

a Startup Repair. What is the error message.

Collapse -


by Remnis In reply to Try

I have already done away with the BSODs by repairing the registry with the original backup created in the Windows Repair folder. I am confident that I can repair the PC at this point, I am just looking for a bit of light to be shed on the phenomenon in general... The BSOD was of the "session manager initialization system process terminated unexpectedly" variety.

Collapse -

See how you go with this

by Jacky Howe In reply to Working....

Press the WinKey + Pause
Click Advanced and under Startup and Recovery select Settings.
Uncheck Automatically restart.
Click on the dropdown arrow under Write debugging information.
Select Small memory dump (64 KB) and the output is %SystemRoot%\Minidump.
Restart the PC normally as this will allow the System to Blue Screen and create the Minidump.

Minidump Files can be found here. C:\WINDOWS\Minidump\Mini122707-02.dmp

How to read the small memory dump files that Windows creates for debugging

To download and install the Windows debugging tools, visit the following Microsoft Web site:

Instructions on using Windbg.

Open Windbg and select file, Symbol file path and browse to the Symbol folder that you have downloaded and installed Symbols to, select OK.
Close the workpage and save the Workspace information. This should lock in the Symbol path.
Open Windbg and select file and select Open Crash Dump then navigate to the minidump, highlight it and select Open.
There are two ways to use !analyze -v the easiest is to click on !analyze -v under Bugcheck Analysis.
When you have ran the initial dump if you look to the bottom of the screen you will see kd> to the right of that type in !analyze -v and press the Enter key.
Ctrl + a will let you copy the information and paste it into notepad.

Look to the bottom of the page for information like this. This was fixed by updating the Graphics Drivers.




PROCESS_NAME: logon.scr

LAST_CONTROL_TRANSFER: from 00000000 to bfef0fea

f6434e6c 00000000 00000000 00000000 00000000 sgiul50!DrvBitBlt+0x585

STACK_COMMAN .thread 0xffffffff864f6a98 ; kb

bfef0fea 75f9 jne sgiul50!DrvBitBlt+0x580 (bfef0fe5)


SYMBOL_NAME: sgiul50!DrvBitBlt+585


MODULE_NAME: sgiul50

IMAGE_NAME: sgiul50.dll


FAILURE_BUCKET_I 0xEA_IMAGE_sgiul50.dll_DATE_2001_08_18

BUCKET_I 0xEA_IMAGE_sgiul50.dll_DATE_2001_08_18

Collapse -

Too Late...

by Remnis In reply to See how you go with this

Thanks Jacky,
Ironically though, I've already addressed the BSOD issue by replacing the registry. I'm working under time constraints... I was more hoping that this was a known issue, albeit a rare one.


Collapse -


by Jacky Howe In reply to Too Late...

disable all non MS services. You will have to work through them to find the culprit.

Collapse -

Or Autoruns

by seanferd In reply to msconfig

I tried SAS, but one of the reasons I didn't quite like it was its invasiveness. There would be roughly 4-6 registry entries in places like HKLM Run and Winlogon. If the software drivers were gone, but the reg entries remained, this would cause boot failure.

Next time you have a machine with SAS installed, have a look. They are fairly obvious.

Collapse -

I'm very curious ...

by OldER Mycroft In reply to Working....

If normal boot resulted in a BSOD and you couldn't boot to Safe Mode - how did you repair the registry?

Collapse -

Sweet mother of mercy, I just did this.

by seanferd In reply to I'm very curious ...

Laptop in reboot loop, same in Safe Mode and Command Prompt Only. (Probably a failed Windows Update, right after Patch Tuesday.) After multiple reboots, catching a glimpse of a BSOD.

Cannot mount registry in offline editor to zero AutoReboot setting in CrashControl. (OS not found.) Chkdsk will not run. Odd, as Windows does boot partially before failing. Still, cannot use most recovery console tools offline.

Finally, a partition editor found some errors to fix. Then chkdsk could find the volume and correct more errors. Then I could mount the reg and edit it. The last step was unnecessary as the problem was now fixed.

I should have tried the partition editor first. Grr.

Collapse -

Out of curiosity

by Jacky Howe In reply to Sweet mother of mercy, I ...

what partition editor do you use.

Collapse -

Partition Magic, I think. I'll have to check.

by seanferd In reply to Out of curiosity

I had it with a bunch of other stuff on a boot CD full of tools.

Related Discussions

Related Forums