Fatal Error Blue Screen OE 0671:10014490

Fatal Error Blue Screen OE 0671:10014490

Started after I installed Avast after avg quit support.

Greg

Greg wrote:
> Fatal Error Blue Screen OE 0671:10014490
>
> Started after I installed Avast after avg quit support.
>
> Greg

Did you make sure to fully uninstall AVG first? AVG was notorious for
not properly removing itself.
Check the *manual* method below, but ONLY do the search for files to
see if you still may have some of it installed.

http://www.avg.com/faq.num-946#faq_946
I'm not sure if the new uninstaller works correctly or with 9X.

If there are no left-overs found, can you provide a bit more
information, such as any halts/falters in AVAST installation, errors or
otherwise.

Did you try uninstalling AVAST and re-installing?

http://forum.avast.com/index.php?board=1.0

----

Another way - manually:
Open Explorer, then open Program Files.
If an AVG folder appears, right click the folder and delete it.
Then go to SEARCH > ALL FILES AND FOLDERS, type in the item name AVG.
Check the files appearing in the list, right click and delete those
known to be related. If you find some that can not be deleted, they may
be in the recycle bin, which you can empty later.
Then go to START > RUN, type in REGEDIT, press OK.
When registry editor appears go to EDIT, then FIND, type in AVG.
If AVG listings appear, check what and where they were loaded from or
reference THEN, choosing ONLY those related AVG entries, > first
highlight and export that entry, THEN right click the item and delete.
Don't delete anything not DIRECTLY RELATED to AVG or you may have other
issues.

Another manual way [a better explanation perhaps]:
http://support.tallemu.com/vbforum/s...5&postcount=11

An automated way:
IF you have issues you can try a re-install then uninstall by using
this trick:

Download Total Uninstall and install. Restart [of course].

Re-install the old version you used of AVG BUT by using Total Uninstall
to do the installation *after* telling it to monitor ALL registry keys
and files/disks. Save the resultant file.

Use the AVG uninstall, restart. Run Total Uninstall and remove the
final issues by choosing the Uninstall - whatever you named the install.

NOT a recommendation for any site, just availability:
http://www.fileheap.com/software-tot...oad-34701.html
*last freeware version
http://www.freewaregeeks.com/?page=d...75&category=59

--
MEB
http://peoplescounsel.org/ref/windows-main.htm
Windows Info, Diagnostics, Security, Networking
http://peoplescounsel.org
The "real world" of Law, Justice, and Government
___---

On Sun, 27 Sep 2009 02:46:10 -0400, MEB <MEB-nothere@hotmail.com>
wrote:

>Greg wrote:
>> Fatal Error Blue Screen OE 0671:10014490
>>
>> Started after I installed Avast after avg quit support.
>>
>> Greg
>
> Did you make sure to fully uninstall AVG first? AVG was notorious for
>not properly removing itself.
> Check the *manual* method below, but ONLY do the search for files to
>see if you still may have some of it installed.
>
>http://www.avg.com/faq.num-946#faq_946
> I'm not sure if the new uninstaller works correctly or with 9X.
>
> If there are no left-overs found, can you provide a bit more
>information, such as any halts/falters in AVAST installation, errors or
>otherwise.
>
> Did you try uninstalling AVAST and re-installing?
>
>http://forum.avast.com/index.php?board=1.0
>
>----
>
>Another way - manually:
>Open Explorer, then open Program Files.
> If an AVG folder appears, right click the folder and delete it.
> Then go to SEARCH > ALL FILES AND FOLDERS, type in the item name AVG.
> Check the files appearing in the list, right click and delete those
>known to be related. If you find some that can not be deleted, they may
>be in the recycle bin, which you can empty later.
> Then go to START > RUN, type in REGEDIT, press OK.
>When registry editor appears go to EDIT, then FIND, type in AVG.
> If AVG listings appear, check what and where they were loaded from or
>reference THEN, choosing ONLY those related AVG entries, > first
>highlight and export that entry, THEN right click the item and delete.
>Don't delete anything not DIRECTLY RELATED to AVG or you may have other
>issues.
>
>Another manual way [a better explanation perhaps]:
>http://support.tallemu.com/vbforum/s...5&postcount=11
>
>An automated way:
> IF you have issues you can try a re-install then uninstall by using
>this trick:
>
> Download Total Uninstall and install. Restart [of course].
>
> Re-install the old version you used of AVG BUT by using Total Uninstall
>to do the installation *after* telling it to monitor ALL registry keys
>and files/disks. Save the resultant file.
>
> Use the AVG uninstall, restart. Run Total Uninstall and remove the
>final issues by choosing the Uninstall - whatever you named the install.
>
>NOT a recommendation for any site, just availability:
>http://www.fileheap.com/software-tot...oad-34701.html
>*last freeware version
>http://www.freewaregeeks.com/?page=d...75&category=59

