Sign in with
Sign up | Sign in
Your question

Help with a Hardware error

Last response: in Windows XP
Share
May 20, 2004 4:50:12 PM

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

A user's XP Pro PC had a stop error. When it rebooted it
had a message saying that the system has recovered from a
serious problem. She had it send the error report to
Microsoft.

Going through the event log I found an error in the system
log:
Source System Error
Category: (102)
Event ID: 1003
Description: Error code 1000008e, parameter1 c0000005,
parameter2 bf860d20, parameter3 f808e78c, parameter4
00000000

I know error code 1000008e is a hardware/driver issue.

My question is this, is there anyway to identify which
hardware component is causing this aside from swapping
them out one by one?

The PC is brand new and all hardware and peripherals
should work with XP.

Thanks for any help.

More about : hardware error

Anonymous
May 20, 2004 5:06:47 PM

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

If it's brand new it comes with a guarantee. SEND IT BACK!!!!!

--
Cari
MS-MVP Windows Technologies - Printing/Imaging/Hardware
www.coribright.com

"Eric" <anonymous@discussions.microsoft.com> wrote in message
news:fd5e01c43ea3$a9d0c7c0$a101280a@phx.gbl...
>A user's XP Pro PC had a stop error. When it rebooted it
> had a message saying that the system has recovered from a
> serious problem. She had it send the error report to
> Microsoft.
>
> Going through the event log I found an error in the system
> log:
> Source System Error
> Category: (102)
> Event ID: 1003
> Description: Error code 1000008e, parameter1 c0000005,
> parameter2 bf860d20, parameter3 f808e78c, parameter4
> 00000000
>
> I know error code 1000008e is a hardware/driver issue.
>
> My question is this, is there anyway to identify which
> hardware component is causing this aside from swapping
> them out one by one?
>
> The PC is brand new and all hardware and peripherals
> should work with XP.
>
> Thanks for any help.
Anonymous
May 20, 2004 7:02:43 PM

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

That's all well and good (an quite glib I must say) but
you did not answer his question which was:

Is there anyway to identify which hardware component is
causing this aside from swapping them out one by one?

I'd like to know the answer too !



>-----Original Message-----
>If it's brand new it comes with a guarantee. SEND IT
BACK!!!!!
>
>--
>Cari
>MS-MVP Windows Technologies - Printing/Imaging/Hardware
>www.coribright.com
>
>"Eric" <anonymous@discussions.microsoft.com> wrote in
message
>news:fd5e01c43ea3$a9d0c7c0$a101280a@phx.gbl...
>>A user's XP Pro PC had a stop error. When it rebooted it
>> had a message saying that the system has recovered from
a
>> serious problem. She had it send the error report to
>> Microsoft.
>>
>> Going through the event log I found an error in the
system
>> log:
>> Source System Error
>> Category: (102)
>> Event ID: 1003
>> Description: Error code 1000008e, parameter1 c0000005,
>> parameter2 bf860d20, parameter3 f808e78c, parameter4
>> 00000000
>>
>> I know error code 1000008e is a hardware/driver issue.
>>
>> My question is this, is there anyway to identify which
>> hardware component is causing this aside from swapping
>> them out one by one?
>>
>> The PC is brand new and all hardware and peripherals
>> should work with XP.
>>
>> Thanks for any help.
>
>
>.
>
Related resources
Anonymous
May 20, 2004 8:46:03 PM

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

Since the PC is under guarantee swapping/removing hardware will probably
invalidate the guarantee.
--
Cari (MS-MVP Windows Client - Printing, Imaging & Hardware)
www.coribright.com

"MGGP" <anonymous@discussions.microsoft.com> wrote in message
news:fe6601c43eb6$2cebfe10$a101280a@phx.gbl...
> That's all well and good (an quite glib I must say) but
> you did not answer his question which was:
>
> Is there anyway to identify which hardware component is
> causing this aside from swapping them out one by one?
>
> I'd like to know the answer too !
>
>
>
> >-----Original Message-----
> >If it's brand new it comes with a guarantee. SEND IT
> BACK!!!!!
> >
> >--
> >Cari
> >MS-MVP Windows Technologies - Printing/Imaging/Hardware
> >www.coribright.com
> >
> >"Eric" <anonymous@discussions.microsoft.com> wrote in
> message
> >news:fd5e01c43ea3$a9d0c7c0$a101280a@phx.gbl...
> >>A user's XP Pro PC had a stop error. When it rebooted it
> >> had a message saying that the system has recovered from
> a
> >> serious problem. She had it send the error report to
> >> Microsoft.
> >>
> >> Going through the event log I found an error in the
> system
> >> log:
> >> Source System Error
> >> Category: (102)
> >> Event ID: 1003
> >> Description: Error code 1000008e, parameter1 c0000005,
> >> parameter2 bf860d20, parameter3 f808e78c, parameter4
> >> 00000000
> >>
> >> I know error code 1000008e is a hardware/driver issue.
> >>
> >> My question is this, is there anyway to identify which
> >> hardware component is causing this aside from swapping
> >> them out one by one?
> >>
> >> The PC is brand new and all hardware and peripherals
> >> should work with XP.
> >>
> >> Thanks for any help.
> >
> >
> >.
> >
Anonymous
May 20, 2004 9:28:39 PM

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

