Blue Screen error STOP: 0X0000008E in Vista

Can you boot normally or does this message stop the startup process?  Can you boot into any safe mode option?  That pretty much limits us to using the disks which may not be enough to identify and resolve the probllem. I've included all the steps here, but if you can't boot normally and if you can't boot into safe mode either, then just do those you can (they're pretty much the ones listed at the top) and reply back with results.

This STOP error can occur during startup or at any other time. The 8 digit hexadecimal number 0x0000000A translates to the bug check code “IRQL_NOT_LESS_OR_EQUAL” which may be caused by the following:

1. A kernel-level application or device driver running in kernel mode tried to read or write to a memory location that had restricted permissions. The code IRQL_NOT_LESS_OR_EQUAL indicates that the interrupt request level (IRQL) was higher than the number that was expected. A process running in kernel mode cannot access a process that has an IRQL which is greater than its own.
2. Components of the hardware may have failed such as the memory chip, the processor or motherboard. It may also indicate problems in video or disk adapters or device driver incompatibility issues.
3. Computer Hardware may not be Vista compatible. This STOP error usually results from the faulty installation of System Services, BIOS firmware or device drivers. It can also be caused by incompatible virus scanners or backup tools.
4. Sometimes viruses or the anti-virus software that is running on the computer may cause problems.
5. Third party software applications such as device drivers may also have software bugs which access unprotected or restricted memory. Sometimes the name of the application or driver that caused this problem will be displayed on the screen immediately after the STOP error information.
6. You are trying to install Vista on a computer with more than 3GB of RAM
7. You are trying to install Vista on a computer which is running a Storport miniport driver
8. You are trying to install Vista on a computer that has a controller that utilizes 32-bit DMA (direct memory access).
9. Repeatedly putting a laptop with Vista operating system on a sleep cycle mode can also cause this problem.
10. Computer runs QuickTime 7 on Vista which is trying to open a movie file with .mov extension.

The only solution offered is a Startup Repair which is described below.

The following about 0x0000008E is courtesy of Spirit MVP (unfortunately, you need to be able to boot to do much of what is suggested but at least we know more about the problem):

BCCode: 8E  0x0000008E is same as 0x1000008E

CauseBluescrren errors typically mean hardware or driver issues (though it could also be software).  Read the posts and follow the procedures set forth by Spirit MVP in the following thread regarding the Blue Screen of Death.  They should help you resolve your problem.http://social.answers.microsoft.com/Forums/en-US/vistarepair/thread/3deab2fa-4000-4136-8c78-a3d22b1db009.  A lot of that is duplicated below but it also offers some other oprtions and explanatons of bluescreen errors. Some of this information may be useful (but again, many of the recommendations require access to the system so they may be of limited use).

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

Common exception codes include the following:

• 0xC0000005: STATUS_ACCESS_VIOLATION indicates that a memory access violation occurred.

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 might find it difficult to obtain a stack trace. Parameter 2 (the exception address) should identify the driver or function that caused this problem.

If you do not know the specific cause of the exception, consider the following items:

• Hardware incompatibility. Make sure that any new hardware installed is listed in the Microsoft Windows Marketplace Tested Products List.
• Faulty device driver or system service. 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 the bug check message lists a driver by name , disable or remove that driver. Also, 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 have 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, you can remove the service by starting the system by using the Recovery Console and then deleting the offending system service file.

Check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing bug check 0x1E. You can disable memory caching of the BIOS to try to resolve the error. You should also run hardware diagnostics, especially the memory scanner, that the system manufacturer supplies. For more information about 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 drive. Check for and delete any temporary files that you do not have to have, Internet cache files, application backup files, and .chk files that contain saved file fragments from disk scans. You can also use another hard disk drive with more free space for the installation.

You can resolve BIOS problems by upgrading the system BIOS version

 Do you know when this problem began?  Try a System Restore to a point in time BEFORE the problem began.  Here's the procedure:http://www.howtogeek.com/howto/windows-vista/using-windows-vista-system-restore/.  Be sure to check the box to show more than 5 days of restore points.  If the first attempt fails, then try an earlier point or two.  NOTE: You will have to re-install any software and updates you installed between now and the restore point, but you can use Windows Update for the updates.  Use the recovery disk if the system prompt doesn’t work. The recovery disk works a bit different from the above procedures but if you follow the prompts from the System Restore menu option with the above information you should be able to restore with no problems.

If the System Restore doesn't work, do a Startup Repair by booting to the genuine Windows Vista Installation Disk (or one you can borrow from ANYONE) or from a Recovery Disk.  Here's the procedure:http://www.bleepingcomputer.com/tutorials/tutorial148.html.  To boot to the CD you may need to change the BIOS to make the CD-drive first in the boot sequence.  To do that, wait for the screen that tells you the F key to push to access the boot menu or boot setup.  Push it quickly. Make the changes, save your work, and exit.  Put the CD in the drive and reboot.  When prompted, push any key to boot from the CD.

If you don't have either disk, you can make a bootable Recovery Disk using http://neosmart.net/blog/2008/windows-vista-recovery-disc-download/ along with burning software like: http://www.snapfiles.com/get/active-isoburner.html and, of course, a blank CD (perhaps with another computer if necessary).

