How to Fix Windows Bug Check 0x00000090 PP1_INITIALIZATION_FAILED

Quick Answer

The Windows stop code PP1_INITIALIZATION_FAILED (0x00000090) indicates that the kernel-mode Plug and Play (PnP) manager failed during Phase 1 initialization. This phase prepares registry information and other system settings required for subsequent device-driver I/O initialization.

The error does not identify one specific faulty driver or hardware component. Troubleshooting should focus on recent hardware and driver changes, Windows startup problems, system configuration, and crash dump analysis. Start with basic hardware checks and Windows recovery options before attempting advanced repairs.

What Is PP1_INITIALIZATION_FAILED?

PP1_INITIALIZATION_FAILED is a Windows kernel bug check commonly displayed as a Blue Screen of Death (BSOD). Its hexadecimal stop code is 0x00000090, equivalent to decimal 144.

Plug and Play (PnP) is a Windows technology that allows the operating system to detect, configure, and manage hardware devices such as USB peripherals, storage devices, network adapters, keyboards, and other connected components.

During startup, Windows initializes its kernel components and device-management infrastructure in different phases. This error occurs when the kernel-mode PnP manager cannot complete its Phase 1 initialization.

Bug Check Technical Details

Property	Details
Bug Check Name	PP1_INITIALIZATION_FAILED
Bug Check Code	0x00000090
Decimal Value	144
Error Type	Windows kernel bug check
Related Component	Kernel-mode Plug and Play manager
Failed Initialization Phase	Phase 1
Bug Check Parameters	None documented
Typical Result	Windows stops and displays a system error screen

Microsoft explains that Phase 1 initialization includes setting up registry files and other environmental settings needed by drivers during subsequent I/O initialization.

Official reference: Microsoft Bug Check 0x90: PP1_INITIALIZATION_FAILED.

Common Causes of PP1_INITIALIZATION_FAILED

Microsoft documents the failed initialization phase but does not identify one universal root cause. The following are possible areas to investigate when diagnosing this stop code.

1. Device Driver Problems

A recently installed, incompatible, damaged, or malfunctioning kernel-mode driver may interfere with device initialization. Pay particular attention to drivers installed or updated shortly before the first crash.

2. Recent Hardware Changes

Newly installed hardware, expansion cards, storage devices, USB peripherals, or replacement components may introduce device initialization or compatibility problems.

3. Windows Registry or Configuration Problems

The PnP manager relies on registry information and system configuration during initialization. Damaged or inconsistent configuration data may be relevant when investigating startup failures, although this stop code alone does not establish registry corruption.

4. Incomplete Windows Updates

An interrupted update or a problem beginning immediately after a Windows update may justify investigating recent system changes and update installation history.

5. Third-Party System Software

Low-level system utilities, device-management applications, security software, and other programs that install kernel drivers may be relevant if the error started after their installation or update.

6. Hardware or Storage Problems

Hardware instability, storage errors, or problems accessing system configuration files may contribute to broader startup failures. Investigate these possibilities using diagnostic evidence rather than assuming that hardware failure is responsible.

Symptoms of the 0x00000090 Error

A computer experiencing this bug check may exhibit one or more of the following symptoms:

• A blue screen displaying PP1_INITIALIZATION_FAILED.
• The hexadecimal error code 0x00000090 appearing on the error screen.
• Unexpected restarts during Windows startup.
• Windows becoming stuck in a repeated boot or restart cycle.
• Failure to reach the Windows sign-in screen.
• Repeated crashes after a hardware or driver change.
• Windows starting successfully sometimes but crashing during other startup attempts.

These symptoms are not unique to this bug check. Other Windows startup and hardware problems can produce similar behavior.

How to Troubleshoot PP1_INITIALIZATION_FAILED

Follow the procedures below in order. Begin with simple checks and move to recovery or advanced diagnostics only when necessary.

1. Restart the Computer and Disconnect Newly Added Devices

If the error appeared only once, allow Windows to restart and check whether the system starts normally.

If the problem continues:

1. Shut down the computer completely.
2. Disconnect recently added USB devices and unnecessary external peripherals.
3. If you recently installed internal hardware, remove it only if you are qualified to do so and can safely access the computer.
4. Reconnect only essential peripherals such as the keyboard, mouse, and display.
5. Start the computer and check whether Windows loads successfully.

