PP0_INITIALIZATION_FAILED: 5 Ways to Fix the BSOD

The PP0_INITIALIZATION_FAILED blue screen error with a bug check (value) of 0x0000008F appears when the Plug and Play (PnP) manager cannot be loaded during the system initialization, i.e. Phase 0.

The PP0 Initialization Failed BSOD error is usually caused by outdated/corrupt drivers, misconfigured boot settings, outdated BIOS, corrupt system files, and low system resources.

Before you start troubleshooting, install all available Windows updates, clear any overclocking settings, and disconnect non-critical peripherals. For many of you, these simple checks should fix the PP0_INITIALIZATION_FAILED BSOD.

How do I fix PP0_INITIALIZATION_FAILED blue screen error?

Tip

If you can’t sign into Windows, boot the PC into Safe Mode with Networking and then try the solutions listed next

1. Update all the drivers

1. Press Windows + X to open the Power User menu, and select Device Manager from the list.
2. Expand the different entries here, individually right-click on the devices listed underneath, and select Update driver.
3. Click on Search automatically for drivers and let Windows install the best locally available version.
4. Similarly, update the other drivers and then restart the PC.

In 3 out of 5 cases, updating the driver quickly fixes the PP0_INITIALIZATION_FAILED Windows crash. If the OS can’t automatically find a better version, head to the manufacturer’s website, locate the latest release, and then manually install the driver!

2. Run the DISM and SFC scans

1. Press Windows + R to open Run, type cmd, and hit Ctrl + Shift + Enter.
2. Click Yes in the UAC prompt.
3. Paste the following DISM commands individually and hit Enter after each: DISM /Online /Cleanup-Image /CheckHealth DISM /Online /Cleanup-Image /ScanHealth DISM /Online /Cleanup-Image /RestoreHealth
4. Now, run this SFC scan command: sfc /scannow
5. Finally, restart the PC and check for improvements.

If you are getting PP0_INITIALIZATION_FAILED Windows blue screen due to corrupt system files, running the SFC (System File Checker) and DISM (Deployment Image Servicing and Management) scans should replace these protected files with their cached copy stored on the PC.

3. Disable fast startup

1. Press Windows + S to open Search, type Control Panel in the text field, and click on the relevant result.
2. Click on System and Security.
3. Now, click on Change what the power buttons do under Power Options.
4. Click on Change settings that are currently unavailable.
5. Untick the checkbox for Turn on fast startup, and then click on Save changes.
6. Reboot the PC and verify whether the BSOD error reappears.

4. Reset or update the BIOS

Since the PP0_INITIALIZATION_FAILED error appears during the system initialization stage, it could have to do with a misconfigured or outdated BIOS. So, you should first reset the BIOS to the default settings, and if that doesn’t work, install the latest BIOS version!

Remember, the steps for both reset and update differ across manufacturers. So, I recommend you visit the OEM’s website, check the exact steps and follow them as is, because changes to the BIOS can prove detrimental if not done precisely.

5. Perform an in-place upgrade

NOTE

The steps listed below are for Windows 11. If you are running the previous iteration, check our dedicated guide on performing a repair upgrade in Windows 10.

1. Go to Microsoft’s official website, choose the OS edition and language, and then download the Windows 11 ISO.
2. Double-click the ISO file, wait for a few seconds, and then click on Open in the confirmation prompt.
3. Run the setup.exe file.
4. Click Yes in the UAC prompt.
5. Click on Next to proceed.
6. Read Microsoft’s license terms and click Accept to continue.
7. Finally, verify that the setup reads, Keep personal files and apps, and then click on Install.
8. Wait for the upgrade to complete. It will take 30-90 minutes.

An in-place upgrade effectively fixes the PP0_INITIALIZATION_FAILED blue screen error in Windows. It’s like reinstalling Windows, except for the fact that your personal files and installed apps remain unaffected.

Advanced users can also check the BSOD crash logs to identify and fix the software-based underlying cause, if any.

In case you still can’t boot Windows due to the BSOD, contact OEM’s support or visit a local repair shop because, at this point, this looks like more of a hardware issue. The professionals will need to check the connections, inspect the components, and make the necessary repairs/replacements!

For any queries or to share which fix worked for you, drop a comment below.