0E errors of all kinds

[Chris]

I get the 0E errors of all kinds, not all at once though. Where do I go to
see what these are all about so that I can get an idea at least?
0E:016F:BFF6A613, 0E:0028:FF1BFE48, FF1BFEAA. And somehow I don't have the
faultlog when I search for it to see what that has recorded. By the way
Google does not get me any useful info. Many thanks.

[Mike M]

What precedes the 0E? Knowing this might help determine the cause. How
long has this been happening? What changes were made to your system just
prior to this problem commencing? Some change must have occurred however
trivial. Such errors are often but by no means always the result of a
driver update of some sort, for example the video or audio drivers.
--
Mike Maltby



Chris > wrote:

> I get the 0E errors of all kinds, not all at once though. Where do I
> go to see what these are all about so that I can get an idea at least?
> 0E:016F:BFF6A613, 0E:0028:FF1BFE48, FF1BFEAA. And somehow I don't
> have the faultlog when I search for it to see what that has recorded.
> By the way Google does not get me any useful info. Many thanks.

[Mart]

0E (or OE) errors are often caused by hardware issues, but can also be
software related.

Next time you get an 0E error, make a note of the EXACT (complete) error
message, there is often a clue in the bit before the 0E:1234:... part of the
error report. And also note exactly what (applications) you were using at
the time and what you did immediately before the error occurred.

BTW - These errors *may* also be related to your previous screen saver
issues

Mart



"Chris" > wrote in message
...
>I get the 0E errors of all kinds, not all at once though. Where do I go to
> see what these are all about so that I can get an idea at least?
> 0E:016F:BFF6A613, 0E:0028:FF1BFE48, FF1BFEAA. And somehow I don't have the
> faultlog when I search for it to see what that has recorded. By the way
> Google does not get me any useful info. Many thanks.

[Mart]

Further to my previous reply, see the MS Knowledge Base article for
example:-
http://support.microsoft.com/kb/265448/en-us

I am not suggesting that this is the actual cause of your problem, but you
can see how difficult it is to try to troubleshoot when a minimal or
incomplete error report is given.

Further, this article also refers to Suspend mode and you refer to "the PC
going into its deep nap" in your previous issue with Noel.

Mart



"Mart" > wrote in message
...
> 0E (or OE) errors are often caused by hardware issues, but can also be
> software related.
>
> Next time you get an 0E error, make a note of the EXACT (complete) error
> message, there is often a clue in the bit before the 0E:1234:... part of
> the error report. And also note exactly what (applications) you were using
> at the time and what you did immediately before the error occurred.
>
> BTW - These errors *may* also be related to your previous screen saver
> issues
>
> Mart
>
>
>
> "Chris" > wrote in message
> ...
>>I get the 0E errors of all kinds, not all at once though. Where do I go to
>> see what these are all about so that I can get an idea at least?
>> 0E:016F:BFF6A613, 0E:0028:FF1BFE48, FF1BFEAA. And somehow I don't have
>> the
>> faultlog when I search for it to see what that has recorded. By the way
>> Google does not get me any useful info. Many thanks.
>
>

[Chris]

Mike, I wanna say I have installed softwares (games by the kids and little
utilities by me), but this has been happening even before them softwares.
Thanks and I will keep an eye.

Mart thanks for the suggestion. I went to the link and read it. I have
previously had Iomega but Uninstalled it. However, I went in the registry and
searched for it and found one key and deleted it. Searchrf in the C drive and
two folders were still there and got ride of them. So, I don't know if this
takes care of it. I will report if I run into them 0Es again. many thanks to
both of you gentlemen!

"Mart" wrote:

> Further to my previous reply, see the MS Knowledge Base article for
> example:-
> http://support.microsoft.com/kb/265448/en-us
>
> I am not suggesting that this is the actual cause of your problem, but you
> can see how difficult it is to try to troubleshoot when a minimal or
> incomplete error report is given.
>
> Further, this article also refers to Suspend mode and you refer to "the PC
> going into its deep nap" in your previous issue with Noel.
>
> Mart
>
>
>
> "Mart" > wrote in message
> ...
> > 0E (or OE) errors are often caused by hardware issues, but can also be
> > software related.
> >
> > Next time you get an 0E error, make a note of the EXACT (complete) error
> > message, there is often a clue in the bit before the 0E:1234:... part of
> > the error report. And also note exactly what (applications) you were using
> > at the time and what you did immediately before the error occurred.
> >
> > BTW - These errors *may* also be related to your previous screen saver
> > issues
> >
> > Mart
> >
> >
> >
> > "Chris" > wrote in message
> > ...
> >>I get the 0E errors of all kinds, not all at once though. Where do I go to
> >> see what these are all about so that I can get an idea at least?
> >> 0E:016F:BFF6A613, 0E:0028:FF1BFE48, FF1BFEAA. And somehow I don't have
> >> the
> >> faultlog when I search for it to see what that has recorded. By the way
> >> Google does not get me any useful info. Many thanks.
> >
> >
>
>
>

[Chris]

Gentlemen, for a few days now no sign of the 0E errors. Who knows maybe it
was due to the screen saver. I hope it was as simple as that. I keep my
fingers crossed. Also, may be getting ride of the remains of the Iomega done
it. At any rate, I will let you know of any recurrences.

