Fatal Error Blue Screen OE 0671:10014490

PCR wrote:
> MEB wrote:
>> glee wrote:
>>> "Greg" <invalid.TakeThisOut@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 DeleteThis @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 DeleteThis @netzero.net

PCR wrote:
> MEB wrote:
>> PCR wrote:
>>> MEB wrote:
>>>> glee wrote:
>>>>> "Greg" <invalid.TakeThisOut@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.TakeThisOut@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.TakeThisOut@netzero.net

On Mon, 28 Sep 2009 00:37:08 -0400, "PCR" <pcrrcp DeleteThis @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

"Bill in Co." <not_really_here.DeleteThis@earthlink.net> wrote in message news:%23o$i0Y%23PKHA.352@TK2MSFTNGP02.phx.gbl...
> Bill Blanton wrote:
>> "Greg" <invalid.DeleteThis@invalid.net> wrote in message
>> news:7ia0vqF30mjq8U1@mid.individual.net...
>>> On Sun, 27 Sep 2009 13:32:26 -0400, "glee" <glee29.DeleteThis@spamindspring.com>
>>> wrote:
>>
>>>> "Greg" <invalid.DeleteThis@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.

And even Quadrovigesimal (base-24) doesn't use the letter 'O', so there is
no confusion with zero..

(I'd never heard that word before either Googled on base 24..
http://en.wikipedia.org/wiki/Base_24