Troubleshooting Guide
Previous Chapter
Chapter 15:
Troubleshooting common problems in Windows
We’ve saved some of the toughest problems that you can experience on Windows 8 for our last chapter. This includes a detailed analysis and solution to the dreaded Blue Screen of Death as well as the infamous “Unfortunately, Explorer.exe has stopped working” error message. We’ve also compiled a complete directory of common hexadecimal error codes, such as 0xc00003E9, and we’ve provided our solutions.
The Windows File Explorer (identified as Explorer.exe in the Task Manager) is an integral part of the Windows operating system. It handles a lot of tasks that we take for granted, such as browsing files and folders our computer. At some point you might face problems with frequent freezes and crashes regarding the Windows File Explorer, 
especially on a lower-spec machine.
Unfortunately, the error messages are usually not very informative. For example, you might get a blank alert window with the title Explorer.exe and a single OK button or an error message with the text “Unfortunately, Explorer.exe has stopped working.”
If this happened for the first time, you should just restart your machine. If the problem does not persist, then it was an isolated incident, likely caused by corrupted system files. On the other hand, if the crashes are frequent, you’ll have to try the solutions below in order to troubleshoot the problem.
Note: If you were looking for solution regarding problems with Internet Explorer (the web browser) then please see our advice on troubleshooting problems with Internet Explorer.
Ensure Windows is Updated and Safe from Malware
Before you continue, you need to make sure that your PC has all the latest Microsoft updates and that there is no malware that could be the source of the issue. If you do not have automatic updates enabled, we highly recommend that you read our guide to Windows Update. To manually check for updates, do the following steps:
Open the Charms Bar and click or tap on Settings.
Click or tap on Change PC settings. Next, click or tap on Update and recovery.
Click or tap on the Check now button.
Click or tap on the Install button and follow the on-screen instructions to download and install missing updates. Some of them might require administrative privileges and you might need to restart your PC.
As for the possibility of malware, you will need to scan your PC. We’ve written a guide on how to protect your PC from malware that provides tips on using Windows Defender.
Corrupted Files and Exception Code 0xc0000005
As mentioned earlier, corrupted system files are usually a common source of frequent Explorer.exe crashes. Some files can easily restore themselves after a system reboot, causing the problem to go away. However, in some cases you will have to take manual action.
Exception code 0xc0000005 is one such example. You can be sure that you have this problem by reading the error dialogue. Here’s an example of the text you might see:
Faulting application name: Explorer.EXE, version: 6.1.7601.17567, time stamp: 0x4d672ee4
Faulting module name: ntdll.dll, version: 6.1.7601.17514, time stamp: 0x4ce7c8f9
Exception code: 0xc0000005
Fault offset: 0x000000000004e4b4
Faulting process id: 0xfb4
Faulting application start time: 0x01cccbea9be513cb
Faulting application path: C:\Windows\Explorer.EXE
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
The faulting module name and path are extremely important in this case, as they show where the source of the problem is located. To repair these problems we recommend that you run the System File Checker (SFC) utility:
Open the Run application:
- You can use the shortcut Windows key + R or
- Open the Charms Bar; select the Search charm and then type “Run”.
In the Run application type “cmd.exe” and click or tap on OK. This will open the command prompt.
Type the command “sfc /scannow” and press Enter. This will run the System File Checker and activate the scan feature.
SFC will now scan your system files and look for outdated or corrupted fragments and replace them if needed.
In case you receive the error text “Windows Resource Protection Could Not Start the Repair Service” when trying to run SFC, you will have to first type the command “net start trustedinstaller”.
Troubleshooting Third Party Applications
If you suspect that your Explorer.exe crashes are being caused by a third-party application then you will need to investigate this problem manually. The best way to troubleshoot them is to use Safe mode and test the applications one by one. Here’s a rundown of the process:
First, restart your PC.
When the manufacturer logo appears on the screen, press the F8 key repeatedly.
This will open the Advanced Boot options screen. Here you should select the boot option Safe mode with networking.
Your PC will now start in Safe mode with minimum processes and services running in the background. No third-party applications will be launched.
Start browsing through your files and folders to confirm that an Explorer.exe crash doesn’t happen when third-party applications are turned off.
If the above is true, then a third-party application may indeed be the culprit.
To discover which one causes the problem, start one application at a time and do some testing to see if the crash will occur before you start the next one.
Problems with Foreign IMEs
If you are using an Input Method Editor (IME) for a foreign language such as Chinese, Korean or Japanese along with Windows 8 (not 8.1), then this could very likely be the source of your problems with Explorer.exe crashes. Typically, this sort of problem is solved by simply updating from Windows 8 to Windows 8.1, where IMEs do not cause problems with system files.
If you cannot update to 8.1 for the time being, then your options are rather limited. IMEs will edit system files, which can cause substantial problems. You can remove your IMEs and then follow the steps described in the previous section to run the System File Checker utility that will restore your system files to their default settings.
The “Blue Screen of Death” is an infamous error that causes the Windows operating system to shut down or restart unexpectedly. It is a very difficult error to troubleshoot if you cannot pinpoint what caused it. However, this problem is not something that can appear out of the blue and it is most likely to occur if you make a mistake while modifying the PC’s hardware.
The problem can also be caused by software, particularly by unauthorized changes to the core system files. As such, viruses and malware are also a potential source of this problem. In this guide we will give you advice on how to fix the Blue Screen of Death, but should this guide not work for you, remember that you can always contact support or do a clean install of Windows 8.1.
Try the Basics First
If you can still log into Windows, your first course of action should be to make sure you have all the latest updates. If you have automatic updates enabled, then you can skip this step as you should have all the latest updated installed and applied. To manually check for updates, do the following:
Open the Charms Bar and click or tap on Settings.
Click or tap on Change PC settings. Next, click or tap on Update and recovery.
Click or tap on the Check now button.
Click or tap on the Install button and follow the on-screen instructions to download and install missing updates. Some of them might require administrative privileges and you might need to restart your PC.
Along with this, you can consider restoring your system to a previous point in time with the help of our guide on how to refresh, reset or restore in Windows 8.1.
Note that you should remember to disconnect all peripheral devices except your keyboard and mouse while you are trying to resolve this problem.
How to Fix the “DRIVER_IRQL_NOT_LESS_THAN_OR_EQUAL_TO” Stop Code
If the Blue Screen of Death is also including DRIVER_IRQL_NOT_LESS_OR_EQUAL the stop code, then your task has become much easier. Namely, you’ll know that you are dealing with a very specific error and usually the screen will contain a lot of useful information (see the orange box on the screenshot below).
You should read it carefully as it might even include a PATH to the source of the error itself.
With this error message, you’ve probably already guessed that it shows a problem with a driver (or multiple drivers). More specifically, it can be case of missing or corrupted drivers. If you’ve just connected a new piece hardware then it’s very likely that the new hardware is the cause of the problem. You should shut down your PC and check that you’ve connected everything correctly.
Our recommendation is to identify the device that is causing the issue and download the latest driver via the device manufacturer’s website.
Once you’ve downloaded the file, here’s how to proceed:
Open the Device Manager.
In the hardware list, locate your device and then double click or (double tap) on it to open the driver menu.
Tap or click on the Driver tab and then click or tap on Update Driver (this may require 
administrative privileges).
Follow the on-screen instructions in the next menu to install the driver you’ve downloaded.
This process should be done via a clean boot in order to prevent third-party applications and services from interfering with the installation or causing another error. If you don’t know how to enter Windows via a clean (safe) boot, do the following:
Open the Run application:
- You can use the shortcut Windows key + R or
- Open the Charms Bar; select the Search charm and then type “Run”.
Type “msconfig” and then press Enter.
Click the Boot tab, then check Safe Boot and click or tap OK. This will restart the computer and launch the OS in Safe Boot.
How to Fix the “PAGE_FAULT_IN_NONPAGED_AREA” Stop Code
The “PAGE_FAULT_IN_NONPAGED_AREA” stop code is also very specific, although its meaning is not as intuitive as the previous one since it requires some technical knowledge. To keep it simple, the error signifies a problem with your hardware and this is usually related to your RAM modules.
To start troubleshooting this particular issue, turn your PC off and check the RAM modules and hardware cables. You can try leaving only one RAM module at a time inside the PC and rebooting Windows to check if any of the individual modules are faulty. If you can identify that one of the units is not functioning properly, then it is a simple matter of replacing it with new ones.
Additionally, if you’ve recently added any new hardware, you should remove and see if that will solve the problem. Assuming that the new hardware is the source of the issue, consider the following:
- You might have connected the hardware incorrectly on your first attempt, causing the error.
- The hardware is incompatible with your operating system. Check with the manufacturer or retailer if this is the case.
- You did not install the proper drivers after connecting the new hardware to your machine.
How to Fix the “KERNEL_MODE_EXCEPTION_NOT_HANDLED” Stop Code
The kernel is a low-level system program that handles input and output between the hardware and software. If the Blue Screen of Death is printing out the “KERNEL_MODE_EXCEPTION_NOT_HANDLED” stop code (error message) then the following will help you solve your problem:
There might be a problem with your primary (sometimes referred to as master) hard disk.
- If you’ve recently done some maintenance or installed a new hard disk, then you might have made a mistake while connecting the cables with the motherboard. Turn the PC off and make sure that the cables are connected properly.
- Your hard disk doesn’t have enough space and this is leading to memory problems. To clean your disk and remove unnecessary files, follow our tutorial on how to optimize the hard drive in Windows 8.1.
If you’ve recently added other hardware to the PC (a graphic card for example), you need to remove it and confirm if this new hardware component was causing the issue. If so, then you’ve either installed the component incorrectly or it is incompatible with your system (visit the manufacturer website to find more information).
While working with just about any software, especially an operating system, it is not uncommon to encounter errors (stop codes). In Windows 8.1 not every error is necessarily a result of a problem with the operating system. These errors can be caused by a third-party application or the network you are connected to. So far, there are around 16,000 known error codes that have been documented.
In this article, we’ve compiled a list of some of the most common error codes in Windows 8.1 along with advice on how to solve them. We’ve sorted them in ascending order based on the value of the error message, starting from the lowest to the highest, to make it easier for you to navigate the page. However, some of them may not be so simple to solve and we’ll redirect to you to the right resources that provide an in-depth solution.
Error number: 4 or 0xc0000004
Error Message: ERROR_TOO_MANY_OPEN_FILES
Solution: This error sounds intuitive to programmers, but not to the average user. The text of the error message would have you think that you’ve opened too many files, but the error message is actually referring to a running application, not the files opened by user. One of the programs that you are running has opened a lot of sockets without closing them properly, causing a resource leak (orphan processes). The easiest way to deal with this error message is to simply restart your PC.
Error number: 5 or 0xc0000005
Error Message: ERROR_ACCESS_DENIED
Solution: If you are receiving this error message while using a third-party program, then the error is a result of the application trying to access files that it has no access to. On the other hand, you could also be receiving this error code while trying to log into a company/domain network. If that is the case, then try again as you might have mistyped your password. If the problem persists, contact your system administrator.
Error number: 8 or 0xc0000008
Error Message: ERROR_NOT_ENOUGH_MEMORY
Solution: Your PC does not have enough memory to execute the operation that you’ve assigned to the program. Consider optimizing your hard drive to free up some storage space.
Error number: 28 or 0xc000001C
Error Message: ERROR_OUT_OF_PAPER
Solution: As the message suggests, your printer is out of paper and you will need to insert more in order to proceed with printing.
Error number: 29 or 0xc000001D and 30 or 0xc000001E
Error Message: ERROR_WRITE_FAULT or ERROR_READ_FAULT
Solution: Usually you will receive this error after failing to write or read from a file on a device (usually an external one). There are three possible causes:
- The program you are using is trying to access a device that is no longer connected to the computer.
- The device is not connected properly. If it is a USB-connected device, consider reading our USB troubleshooter.
- Your device is connected properly, but there are missing drivers. If there was an installation disk that came with the device, insert it into the PC and install the drivers. If not, search online (especially on the manufacturer’s website) to download the latest drivers. If you don’t know how to install drivers, have a look at our guide to downloading and installing drivers for Windows 8.1.
Error number: 50 or 0xc0000032
Error Message: ERROR_NOT_SUPPORTED
Solution: This error indicates that Windows is having trouble connecting to a network, generally to your Internet Service Provider. The error is most common with dial-up connections. It is recommended that you restart or even reinstall your modem. If the error persists, call your ISP for support.
Error number: 54 or 0xc0000036
Error Message: ERROR_NETWORK_BUSY
Solution: This is a very generic error that signifies that the network (usually a corporate domain) you are connected to is having some problems. Sometimes the network simply didn’t have the resources to service every request and the problem fixes itself after a few minutes. It’s best to contact your system administrator for support.
Error number: 71 or 0xc0000047
Error Message: ERROR_REQ_NOT_ACCEP
Solution: You are trying to connect to a remote computer, but that computer cannot accept any more incoming connections and requests.
Error number: 534 or 0xc0000216
Error Message: ERROR_ARITHMETIC_OVERFLOW
Solution: This error message is a result of bad programming. The program you are running has received a calculation result that exceeds the standard 32bits and the application does not know how to handle this overflow. Unfortunately, there is no way for the user to resolve this problem.
Error number: 1001 or 0xc00003E9
Error Message: ERROR_STACK_OVERFLOW
Solution: Overflowing the stack is a common problem in programming. The program that you’re using has run out of memory addresses and the pointer has overflowed from its stack. You can try restarting the application or the PC if this problem persists. If you are running resource-heavy software on a low-spec machine, consider upgrading your RAM increase performance to avoid memory-related issues in the future.
Error number: 1203 or 0xc0000483
Error Message: ERROR_NO_NET_OR_BAD_PATH
Solution: Usually, this error is the result of a typo. You’ve typed in the wrong network path or you’ve typed in the network path incorrectly.
Error number: 1314 or 0xc0000522
Error Message: ERROR_PRIVILEGE_NOT_HELD
Solution: The program/client that you are using is trying to execute a command or access resource that requires administrative privileges. There are two possible reasons and solutions for this problem:
- If you are using a local guest account or another type of account with only the basic access rights, then you cannot authorize the program to perform the required task. You’ll need to log into an account with higher privileges.
- If you do have administrator rights, you can close the program and then re-open it by right-clicking (or press and hold) the program’s icon and selecting Run as Administrator from the contextual menu.
Error number: 1642 or 0xc000066A
Error Message: ERROR_PATCH_TARGET_NOT_FOUND
Solution: This error occurs when the user tries to install an upgrade patch for a third-party program. It is likely that the program you are trying to upgrade has been deleted or the upgrade patch can only update a different version of the program. Your only course of action is to verify that the program exists on your machine and that the target path for the patch is accurate. If the software vendor provides support for their product be sure to contact them for assistance.
Error number: 2404 or 0xc0000 964
Error Message: ERROR_DEVICE_IN_USE
You are trying to disconnect (for example, via safely remove hardware) or remove (uninstall) a device that is currently being used by a program or process. Use the Task Manager to identify and close the programs that are using the device and then try again. If you are not sure how to do this, read up on our tutorial on using the Task Manager in Windows 8.1.
