Issues with booting on ROG Strix G513

[KiraX86]

This problem has been appeared once before today to me and it "fixed" itself within around 1 hour but today it rendered my ROG Strix G513 inoperable for around 7 hours.

The issue as it presents itself: When the laptop lid was closed and reopened about 15 minutes later the screen would be completely black. Both the activity indicator and the airplane mode indicator are a solid white light. No blinking from I/O activity but the light for the battery will activate is charging. The back lighting on the laptop is normally turned off and remains off until I restart the device (holding the power button for ~10 seconds until the red indicator on the power button turns off. Then the activity indicator will turn off but for about 15 seconds after shutdown the airplane mode will remain as the only light on.

After reboot no ROG logo will appear and the backlighting will turn on in the default rainbow pulsing.  The only indicators that power on are the activity/power on indicator and the airplane mode indicator. This is odd because I never use airplane mode. The system will not boot after the restart and the screen will remain black during this time. No fan sounds can be heard. No matter how many times it is restarted or how long it is left on while in this state it will not display anything and is unusable.

Things I have tried to fix this:

• Rebooting (duh)
• Removing all USB, HDMI, power cables plugged in
• Letting the laptop die and then charging it to full and rebooting
• Booting up with a second monitor to see if anything displays to the device
• Disconnecting the battery and then letting the device sit and rebooting

The first time this happened it was fixed when I plugged it into a monitor (This may not have fixed it as it was not the only thing I was doing to solve the issue at the time) and this second time it booted after being left in this state for about 45 minutes. I do know for a fact that it is not a operating system issue as I have read through the logs produced during boot-up from `journalctl -b` and they appear to be completely normal and match ones from around 2 months ago. That can not be farther from the truth with logs produced from `last -x` that read as follows:

kira pts/1 :1 Fri Sep 20 15:38 still logged in                                     //current session
kira pts/0 :1 Thu Oct 26 08:56 gone - no logout                              // This is in order from most reason to least, I swear.
kira tty1 Thu Oct 26 08:56 gone - no logout
runlevel (to lvl 5) 6.5.0-44-generic Thu Oct 26 08:55 still running
reboot system boot 6.5.0-44-generic Thu Oct 26 08:55 still running
kira pts/0 :1 Fri Sep 20 07:24 - crash (-329+22:28)
kira tty1 Fri Sep 20 07:23 - crash (-329+22:28)
runlevel (to lvl 5) 6.5.0-44-generic Fri Sep 20 07:23 - 08:55 (-329+22:27)
reboot system boot 6.5.0-44-generic Fri Sep 20 07:23 still running     // this morning before the "crash" that started this

I think the biggest thing to note is the time "skip" it is actually happening into the past to Oct 26. NTPD logs showed that it was correcting it's time from Oct 26 2023. At first this seemed to make full logical sense to me and I just assumed that my CMOS was dying/dead and that I would need to replace it but that does not appear to be fully correct. Information from /proc/driver/rtc seems to point to the battery still being charged. This could be incorrect as I am not fully sure why/how that is able to tell CMOS charge.

Information to note: I am running the following linux build gathered from `uname -a`:

Linux kiraX86rog 6.5.0-44-generic #44-Ubuntu SMP PREEMPT_DYNAMIC Fri Jun 7 15:10:09 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

While I am a pretty good with computers this is outside my area of expertise as I have a limited knowledge of hardware for laptops. With this happening 2 days ago and then again today I can only hope that this is a freak occurrence but I can not be certain after it repeating today. Any advice about what could be happening would be greatly appreciated. I am willing to send logs or share data if requested.

Thank you,

-Kira x86-64