ASUS g14 2022 GA402RJ restarts when use on battery

Question

ASUS g14 2022 GA402RJ restarts when use on battery

Kon 0

September 12th

Hello, I am experiencing random crashes/reboots on my ASUS ROG Zephyrus G14 GA402RJ (Ryzen 7 6800HS + RX 6700S, Windows 11).

Main issue:

Crashes only happen on battery power.

No crashes have occurred while plugged in (tested for ~3 weeks).

Usually happens a few minutes after:

Cold boot on battery

  Opening from hibernation/lid close
  
     Sometimes while idle with WiFi connected

Errors observed:

BugCheck 1001:

CLOCK_WATCHDOG_TIMEOUT (0x101)

  Related drivers mentioned: `dxgmms2.sys`
  
  WHEA-Logger Event ID 1
  
  Kernel-Power Event ID 41
  
  volmgr Event ID 161/162
  
  Kernel-PnP Event ID 219 (`WUDFRd`, Windows Hello driver)
  
  Startup BSODs:
  
     SYSTEM_THREAD_NOT_HANDLED
     
        KMODE_EXCEPTION_NOT_HANDLED

Troubleshooting performed:

Replaced battery (issue remained)

Updated AMD chipset driver (including power management fixes)

Updated GPU drivers from ASUS support

Disabled Hyper-V

Tested CPU minimum processor state:

100%

  99%
  
     80% (crashes still occurred)
     
     Reset Windows power plans:
     
     ```yaml
     powercfg -restoredefaultschemes

powercfg /h off powercfg /h on ```

     Reseated internal components after battery replacement
     
     Considered Windows reset/cloud recovery but not performed

Current suspicion: The issue seems related to battery power management/power state transitions because:

It never happens on AC power

It happens during idle/light usage on battery

Dumps show involvement of AMD power management/ACPI components (amdppm.sys, AmdMicroPEP.sys, ACPI.sys, pci.sys)

I would like assistance identifying whether this is a firmware/BIOS, driver, battery, motherboard power management, or Windows issue. Hello, I am experiencing random crashes/reboots on my ASUS ROG Zephyrus G14 GA402RJ (Ryzen 7 6800HS + RX 6700S, Windows 11).

Main issue:

Crashes only happen on battery power.

No crashes have occurred while plugged in (tested for ~3 weeks).

Usually happens a few minutes after:

Cold boot on battery

  Opening from hibernation/lid close
  
     Sometimes while idle with WiFi connected

Errors observed:

BugCheck 1001:

CLOCK_WATCHDOG_TIMEOUT (0x101)

  Related drivers mentioned: `dxgmms2.sys`
  
  WHEA-Logger Event ID 1
  
  Kernel-Power Event ID 41
  
  volmgr Event ID 161/162
  
  Kernel-PnP Event ID 219 (`WUDFRd`, Windows Hello driver)
  
  Startup BSODs:
  
     SYSTEM_THREAD_NOT_HANDLED
     
        KMODE_EXCEPTION_NOT_HANDLED

Troubleshooting performed:

Replaced battery (issue remained)

Updated AMD chipset driver (including power management fixes)

Updated GPU drivers from ASUS support

Disabled Hyper-V

Tested CPU minimum processor state:

100%

  99%
  
     80%  
     (crashes still occurred)
     
     Reset Windows power plans:
     
     ```yaml
     powercfg -restoredefaultschemes

powercfg /h off powercfg /h on ```

     Reseated internal components after battery replacement
     
     Considered Windows reset/cloud recovery but not performed

Current suspicion: The issue seems related to battery power management/power state transitions because:

It never happens on AC power

It happens during idle/light usage on battery

Dumps show involvement of AMD power management/ACPI components (amdppm.sys, AmdMicroPEP.sys, ACPI.sys, pci.sys)

I would like assistance identifying whether this is a firmware/BIOS, driver, battery, motherboard power management, or Windows issue.

SEPTEMBER 29th
RELEVANT UPDATE: I had assistance and was able to get the device stable on battery for 2 weeks from september 12 to 28 by turning off PCIe LPSM on battery.

The device had been working perfectly for several weeks, and I used it normally without changing or tweaking any settings. Reliability Monitor also showed no critical issues during that period.

Recently, however, the problems gradually returned:

I used a restore point, but the restoration was incomplete and some applications subsequently failed to open due to missing files.

Windows Search then stopped displaying any results.