That Avast does have a memory problem with the August full release,
there are suppose to fix it with the next full release. It affects
xp system with 128mb ram with a blue screen error and cant do a boot
scan. It using to much memory. I was asking in the XP groups
for a friend. Avg might clause the same thing.

Greg

Greg wrote:
> On Sun, 27 Sep 2009 02:46:10 -0400, MEB <MEB-nothere@hotmail.com>
> wrote:
>
>> Greg wrote:
>>> Fatal Error Blue Screen OE 0671:10014490
>>>
>>> Started after I installed Avast after avg quit support.
>>>
>>> Greg
>> Did you make sure to fully uninstall AVG first? AVG was notorious for
>> not properly removing itself.
>> Check the *manual* method below, but ONLY do the search for files to
>> see if you still may have some of it installed.
>>
>> http://www.avg.com/faq.num-946#faq_946
>> I'm not sure if the new uninstaller works correctly or with 9X.
>>
>> If there are no left-overs found, can you provide a bit more
>> information, such as any halts/falters in AVAST installation, errors or
>> otherwise.
>>
>> Did you try uninstalling AVAST and re-installing?
>>
>> http://forum.avast.com/index.php?board=1.0
>>
>> ----
>>
>> Another way - manually:
>> Open Explorer, then open Program Files.
>> If an AVG folder appears, right click the folder and delete it.
>> Then go to SEARCH > ALL FILES AND FOLDERS, type in the item name AVG.
>> Check the files appearing in the list, right click and delete those
>> known to be related. If you find some that can not be deleted, they may
>> be in the recycle bin, which you can empty later.
>> Then go to START > RUN, type in REGEDIT, press OK.
>> When registry editor appears go to EDIT, then FIND, type in AVG.
>> If AVG listings appear, check what and where they were loaded from or
>> reference THEN, choosing ONLY those related AVG entries, > first
>> highlight and export that entry, THEN right click the item and delete.
>> Don't delete anything not DIRECTLY RELATED to AVG or you may have other
>> issues.
>>
>> Another manual way [a better explanation perhaps]:
>> http://support.tallemu.com/vbforum/s...5&postcount=11
>>
>> An automated way:
>> IF you have issues you can try a re-install then uninstall by using
>> this trick:
>>
>> Download Total Uninstall and install. Restart [of course].
>>
>> Re-install the old version you used of AVG BUT by using Total Uninstall
>> to do the installation *after* telling it to monitor ALL registry keys
>> and files/disks. Save the resultant file.
>>
>> Use the AVG uninstall, restart. Run Total Uninstall and remove the
>> final issues by choosing the Uninstall - whatever you named the install.
>>
>> NOT a recommendation for any site, just availability:
>> http://www.fileheap.com/software-tot...oad-34701.html
>> *last freeware version
>> http://www.freewaregeeks.com/?page=d...75&category=59
>
> That Avast does have a memory problem with the August full release,
> there are suppose to fix it with the next full release. It affects
> xp system with 128mb ram with a blue screen error and cant do a boot
> scan. It using to much memory. I was asking in the XP groups
> for a friend. Avg might clause the same thing.
>
> Greg

Oh, not good. I didn't check on AVAST forums as 9X support is ending.

As this appears to be an issue with the base programming [at least in
NT supported version] 9X users may not receive that updated/fixed error
for the version or next version.

Perhaps someone that did take the recent program updates with an OLDER
version already installed, could provide information on whether just
doing the update to an already installed previous version caused any issues.
That would help localize the issue to the offered new full version
verses a normally upgraded *already installed* AVAST.

And yes, might want to check for residual AVG issues, AVG left-overs
have been known to cause numerous problems. Similar issues for the
removal of AVAST.

