BCCode : 10000008e

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Can anyone tell me what this specific error means. I cannot find any
document that matches this string of errors exactly.

BCCode: 1000008e
BCP1: C0000005
BCP2: F734B8B2
BCP3: F1DC57B4
BCP4: 00000000

OSVer: 5_1_2600 SP 2_0 Product 256_1

Closest thing I can find to this error is recommends a BIOS update, and the
PC being infected by the Haxdoor virus. The only problem with both of these
solutions is that the error codes described are not exact to the error code
I'm getting. Any help would be appreciated.
 
Sarah said:
Can anyone tell me what this specific error means. I cannot find any
document that matches this string of errors exactly.

BCCode: 1000008e
KERNEL_MODE_EXCEPTION_NOT_HANDLED

BCP1: C0000005

The Exception Code that cause the error was STATUS_ACCESS_VIOLATION
BCP2: F734B8B2

The error occurred at this address in memory.

BCP3: F1DC57B4

Trap frame address (probably not relevant to this exception code)
BCP4: 00000000

Parameter 4 is not used by this error code.

OSVer: 5_1_2600 SP 2_0 Product 256_1

Closest thing I can find to this error is recommends a BIOS update, and the
PC being infected by the Haxdoor virus. The only problem with both of these
solutions is that the error codes described are not exact to the error code
I'm getting. Any help would be appreciated.


From the MSDN reference document for this error code:

"If the specific cause of the exception is unknown, the following
should be considered:

Hardware incompatibility. First, make sure that any new hardware
installed is listed in the Microsoft Windows Catalog.

Faulty device driver or system service. In addition, a faulty device
driver or system service might be responsible for this error. Hardware
issues, such as BIOS incompatibilities, memory conflicts, and IRQ
conflicts can also generate this error."



The absence of a specific driver file name makes the problem a bit
more difficult. There is a procedure using the PSTAT utility that can
identify the problem driver, but it is a bit cumbersome. If the
problem recurs then post a response back here and I will give you
instructions on how to do it.

Also check in Event Viewer for any other error messages that occurred
at or nearly at the same time as this one. Right-click on My
Computer and select Manage. Click on the + to expand the Event Viewer
category to show the 3 or 4 subcategories. Browse through the System
and Application categories and check out any entries there with date
and time stamps that correspond to your error.

Good luck




Good luck
Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2006)
On-Line Help Computer Service
http://onlinehelp.bc.ca

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."
 
Thanks Ron. This helps a lot...as in now I know which direction to go with.
I will get back with you on the events that I can find. I know this has
happened more than once over the past week with the particular user of this
computer. Thanks again for all of the information.
 
Back
Top