Is there anyway to identify which hardware component is
causing this ?

You could just say I DON'T KNOW


>-----Original Message-----
>Since the PC is under guarantee swapping/removing
hardware will probably
>invalidate the guarantee.
>--
>Cari (MS-MVP Windows Client - Printing, Imaging &
Hardware)
>www.coribright.com
>
>"MGGP" <anonymous@discussions.microsoft.com> wrote in
message
>news:fe6601c43eb6$2cebfe10$a101280a@phx.gbl...
>> That's all well and good (an quite glib I must say) but
>> you did not answer his question which was:
>>
>> Is there anyway to identify which hardware component is
>> causing this aside from swapping them out one by one?
>>
>> I'd like to know the answer too !
>>
>>
>>
>> >-----Original Message-----
>> >If it's brand new it comes with a guarantee. SEND IT
>> BACK!!!!!
>> >
>> >--
>> >Cari
>> >MS-MVP Windows Technologies - Printing/Imaging/Hardware
>> >www.coribright.com
>> >
>> >"Eric" <anonymous@discussions.microsoft.com> wrote in
>> message
>> >news:fd5e01c43ea3$a9d0c7c0$a101280a@phx.gbl...
>> >>A user's XP Pro PC had a stop error. When it
rebooted it
>> >> had a message saying that the system has recovered
from
>> a
>> >> serious problem. She had it send the error report to
>> >> Microsoft.
>> >>
>> >> Going through the event log I found an error in the
>> system
>> >> log:
>> >> Source System Error
>> >> Category: (102)
>> >> Event ID: 1003
>> >> Description: Error code 1000008e, parameter1
c0000005,
>> >> parameter2 bf860d20, parameter3 f808e78c, parameter4
>> >> 00000000
>> >>
>> >> I know error code 1000008e is a hardware/driver
issue.
>> >>
>> >> My question is this, is there anyway to identify
which
>> >> hardware component is causing this aside from
swapping
>> >> them out one by one?
>> >>
>> >> The PC is brand new and all hardware and peripherals
>> >> should work with XP.
>> >>
>> >> Thanks for any help.
>> >
>> >
>> >.
>> >
>
>
>.
>
May 23, 2004 2:35:52 AM

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

It seems that the error has a multitude of possible causes listed in the
MSKB
One such is:
http://support.microsoft.com/default.aspx?scid=kb;en-us;322267

"MGGP" <anonymous@discussions.microsoft.com> wrote in message
news:fe6601c43eb6$2cebfe10$a101280a@phx.gbl...
> That's all well and good (an quite glib I must say) but
> you did not answer his question which was:
>
> Is there anyway to identify which hardware component is
> causing this aside from swapping them out one by one?
>
> I'd like to know the answer too !
>
>
>
> >-----Original Message-----
> >If it's brand new it comes with a guarantee. SEND IT
> BACK!!!!!
> >
> >--
> >Cari
> >MS-MVP Windows Technologies - Printing/Imaging/Hardware
> >www.coribright.com
> >
> >"Eric" <anonymous@discussions.microsoft.com> wrote in
> message
> >news:fd5e01c43ea3$a9d0c7c0$a101280a@phx.gbl...
> >>A user's XP Pro PC had a stop error. When it rebooted it
> >> had a message saying that the system has recovered from
> a
> >> serious problem. She had it send the error report to
> >> Microsoft.
> >>
> >> Going through the event log I found an error in the
> system
> >> log:
> >> Source System Error
> >> Category: (102)
> >> Event ID: 1003
> >> Description: Error code 1000008e, parameter1 c0000005,
> >> parameter2 bf860d20, parameter3 f808e78c, parameter4
> >> 00000000
> >>
> >> I know error code 1000008e is a hardware/driver issue.
> >>
> >> My question is this, is there anyway to identify which
> >> hardware component is causing this aside from swapping
> >> them out one by one?
> >>
> >> The PC is brand new and all hardware and peripherals
> >> should work with XP.
> >>
> >> Thanks for any help.
> >
> >
> >.
> >
!