Per AVAST ending support:
http://groups.google.com/group/micro...d92debbbbab65a

--
MEB
http://peoplescounsel.org/ref/windows-main.htm
Windows Info, Diagnostics, Security, Networking
http://peoplescounsel.org
The "real world" of Law, Justice, and Government
___---

"Greg" <invalid@invalid.net> wrote in message
news:7i85jjF2vj7ecU1@mid.individual.net...
> Fatal Error Blue Screen OE 0671:10014490
>
> Started after I installed Avast after avg quit support.

It's 0e (zero-e), not Oe

Is that the entire error message? Does it state "Fatal Exception Error
0E0671:10014490" or is there more on the screen? Post everything you see.

Can you start Windows? Can you start in Safe Mode?
If you can get into Windows either of those ways, disable the Boot Scan if it is
enabled:

*Right click on the the blue ball Avast icon on the right side of the task bar and
select "Start avast! Antivirus."
*In the avast! Simple User Interface (upper-left-hand corner), left-click on the
menu control and select "Schedule Boot-Time Scan..."
*If a scan is already set, it will ask you "avast!: Boot-time scan is already
scheduled. Do you want to unschedule the boot-time scan?" Click yes and then click
the X in the upper-right-hand corner to close it.
*If a scan is not already scheduled, the Schedule window will just appear, and you
can click Cancel.

Post back with whether it was enabled or not.
--
Glen Ventura, MS MVP Windows, A+
http://dts-l.net/

glee wrote:
> "Greg" <invalid@invalid.net> wrote in message
> news:7i85jjF2vj7ecU1@mid.individual.net...
>> Fatal Error Blue Screen OE 0671:10014490
>>
>> Started after I installed Avast after avg quit support.
>
> It's 0e (zero-e), not Oe
>
> Is that the entire error message? Does it state "Fatal Exception Error
> 0E0671:10014490" or is there more on the screen? Post everything you see.
>
> Can you start Windows? Can you start in Safe Mode?
> If you can get into Windows either of those ways, disable the Boot Scan
> if it is enabled:
>
> *Right click on the the blue ball Avast icon on the right side of the
> task bar and select "Start avast! Antivirus."
> *In the avast! Simple User Interface (upper-left-hand corner),
> left-click on the menu control and select "Schedule Boot-Time Scan..."
> *If a scan is already set, it will ask you "avast!: Boot-time scan is
> already scheduled. Do you want to unschedule the boot-time scan?" Click
> yes and then click the X in the upper-right-hand corner to close it.
> *If a scan is not already scheduled, the Schedule window will just
> appear, and you can click Cancel.
>
> Post back with whether it was enabled or not.

Is that available in the 9X version/installation?
Previously, it was not available.
Or was this for the XP part?

--
MEB
http://peoplescounsel.org/ref/windows-main.htm
Windows Info, Diagnostics, Security, Networking
http://peoplescounsel.org
The "real world" of Law, Justice, and Government
___---

On Sun, 27 Sep 2009 13:32:26 -0400, "glee" <glee29@spamindspring.com>
wrote:

>"Greg" <invalid@invalid.net> wrote in message
>news:7i85jjF2vj7ecU1@mid.individual.net...
>> Fatal Error Blue Screen OE 0671:10014490
>>
>> Started after I installed Avast after avg quit support.
>
>It's 0e (zero-e), not Oe
>
>Is that the entire error message? Does it state "Fatal Exception Error
>0E0671:10014490" or is there more on the screen? Post everything you see.
>
>Can you start Windows? Can you start in Safe Mode?
>If you can get into Windows either of those ways, disable the Boot Scan if it is
>enabled:
>
>*Right click on the the blue ball Avast icon on the right side of the task bar and
>select "Start avast! Antivirus."
>*In the avast! Simple User Interface (upper-left-hand corner), left-click on the
>menu control and select "Schedule Boot-Time Scan..."
>*If a scan is already set, it will ask you "avast!: Boot-time scan is already
>scheduled. Do you want to unschedule the boot-time scan?" Click yes and then click
>the X in the upper-right-hand corner to close it.
>*If a scan is not already scheduled, the Schedule window will just appear, and you
>can click Cancel.
>
>Post back with whether it was enabled or not.


