AMD PSP 11.0 Device Power Failure | Fix Sleep Crashes

Guide / By

A PSP 11.0 power failure warning is often a driver and firmware power-state mismatch; chipset and BIOS updates plus a clean power plan can clear it.

If your PC wakes from sleep and feels “half awake,” the AMD PSP device is one place to look. The warning often shows up as a yellow mark in Device Manager under Security devices, sometimes paired with random reboots, failed sleep, or Windows Hello acting up.

The good news is that most cases are fixable with tidy updates and a few Windows power tweaks. You do not need to replace parts right away. Start with the checks that change the fewest things, then move to deeper fixes only if the error keeps coming back.

When the fault shows after sleep, aim for a wake cycle you can trust for straight days, not hours.

What The AMD PSP Device Does In Windows

AMD PSP stands for Platform Security Processor. It’s a small controller inside many AMD systems that helps with platform security tasks and trusted functions that Windows relies on. On Windows 10 and Windows 11, it may tie into features like the TPM stack, Windows Hello sign-in, and security checks during boot.

When Windows says the device hit a power failure, it’s often reporting that the device did not transition cleanly between power states. That can happen after sleep, hibernate, or fast startup, when firmware, chipset drivers, and Windows power policy all have to agree on the next state.

This message can feel scary because it mentions “power failure,” yet it’s frequently a software handshake problem, not a dead chip. Still, treat it seriously because it can lead to crashes, resume problems, or security features turning flaky until the next restart.

Common Signs And Where To Confirm Them

Most people first spot the issue in Device Manager. Others see it in Event Viewer, often after a wake-from-sleep crash or a restart that had no blue screen. Before you change settings, confirm what Windows is reporting and when it happens.

Symptom Where You See It What It Often Means
Yellow mark on AMD PSP 11.0 Device Device Manager → Security devices Driver failed to start after a power-state change
Code 10 with STATUS_DEVICE_POWER_FAILURE Device properties → Device status PSP driver did not resume cleanly
Sleep or hibernate won’t resume Black screen, fans spin, no response Resume path is unstable with current BIOS or chipset stack
Windows Hello fails until reboot Sign-in screen after sleep Trusted component did not come back online

Check Device Manager First

Open Device Manager, expand Security devices, and click AMD PSP 11.0 Device. If you see a device status message that mentions a power failure or Code 10, note the text. Also check the Driver tab to see the driver date and provider.

Check Event Viewer Around The Time It Broke

Open Event Viewer and look under Windows Logs and System. Filter by Critical and Error, then scan the minute or two before the reboot or failed resume. You’re looking for patterns: repeated device start failures, sleep transitions, or storage and power events that line up with the same timestamp.

AMD PSP 11.0 Device Power Failure Fix Steps

Work in order. After each step, put the PC to sleep, wake it, and see if the error returns. If the issue only shows after hibernate, test that too. One clean test cycle beats guessing.

  1. Restart once — A full restart can bring the PSP back online and clears a one-off resume glitch.
  2. Install Windows updates — Run Windows Update, then reboot again so the new kernel and power components actually load.
  3. Update AMD chipset drivers — Get the newest chipset package for your CPU and board, install it, then reboot.
  4. Update your BIOS — BIOS updates often include PSP and power-management fixes. Follow your PC or motherboard vendor’s steps and keep AC power connected during the flash.
  5. Load BIOS defaults once — After a BIOS update, load default settings, save, and boot. Then reapply only the settings you truly use.
  6. Disable Fast Startup — Fast Startup mixes shutdown with hibernate, which can keep the problem alive across “shutdowns.”
  7. Reinstall the PSP driver cleanly — If the device stays broken, remove the chipset package from Installed apps, reboot, then install the chipset package again.

How To Turn Off Fast Startup

Fast Startup can mask driver changes and keep a bad state cached. Turning it off forces Windows to do a cleaner boot path, which helps when a device fails after resume.

  1. Open Control Panel — Search Control Panel, then open Power Options.
  2. Open power button settings — Click “Choose what the power buttons do.”
  3. Change locked options — Click “Change settings that are currently unavailable.”
  4. Turn off Fast Startup — Clear “Turn on fast startup,” save, then reboot.

How To Update Chipset Drivers The Safe Way

Chipset drivers are a bundle. Pulling out single devices in Device Manager can leave the stack in a weird state. A clean install through Windows’ normal app removal path is safer for most systems.

  1. Open Installed apps — Go to Settings, then Apps, then Installed apps.
  2. Remove AMD Chipset Software — Uninstall it, then reboot when prompted.
  3. Install the latest package — Run the newest AMD chipset installer, finish setup, then reboot again.
  4. Test sleep and wake — Put the system to sleep, wake it, then check Device Manager for the PSP status.