If disconnecting a particular device changes the behavior, investigate its compatibility, firmware, connection, and manufacturer-provided driver.

2. Start Windows in Safe Mode

Safe Mode starts Windows with a limited set of drivers and services. It can help determine whether a recently installed driver or nonessential startup component is involved.

If Windows cannot start normally, use the Windows Recovery Environment (WinRE).

1. Allow Windows to attempt startup and enter the recovery environment if automatic recovery becomes available.
2. Select Troubleshoot.
3. Open Advanced options.
4. Select Startup Settings.
5. Select Restart.
6. After restarting, press the number key for Enable Safe Mode.

If device encryption or BitLocker is enabled, Windows may require the recovery key to access recovery options.

If Windows works in Safe Mode but crashes during normal startup, investigate drivers, services, and other components that are not loaded in the same way in Safe Mode. This observation narrows the investigation but does not identify the exact cause.

Reference: Microsoft Windows Startup Settings.

3. Check Device Manager for Driver Problems

If Windows starts successfully, inspect Device Manager for devices reporting problems.

1. Right-click the Start button.
2. Select Device Manager.
3. Expand relevant hardware categories.
4. Look for devices displaying a yellow warning symbol.
5. Open the device properties and review its status and driver details.
6. If a problem started after a driver update, consider using the Roll Back Driver option when available.

If a newly installed device or driver appears related to the crash, obtain the appropriate driver from the computer manufacturer or hardware vendor.

Avoid installing random driver packages from unofficial download websites. Do not disable or uninstall essential storage, boot, or system devices without understanding the recovery implications.

4. Review Recent Windows Updates

If PP1_INITIALIZATION_FAILED started immediately after a Windows update, investigate whether the update is associated with the change in behavior.

If Windows starts:

1. Open Settings.
2. Select Windows Update.
3. Open Update history.
4. Review recently installed updates.
5. Check whether the first crash occurred after a particular update.

If Windows cannot start, you may be able to uninstall a recent update through Windows Recovery Environment:

1. Boot into Windows Recovery Environment.
2. Select Troubleshoot.
3. Open Advanced options.
4. Select Uninstall Updates.
5. Choose the appropriate update removal option and follow the instructions.

Removing an update is appropriate when the timing and available evidence support investigating it. It is not a confirmed fix for every 0x90 error.

5. Check Available Disk Space and Storage Health

Insufficient free space or storage problems can contribute to broader Windows stability and startup issues.

If Windows is accessible:

1. Open File Explorer.
2. Select This PC.
3. Check the available space on the Windows system drive.
4. Investigate any unusually low free-space condition.

Also review storage health using the computer manufacturer's diagnostic utility or the storage manufacturer's supported diagnostic software.

Do not format, repartition, or initialize a drive during initial troubleshooting. These operations can destroy data and do not address the documented meaning of this bug check.

6. Install Appropriate Windows and Hardware Updates

If Windows is running reliably enough to perform updates, install applicable Windows updates and supported hardware drivers.

1. Open Settings.
2. Navigate to Windows Update.
3. Select Check for updates.
4. Review available updates.
5. Install applicable updates and restart the computer.

For manufacturer-specific hardware drivers, check the computer or component manufacturer's official support website. Confirm the exact device model and Windows compatibility before installing a driver.

If the error began immediately after a particular update, investigate that update before installing further changes.

Advanced Troubleshooting

If the basic procedures do not resolve the issue, further investigation may be necessary. These procedures are intended primarily for experienced users and IT support technicians.

1. Review Windows Crash Dump Files

Windows may create crash dump files when a bug check occurs. These files can help identify the circumstances of a system crash and provide information for kernel-level debugging.

Common dump locations include:

• Small memory dumps: C:\Windows\Minidump
• Kernel or complete memory dump: C:\Windows\MEMORY.DMP, when configured and successfully generated.

The availability and contents of dump files depend on Windows crash-dump settings, system configuration, available storage, and whether the dump was successfully written.

For advanced analysis, IT professionals can use Microsoft's WinDbg debugger to inspect a crash dump.

A debugger may help identify the bug check, loaded modules, stack information, and other diagnostic evidence. However, the presence of a particular driver or module in a crash report does not automatically prove that it caused the failure.