I am running windows 98se, my friend is running windows xp sp3 both
have Avast installed with 128mb memory.

Avast doesn't have boot scanner for windows 98se, just windows xp.

His error with Avast was not enough storage space to run boot scanner.

it was an letter O by the way or at least it looked like. Aren't
letter O's that looks like zeros, have a diagonal / line in the
letter O?

Then later, I found out Avast was having a memory problem.

The memory is supposed to be fixed in next sub full release (Not the
release that ends windows 98se support)

Greg.

"Greg" <invalid@invalid.net> wrote in message news:7ia0vqF30mjq8U1@mid.individual.net...

> On Sun, 27 Sep 2009 13:32:26 -0400, "glee" <glee29@spamindspring.com>
> wrote:

>>"Greg" <invalid@invalid.net> wrote in message
>>news:7i85jjF2vj7ecU1@mid.individual.net...
>>> Fatal Error Blue Screen OE 0671:10014490
>>>

>>It's 0e (zero-e), not Oe

> it was an letter O by the way or at least it looked like. Aren't
> letter O's that looks like zeros, have a diagonal / line in the
> letter O?

Depends on the font. In the case of your blue screen error message,
it is the hex number 0E as glen noted. It's a common mistake. Next
to the E most people assume it is an O.

Bill Blanton wrote:
> "Greg" <invalid@invalid.net> wrote in message
> news:7ia0vqF30mjq8U1@mid.individual.net...
>> On Sun, 27 Sep 2009 13:32:26 -0400, "glee" <glee29@spamindspring.com>
>> wrote:
>
>>> "Greg" <invalid@invalid.net> wrote in message
>>> news:7i85jjF2vj7ecU1@mid.individual.net...
>>>> Fatal Error Blue Screen OE 0671:10014490
>>>>
>
>>> It's 0e (zero-e), not Oe
>
>> it was an letter O by the way or at least it looked like. Aren't
>> letter O's that looks like zeros, have a diagonal / line in the
>> letter O?
>
> Depends on the font. In the case of your blue screen error message,
> it is the hex number 0E as glen noted. It's a common mistake. Next
> to the E most people assume it is an O.

Besides which, there is no "O" in hexadecimal. It only goes to F. :-)

MEB wrote:
> glee wrote:
>> "Greg" <invalid@invalid.net> wrote in message
>> news:7i85jjF2vj7ecU1@mid.individual.net...
>>> Fatal Error Blue Screen OE 0671:10014490
>>>
>>> Started after I installed Avast after avg quit support.
>>
>> It's 0e (zero-e), not Oe
>>
>> Is that the entire error message? Does it state "Fatal Exception
>> Error 0E0671:10014490" or is there more on the screen? Post
>> everything you see.
>>
>> Can you start Windows? Can you start in Safe Mode?
>> If you can get into Windows either of those ways, disable the Boot
>> Scan if it is enabled:
>>
>> *Right click on the the blue ball Avast icon on the right side of the
>> task bar and select "Start avast! Antivirus."
>> *In the avast! Simple User Interface (upper-left-hand corner),
>> left-click on the menu control and select "Schedule Boot-Time
>> Scan..." *If a scan is already set, it will ask you "avast!:
>> Boot-time scan is already scheduled. Do you want to unschedule the
>> boot-time scan?" Click yes and then click the X in the
>> upper-right-hand corner to close it. *If a scan is not already
>> scheduled, the Schedule window will just appear, and you can click
>> Cancel.
>>
>> Post back with whether it was enabled or not.
>
> Is that available in the 9X version/installation?
> Previously, it was not available.
> Or was this for the XP part?

My 9x avast! Home Edition v.4.8.1351 has the item in the menu, but it is
ghosted & unusable. Maybe you had to pay for it.

But who wants to do a full scan every boot, anyhow? I have always been
well satisfied with just the memory scan at boot & the On-Access
Protection!


--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR
pcrrcp@netzero.net

