I saw this error many times on my display screen. Although MS uses this
error for many occurrence depending what program or process was being used
at the time of the system failure. In my case I was pointed to a display
driver like you were. After a number of trial and error replacements , ram
was the culprit. Try here. Jym
http://support.microsoft.com/?kbid=330187
"Walter Cohen" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hmmm....where have you seen the '8e' before? Is there some master list of
> these codes that I can refer to? I believe my RAM is decent. From when I
> built my system I put in CAS2 ram.
>
> Why do you say RAM when the message states 'device driver'?
>
> Thanks,
> Walter
>
> "Jym" <I'(E-Mail Removed)> wrote in message
> news:#(E-Mail Removed)...
> > The "8E" error code usually relates to bad or poor performing system
ram.
> Do
> > you have high quality ram installed? XP unfortunately need a better
> quality
> > of ram than the Win 98 products. Bad ram will cause many types of system
> > problems. Jym
> >
> >
> >
> > "Walter Cohen" <(E-Mail Removed)> wrote in message
> > news:%(E-Mail Removed)...
> > > I periodically get the typical XP recovery message saying that an
error
> > > occurred by a device drive and I should send it to MS. It always
flags
> a
> > > device driver but I have yet to determine what device driver it refers
> to.
> > >
> > > Here's the message:
> > > 'A device driver installed on your system caused the problem, but we
> > cannot
> > > determine the precise cause.'
> > >
> > > I have gone into event viewer but still no luck.
> > > It tells me 'System Error', category (102), Event 1003
> > > The event error log shows:
> > >
> > > Sunday, January 18, 2004 System Error Error code 1000008e,
> > parameter1
> > > c0000005, parameter2 bf8713ef, parameter3 ef1deb7c, parameter4
00000000.
> > >
> > > Any ideas on how to determine the device drive rcausing the crash is
> > > appreciated.
> > > Thanks.
> > > Walter
> > >
> > >
> >
> >
>
>
Similar Threads