If that doesn't work, try to boot into safe mode (repeatedly click the F8 key while booting and go to safe mode with networking – or do so from the command prompt on the disk).  Then let's check some of your system files:

Go to Start / All Programs / Accessories / Command prompt and right click on command prompt and click run as Administrator (you can skip this step if using the disk).

If using the disk, cd to C:\Windows\System32. Type sfc /scannow and enter and let it run.  It will scan and try to fix some of your system files.  Hopefully it will complete with no corruption it could not repair (if there is such corruption post back here or try to analyze it to find the problem file(s) using http://support.microsoft.com/kb/928228.  Try to post any corrupted files here so we can see if they can be repaired with good copies from the installation disk (unless there are too many).

While in Command Prompt, type chkdsk /f /r and enter and let it run.  It will want to schedule itself to run at the next restart.   Answer yes and then reboot to run the program.  It will scan and try to fix any corruption or bad sectors on your hard drive and mostly remove that as a potential cause.

If that doesn't work, then please post any repeating error messages from the Event Viewer concerning shutdown (Start / Control Panel / Administrative Tools / Event Viewer – or typing eventvwr from the command prompt starting from C:\Windows\System32).  Here's how to use Event Viewer:http://www.petri.co.il/vista-event-viewer.htm.  Look in the System section.

You can also use Skydrivehttp://news.softpedia.com/news/SkyDrive-Microsoft-s-Windows-Live-Storage-Service-in-the-Cloud-61977.shtml to upload dump and text files related to the error which may help us identify the problem.  Just post back the link to where they are.

You may be infected with malware. Try to run anti-malware programs (in safe mode with networking ifnecessary). To fix this problem (if it is a problem) download, install, and run the following two programs:http://www.malwarebytes.org/mbam.php andhttp://www.safer-networking.org/en/index.html.  You may also want to try a free trial of Pandasoft (http://www.pandasecurity.com/usa/homeusers/solutions/global-protection/).  Before downloading pandasoft, uninstall whatever anti-virus program you are currently using (because installing and running two at the same time can cause conflicts, freezes, and all sorts of problems).  Once you've uninstalled your current AV program, download, install, update, and scan using Pandasoft.  I think you might be amazed at how much it finds that the other software missed.  Once complete, uninstall pandasoft and re-install your current AV program (unless you decide to switch which I did when I first tried it about 4 years ago).  You may also want to try the new, free Microsoft Security Essentialshttp://www.softpedia.com/progDownload/Microsoft-Security-Essentials-Download-131683.html (with the same caveat that only ONE AV program can be installed and running on your system at any one time).  You may also want to try the free Avira at:http://www.free-av.com/ and Avast at:http://www.avast.com/index.  Reboot after completing all the scans.  You may also want to try the free OneCare athttp://onecare.live.com/site/en-us/default.htm and let it run all the options (except the registry cleaner) because that’s good maintenance (it will take some time to complete but can be done in the background).

If that doesn't work, try a clean boot http://support.microsoft.com/kb/929135.  If the problem goes away then it's just a matter of tracking down the culprit causing the problem.   Follow the procedures in the article.  Once found, delete, remove, deactivate, or uninstall it.  Once done be sure to reset Vista back to normal status as explained in the procedures. If the problem occurs in clean mode then just restore the system to normal status and reboot - this solution is not going to work.

Boot into Safe mode with networking and see if the problem occurs there.  Either result helps us narrow down the search for the cause.

You may be having troubles with your device drivers.  Go to Device Manager by going tostart / search box and type device manager and enter and then double-click on the program icon that appears.  Check each device for a red x, yellow ! or white ?.  These identify devices with problems (probably drivers, but also conflicts or something else).  Click on each for further details and troubleshooting tips.  If you need to get drivers (and you should get any you have time to do - they may help in ways beyond just resolving this problem), do so from the computer vendor or device manufacturer (NOT from Microsoft Updates).  In fact, you should turn off automatic driver updates from Windows Update as follows:http://www.addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/. Proceed as follows to get the drivers: http://pcsupport.about.com/od/driverssupport/ht/driverdlmfgr.htm.  Once you have the drivers, you can install them through Device Manager as follows:http://www.vistax64.com/tutorials/193584-device-manager-install-driver.html.You may also want to try the Driver Verifier Manager to see if you can identify the driver or device responsible:http://support.microsoft.com/kb/244617.

Let's test your hard drive and RAM for hardware problems

To test your hard drive, check the manufacturer and then get the diagnostic utility from:http://www.techsupportforum.com/hardware-support/hard-drive-support/302602-hard-drive-diagnostic-utilities.html (and/or get one from your hard drive or computer manufacturer if they have one available – it wouldn’t hurt to try both).  If it fails the test, replace it.  If it passes the test, then there's probably nothing wrong with it.

You can also test your RAM at http://www.memtest.org/.  If it fails, test each chip individually to find those that are bad and replace them.  If it passes, RAM is probably OK.

Here's a link for some additional hardware troubleshooting techniques which may help:http://elephantboycomputers.com/page2.html#Hardware_Tshoot.

Hopefully one of these procedures will resolve or at least identify the cause of your problem.  If not, post back with results from what you tried and copies of some of the scans and we'll try something else.  Post back in any case so we'll know how it turned out.

Good luck!