A Windows 98 & ME forum. Win98banter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » Win98banter forum » Windows 98 » General
Site Map Home Authors List Search Today's Posts Mark Forums Read Web Partners

Fatal Error Blue Screen OE 0671:10014490



 
 
Thread Tools Display Modes
  #11  
Old September 27th 09, 07:23 PM posted to microsoft.public.win98.gen_discussion
MEB[_18_]
External Usenet User
 
Posts: 537
Default Fatal Error Blue Screen OE 0671:10014490


glee wrote:
"Greg" wrote in message
...
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
___---
  #12  
Old September 27th 09, 09:42 PM posted to microsoft.public.win98.gen_discussion
Greg[_2_]
External Usenet User
 
Posts: 143
Default Fatal Error Blue Screen OE 0671:10014490

On Sun, 27 Sep 2009 13:32:26 -0400, "glee"
wrote:

"Greg" wrote in message
...
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.

  #13  
Old September 27th 09, 09:42 PM posted to microsoft.public.win98.gen_discussion
Greg[_2_]
External Usenet User
 
Posts: 143
Default Fatal Error Blue Screen OE 0671:10014490

On Sun, 27 Sep 2009 13:32:26 -0400, "glee"
wrote:

"Greg" wrote in message
...
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.

  #14  
Old September 28th 09, 12:49 AM posted to microsoft.public.win98.gen_discussion
Bill Blanton
External Usenet User
 
Posts: 441
Default Fatal Error Blue Screen OE 0671:10014490

"Greg" wrote in message ...

On Sun, 27 Sep 2009 13:32:26 -0400, "glee"
wrote:


"Greg" wrote in message
...
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.




  #15  
Old September 28th 09, 12:49 AM posted to microsoft.public.win98.gen_discussion
Bill Blanton
External Usenet User
 
Posts: 441
Default Fatal Error Blue Screen OE 0671:10014490

"Greg" wrote in message ...

On Sun, 27 Sep 2009 13:32:26 -0400, "glee"
wrote:


"Greg" wrote in message
...
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.




  #16  
Old September 28th 09, 03:48 AM posted to microsoft.public.win98.gen_discussion
Bill in Co.
External Usenet User
 
Posts: 1,335
Default Fatal Error Blue Screen OE 0671:10014490

Bill Blanton wrote:
"Greg" wrote in message
...
On Sun, 27 Sep 2009 13:32:26 -0400, "glee"
wrote:


"Greg" wrote in message
...
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. :-)


  #17  
Old September 28th 09, 03:48 AM posted to microsoft.public.win98.gen_discussion
Bill in Co.
External Usenet User
 
Posts: 1,335
Default Fatal Error Blue Screen OE 0671:10014490

Bill Blanton wrote:
"Greg" wrote in message
...
On Sun, 27 Sep 2009 13:32:26 -0400, "glee"
wrote:


"Greg" wrote in message
...
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. :-)


  #18  
Old September 28th 09, 04:14 AM posted to microsoft.public.win98.gen_discussion
PCR
External Usenet User
 
Posts: 4,396
Default Fatal Error Blue Screen OE 0671:10014490

MEB wrote:
glee wrote:
"Greg" wrote in message
...
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



  #19  
Old September 28th 09, 04:14 AM posted to microsoft.public.win98.gen_discussion
PCR
External Usenet User
 
Posts: 4,396
Default Fatal Error Blue Screen OE 0671:10014490

MEB wrote:
glee wrote:
"Greg" wrote in message
...
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



  #20  
Old September 28th 09, 04:50 AM posted to microsoft.public.win98.gen_discussion
MEB[_18_]
External Usenet User
 
Posts: 537
Default Fatal Error Blue Screen OE 0671:10014490

PCR wrote:
MEB wrote:
glee wrote:
"Greg" wrote in message
...
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
___---
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
blue screen of ' fatal error' johnn General 18 September 2nd 06 08:04 PM
blue screen fatal exception charles bridges Setup & Installation 1 January 11th 06 07:31 PM
Fatal Blue Screen mjfox General 2 March 16th 05 08:34 AM
Fatal Exception with blue screen Robin Improving Performance 0 June 23rd 04 09:23 PM
blue screen with message fatal error OE has ocurred at line casper Improving Performance 0 May 22nd 04 07:19 AM


All times are GMT +1. The time now is 05:01 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 Win98banter.
The comments are property of their posters.