Table of Contents:
- What Is a Blue Screen Error?
- Check the Action Center for Problems and Solutions
- Run an Online Diagnostic
- Troubleshooting Common Blue Screen Error Messages
- UNMOUNTABLE BOOT VOLUME and INACCESSIBLE BOOT DEVICE
- NTFS FILE SYSTEM
- SYSTEM THREAD EXEPTION NOT HANDLED and KERNEL MODE EXCEPTION NOT HANDLED
- PAGE FAULT IN NON PAGED AREA
- DRIVER IRQL NOT LESS THAN OR EQUAL TO
- THREAD STUCK IN DEVICE DRIVER
- Look for information about error message
This article is for Microsoft Windows 8.
Click below to change the operating system.
Troubleshoot Blue Screen Issues in Windows
Closed captions: Available in multiple languages Click the Closed Caption icon and select the language that you want.
When Windows encounters certain situations, it stops and the resulting diagnostic information is displayed in white text on a blue screen. The appearance of these errors is where the term "Blue Screen" or "Blue Screen" has come from. For Windows 8, the blue screen has changed and now displays an ASCII frown face and the statement "Your PC ran into a problem that it could not handle, and now it must restart." followed by the error type. The familiar "OxXXXXXXXX" error code has been removed.
Blue Screen errors occur when:
- Windows detects an error that it cannot recover from without losing data
- Windows detects that critical operating system data has become corrupted
- Windows detects that hardware has failed in a nonrecoverable fashion
- The exact text displayed has changed over the years from a dense wall of information in Windows NT 4.0 to the comparatively sparse message employed by modern versions of Windows.
Windows 8 crash errors are collected in Action Center and referenced against other crash data that is available online. To access the Action Center, follow these instructions:
- Type "Problem Reports and Solutions" at the Start Screen, then select View all problem Reports to view a list of errors that have occurred on your computer and possible solutions for them, such as updating drivers, flash your system BIOS, or check for updates to software.
- Alternate Instructions:
- Swipe in from the right side of the screen to open your Charms bar (if using a mouse, hover on the upper right corner of the screen and move the pointer down to open the Charms bar) then select Settings. Alternately, press the Windows + I keys to go directly to the Settings Charm.
- Select Control Panel.
- Select System and Maintenance.
- Select Problem Reports and Solutions.
Dell has created a set of online diagnostics that can identify problems with your computer hardware or configuration that may be causing the issue. Browse to the Dell Online Diagnostics to get more information and run a scan of your computer.
UNMOUNTABLE BOOT VOLUME
INACCESSIBLE BOOT DEVICE
These two errors have similar causes, and the same troubleshooting steps apply to both of them. These stop codes always occur during the startup process. When you encounter one of these stop codes, the following has happened:
- The system has completed the Power-On Self-Test (POST).
- The system has loaded NTLDR and transferred control of the startup process to NTOSKRNL (the kernel).
- NTOSKRNL is confused. Either it cannot find the rest of itself, or it cannot read the file system at the location it believes it is stored.
When troubleshooting this error, your task is to find out why the Windows kernel is confused and fix the cause of the confusion.
Things to check
- The SATA controller configuration in the system BIOS If the SATA controller gets switch from ATA to AHCI mode (or conversely), then Windows cannot talk to the SATA controller because the different modes require different drivers. Try switch the SATA controller mode in the BIOS.
- RAID settings You may receive this error if you have been experimenting with the RAID controller settings. Try changing the RAID settings back to Autodetect (usually accurate).
- Improperly or poorly seated cabling Try reseating the data cables that connect the drive and its controller at both ends.
- Hard drive failure Run the integrated diagnostics on the hard drive. Remember: Code 7 signifies correctable data corruption, not disk failure.
- File system corruption Launch the recovery console from the Windows installation disc and run chkdsk /f /r.
- Improperly configured BOOT.INI (Windows Vista) If you have inadvertently erased or tinkered with the boot.ini file, you may receive stop code 0x7B during the startup process. Launch the recovery console from the Windows installation disc and run BOOTCFG /REBUILD
This stop code indicates that the NTFS file system driver encountered a situation it could not handle, and is almost always caused by 3 things:
- Data corruption on the disk
- Data corruption in memory
- The system completely running out of memory (this typically only happens on heavily loaded servers)
Things to check
- Reseat the memory and all drive data cables to eliminate data corruption issues stemming from poorly or improperly seated hardware.
- Run a complete memory and hard drive diagnostic. The quick test will not be thorough enough here. You must run the full system diagnostic.
- If those diagnostics pass, run a full file system check from the Recovery Console (chkdsk /f /r) to detect and (potentially) fix any corrupted data.
- If none of the above solves the issue, reinstall Windows.
- If that does not fix the issue, replace the hard drive.
SYSTEM THREAD EXEPTION NOT HANDLED
KERNEL MODE EXCEPTION NOT HANDLED
These two errors indicate that a program running in the kernel encountered an unexpected condition it could not recover from. They have identical troubleshooting and resolution steps, and you will probably need to use the Windows Debugger to find out what caused the error.
Things to check
- If the Blue Screen message mentions a driver or library file, figure out what driver or application that file is part of and update or disable it.
- Update the system BIOS to the latest available revision.
- Uninstall any recently installed programs, and roll back any recently installed drivers.
- Run diagnostics on the computer's memory.
PAGE FAULT IN NON PAGED AREA
This stop code means that the system tried to access a nonexistent piece of memory, almost always due to:
- A driver trying to access a page of memory that is not present
- A system service (ex. virus scanner) failing in an exceptional way
- Faulty or incorrectly seated memory
- Corrupted data on the hard drive
Use the Windows Debugger to pinpoint the exact cause of these errors.
Things to check
- If the Blue Screen error mentions a driver or library file, figure out what driver or program the file is a part of and either upgrade to the latest version or uninstall the driver or program.
- If the error happens during the startup process, try booting to the Last Known Good Configuration.
- If the error started appearing after a program or driver was installed, uninstall that program or driver.
- Try running a full hard drive and memory diagnostic after reseating the memory and hard drive data cables.
DRIVER IRQL NOT LESS THAN OR EQUAL TO
This stop code indicates that a driver tried to access a certain area of memory when it should not have, meaning there is a flaw in the driver itself. The goal of your troubleshooting is to find that driver and either disable or replace it. Use the Windows Debugger to troubleshoot this error.
Without the debugger, you are limited to uninstalling/updating/rolling back the driver that contains the driver file the Blue Screen mentions.
THREAD STUCK IN DEVICE DRIVER
This Blue Screen error indicates that a device driver-almost always a video card driver-is stuck waiting for something (usually a hardware operation) to happen. Most of you have probably seen nv4_disp.sys associated with this Blue Screen.
Things to check:
- Ensure that the video drivers are updated to the latest Dell version.
- The system BIOS is fully up to date.
- If both the video driver and the system BIOS are fully up-to-date, check with the manufacturer for recent driver updates.
- As a last resort, try exchanging the video card.
NOTE: Reinstalling Windows is not likely to prevent this error from recurring.
If these solutions have not resolved your issue, try searching for additional solutions on the Web.
Click on your preferred search engine below, then describe your problem, including any specific error messages.
The Microsoft Bug Check Code Reference
site has an extensive list of blue screen error codes descriptions and possible causes. If you have recorded your STOP 0xXXXXXX code, and the above steps have not resolved your issue try looking it up on this site.
Search Dell Search Microsoft Search Google Search Bing
No Cause Information is Available.
No Resolution Information is Available.