Official reference: Microsoft Windows Debugging Documentation.

2. Investigate Driver and System Configuration Changes

For systems managed by IT professionals, compare the current configuration with the last known working configuration.

Review:

• Recently installed or updated device drivers.
• New hardware and device-management changes.
• Recent system configuration changes.
• Windows update installation history.
• Crash timestamps and available diagnostic logs.
• Changes to low-level security or system-management software.

Use available evidence to narrow down the affected component. Avoid making multiple unrelated configuration changes at once because this makes it difficult to identify which change affected the system.

3. Consider System Restore

If the problem started after a recent software, driver, or configuration change, System Restore may help return Windows system files and settings to an earlier restore point.

To use System Restore from Windows Recovery Environment:

1. Enter Windows Recovery Environment.
2. Select Troubleshoot.
3. Select Advanced options.
4. Choose System Restore, if available.
5. Select an appropriate restore point created before the problem began.
6. Follow the on-screen instructions.

System Restore is not available on every system or in every recovery situation. Review the selected restore point and understand which applications and system settings may be affected.

What If Windows Cannot Start?

If the computer repeatedly displays PP1_INITIALIZATION_FAILED and cannot reach the desktop, use the recovery options available in Windows Recovery Environment.

Consider the following order:

1. Disconnect recently added external devices.
2. Try Startup Settings and Safe Mode.
3. Uninstall a recent update if the timing supports investigating it.
4. Use System Restore if a suitable restore point exists.
5. Consider manufacturer-supported recovery options if the earlier procedures fail.

Before performing major recovery operations, back up important data whenever possible. Some recovery methods can remove applications, settings, or personal files. If BitLocker is enabled, ensure that the recovery key is available.

Refer to Microsoft Recovery Options in Windows for available recovery methods and their limitations.

When to Seek Professional Technical Assistance

Contact a qualified computer technician or system administrator when:

• The computer repeatedly crashes before Windows starts.
• Multiple recovery options fail.
• Crash dumps require kernel-level analysis.
• The system contains important data that has not been backed up.
• Storage or hardware diagnostics report failures.
• The computer is part of a business network or managed IT environment.

Provide the technician with the exact stop code, the time the error started, recent hardware and software changes, Windows version, and any available crash dump files. Memory dumps can contain sensitive system information, so share them only through trusted channels.

Frequently Asked Questions

What does PP1_INITIALIZATION_FAILED 0x00000090 mean?

It means Windows could not complete Phase 1 initialization of its kernel-mode Plug and Play manager. This initialization phase includes preparing registry files and other settings needed for subsequent driver I/O initialization.

Is PP1_INITIALIZATION_FAILED a hardware or software error?

The stop code identifies a failure in kernel-mode PnP initialization, not a specific defective hardware component or software package. Drivers, configuration changes, hardware changes, and other startup-related problems are areas to investigate.

Can a faulty device driver cause error 0x00000090?

A problematic driver is a reasonable area to investigate, particularly if the crash began after a driver installation or update. However, Microsoft does not identify a specific driver as the universal cause of this bug check.

Does PP1_INITIALIZATION_FAILED mean the motherboard is damaged?

No. The error does not establish motherboard failure. Investigate hardware and system configuration using appropriate diagnostics before deciding that a motherboard or another component needs replacement.

Can Safe Mode help resolve PP1_INITIALIZATION_FAILED?

Safe Mode can help narrow down startup problems by loading a limited set of drivers and services. If Windows works in Safe Mode, investigate recently installed drivers and nonessential startup components.

Does this error have bug check parameters?

Microsoft's official documentation does not specify bug check parameters for PP1_INITIALIZATION_FAILED (0x00000090).

Should I reinstall Windows to fix this error?

Reinstalling Windows should not be the first troubleshooting step. Investigate hardware changes, drivers, updates, and available recovery options first. Reinstallation may remove applications, settings, and personal data, depending on the method selected.

Sources

• Microsoft Learn – Bug Check 0x90: PP1_INITIALIZATION_FAILED
• Microsoft Learn – Bug Check Code Reference
• Microsoft Support – Windows Startup Settings
• Microsoft Support – Recovery Options in Windows
• Microsoft Learn – Windows Debugging Documentation