PCR wrote:
> MEB wrote:
>> glee wrote:
>>> "Greg" <invalid@invalid.net> wrote in message
>>> news:7i85jjF2vj7ecU1@mid.individual.net...
>>>> Fatal Error Blue Screen OE 0671:10014490
>>>>
>>>> Started after I installed Avast after avg quit support.
>>> It's 0e (zero-e), not Oe
>>>
>>> Is that the entire error message? Does it state "Fatal Exception
>>> Error 0E0671:10014490" or is there more on the screen? Post
>>> everything you see.
>>>
>>> Can you start Windows? Can you start in Safe Mode?
>>> If you can get into Windows either of those ways, disable the Boot
>>> Scan if it is enabled:
>>>
>>> *Right click on the the blue ball Avast icon on the right side of the
>>> task bar and select "Start avast! Antivirus."
>>> *In the avast! Simple User Interface (upper-left-hand corner),
>>> left-click on the menu control and select "Schedule Boot-Time
>>> Scan..." *If a scan is already set, it will ask you "avast!:
>>> Boot-time scan is already scheduled. Do you want to unschedule the
>>> boot-time scan?" Click yes and then click the X in the
>>> upper-right-hand corner to close it. *If a scan is not already
>>> scheduled, the Schedule window will just appear, and you can click
>>> Cancel.
>>>
>>> Post back with whether it was enabled or not.
>> Is that available in the 9X version/installation?
>> Previously, it was not available.
>> Or was this for the XP part?
>
> My 9x avast! Home Edition v.4.8.1351 has the item in the menu, but it is
> ghosted & unusable. Maybe you had to pay for it.

Yeah, that's what I remembered. So did you take the update?

>
> But who wants to do a full scan every boot, anyhow? I have always been
> well satisfied with just the memory scan at boot & the On-Access
> Protection!
>
>

I did, it was one the things I liked about AVG. It had an actual Boot
scanner for 9X (from autoexec), not the entire disk but crucial file
areas, preload memory, and a few other areas. No other way to autotest,
as once the system is fully running, whatever MAY have been in memory or
running from disk could easily have placed itself into an unreachable
mode. AVAST's Boot checks appears to provide similar to the NTs.
Not entirely reliable as the *only* test run, but similar to the old
DOS days of scanning before running a shell or whatever, or a TSR AV
monitoring activity.

--
MEB
http://peoplescounsel.org/ref/windows-main.htm
Windows Info, Diagnostics, Security, Networking
http://peoplescounsel.org
The "real world" of Law, Justice, and Government
___---

MEB wrote:
> PCR wrote:
>> MEB wrote:
>>> glee wrote:
>>>> "Greg" <invalid@invalid.net> wrote in message
>>>> news:7i85jjF2vj7ecU1@mid.individual.net...
>>>>> Fatal Error Blue Screen OE 0671:10014490
>>>>>
>>>>> Started after I installed Avast after avg quit support.
>>>> It's 0e (zero-e), not Oe
>>>>
>>>> Is that the entire error message? Does it state "Fatal Exception
>>>> Error 0E0671:10014490" or is there more on the screen? Post
>>>> everything you see.
>>>>
>>>> Can you start Windows? Can you start in Safe Mode?
>>>> If you can get into Windows either of those ways, disable the Boot
>>>> Scan if it is enabled:
>>>>
>>>> *Right click on the the blue ball Avast icon on the right side of
>>>> the task bar and select "Start avast! Antivirus."
>>>> *In the avast! Simple User Interface (upper-left-hand corner),
>>>> left-click on the menu control and select "Schedule Boot-Time
>>>> Scan..." *If a scan is already set, it will ask you "avast!:
>>>> Boot-time scan is already scheduled. Do you want to unschedule the
>>>> boot-time scan?" Click yes and then click the X in the
>>>> upper-right-hand corner to close it. *If a scan is not already
>>>> scheduled, the Schedule window will just appear, and you can click
>>>> Cancel.
>>>>
>>>> Post back with whether it was enabled or not.
>>> Is that available in the 9X version/installation?
>>> Previously, it was not available.
>>> Or was this for the XP part?
>>
>> My 9x avast! Home Edition v.4.8.1351 has the item in the menu, but
>> it is ghosted & unusable. Maybe you had to pay for it.
>
> Yeah, that's what I remembered. So did you take the update?

Wasn't 1351 the last update? I haven't been informed of another.

