Lenovo Legion Go (8APU1) Error DRIVER_POWER_STATE_FAILURE (0x0000009F): TrueStrike Controller Sleep Crash
A Windows kernel bugcheck 0x9F (DRIVER_POWER_STATE_FAILURE) occurs when the system transitions into Modern Standby (S0ix) or S3/S4 states while a TrueStrike controller is physically detached. The driver fails to complete an IRP_MJ_POWER request within the allotted watchdog timeout because the PnP USB/UART power state handshake between the tablet pogo-pin interface and controller MCU hangs.
Hardware Diagnostic Matrix
Spec Ref #cee0a8ccRequired Diagnostic Tools & Instrumentation
Multimeter Probing Targets & Circuit Tolerances
Bench Calibrated ±5%| Test Point / Circuit | Target Nominal Spec | Expected State | Fault Condition |
|---|---|---|---|
| Main Logic DC Bus | 3.3V / 5.0V DC (±0.1V) | Stable DC Potential | <2.9V (Brownout / Sag) |
| Thermistor / NTC Sensor | 10kΩ - 100kΩ @ 25°C | Smooth Thermal Curve | 0Ω (Short) or ∞ (Open) |
| Safety Ground / PE Continuity | < 0.5Ω Resistance | Solid Earth Bond | > 1.0Ω (Floating Chassis) |
Common Symptoms & Fault Manifestations
- BSOD displaying DRIVER_POWER_STATE_FAILURE (0x0000009F) with IRP timeout pointing to legioncontroller.sys or hidclass.sys
- System fails to wake from Modern Standby or hangs indefinitely with power LED pulsing after detaching either TrueStrike controller
- Detached TrueStrike controller fails to reconnect over 2.4GHz RF/Bluetooth after tablet sleep transition
Root Causes & System Failure Modes
ACPI power state mismatch and IRP_MN_SET_POWER deadlock in Legion Controller firmware/driver during S0ix state entry
Oxidation or poor contact on the 10-pin pogo connector disrupting the 3.3V VREG_CTRL bus line during detachment transition
Outdated controller MCU firmware failing to gracefully renegotiate power delivery and RF fall-through when disconnected from rail
High-Voltage & Mechanical Safety Isolation
Prior to opening access panels, disconnecting terminals, or probing wiring, perform complete lock-out / tag-out (LOTO). Disconnect all AC mains, DC string isolators, and lithium battery banks. Allow internal smoothing capacitors at least 3 to 5 minutes to dissipate stored residual energy below safe threshold (<30VDC).
Step-by-Step Diagnostic & Resolution Procedure
Safe Isolation & Force Reset
Force power down the Legion Go by holding the power button for 15 seconds. Detach both TrueStrike controllers and power them off completely by holding their respective Legion (L/R) buttons for 7 seconds until the indicator LEDs extinguish.
Physical Interface & Pogo Pin Diagnostic
Inspect the 10-pin sprung pogo rail on the tablet chassis and matching pads on the controllers. Clean all contacts with 99.9% IPA. Using a multimeter in DC mode, check standby potential on the VBUS pin (nominal 5.0V with charger connected) and control sense line (nominal 3.3V); verify no bent or stuck spring-loaded pins.
Controller MCU Firmware & Driver Stack Reflash
Boot Windows into Safe Mode or clean state. Reseat both controllers securely into rails. Launch Legion Space with Administrator privileges and flash the latest Controller MCU firmware (v02.03.00.01 or later). In Device Manager, expand 'Human Interface Devices', right-click 'Legion Controller', select 'Uninstall device' (checking delete driver software), and reinstall the validated Lenovo System Interface Foundation and TrueStrike driver packages.
Power Management & Recalibration Verification
Navigate to Device Manager > Universal Serial Bus controllers > USB Root Hub > Properties > Power Management, and disable 'Allow the computer to turn off this device to save power' on controller-linked hubs. Re-dock controllers, power cycle into BIOS (Hold Vol+ & Power), load setup defaults (F9), save and exit (F10). Run detachment cycles while entering/waking from sleep to verify crash resolution.
Hardware Reset & Fault Clear Sequence
Controller ProcedurePrevention & Routine Maintenance Guidelines
- Always update controller MCU firmware with both controllers physically docked to the host unit to prevent partial sync states.
- Keep pogo-pin dock tracks clean of pocket lint and debris to prevent intermittent hardware disconnects during power down transitions.
Frequently Asked Diagnostic Questions
What does error code DRIVER_POWER_STATE_FAILURE (0x0000009F) indicate on Lenovo Legion Go (8APU1)?
A Windows kernel bugcheck 0x9F (DRIVER_POWER_STATE_FAILURE) occurs when the system transitions into Modern Standby (S0ix) or S3/S4 states while a TrueStrike controller is physically detached. The driver fails to complete an IRP_MJ_POWER request within the allotted watchdog timeout because the PnP USB/UART power state handshake between the tablet pogo-pin interface and controller MCU hangs. In engineering telemetry, it indicates truestrike controller sleep crash requiring circuit verification.
What are the primary triggers causing error DRIVER_POWER_STATE_FAILURE (0x0000009F)?
Diagnostic bench telemetry isolates the following common root causes: ACPI power state mismatch and IRP_MN_SET_POWER deadlock in Legion Controller firmware/driver during S0ix state entry; Oxidation or poor contact on the 10-pin pogo connector disrupting the 3.3V VREG_CTRL bus line during detachment transition; Outdated controller MCU firmware failing to gracefully renegotiate power delivery and RF fall-through when disconnected from rail.
How do I reset and clear Lenovo error DRIVER_POWER_STATE_FAILURE (0x0000009F)?
Perform a controller hardware MCU reset: with controllers detached, press and hold the small recessed pinhole reset switch on the inner rail edge of each controller for 5 seconds using a SIM ejector tool, then reconnect both controllers while the main unit is booted. If the error status repeats immediately after clearing, discontinue clearing and test circuit continuity.
Can I safely resolve error DRIVER_POWER_STATE_FAILURE (0x0000009F) without specialized shop tooling?
This fault is graded as Intermediate difficulty with High severity. Standard diagnostics require an insulated digital multimeter and appropriate hand tools. Always observe high-voltage isolation procedures.