The laptop began occasionally failing to shut down/start normally, instead entering Startup Repair before eventually booting successfully.

Since then, I have experienced multiple crashes, particularly while the laptop is running on battery.

These crashes only started yesterday; before that, the laptop had been functioning normally.

The only troubleshooting I performed was running SFC /scannow and DISM /RestoreHealth. During one DISM operation, the progress appeared to freeze, so I eventually hibernated the laptop and continued using it before later shutting it down while DISM was still incomplete.

I have also collected the minidump files from the recent crashes and can provide the compressed file for analysis.

I would really appreciate any help identifying what may be causing the instability.

DUMP FILES: https://drive.google.com/file/d/1cJvVGq79kkQvZvBodfBduBwZIYqF8_4S/view?usp=sharing

0 comments

2 answers

Your answer

Answer 1

Ivan B 124.8K Independent Advisor

Hii,

I’ve seen this issue before. When the battery was replaced, was it done under warranty, or did you perform the swap yourself?

When the device freezes while running on battery power, does it take longer than usual to restart?

Have you updated the BIOS?

The problem I experienced wasn't with this specific model but with a 2020 Asus TUF; the issue turned out to be the motherboard, which had to be replaced along with the battery. One setting that helped was "AHCI Link Power Management"—changing it to "Active" mode (in addition to the PCI Express setting).

Open the Command Prompt (as administrator) and run this command:

powercfg -attributes SUB_DISK 0b2d69d7-a2a1-449c-9680-f91c70521c60 -ATTRIB_HIDE

Go to Control Panel > Power Options > Change plan settings > Change advanced power settings > Hard disk > AHCI Link Power Management. Change it to "Active" or "DIPM".

Based on your description, Windows might be corrupted. I would recommend refreshing Windows or performing a clean install; I can guide you through that.

To perform a refresh, go to the Start menu > Settings > System > Recovery > Problems with Windows Update > Reinstall now.

This refresh process won't format your PC; it will keep your files and programs intact.

Thanks.

Kon 0 Reputation points

2026-09-29T16:21:17.4033333+00:00

Hello Ivan,

I did replace the battery myself, however the issue was already present prior the battery swap.

The restarts are almost immediate when the BSOD happens. When it does freeze the restart time isnt affected.

Im currently doing a fresh install and seeing if that fixes it. If it does, then Ill leave it be since meddling with settings can cause issues. If it doesnt work Ill definitely look into AHCI.

Just wondering how the random restarts only happens on battery. Im really wondering if the 2 weeks of perfect functional use was just a fluke.... anyways will keep you updated thanks!
Ivan B 124.8K Reputation points Independent Advisor

2026-09-29T16:25:57.1833333+00:00

Hi,

I understand the situation—I’ve had this problem myself, and it turned out to be a hardware issue. Performing a clean install is a good starting point; I also recommend updating the BIOS to the latest version. It sounds just like the issue I had with an ASUS TUF laptop—the exact same scenario.

Please keep me posted. Regarding the AHCI setting—I also tried adjusting that for the SSD, and while it improved things, it didn't fully solve the problem; it only reduced the frequency of BSODs when running on battery power (and occasionally when plugged in).

Thanks.
Kon 0 Reputation points

2026-09-29T23:30:46.2+00:00

Alright, well I really hope it isn't a hardware issue the difference from my issue to your issues with the TUF is this never happens on plug.

UPDATE: I have freshly repaired my windows using the settings > System > Recovery > Problems with Windows Update > Reinstall now. It seems to have fix a few issues of some apps not opening. The biggest visible fix was that the search bar actually shows things now. After performing the fresh installation I tried using my device for an hour and there were no crashes.

I will keep you updated and see how it performs in school. Thanks :)
Ivan B 124.8K Reputation points Independent Advisor

2026-09-30T00:43:02.2666667+00:00

Hi,

I understand. I hope everything works out—please keep me posted.

Thanks.

Kon 0

Hi, it crashed again in school but it did take longer. There really isn't a fixed pattern so I'm concerned now. Here's the DMP:

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*

************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : true
   AllowNugetExeUpdate : true
   NonInteractiveNuget : true
   AllowNugetMSCredentialProviderInstall : true
   AllowParallelInitializationOfLocalRepositories : true

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.047 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 46

