BSOD Stop error 0x0000008e



dave
07-10-2005, 12:50 AM
Hi, I've been getting sporadic BSODs since the weekend when I happened
to run Scandisk. Every time I get an error saying 0x0000008e which
I've seen has to do with hardware - does anyone have any idea what
specifically (or typically) it relates to?
I haven't changed any hardware or software recently.

After the Stop message it also gives an error with WIN32K.sys or
NTFS.sys. I tried to rename WIN32K.sys to .old and rebooted but this
has not solved the problem at all.

Does anyone have any ideas about it? Thanks, in advance.

Maurice N ~ MVP
07-10-2005, 12:50 AM
The error you note is 0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
Take a look at the Troubleshooting Windows STOP messages at Aumha.org

http://aumha.org/win5/kbestop.php



I'm concerned you have other complications on Win32k.sys & NTFS.sys

Do you have a retail or full OEM CD of Windows XP? and not just a System
Recovery CD?


Configure your computer to start from the CD-ROM drive. You do that from the
pc BIOS setup screen. You specify CDROM as the first drive to boot from.


Insert your Windows XP CD into your CD-ROM drive, and then restart your pc.


When the "Press any key to boot from CD" message is displayed on your
screen, press a key to boot pc from the XP CD.


When you see the following message displayed on the Welcome to Setup screen,
press ENTER:
To setup Windows XP now, press ENTER.


At this point an option to press R to enter the Recovery Console is
displayed. Select this option.


NTFS.SYS needs to be at %windir%\system32\drivers [where %windir% =
C:\windows or C:\WINNT ]


You should be able to find NTFS.SYS at %windir%\ServicePackFiles\i386


You can COPY from the \i386 folder to the \system32\drivers folder ....
while in the Recovery Console


COPY C:\Windows\ServicePackFiles\I3ญญ86\NTFS.SYS C:\Windows\System32\drivers




Do likewise for Win32k.sys.

{ change Windows to WINNT if your Windows folder is WINNT }


Once you have stabilized your system, make a complete backup to offline
storage media (CD or DVD).

And then make a visit to Windows Updates to insure you have the latest
critical & security updates.

http://windowsupdate.microsoft.com



--
Maurice N
MVP Windows - Shell / User
---

"dave" wrote
> Hi, I've been getting sporadic BSODs since the weekend when I happened
> to run Scandisk. Every time I get an error saying 0x0000008e which
> I've seen has to do with hardware - does anyone have any idea what
> specifically (or typically) it relates to?
> I haven't changed any hardware or software recently.
>
> After the Stop message it also gives an error with WIN32K.sys or
> NTFS.sys. I tried to rename WIN32K.sys to .old and rebooted but this
> has not solved the problem at all.
>
> Does anyone have any ideas about it? Thanks, in advance.
>

Carey Frisch [MVP]
07-10-2005, 12:50 AM
One or more of the random access memory (RAM) modules
that are installed on your computer may be faulty.

Windows Memory Diagnostic Tool
http://oca.microsoft.com/en/windiag.asp

DocMemory Diagnostic, an advanced self-bootable PC Memory
Diagnostic Software is a user friendly software designed to capture
all possible memory failures in PC.
http://www.simmtester.com/PAGE/products/doc/docinfo.asp

--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User
Microsoft Newsgroups

Get Windows XP Service Pack 2 with Advanced Security Technologies:
http://www.microsoft.com/athome/security/protect/windowsxp/choose.mspx

-------------------------------------------------------------------------------------------

"dave" wrote:

| Hi, I've been getting sporadic BSODs since the weekend when I happened
| to run Scandisk. Every time I get an error saying 0x0000008e which
| I've seen has to do with hardware - does anyone have any idea what
| specifically (or typically) it relates to?
| I haven't changed any hardware or software recently.
|
| After the Stop message it also gives an error with WIN32K.sys or
| NTFS.sys. I tried to rename WIN32K.sys to .old and rebooted but this
| has not solved the problem at all.
|
| Does anyone have any ideas about it? Thanks, in advance.

Ron Martell
07-10-2005, 12:50 AM
"Maurice N ~ MVP" <maurice@mvps.org> wrote:

>The error you note is 0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
>Take a look at the Troubleshooting Windows STOP messages at Aumha.org
>
>http://aumha.org/win5/kbestop.php
>
>

Actually a better link for that page is
http://aumha.org/win5/kbestop.htm

That way the index panels are included with the page.


Ron Martell Duncan B.C. Canada
--
Microsoft MVP
On-Line Help Computer Service
http://onlinehelp.bc.ca

In memory of a dear friend Alex Nichol MVP
http://aumha.org/alex.htm

Ron Martell
07-10-2005, 12:50 AM
"dave" <gavfrancis@gmail.com> wrote:

