Sorry abot that first one....
I can't seem to open Spyware Blaster v.3.3. Whenever I try to open it I get
a pop up notifying the following error:
SPYWAREBLASTER caused an exception 03H in module <unknown> at c19e:00000001.
Registers:
EAX=00000000 CS=0177 EIP=00000001 EFLGS=00200246
EBX=009bcef2 SS=017f ESP=009bce8c EBP=009bcec0
ECX=00602528 DS=017f ESI=00009f16 FS=279f
EDX=81b1521c ES=017f EDI=009bcea8 GS=0000
Bytes at CS:EIP:
00 ff ff 2b 04 70 00 c3 e2 00 f0 2b 04 70 00 2b
Stack dump:
00602528 000001a0 0000105a 00000000 00000000 00009f16 bff63613 000001a0
0000105a 00000000 00000000 9ef027a7 0000017f 009bced4 bff848f7 266f9f16
How can I fix this and get Spyware Blaster up and running again?
The only time I have seen the O3H Exception it has been associated with
corruption in one or more of the following three files: User32.dll
Gdi32.dll Winmm.dll and it would prevent the machine from booting properly.
This was due to a virtual device driver, cmapieng.vxd and only resulted
after performing a scandisk or defrag. This particular .vxd was contained
within certain McAfee products and has, long since, been fixed.
Has SB 3.3 ever worked or did it fail from the onset of installation? If
the latter, did you properly uninstall the previous version after disabling
its' protection? Lastly, have you tried uninstalling, downloading a fresh
copy and reinstalling?? (it is conceivable you may have a corrupt download).
If the above does not resolve the issue, do a System Restore to the latest
point prior to installing the version 3.3. Please post back, I am most
interested in the cause and resolution.
Heirloom, old and the latex is back
> Sorry abot that first one....
>
[quoted text clipped - 14 lines]
>
> How can I fix this and get Spyware Blaster up and running again?
Mart - 14 Mar 2005 10:39 GMT
Hi HL, - 'possible' pointer? :-
"Exception 03h in Module..." Error Message Starting Windows Me
http://support.microsoft.com/default.aspx?scid=kb;en-us;275003
I guess that this is what you are referring to.
Mart
> The only time I have seen the O3H Exception it has been associated with
> corruption in one or more of the following three files: User32.dll
[quoted text clipped - 36 lines]
>>
>> How can I fix this and get Spyware Blaster up and running again?
Jack E Martinelli - 14 Mar 2005 13:35 GMT
Very nice research, Mart.
Unfortunately, a rather similar issue as seen with Norton AV, Live Update,
and WinME's System Restore.
The difference is that Network Associates responded with a fix, unlike
Symantec.

Signature
Jack E. Martinelli 2002-05 MS MVP for Shell/User / DTS
Help us help you: http://www.dts-L.org/goodpost.htm
http://www.microsoft.com/athome/security/protect/default.aspx
In Memorium: Alex Nichol
http://www.microsoft.com/windowsxp/expertzone/meetexperts/nichol.mspx
Your cooperation is very appreciated.
------
> Hi HL, - 'possible' pointer? :-
>
[quoted text clipped - 45 lines]
> >>
> >> How can I fix this and get Spyware Blaster up and running again?
Dabeez - 14 Mar 2005 13:29 GMT
Thanks for your replies.
I do not have any McAfee products installed and before I installed the new
SpwareBlaster 3.3 I did disable all protection first, and then uninstalled
the older version. I reinstalled the newer version three times with reboots,
to see if that would fix, to no avail. The newer version of spyware blaster
did work at first after installing it two days ago. The 03H error just
started today.
You and mentioned user32.dll and gdi32.dll. Do you suggest (as the
article in Mart's post) that I do the renaming of these files even if McAfee
is not on my computer, and that as far as I can tell my computer is booting
with no problems,although I did not check the bootlog. txt to see if
something failed to load. Do you suggest the renaming of user32.dll and
gdi32.dll?
I might add that the 03H error only happens when opening SpywareBlaster.
When opening spywareblaster, there is is a white flash then the 03H error
pops up.
> The only time I have seen the O3H Exception it has been associated with
> corruption in one or more of the following three files: User32.dll
[quoted text clipped - 33 lines]
> >
> > How can I fix this and get Spyware Blaster up and running again?
Dabeez - 14 Mar 2005 17:19 GMT
I found the cause of why spyware blaster would not open. I was searching the
Wilderscurity site for some clues and I came accross this:
http://www.wilderssecurity.com/showthread.php?t=12266.
I installed vbrun60sp5.exe and now spyware blaster is back to normal.
> The only time I have seen the O3H Exception it has been associated with
> corruption in one or more of the following three files: User32.dll
[quoted text clipped - 33 lines]
> >
> > How can I fix this and get Spyware Blaster up and running again?
heirloom - 14 Mar 2005 18:11 GMT
Great sleuthing, Dabeez! Although not needed now, I was NOT suggesting
that you perform the steps regarding the .dll files, as this would have
affected booting.......only making reference to the older issue. I am
surprised that the older version of SB worked without the vbrun60 file, let
alone the ver 3.3.
You have provided some excellent info that I am sure will be helpful to
others.....thanks.
Heirloom, old and you did good
> I found the cause of why spyware blaster would not open. I was searching the
> Wilderscurity site for some clues and I came accross this:
[quoted text clipped - 39 lines]
> > >
> > > How can I fix this and get Spyware Blaster up and running again?
Dabeez - 14 Mar 2005 19:39 GMT
Maybe needing this visual basic file was because of a reinstallation IE6.
Not sure.
I then checked out why 03H errors occur and found some mention on faulty ram.
What had me suspicious though, was the error only popping up when trying
start SpywareBlaster. Thanks for nudging me in the direction.
> Great sleuthing, Dabeez! Although not needed now, I was NOT suggesting
> that you perform the steps regarding the .dll files, as this would have
[quoted text clipped - 60 lines]
> > > >
> > > > How can I fix this and get Spyware Blaster up and running again?
Mart - 14 Mar 2005 18:23 GMT
Well done Dabeez! - Yours was an interesting error report for the missing
.dll, instead of that shown on the wilderssecurity site.
But it fixed it and credit to you for persevering.
Mart
>I found the cause of why spyware blaster would not open. I was searching
>the
[quoted text clipped - 46 lines]
>> >
>> > How can I fix this and get Spyware Blaster up and running again?