Microsoft (R) Windows Debugger Version 10.0.29617.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\093026-9359-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: TriageDumpDataExtArray.HeaderSize is 0
WARNING: Failed to read dump data exension data

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 26100 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff801`9e000000 PsLoadedModuleList = 0xfffff801`9eef5410
Debug session time: Wed Sep 30 11:50:24.401 2026 (UTC + 8:00)
System Uptime: 0 days 11:32:50.403
Loading Kernel Symbols
..

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.............................................................
................................................................
................................................................
..................................................
Loading User Symbols

Loading unloaded module list
.................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`9e4fd130 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffc88b`7ed3fa10=00000000000000e1
10: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..................................................
Loading User Symbols

Loading unloaded module list
.................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WORKER_THREAD_RETURNED_AT_BAD_IRQL (e1)
Arguments:
Arg1: fffff8019e48fc90, address of worker routine (do ln on this to find guilty driver)
Arg2: 0000000000000002, IRQL returned at (should have been 0, but isn't).
Arg3: ffffa70b8516c5b0, workitem parameter
Arg4: ffffa70b8516c5b0, workitem address

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3421

    Key  : Analysis.Elapsed.mSec
    Value: 3484

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 0

    Key  : Analysis.Init.CPU.mSec
    Value: 781

    Key  : Analysis.Init.Elapsed.mSec
    Value: 8749

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 85

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29617.1000

    Key  : Analysis.Version.Description
    Value: 10.2604.29.1 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2604.29.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xe1

    Key  : Bugcheck.Code.TargetModel
    Value: 0xe1

    Key  : Dump.Attributes.AsUlong
    Value: 0x21808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0x0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: 0xE1_nt!CcWorkerThread

    Key  : Failure.Exception.IP.Address
    Value: 0xfffff8019e48fc90

    Key  : Failure.Exception.IP.Module
    Value: nt

    Key  : Failure.Exception.IP.Offset
    Value: 0x48fc90

    Key  : Failure.Hash
    Value: {0d96d2f0-ad5f-a6eb-937c-a56c73e690fb}

    Key  : Faulting.IP.Type
    Value: Paged

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x7497cf94

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 1

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 38408431

    Key  : Hypervisor.Flags.ValueHex
    Value: 0x24a10ef

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 0x3f7


BUGCHECK_CODE:  e1

BUGCHECK_P1: fffff8019e48fc90

BUGCHECK_P2: 2

BUGCHECK_P3: ffffa70b8516c5b0

BUGCHECK_P4: ffffa70b8516c5b0

FILE_IN_CAB:  093026-9359-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffa70b9f204040

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon) (!blackboxwinlogonnotify)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