>>
>> But who wants to do a full scan every boot, anyhow? I have always
>> been well satisfied with just the memory scan at boot & the On-Access
>> Protection!
>>
>>
>
> I did, it was one the things I liked about AVG. It had an actual Boot
> scanner for 9X (from autoexec), not the entire disk but crucial file
> areas, preload memory, and a few other areas. No other way to
> autotest, as once the system is fully running, whatever MAY have been
> in memory or running from disk could easily have placed itself into
> an unreachable mode. AVAST's Boot checks appears to provide similar
> to the NTs. Not entirely reliable as the *only* test run, but
> similar to the old DOS days of scanning before running a shell or
> whatever, or a TSR AV monitoring activity.

I see what you're saying. Yea, sounds useful. Still, hopefully the
On-Access Scan, E-Mail Scan &/or the WEB Shield catches them before they
get in. That's how I'm set.


--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR
pcrrcp@netzero.net

PCR wrote:
> MEB wrote:
>> PCR wrote:
>>> MEB wrote:
>>>> glee wrote:
>>>>> "Greg" <invalid@invalid.net> wrote in message
>>>>> news:7i85jjF2vj7ecU1@mid.individual.net...
>>>>>> Fatal Error Blue Screen OE 0671:10014490
>>>>>>
>>>>>> Started after I installed Avast after avg quit support.
>>>>> It's 0e (zero-e), not Oe
>>>>>
>>>>> Is that the entire error message? Does it state "Fatal Exception
>>>>> Error 0E0671:10014490" or is there more on the screen? Post
>>>>> everything you see.
>>>>>
>>>>> Can you start Windows? Can you start in Safe Mode?
>>>>> If you can get into Windows either of those ways, disable the Boot
>>>>> Scan if it is enabled:
>>>>>
>>>>> *Right click on the the blue ball Avast icon on the right side of
>>>>> the task bar and select "Start avast! Antivirus."
>>>>> *In the avast! Simple User Interface (upper-left-hand corner),
>>>>> left-click on the menu control and select "Schedule Boot-Time
>>>>> Scan..." *If a scan is already set, it will ask you "avast!:
>>>>> Boot-time scan is already scheduled. Do you want to unschedule the
>>>>> boot-time scan?" Click yes and then click the X in the
>>>>> upper-right-hand corner to close it. *If a scan is not already
>>>>> scheduled, the Schedule window will just appear, and you can click
>>>>> Cancel.
>>>>>
>>>>> Post back with whether it was enabled or not.
>>>> Is that available in the 9X version/installation?
>>>> Previously, it was not available.
>>>> Or was this for the XP part?
>>> My 9x avast! Home Edition v.4.8.1351 has the item in the menu, but
>>> it is ghosted & unusable. Maybe you had to pay for it.
>> Yeah, that's what I remembered. So did you take the update?
>
> Wasn't 1351 the last update? I haven't been informed of another.

I thought S/C mentioned another program update you were going to do
some time in the future... can't help, my recently installed 9X is
locked away and running without anything but a firewall to block *any*
access except from the specific local, and scanned via Linux.

>
>>> But who wants to do a full scan every boot, anyhow? I have always
>>> been well satisfied with just the memory scan at boot & the On-Access
>>> Protection!
>>>
>>>
>> I did, it was one the things I liked about AVG. It had an actual Boot
>> scanner for 9X (from autoexec), not the entire disk but crucial file
>> areas, preload memory, and a few other areas. No other way to
>> autotest, as once the system is fully running, whatever MAY have been
>> in memory or running from disk could easily have placed itself into
>> an unreachable mode. AVAST's Boot checks appears to provide similar
>> to the NTs. Not entirely reliable as the *only* test run, but
>> similar to the old DOS days of scanning before running a shell or
>> whatever, or a TSR AV monitoring activity.
>
> I see what you're saying. Yea, sounds useful. Still, hopefully the
> On-Access Scan, E-Mail Scan &/or the WEB Shield catches them before they
> get in. That's how I'm set.
>
>

Right, that's how I was set as well. Still missed that extra bit of
protection though...

--
MEB
http://peoplescounsel.org/ref/windows-main.htm
Windows Info, Diagnostics, Security, Networking
http://peoplescounsel.org
The "real world" of Law, Justice, and Government
___---

