Hello! I've encountered an issue with my Asus ROG Ally (2023). Yesterday, I started a game, and after about 1-2 hours of gameplay, something happened that hadn't occurred before the 338 BIOS update. My console stopped charging. The device no longer recognizes the charger. I used the original charger that came with the Asus device, I didn't use any third-party software or programs, and the charger is working fine as it charges other devices without any issues.
The first thing I did was restart the device, and (not immediately, but eventually) the charging started working again. I repeated the game session, and after 30 minutes, the issue happened again, but this time I monitored the resources and noticed that as soon as the CPU temperature reached 95 degrees, the charging stopped. I turned off the game, waited for the temperature to drop, and at around 45-50 degrees, the charging resumed.
I repeated my tests several times, and here's what I found:
- The device was in Turbo mode (default setting).
- Before the 338 BIOS update, on version 337, I played the same game (Elden Ring), and the fan was slightly louder, which is noticeable now.
- Currently, the device heats up to about 95±2 degrees in Turbo mode in about 1.5 hours, and the charging stops.
- On BIOS version 337, this didn't happen; the temperature was stable at around 83-86 degrees, and there were no issues with charging.
- On the ASUS forum, I've seen similar issues, and people suggested creating a custom "Manual" turbo mode and increasing the fan speed at certain temperatures.
- I followed their advice, and to my surprise, for at least 3 hours, the temperature was around 85-87 degrees, and there were no charging issues.
Unfortunately, I only encountered this issue yesterday, and today I have many questions that I would like ASUS to comment on. This is not an isolated incident; it clearly (appears to be) related to their latest BIOS update. I am concerned about other projects and programs that might affect my device. I want to make sure ASUS is aware of the problem and is addressing it.
If anyone else has encountered the same issue, please support this post so it gets more attention. Or am I one of the few unlucky ones?
