0x00000090 Windows BSOD Fixes, Checks, and Recovery

0x00000090 is the PP1_INITIALIZATION_FAILED bug check, which means the Plug and Play (PnP) manager could not be initialized. An error occurred during Phase 1 initialization of the kernel-mode PnP manager. Start by checking the crash pattern, the minidump, and any recent driver or device changes before you make broader repairs. Guessing can waste time and send you toward the wrong fix.

This guide is part of our Windows BSOD stop codes: full list and fixes series.

What 0x00000090 means on Windows

0x00000090 is associated with the PP1_INITIALIZATION_FAILED bug check. In plain language, Windows hit a problem while initializing the kernel-mode Plug and Play manager during early startup. That makes the crash timing important: a failure during boot or immediately after a device change can help narrow down the trigger.

The crash timing is an early clue. A failure during boot points toward a driver or startup-related problem. A crash after sleep, resume, or plugging in hardware may point toward a device stack issue. An idle crash can still be driver related, but the dump usually gives a better answer than guessing.

Triage checklist: symptom, timing, likely fault, first test

What the minidump file tells you

The minidump is the fastest way to confirm the failing module and the repeat trigger. Windows keeps small crash dumps that are often enough to show whether the same driver or kernel path failed each time.

Dump timing matters. If every dump appears after resume, that points away from a random crash and toward a power-state or driver branch. If the same module appears across several crashes, that is better evidence than a long list of symptoms.

How to open a dump in WinDbg

1. Install WinDbg, then launch it as administrator.
2. Open the newest crash dump file from the dump location on the affected PC.
3. Use the debugger’s analysis command to inspect the bug check data and stack trace.
4. Look for the module named in the failing stack, the “probably caused by” line, and any repeated driver name across crashes.

If the same third-party driver appears more than once, fix that branch first. If the dump points to Windows kernel code without a clear third-party module, move to driver, device, and Windows file checks next.

Is this a hardware or driver error?

Most often, this branch starts with a driver, especially if the crash follows sleep, resume, a new device, or a recent update. Use Device Manager to check for problem devices, recent changes, and whether a rollback is available. Hardware is still possible, but do not start there without dump evidence.

Driver branch: Device Manager first

1. Open Device Manager.
2. Check Display adapters, Storage controllers, Disk drives, Network adapters, and System devices for warning icons.
3. Right-click the suspect device and open Properties > Driver.
4. Choose Roll Back Driver if the crash started after an update.
5. If rollback is unavailable, choose Update driver or Uninstall device, then reboot and retest.

After a feature update, also check recently changed storage, chipset, GPU, and network drivers.

How do I fix a 0x00000090 blue screen on Windows 11?

Start with the branch that matches the crash pattern: driver first if it follows an update or hardware action, then Windows repair commands. A simple reboot may not clear a bad driver path that stays active across restarts.

First-aid order for Windows 11

1. Boot into Safe Mode and check if the stop code still appears.
2. Open Settings > Windows Update and install any pending updates.
3. Open Device Manager and roll back or update the suspect driver.
4. Run sfc /scannow in an elevated Command Prompt.
5. Run DISM /Online /Cleanup-Image /RestoreHealth.
6. If the crash follows sleep or resume, disable Fast Startup in Control Panel > Power Options > Choose what the power buttons do.

If the stop code returns after those steps, use dump analysis before trying a repair install or Reset This PC.