Power Settings That Commonly Trigger The Error

If updates don’t stick, the next culprit is the power path. Some systems hit the error only with specific sleep modes or when hibernate is in play. Small changes here can stop the PSP from getting stuck.

Modern Standby And Sleep Mode

Many Windows 11 laptops use Modern Standby (S0). Some desktops and older boards still offer the classic S3 sleep state. If your BIOS lets you pick a sleep mode, try the other mode for a few days and see if wake becomes stable.

Hibernate And Hybrid Shutdown

If the issue appears after “shutdown” more than after sleep, Fast Startup is often involved. If it appears after hibernate, test with hibernate turned off for a while to see if the resume path is the trigger.

  1. Open an admin terminal — Search Windows Terminal, right-click, then choose Run as administrator.
  2. Turn off hibernate — Run powercfg /h off, then reboot.
  3. Test for a day — Use sleep only, then check if the device stays healthy.

PCI Express Link State Power Management

On some systems, aggressive link state settings can line up with resume glitches. Setting it to a less aggressive mode can smooth wake behavior.

  1. Open Power Options — Control Panel, then Power Options, then Change plan settings.
  2. Open advanced settings — Click Change advanced power settings.
  3. Set Link State to Off — Under PCI Express, set Link State Power Management to Off, then test sleep and wake.

When A Normal Update Isn’t Enough

Sometimes Windows keeps reinstalling the same broken driver version. Other times, the BIOS update didn’t reset stale settings. If you keep seeing the warning after a clean chipset install, try these moves.

  1. Block driver updates for a moment — Disconnect from the internet during the chipset install so Windows Update does not swap drivers mid-setup.
  2. Remove the device and rescan — In Device Manager, uninstall AMD PSP 11.0 Device, reboot, then let Windows detect it again.
  3. Run a clean boot test — Disable third-party startup apps, reboot, then test sleep and wake to see if a service is colliding with resume.
  4. Reset the power plan — Switch to Balanced, apply, reboot, then test again.

Clean Boot Sleep Test

Resume problems can be triggered by tools that hook into power events, RGB suites, fan control apps, VPN clients, or low-level monitoring tools. A clean boot helps you see whether the error happens with only Microsoft services running.

  1. Open System Configuration — Press Windows+R, type msconfig, and press Enter.
  2. Hide Microsoft services — On the Services tab, tick “Hide all Microsoft services.”
  3. Disable the rest — Click Disable all, then reboot.
  4. Test sleep and wake — If the error stops, re-enable items in small groups until you find the trigger.

Last-Resort Checks If The Error Keeps Returning

If you’re still stuck, shift from “try fixes” to “narrow the cause.” The goal is to learn whether the problem tracks to BIOS settings, a Windows install issue, or power delivery quirks that show up under load and sleep transitions.

Check BIOS Security And Virtualization Toggles

Switching fTPM, Secure Boot, or virtualization features can change what the PSP does during boot and resume. If you recently changed these, roll back to what you used before and test again. If you use BitLocker, save your BitLocker recovery code before changing TPM-related settings.

Run System File Checks

Corrupted system files can break driver loading and power transitions. These commands are built into Windows and are safe to run.

  1. Open an admin terminal — Run Windows Terminal as administrator.
  2. Run DISM repair — Execute DISM /Online /Cleanup-Image /RestoreHealth and wait for completion.
  3. Run SFC — Execute sfc /scannow, then reboot.

Watch For Power-Related Patterns

If the PC restarts under load and also logs PSP power failures, the real cause might be unstable power delivery, a loose cable, or a PSU that’s struggling. Reseat power connectors, check CPU and GPU power leads, and test with stock clocks and stock memory settings.

If you need to share details with a technician, capture a screenshot of the Device Manager status message and note the exact time it happened. Include whether the failure happened after sleep, after hibernate, or after a shutdown and cold boot. Those timing details speed up a real diagnosis.

When you’re ready to sanity-check your result, do one last pass: put the PC through five sleep and wake cycles, then check Device Manager again. If AMD PSP 11.0 stays clean through repeat resumes, you’ve likely solved the root cause.

In stubborn cases where updates and power tweaks don’t change anything, a repair install of Windows can reset the driver and power stack without wiping your files. Back up first, then use the Windows installation media option that keeps personal data.

amd psp 11.0 device power failure can look like a hardware fault, yet most people clear it with BIOS and chipset updates plus a cleaner sleep path. If it comes back only on battery, test on AC only for a day and see if the pattern changes.

If the warning returns right after you install a chipset package, roll back that chipset install and try a newer or older package from your system vendor. amd psp 11.0 device power failure tends to track with the chipset stack and firmware pairing, so matching those parts often stops the loop.