Device:
- Razer Blade 15 Base Model (Early 2020) – RZ09-0328
- Intel i7-10750H
- RTX 2060 Max-P
- BIOS 1.06
- Windows 11 Home
Issue Summary:
For several months, my Blade 15 appeared to become stuck in an abnormal high-power idle state that caused:
- persistent fan activity,
- significantly elevated idle battery drain,
- and unstable idle behavior despite near-zero visible workload.
The issue did not behave like a hardware failure. Instead, it appeared related to platform-level power-state synchronization between firmware, drivers, and Windows power management.
Observed Behavior:
- Idle discharge rates often ranged between ~30–45W with no meaningful foreground workload.
- Fans remained active/loud even during light usage.
- GPU usage frequently appeared near 0%, yet the platform still behaved as if under sustained load.
- Rebooting alone did not consistently resolve the issue.
- Behavior persisted for months.
Important Observation:
After extensive low-level troubleshooting, the system suddenly recovered and now behaves normally:
- CPU package power now drops to ~1–3W at idle,
- GPU correctly enters idle state,
- fan noise becomes minimal after stabilization,
- and estimated battery life improved dramatically.
This strongly suggests the system had entered a persistent invalid or degraded platform power state rather than experiencing hardware failure.
Changes Made Before Recovery:
The recovery did not occur after a single obvious fix, but after multiple changes involving:
- WLAN driver power behavior,
- background Wi-Fi scan policies,
- preferred wireless band settings,
- power-management configuration,
- and repeated driver/state reinitialization cycles.
This makes the issue appear related to platform state synchronization/recovery rather than simple user misconfiguration.
Technical Suspicion (Observation-Based):
The behavior may involve interaction between:
- EC firmware,
- ACPI/power-state transitions,
- Intel/NVIDIA idle coordination,
- Windows Modern Standby behavior,
- and/or WLAN wake/scan behavior.
The key issue is not merely temporary boot activity, but that the system appeared unable to automatically recover from this degraded idle-power state for an extended period of time.
Why This Matters:
Most users will never inspect:
- CPU package power,
- C-state residency,
- wake behavior,
- or WLAN scan policies.
From a user-experience perspective, a premium device should ideally recover automatically from invalid/transient platform power states without requiring manual low-level debugging.
Suggestion:
Please investigate possible Blade platform edge cases involving:
- idle-state recovery robustness,
- EC fan-control synchronization,
- Modern Standby transitions,
- WLAN background scan wake behavior,
- and Intel/NVIDIA idle-state coordination.
The hardware itself is excellent. This feels much more like a firmware/software recovery robustness issue than a hardware limitation