Stop Error Message on Boot

[Guest]

I am getting a stop error message on boot. The code it shows is 0x0000008E
(0xc0000005,0xc0000128,0xX7abc3fc,0x00000000). I get nothing on this when i
do a google search. The computer automatically reboots when this bsod shows.
It goes by so quick i had to videotape my screen and then play it back frame
by frame. Any suggestions on how to fix this?

 

[David Candy]

Driver Development Tools: Windows DDK

Bug Check 0x8E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
The KERNEL_MODE_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000008E. This indicates that a kernel-mode program generated an exception which the error handler did not catch.

Parameters
The following parameters are displayed on the blue screen.

Parameter Description
1 The exception code that was not handled
2 The address at which the exception occurred
3 The trap frame
4 Reserved


Cause
This is a very common bug check. To interpret it, you must identify which exception was generated.

Common exception codes include:

a.. 0x80000002: STATUS_DATATYPE_MISALIGNMENT
An unaligned data reference was encountered.

b.. 0x80000003: STATUS_BREAKPOINT
A breakpoint or ASSERT was encountered when no kernel debugger was attached to the system. •

c..

d.. 0xC0000005: STATUS_ACCESS_VIOLATION

A memory access violation occurred.

For a complete list of exception codes, see the ntstatus.h file located in the inc directory of the Windows DDK.

Resolving the Problem
If you are not equipped to debug this problem, you should use some basic troubleshooting techniques. Make sure you have enough disk space. If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates. Try changing video adapters. Check with your hardware vendor for any BIOS updates. Disable BIOS memory options such as caching or shadowing.

If you plan to debug this problem, you may find it difficult to obtain a stack trace. Parameter 2 (the exception address) should pinpoint the driver or function that caused this problem.

If exception code 0x80000003 occurs, this indicates that a hard-coded breakpoint or assertion was hit, but the system was started with the /NODEBUG switch. This problem should rarely occur. If it occurs repeatedly, make sure a kernel debugger is connected and the system is started with the /DEBUG switch.

If exception code 0x80000002 occurs, the trap frame will supply additional information.

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 on the Microsoft Windows Hardware Compatibility List (HCL).

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.

If a driver is listed by name within the bug check message, disable or remove that driver. Disable or remove any drivers or services that were recently added. If the error occurs during the startup sequence and the system partition is formatted with NTFS file system, you might be able to use Safe Mode to rename or delete the faulty driver. If the driver is used as part of the system startup process in Safe Mode, you need to start the computer by using the Recovery Console to access the file.

If the problem is associated with Win32k.sys, 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.

Check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing bug check 0x1E. Disabling memory caching of the BIOS might also resolve the error. You should also run hardware diagnostics, especially the memory scanner, supplied by the system manufacturer. For details on these procedures, see the owner’s manual for your computer.

The error that generates this message can occur after the first restart during Windows Setup, or after Setup is finished. A possible cause of the error is lack of disk space for installation and system BIOS incompatibilities. For problems during Windows installation that are associated with lack of disk space, reduce the number of files on the target hard disk. Check for and delete any unneeded temporary files, Internet cache files, application backup files, and .chk files containing saved file fragments from disk scans. You can also use another hard disk with more free space for the installation. BIOS problems can be resolved by upgrading the system BIOS version.

Try choosing Last Known Good from the startup menu. Try choosing Safe Mode. What did you do on the last working boot?

 

[Drew Tognola]

This link should give a little more insight into your problem.
http://msdn.microsoft.com/library/d..._12795dee-19a9-4461-a135-bbb882b81455.xml.asp

Drew

I am getting a stop error message on boot. The code it shows is 0x0000008E
(0xc0000005,0xc0000128,0xX7abc3fc,0x00000000). I get nothing on this when i
do a google search. The computer automatically reboots when this bsod
shows.
It goes by so quick i had to videotape my screen and then play it back
frame
by frame. Any suggestions on how to fix this?

 

[Richard Urban]

You didn't Google very well.