"Chris" wrote:

> Mike, I wanna say I have installed softwares (games by the kids and little
> utilities by me), but this has been happening even before them softwares.
> Thanks and I will keep an eye.
>
> Mart thanks for the suggestion. I went to the link and read it. I have
> previously had Iomega but Uninstalled it. However, I went in the registry and
> searched for it and found one key and deleted it. Searched in the C drive and
> two folders were still there and got ride of them. So, I don't know if this
> takes care of it. I will report if I run into them 0Es again. many thanks to
> both of you gentlemen!
>
> "Mart" wrote:
>
> > Further to my previous reply, see the MS Knowledge Base article for
> > example:-
> > http://support.microsoft.com/kb/265448/en-us
> >
> > I am not suggesting that this is the actual cause of your problem, but you
> > can see how difficult it is to try to troubleshoot when a minimal or
> > incomplete error report is given.
> >
> > Further, this article also refers to Suspend mode and you refer to "the PC
> > going into its deep nap" in your previous issue with Noel.
> >
> > Mart
> >
> >
> >
> > "Mart" > wrote in message
> > ...
> > > 0E (or OE) errors are often caused by hardware issues, but can also be
> > > software related.
> > >
> > > Next time you get an 0E error, make a note of the EXACT (complete) error
> > > message, there is often a clue in the bit before the 0E:1234:... part of
> > > the error report. And also note exactly what (applications) you were using
> > > at the time and what you did immediately before the error occurred.
> > >
> > > BTW - These errors *may* also be related to your previous screen saver
> > > issues
> > >
> > > Mart
> > >
> > >
> > >
> > > "Chris" > wrote in message
> > > ...
> > >>I get the 0E errors of all kinds, not all at once though. Where do I go to
> > >> see what these are all about so that I can get an idea at least?
> > >> 0E:016F:BFF6A613, 0E:0028:FF1BFE48, FF1BFEAA. And somehow I don't have
> > >> the
> > >> faultlog when I search for it to see what that has recorded. By the way
> > >> Google does not get me any useful info. Many thanks.
> > >
> > >
> >
> >
> >

[Mart]

Thanks for the update, let's just hope it was either the screensaver or
Iomega issue. I suppose it really depends on how frequent the (inconsistent)
error reports were before - be sure to make a note of the full error reports
for future, should the recur - good luck.

Mart


"Chris" > wrote in message
...
> Gentlemen, for a few days now no sign of the 0E errors. Who knows maybe it
> was due to the screen saver. I hope it was as simple as that. I keep my
> fingers crossed. Also, may be getting ride of the remains of the Iomega
> done
> it. At any rate, I will let you know of any recurrences.
>
> "Chris" wrote:
>
>> Mike, I wanna say I have installed softwares (games by the kids and
>> little
>> utilities by me), but this has been happening even before them softwares.
>> Thanks and I will keep an eye.
>>
>> Mart thanks for the suggestion. I went to the link and read it. I have
>> previously had Iomega but Uninstalled it. However, I went in the registry
>> and
>> searched for it and found one key and deleted it. Searched in the C drive
>> and
>> two folders were still there and got ride of them. So, I don't know if
>> this
>> takes care of it. I will report if I run into them 0Es again. many thanks
>> to
>> both of you gentlemen!
>>
>> "Mart" wrote:
>>
>> > Further to my previous reply, see the MS Knowledge Base article for
>> > example:-
>> > http://support.microsoft.com/kb/265448/en-us
>> >
>> > I am not suggesting that this is the actual cause of your problem, but
>> > you
>> > can see how difficult it is to try to troubleshoot when a minimal or
>> > incomplete error report is given.
>> >
>> > Further, this article also refers to Suspend mode and you refer to "the
>> > PC
>> > going into its deep nap" in your previous issue with Noel.
>> >
>> > Mart
>> >
>> >
>> >
>> > "Mart" > wrote in message
>> > ...
>> > > 0E (or OE) errors are often caused by hardware issues, but can also
>> > > be
>> > > software related.
>> > >
>> > > Next time you get an 0E error, make a note of the EXACT (complete)
>> > > error
>> > > message, there is often a clue in the bit before the 0E:1234:... part
>> > > of
>> > > the error report. And also note exactly what (applications) you were
>> > > using
>> > > at the time and what you did immediately before the error occurred.
>> > >
>> > > BTW - These errors *may* also be related to your previous screen
>> > > saver
>> > > issues
>> > >
>> > > Mart
>> > >
>> > >
>> > >
>> > > "Chris" > wrote in message
>> > > ...
>> > >>I get the 0E errors of all kinds, not all at once though. Where do I
>> > >>go to
>> > >> see what these are all about so that I can get an idea at least?
>> > >> 0E:016F:BFF6A613, 0E:0028:FF1BFE48, FF1BFEAA. And somehow I don't
>> > >> have
>> > >> the
>> > >> faultlog when I search for it to see what that has recorded. By the
>> > >> way
>> > >> Google does not get me any useful info. Many thanks.
>> > >
>> > >
>> >
>> >
>> >