Tom's Hardware > Forum > Windows XP > Windows XP General Discussion > Help with a Hardware error

Help with a Hardware error

Forum Windows XP : Windows XP General Discussion - Help with a Hardware error

Tom's Hardware: Over 1.4 million members in 6 different countries available to answer all your high-tech questions. Sign up now! Its free!
Word :    Username :           
 

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.

Sponsored Links
Register or log in to remove.

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.

Reply to Anonymous

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.
>
>
>.
>

Reply to Anonymous

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.
> >
> >
> >.
> >

Reply to Anonymous

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.
>> >
>> >
>> >.
>> >
>
>
>.
>

Reply to Anonymous
- 0 +

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/defau [...] -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.
> >
> >
> >.
> >

Reply to Chuck
Tom's Hardware > Forum > Windows XP > Windows XP General Discussion > Help with a Hardware error
Go to:

There are 1271 identified and unidentified users. To see the list of identified users, Click here.

Please mind

You are about to answer a thread that has been inactive for more than 6 months.
If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.

Add a reply Cancel
Sponsored links
  • Ask the community now
  • Publish
Ad
They won a badge
Join us in greeting them