MEB wrote:
> PCR wrote:
>> MEB wrote:
>>> PCR wrote:
>>>> MEB wrote:
>>>>> glee wrote:
>>>>>> "Greg" <invalid@invalid.net> wrote in message
>>>>>> news:7i85jjF2vj7ecU1@mid.individual.net...
>>>>>>> Fatal Error Blue Screen OE 0671:10014490
>>>>>>>
>>>>>>> Started after I installed Avast after avg quit support.
>>>>>> It's 0e (zero-e), not Oe
>>>>>>
>>>>>> Is that the entire error message? Does it state "Fatal Exception
>>>>>> Error 0E0671:10014490" or is there more on the screen? Post
>>>>>> everything you see.
>>>>>>
>>>>>> Can you start Windows? Can you start in Safe Mode?
>>>>>> If you can get into Windows either of those ways, disable the
>>>>>> Boot Scan if it is enabled:
>>>>>>
>>>>>> *Right click on the the blue ball Avast icon on the right side of
>>>>>> the task bar and select "Start avast! Antivirus."
>>>>>> *In the avast! Simple User Interface (upper-left-hand corner),
>>>>>> left-click on the menu control and select "Schedule Boot-Time
>>>>>> Scan..." *If a scan is already set, it will ask you "avast!:
>>>>>> Boot-time scan is already scheduled. Do you want to unschedule
>>>>>> the boot-time scan?" Click yes and then click the X in the
>>>>>> upper-right-hand corner to close it. *If a scan is not already
>>>>>> scheduled, the Schedule window will just appear, and you can
>>>>>> click Cancel.
>>>>>>
>>>>>> Post back with whether it was enabled or not.
>>>>> Is that available in the 9X version/installation?
>>>>> Previously, it was not available.
>>>>> Or was this for the XP part?
>>>> My 9x avast! Home Edition v.4.8.1351 has the item in the menu, but
>>>> it is ghosted & unusable. Maybe you had to pay for it.
>>> Yeah, that's what I remembered. So did you take the update?
>>
>> Wasn't 1351 the last update? I haven't been informed of another.
>
> I thought S/C mentioned another program update you were going to do
> some time in the future... can't help, my recently installed 9X is
> locked away and running without anything but a firewall to block *any*
> access except from the specific local, and scanned via Linux.

You remembered correctly, but v.4.8.1351 was it. When I tried to
download the full program at the site, I seemed to get only 301 KB. I
ran that & was still the prior version! So, I had to update it using
avast!'s menus instead.

But I never got the error Greg spoke of, which glee seems to have
solved.

>>
>>>> But who wants to do a full scan every boot, anyhow? I have always
>>>> been well satisfied with just the memory scan at boot & the
>>>> On-Access Protection!
>>>>
>>>>
>>> I did, it was one the things I liked about AVG. It had an actual
>>> Boot scanner for 9X (from autoexec), not the entire disk but
>>> crucial file areas, preload memory, and a few other areas. No other
>>> way to autotest, as once the system is fully running, whatever MAY
>>> have been in memory or running from disk could easily have placed
>>> itself into an unreachable mode. AVAST's Boot checks appears to
>>> provide similar to the NTs. Not entirely reliable as the *only*
>>> test run, but
>>> similar to the old DOS days of scanning before running a shell or
>>> whatever, or a TSR AV monitoring activity.
>>
>> I see what you're saying. Yea, sounds useful. Still, hopefully the
>> On-Access Scan, E-Mail Scan &/or the WEB Shield catches them before
>> they get in. That's how I'm set.
>>
>>
>
> Right, that's how I was set as well. Still missed that extra bit of
> protection though...

OK. But I'm well satisfied as is.


--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR
pcrrcp@netzero.net

On Mon, 28 Sep 2009 00:37:08 -0400, "PCR" <pcrrcp@netzero.net> wrote:

>
>But I never got the error Greg spoke of, which glee seems to have
>solved.

It has not been solved. I just hope my mainboard is not crashing.


One think I dont like about new computers.
No floppy drives
No dial up modem (Not everyone is on Dsl or wireless)
I pay $10,95 for dial-up (No, not netzero or juno)

I would like a laptop, not wide screen 16.9 or 17 inch flat screen
and a resolution of 800 x 600 with a 56k modem, and a floppy drive,
cdrw drive and network card in case I can get an dsl or wireless
service some day.

I read and heard windows 7 is supposed to be better and faster and run
like windows xp

I am hoping to get windows xp home off of ebay and I hope a legal
version that has not been activated.


Greg