"<*(((><{" <> wrote in message
news:...
> Who can help me ID this error:
> I have XP Home SP2, and just installed these updates:
> Recovered from a Serious Error:
> Error Signature
> BCCode : 1000008e BCP1 : C0000005 BCP2 : EF7670E8 BCP3 :
> EFDD5B80
> BCP4 : 00000000 OSVer : 5_1_2600 SP : 2_0 Product : 768_1
That is often caused by an error in a device driver.
There should be additional information given on the blue screen
with the stop code. E.g. see the example in this article:
<title>KB310740 - A "STOP: 0x1000008E In
....
Ignore the title. Just look at the example.
Actually I think you could equally well refer to the more common
stop code 0x0000008E as well. I'm pretty sure that that high
order nibble is just a dump action flag (e.g. the whole thing is not
a significantly different code.)
More information:
http://aumha.org/win5/kbestop.php
That article tried to link us back to an MSDN article
but as usual it was moved and renamed. ; ]
Here's the new location (for who knows how long ; } )
http://msdn.microsoft.com/library/de...d0ddbf.xml.asp
Alternatively you might be able to get a clue about the driver involved
from the second parameter. E.g. using pstat -s (in a cmd window)
see if you can find a module which contains that address.
pstat.exe is a command line tool which comes in the
XP Support Tools package.
HTH
Robert Aldwinckle
---
Similar Threads
Linear Mode