My first try here
http://www.google.com/search?hl=en&q=0x0000008E&btnG=Google+Search

--
Regards,

Richard Urban

aka Crusty (-: Old B@stard

If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

 

[Guest]

I already looked through many of those posts, none of them are for my
specific problem, there are many 0x0000008E problems, my "specific" one does
not show up in google. I know that 0x0000008E will show up.

 

[Rick \Nutcase\ Rogers]

Hi,

The group of codes following the 0x8E error may be random, though the first
one indicates a memory access violation (program trying to access a
protected area of memory). If this just started, there is a good chance that
the system was infected with spy or adware since the last boot. Sometimes
you can use the last known good config, or get past it by booting safe mode.
Then run spyware cleaners like AdAware (www.lavasoft.de) or Spybot
(www.safer-networking.org).

If that fails, create a boot disk with BartPE (http://www.nu2.nu/pebuilder)
and include those programs, and also stinger
(http://vil.nai.com/vil/stinger) to check for viruses. Then boot the system
with this disk and run them.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org

 

[Ron Martell]

I am getting a stop error message on boot. The code it shows is 0x0000008E
(0xc0000005,0xc0000128,0xX7abc3fc,0x00000000). I get nothing on this when i
do a google search. The computer automatically reboots when this bsod shows.
It goes by so quick i had to videotape my screen and then play it back frame
by frame. Any suggestions on how to fix this?

To stop the reboots use Control Panel - System - Advanced and click on
the Settings button in the Startup and Recovery (bottom) section. In
the Startup and Recovery window click on the checkbox for
"automatically restart" to clear it. Click on Apply and OK as needed
to exit.

See http://www.aumha.org/win5/kbestop.htm and click on the "8E: Kernel
Mode Except..." link in the left side column for some more detailed
information about your error and the possible causes.

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

 

[Guest]

Let me tell all of you what I have done so far and maybe someone else can
think of something else. I have done 3 virus scans, i have used ad-aware,
spybot and xoftspy. I have replaced the video driver, the sound driver, the
network driver, and the cd burner driver, i have flashed the bios, i have
tryed last known good and i have also tryed to go to an earler configuration,
none of that has worked. Anything else other than a clean wipe?

 

[Kelly]

Read here:
http://www.google.com/search?hl=en&q=0x0000008E&btnG=Google+Search

--
In memory of our dear friend, MVP Alex Nichol: http://www.dts-l.org/

All the Best,
Kelly (MS-MVP)

Troubleshooting Windows XP
http://www.kellys-korner-xp.com

 

[David Candy]

If you can't boot how did you do all that? If you can boot it's simple to find the cause.

 

[Ron Martell]

Let me tell all of you what I have done so far and maybe someone else can
think of something else. I have done 3 virus scans, i have used ad-aware,
spybot and xoftspy. I have replaced the video driver, the sound driver, the
network driver, and the cd burner driver, i have flashed the bios, i have
tryed last known good and i have also tryed to go to an earler configuration,
none of that has worked. Anything else other than a clean wipe?

As a driver related issue is the prime suspect for this type of error
you could try using the Driver Verifier utility that comes with
Windows XP.

Use Start - Run and enter VERIFIER in the dialog box.
Choose the "Create Standard Settings" option and click on Next
Choose the "Automatically select unsigned drivers" option and click on
Next
Click on Finish and then shut down and restart the computer.

You will (hopefully) be presented with a new "Blue Screen Of Death"
STOP error message that will identify the specific driver and the
exact problem involved.

Note: You will have to reboot into Safe Mode or into "last known good
configuration" if you get the BSOD when running Verifier.

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

 

[Guest]

I cannot boot into regular windows mode, i can only boot into safe mode

 

[Guest]

Thanks for the try, but that did not work either, i still get the exact same
blue screen.

 

[David Candy]

Turn verifier on, turn create Small Memory Dump (a minidump) on (type Small Memory Dump in Help if you don't know how). Try to boot. A minidump file will be created. Type minidump in Start Run to find it. Email it to david at mvps.org. My answer will be posted back here after I analyse it.