>Hi, I've been getting sporadic BSODs since the weekend when I happened
>to run Scandisk. Every time I get an error saying 0x0000008e which
>I've seen has to do with hardware - does anyone have any idea what
>specifically (or typically) it relates to?
>I haven't changed any hardware or software recently.
>
>After the Stop message it also gives an error with WIN32K.sys or
>NTFS.sys. I tried to rename WIN32K.sys to .old and rebooted but this
>has not solved the problem at all.
>
>Does anyone have any ideas about it? Thanks, in advance.

If the reference to Win32k.sys is on the same BSOD screen as the STOP
message then the source of the error might be a third-party remote
control program. If such software is installed, the service can be
removed by starting the system using the Recovery Console and deleting
the offending system service file.


Good luck


Ron Martell Duncan B.C. Canada
--
Microsoft MVP
On-Line Help Computer Service
http://onlinehelp.bc.ca

In memory of a dear friend Alex Nichol MVP
http://aumha.org/alex.htm

Maurice N ~ MVP
07-10-2005, 12:50 AM
I got the address from the properties of the page. Should have gotten it from the address bar. <g>
Thanks, Ron.
--
Maurice N
MVP Windows - Shell / User
-----

"Ron Martell" wrote
> "Maurice N ~ MVP" wrote:
>
>>The error you note is 0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
>>Take a look at the Troubleshooting Windows STOP messages at Aumha.org
>>
>>http://aumha.org/win5/kbestop.php
>>
>>
>
> Actually a better link for that page is
> http://aumha.org/win5/kbestop.htm
>
> That way the index panels are included with the page.
>
>
> Ron Martell Duncan B.C. Canada
> --
> Microsoft MVP
> On-Line Help Computer Service
> http://onlinehelp.bc.ca
>
> In memory of a dear friend Alex Nichol MVP
> http://aumha.org/alex.htm

w_tom
07-10-2005, 12:50 AM
Carey's recommendation is to confirm hardware integrity
before fixing software. Her recommendation has merit. Fixing
software on hardware that is problematic can double the
problems.

Usual hardware suspects for such problems include memory,
soundcard, and video controller. Memory being a most common
suspect.

Execute memory diagnostics at room temperature. Then repeat
that diagnostic with memory at temperatures that all good
memory loves. Heat those semiconductors with a hairdryer on
high - to be uncomfortable to touch but does not burn skin.
Then execute the diagnostic again.

Intermittent memory that passes diagnostics at 70 degree F
tend to concede internal problems when operated at above 100
degrees F. Semiconductors must work just fine at temperatures
well above 'hairdryer on high'. Heat semiconductors so that a
diagnostic can find the intermittent failure.

Once hardware integrity is verified under higher
temperature, then move on to the usual software suspects.
Heat is how one finds hardware failures before those failures
become problems.

"Carey Frisch [MVP]" wrote:
> One or more of the random access memory (RAM) modules
> that are installed on your computer may be faulty.
>
> Windows Memory Diagnostic Tool
> http://oca.microsoft.com/en/windiag.asp
>
> DocMemory Diagnostic, an advanced self-bootable PC Memory
> Diagnostic Software is a user friendly software designed to capture
> all possible memory failures in PC.
> http://www.simmtester.com/PAGE/products/doc/docinfo.asp

T. Waters
07-10-2005, 12:50 AM
Great advice.
PS: "Carey" is traditionally a guy name and our Carey has chromosomes of the
XY variety.

w_tom wrote:
> Carey's recommendation is to confirm hardware integrity
> before fixing software. Her recommendation has merit. Fixing
> software on hardware that is problematic can double the
> problems.
>
> Usual hardware suspects for such problems include memory,
> soundcard, and video controller. Memory being a most common
> suspect.
>
> Execute memory diagnostics at room temperature. Then repeat
> that diagnostic with memory at temperatures that all good
> memory loves. Heat those semiconductors with a hairdryer on
> high - to be uncomfortable to touch but does not burn skin.
> Then execute the diagnostic again.
>
> Intermittent memory that passes diagnostics at 70 degree F
> tend to concede internal problems when operated at above 100
> degrees F. Semiconductors must work just fine at temperatures
> well above 'hairdryer on high'. Heat semiconductors so that a
> diagnostic can find the intermittent failure.
>
> Once hardware integrity is verified under higher
> temperature, then move on to the usual software suspects.
> Heat is how one finds hardware failures before those failures
> become problems.
>
> "Carey Frisch [MVP]" wrote:
>> One or more of the random access memory (RAM) modules
>> that are installed on your computer may be faulty.
>>
>> Windows Memory Diagnostic Tool
>> http://oca.microsoft.com/en/windiag.asp
>>
>> DocMemory Diagnostic, an advanced self-bootable PC Memory
>> Diagnostic Software is a user friendly software designed to capture
>> all possible memory failures in PC.
>> http://www.simmtester.com/PAGE/products/doc/docinfo.asp


BSOD Stop error 0x0000008e