Fix: 0xc0000142 Blue Screen error on Windows 11/10

The 0xc0000142 blue screen error comes with the bug check STATUS_DLL_INIT_FAILED. It indicates that a dynamic link library (DLL) file failed to initialize while running an application or a system process, causing it to crash abnormally.

It results in a Blue Screen of Death (BSOD) error if this crash affects some important system processes. However, you may also get a non-fatal (that doesn’t cause a shutdown) error while opening certain applications with the same code. The solutions in both scenarios are similar but in this article, we focus more on the BSOD.

There are two potential causes of this Blue Screen error, corruption of DLL files and bugs in the application and system processes that call those DLL files. So you need to repair the files or the processes to resolve the issue.

How to Fix 0xc0000142 Blue Screen Error?

First, restart your PC in case the BSOD results due to minor issues with your system. If you still encounter the issue, you need to apply the possible solutions we have mentioned below.

Run Startup Repair

If you get stuck in a startup loop, the first thing you should do is run startup repair. It will likely enable you to log in to an account and you can perform further troubleshooting methods to resolve the error.

1. Press and hold the power button for two seconds to force shut down your PC. Then, boot it up again.
2. Repeat this step an additional three times.
3. Then click on Advanced options when you get to a blue screen to access the Advanced Startup options.
4. Here, go to Troubleshoot > Advanced options > Startup Repair.
   

If startup repair doesn’t get you out of the startup loop, you need to boot in safe mode and apply the successive fixes.

Repair Corrupt System Files

Since this error results due to issues with the DLL files, you should check for system integrity violations and repair any corrupt files.

You can use the System File Checker (SFC) and Deployment Image Servicing and Management (DISM) for this purpose. It’s also better to run CHKDSK in case some sectors of your system drivers are corrupt.

Here’s how you can run these utilities:

1. Press Win + R to open Run.
2. Type cmd and press Ctrl + Shift + Enter to open the Elevated Command Prompt.
3. Enter the following commands:
   • dism /online /cleanup-image /restorehealth
   • sfc /scannow
   • chkdsk /r /x C:
     

If you are stuck in a startup BSOD loop, you can also perform this method from boot.

1. Go to the Advanced Startup options using the steps from the first method.
2. Then, select Troubleshoot > Advanced options > Command Prompt.
3. Type bcdedit and press Enter.
4. Under Boot Loader, check the drive letter in device and osdevice. In our example, we use E: and D: respectively.
   
5. Then, enter the following commands:
   • chkdsk /r /x D:
   • dism  /image:D: /cleanup-image  /restorehealth
   • sfc /scannow /offbootdir=E: /offwindir=D:\Windows

Reinstall Application

If you are experiencing this BSOD while running any application, the issue is likely with the app’s software. In such a case, you need to uninstall the app and install the latest version. Before that, you should check the official websites for any compatibility issues.

Regardless, here’s how you can reinstall the program:

1. Open Run by pressing Win + R.
2. Type appwiz.cpl and press Enter to open Programs and Features.
3. Search for and click on the recently installed software.
4. Select Uninstall and follow the on-screen instructions.
   
5. Then, go to the official website of the application.
6. Download its installer and run it to reinstall the app.

Update or Roll back Windows

Developers create the latest applications while considering the latest system. If your OS is outdated, it may not support all applications and drivers leading to this issue. It’s best to install Windows updates as soon as they are available.

Follow the instructions below to manually update your system:

1. Open Run (Win + R).
2. Enter ms-settings:windowsupdate to open Update Settings.
3. If updates are available, click Install now or Download & install. Otherwise, click on Check for updates.
   

If you started encountering this issue right after a system update, you need to roll back Windows until further updates are available. To do so,

1. Open Run and enter appwiz.cpl.
2. Go to View installed updates.
3. Select the most recent update by checking the Installed On column and click Uninstall > Yes.
   

If you are stuck in a startup look and can’t log in, you can go to Troubleshoot > Advanced options > Uninstall Recent Updates after booting to Advanced Startup to roll back your system.

Disable Arbitrary Loading of DLLs

Windows includes a setting that causes even inessential DLL files to load on each user-mode process. So, if you open any application, the system loads even those DLL files that the program doesn’t need. In such cases, if the unnecessary DLL file is corrupt, you will encounter this BSOD error.

You can disable this setting to prevent such issues. To do so,

1. Open Run.
2. Type regedit and press Enter to open the Registry Editor.
3. Navigate to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows
4. Double-click on LoadAppinit_DLLs and set the Value data to 0.
   
5. Click OK.

Restart your PC to apply the changes to this entry.

Analyze Minidump File

Analyzing a minidump file is an advanced troubleshooting method that you can adopt to pinpoint the exact cause of a BSOD error. You need a debugger to analyze the file. So, here are the necessary steps to install a debugger and examine the minidump:

1. Go to Microsoft Install Microsoft WinDbg Preview from Microsoft Store.
2. Search for the app on the search bar.
3. Right-click on it and select Run as administrator.
   
4. Press Ctrl + D, navigate to C:\Windows\Minidump and select the minidump file.
5. Click Open to load the file to the debugger.
6. On the bottom part of the window, you will find a command line interface. Enter !analyze -v there. If you can’t find it, select View > Command.
   
7. After the analysis is complete, look out for MODULE_NAME and probably caused by to determine the cause of the BSOD.

If it points to a driver or an application, you can update or reinstall them. And if it points to some system files, you need to repair them or restore your system to a healthy state.

Perform In-place Repair

Another method you can use to repair your DLL and other system files is to perform an in-place repair. It reinstalls all Windows system files without affecting your applications and user files.

Follow the instructions below to perform the repair:

1. Download Windows ISO installation file matching your system build and language.
2. Double-click on it to mount it to a virtual drive and open the drive.
3. Run setup.exe by double-clicking on it.
4. Select Change how Windows Setup downloads updates.
   
5. Tick Not right now and click Next.
6. If it displays the license terms, accept it.
7. On the Ready to install page, click Install.
   

Run System Restore

If the previous methods fail to resolve your BSOD error, you need to restore your system to the restore point at the time when you had not encountered this error. Here’s how you can do so,

1. Open Run and enter rstrui to open System Restore.
2. Select the appropriate restore point and follow the on-screen instructions.
   

You can also run the System Restore app from Advanced Startup by going to Troubleshoot > Advanced options > System Restore.

If you don’t have a suitable restore point, you need to reset your system or clean install Windows.