IP_IN_PAGED_CODE: 
nt!CcWorkerThread+0
fffff801`9e48fc90 4c8bdc          mov     r11,rsp

STACK_TEXT:  
ffffc88b`7ed3fa08 fffff801`9e30ff49     : 00000000`000000e1 fffff801`9e48fc90 00000000`00000002 ffffa70b`8516c5b0 : nt!KeBugCheckEx
ffffc88b`7ed3fa10 fffff801`9e4944ca     : ffffa70b`9f204040 ffffa70b`7f553040 ffffa70b`9f204040 00000000`00000080 : nt!ExpWorkerThread+0x649
ffffc88b`7ed3fbb0 fffff801`9e6af7f4     : ffff8281`f8b90180 ffffa70b`9f204040 fffff801`9e494470 09658bc8`09658b9c : nt!PspSystemThreadStartup+0x5a
ffffc88b`7ed3fc00 00000000`00000000     : ffffc88b`7ed40000 ffffc88b`7ed39000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  nt!CcWorkerThread+0

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.26100.9457

STACK_COMMAND: .process /r /p 0xffffa70b7f553040; .thread /r /p 0xffffa70b9f204040 ; kb

BUCKET_ID_FUNC_OFFSET:  0

FAILURE_BUCKET_ID:  0xE1_nt!CcWorkerThread

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {0d96d2f0-ad5f-a6eb-937c-a56c73e690fb}

Followup:     MachineOwner

Kon 0 Reputation points

2026-09-30T04:07:19.21+00:00

I'd also like to add that when I did my testing 2 weeks ago, I uninstalled armoury crate and g-helper and ran the device on default windows. It worked just fine for 2 days on battery so I'm also wondering if it's a driver issue..? Anyways I'm going to see if wiping windows and starting from scratch will help. I really hope it does
Kon 0 Reputation points

2026-09-30T04:08:13.8033333+00:00

12345
Ivan B 124.8K Reputation points Independent Advisor

2026-09-30T10:17:01.84+00:00

Hi,

If possible, please upload the recent minidump files before starting the clean install process.

If you have already started the process, as a precaution, try testing without Armoury Crate installed; install only the drivers from ASUS (except the NVIDIA one), set the power plan to "High Performance," and run the 3DMark demo in both DX11 and DX12 modes.

Thanks.
Kon 0 Reputation points

2026-09-30T10:46:10.9466667+00:00

Hey, I just ran the laptop without armoury crate and sadly it crashed... I ran the laptop in school with windows default settings on balanced mode and power efficiency and both still crashed. I will provide the necessary dump files through a google drive link: https://drive.google.com/file/d/11HIk5rr2kqj9P4AE7CeqyvJa3irdCgst/view?usp=sharing

Also I would like to ask what is the significance of running 3dmark demo in Dx11 and Dx12? Is this to rule out any hardware issues? Would I need to run this test on battery or off battery?

PS: I transferred to a foreign country and don't really know where to get a repair shop. My warranty has already expired so I don't think I can reach out to ASUS. So I really hope I can solve this without needing to do a physical repair...
Ivan B 124.8K Reputation points Independent Advisor

2026-09-30T11:29:28.8366667+00:00

Hi,

Regarding this test to confirm whether the hardware failure is in the iGPU or dGPU—I do believe it's a hardware issue, as I’ve had a similar problem. The idea is to stress the components to identify exactly which one is causing the trouble; I still suspect the motherboard, given that the minidumps indicate both a kernel failure and a processor-related error.

That’s the reason for these tests.

Thanks.
Kon 0 Reputation points

2026-09-30T13:32:39.1766667+00:00

Hi i'd like to clarify whether I should do this on battery or on plug?
Ivan B 124.8K Reputation points Independent Advisor

2026-09-30T13:47:37.79+00:00

Hi,

I recommend testing in both cases.

If possible.

Thanks.
Kon 0 Reputation points

2026-10-01T00:52:52.9466667+00:00

During the tests, there were no BSODS. I did do the time spy twice because I forgot to take a screen shot of the 1st test
Ivan B 124.8K Reputation points Independent Advisor

2026-10-01T02:19:18.9633333+00:00

Hi,

That’s strange—was this test performed using the charger or on battery power?

Thanks.
Kon 0 Reputation points

2026-10-01T10:59:59.33+00:00

Using charger, I also did a windows 11 fresh install but I chose the option to keep my files using the media creation tool. I'll test this on battery and let you know.

EDIT: I did the tests on battery and same results came out
Ivan B 124.8K Reputation points Independent Advisor

2026-10-01T22:26:58.45+00:00

Hi,

After the clean install, did you test the battery and charger with the Armoury Crate software installed, and did everything work correctly?

Thanks.
Kon 0 Reputation points

2026-10-02T03:17:58.8033333+00:00

I'll be testing it more but yesterday after the clean installation of windows and using g-helper there were no crashes on my battery usage session. I'll keep using it more to get a reliable result. However the sleep function is still buggy as whenever the g14 goes to sleep there are times it just doesnt wake up (it occurs on battery and on plug) so I force a shutdown. I've read in reddit that many others come across this issue and just disable sleep. I disabled sleep with a command so I only have shut down restart and hibernation.

I'll keep you updated :)
Ivan B 124.8K Reputation points Independent Advisor

2026-10-02T15:59:06.11+00:00

Hi,

Thanks. If possible, please keep running the battery tests in most cases.

Thanks.
Kon 0 Reputation points

2026-10-03T04:14:38.4933333+00:00

Hey I'm here to update you. For the past 2 days I used it on battery and I did not encounter any crashes or anything. I've drained the battery from 80-20% 3 times watching movies and doing work stuff.

It's looking good :) I will try to update a longer term result but I really appreciate your guidance.

Wishing you the best :)
Ivan B 124.8K Reputation points Independent Advisor

2026-10-03T04:18:58.72+00:00

Hi,

I'm happy to help. You can always count on the Microsoft Q&A community for assistance. Have a good week, and I look forward to hearing your long-term results.

Please consider rating the question (accepting the answer or not) and visiting the Microsoft Q&A community if you have further questions.

Thanks.

Answer 2

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: