Resolve Blue Screen Error 0x00000109

The Error 0x00000109 (BSOD) occurs during the startup sequence and prevents affected users from using their computers. In most cases, this error will occur during every system startup, making the affected PC completely unusable.

What’s causing the Error 0x00000109 and How to Troubleshoot it?

Method 1: Booting in Safe Mode

For the vast majority of affected users, the issue doesn’t return once they manage to boot their computer in Safe mode. This is confirmation that the problem occurs due to a 3rd party application or due to a recently installed driver that is somehow interfering with the BCD (Boot Configuration Data).

If this scenario is applicable, you should boot your computer in Safe Mode and see if the 0x00000109 error still occurs during the startup sequence. If it doesn’t occur in Safe Mode, you will confirm that a driver or application is causing the stop error.

In this case, you can fix the issue by reverting your machine state to an earlier state or by pinpointing and identifying the problematic driver/application

Here’s a quick guide on booting your computer in Safe Mode:

1. Power on your computer.
2. As soon as you see the initial startup screen, start pressing the F8 key repeatedly until you see that the Advanced Boot Options menu comes up.
3. Once you’re inside the Advanced Boot Options menu, use the arrow keys to select Safe Mode or press the corresponding key (F4).

   

4. Wait until the booting sequence is complete. If you no longer see the Stop Error 0x00000109 Blue Screen of Death, you can conclude that the issue is being caused by a 3rd party driver or application.

Note: If the same Stop Error 0x00000109 occurs even in Safe Mode, move directly to Method 3. 

If this scenario is applicable and the error doesn’t occur while you boot in Safe Mode, follow the methods below for multiple ways of pinpointing and taking care of the culprit.

Method 2: Using System Restore

If the investigation above has revealed that a driver or a recently installed service or process ends up producing the error code during the startup procedure, there’s only one method that will allow you to take care of the issue swiftly.

Sure, you might attempt to identify the culprit by looking through the crash logs, but depending on the file responsible, you might not come up with any leads.

One universal fix with the potential of resolving the Stop Error 0x00000109 regardless of the responsible culprit is to use the System Restore utility to return your PC state back to a healthy state in which the same circumstances that are currently causing the problem weren’t present.

Here’s a quick guide on using the System Restore utility to circumvent the Stop Error 0x00000109:

1. If you’re not already in Safe Mode, follow Method 1 again to boot safely and avoid the stop error.
2. Press Windows key + R to open up a Run dialog box. Next, type ‘rstrui’ and press Enter to open up the System Restore wizard.

   

3. Once you’re ar the first System Restore wizard screen, click Next at the first screen.

   

4. After you manage to get to the next screen, start by checking the box associated with Show more restore points. Next, select a restore point that is dated before you started to deal with this particular startup error. Once the correct restore point is selected, click Next to advance to the next menu.

   

5. Once you get this far, the utility is ready to go. All you have to do now is click on Finish to start the process.

   

   Note: Before you start this process, you need to understand that every change that was that you implemented after the change was enforced (including installed drivers, apps and everything else) will be lost in this process.

6. Once the process is complete, your computer will automatically restart and the old state will be enforced during the next startup.

If the same issue is still occurring during the next system startup, move down to the next method below.

Method 3: Running SFC and DISM Commands

If the investigations above have revealed that the issue is not being caused by an installed application or a recent driver change, there’s a high chance that the issue is being caused by some type of system file corruption.

Since this stop error doesn’t allow you to get past the boot sequence, you will need to perform reparations without actually booting your Windows installation. The only way to do this is to open an elevated Command Prompt using the Advanced Options menu.

To fix OS corrupted files, we will use two built-in utilities that are capable of dealing with system file corruption – DISM (Deployment Image Servicing and Management) and SFC (System File Checker).

DISM is better at fixing corrupted dependencies while SFC is equipped to tackle logical error, so our recommendation is to run both utilities in order.

Here’s a quick guide on do running SFC and DISM scans from a CMD opened inside the Advanced Options menu:

1. Start by inserting an installation media compatible with your computer. Then, restart your computer and press any key when you see prompt.

   

   Note: If you don’t own a compatible installation media, you can also force the Advanced Startup Options menu to come up by forcing three consecutive startup interruptions. To do this, shut down your computer during the booting sequence.  In this case, jump directly to step 3.

2. Once you manage to boot from the installation media, click on Repair your computer (bottom-left corner of the screen).

   

3. At the next menu, select the Troubleshooting menu from the list of available options, then select Advanced options. Next, choose Command Prompt to open up an elevated CMD.

   

4. Once you manage to get inside the elevated Command prompt window, type the following command and press Enter to start the System File Checker scan:

   sfc /scannow

   Note: SFC uses a locally stored folder to replace corrupted files with healthy equivalents. It’s not advisable to interrupt this process until the process is complete. Doing so means that you leave your system exposed to additional logical errors.

5. Once the scan is complete, restart your computer and re-follow the steps above to return to the same elevated CMD screen as before. After you manage to return, type the following commands in order and press Enter after each one to investigate and fix corruption issues using DISM:

   Dism /Online /Cleanup-Image /CheckHealth
   Dism /Online /Cleanup-Image /ScanHealth
   Dism /Online /Cleanup-Image /RestoreHealth

   Note: DISM uses a Windows update subcomponent to download healthy copies of the files that are corrupted and need to be replaced. Before you initiate this procedure, make sure you are connected to a stable network.

6. After the second scan is finished, restart your computer and see if the issue is resolved.

If the same Stop 0x00000109 error is still occurring, move down to the next potential fix below.

Method 4: Performing a repair install / clean install

If none of the methods above have allowed you to resolve the issue, it’s clear that you’re dealing with some type of system file corruption that cannot be resolved with non-intrusive methods. If this scenario is applicable, the only way that will allow you to fix your Windows installation and allow it to boot without the 0x00000109 error is to refresh every Windows component and any Boot related data.

Looking at your options, there are two different ways that will allow you to do this:

• Repair install – This is a tedious process that will require you to use the installation media, but the major advantage is that it will allow you to keep all your personal files without having to back them up in advance. This includes applications, games, personal media, and even some user preferences.
• Reinstall Windows – This is easier to perform and it doesn’t require any installation media on Windows 10. But be prepared for complete data loss if it’s stored on the OS drive (it will be wiped completely during this operation).