The pattern points most strongly to a driver or firmware power-state problem on battery, not the replacement battery itself.
The most relevant signals are:
- Crashes happen only during battery use.
- They occur around sleep, hibernation, lid-close, idle, and resume scenarios.
- The system was temporarily stable after disabling PCIe Link State Power Management, which strongly suggests a power transition trigger.
- The stop/error data mentioned in the dumps and events is consistent with device, chipset, ACPI, PCI, or related driver power-state handling.
Based on the supported guidance, the best next steps are:
- Focus on recently changed drivers first Since the issue returned after the system had been stable, check for any recent driver or service changes around the time the crashes resumed. Recent driver updates are a common cause of bug checks and unexpected reboots. If a recent driver was installed, remove or roll it back and test again on battery.
- Check Device Manager for problem devices
Right-click Start > Device Manager.
- Look for any device with an exclamation point (!).
- For suspect devices, open Properties and review any related events.
- Try Update driver first.
- If the issue began after a driver change, try disabling or uninstalling the affected device/driver and then reinstall the vendor-provided version.
- Review Event Viewer around each crash Open Event Viewer and inspect the System log for critical or error events in the same time window as the blue screen or reboot. This is specifically recommended for isolating the device or driver causing power-related bug checks.
- Temporarily disable power-saving features for isolation Because the system was stable when PCIe link-state power saving was turned off, continue using that as a diagnostic control. For DRIVER_POWER_STATE_FAILURE-style issues, temporarily disabling power save features is a documented isolation step because some driver problems are tied to hibernation, suspend, and resume states.
- Check BIOS/firmware availability from the manufacturer Power-state failures can also involve ACPI/BIOS or firmware behavior. Check whether the manufacturer provides an updated system ACPI/BIOS or other firmware for the GA402RJ.
- Remove or test recently added hardware if applicable If any internal component, peripheral, or hardware change coincided with the issue, remove or replace it for testing.
- Run manufacturer hardware diagnostics Hardware diagnostics from the system manufacturer are recommended when the issue may involve platform power management or firmware interaction.
- Install the latest Windows 11 updates Go to Start > Settings > Windows Update > Check for updates.
- If Windows became unstable after the incomplete restore/DISM sequence, use recovery The later symptoms—failed app launches, broken search, Startup Repair, and renewed crashes after an incomplete restore/DISM interruption—suggest Windows may now also have system-state corruption. If the driver and firmware checks do not stabilize the device, use a System Restore point or another Recovery option in Windows 11.
What this most likely indicates:
- Most likely: chipset / PCI / ACPI / device driver power-state handling on battery.
- Also possible: BIOS or firmware interaction with low-power transitions.
- Less likely: the battery itself, since replacement did not change the behavior.
- Possible secondary issue now: Windows corruption after the incomplete restore/DISM workflow.
The strongest practical conclusion from the current evidence is:
- The original fault pattern is most consistent with a battery-only power transition driver/firmware issue.
- The newer instability may be that same issue plus Windows corruption introduced after the interrupted recovery/servicing activity.
References: