a month ago
Several people have reported this issue on Reddit; I've encountered it myself as well.
I created this thread on the ROGAllyX subreddit to try and gather info, no one else has added to it yet but it also has links to all the other threads I've seen about this matter: https://www.reddit.com/r/ROGAllyX/comments/1eoch1d/rog_ally_x_black_screen_crashes_has_it_happened/
Wondering if anyone can shed any more light on the cause and/or workarounds, or if an upcoming update is going to sort it.
a month ago - last edited a month ago
One Redditor in that thread has reported a situation that *consistently* triggers this crash - they consistently get a crash after the Class Select screen in Kingdom Hearts 1.5. The same Redditor also reported the crashes are occuring on both Windows and Linux.
4 weeks ago
Hi @nvera ,
Thank you for gathering information on the crashing and black screen issue. According to user feedback, the problem seems to occur during gameplay. Since different games have varying settings, there could be multiple factors affecting this issue. If possible, please try adjusting the VRAM settings in the game to see if it improves the situation. Additionally, ensure that you are using the ASUS-verified AMD graphics driver version V31.0.24028.3. Thank you.
4 weeks ago - last edited 4 weeks ago
Thanks for the response.
I haven't changed the GPU driver on my own system - Armory Crate or Adrenalin might have updated it, but otherwise I'm using the one the Ally X shipped with. Other users with this issue have reported it on both the stock driver and one obtained directly from AMD, as well as on non-Windows OSes (which presumably use a different driver altogether). Feels more likely to be a BIOS issue?
I've done an EC reset as suggested by ASUS live chat, hard to say if it helped - haven't had a crash since, but it's a very random thing, and I hadn't had one for a little while before that either. However another user reports continuing to get the crashes even after an EC reset.
Except for the GPU driver one, I have tried all the older suggestions in that thread. I stopped getting crashes after I installed those missing drivers from AMD; however other users have reported still getting crashes after that, so likely coincidence.
4 weeks ago
We finally have an exciting update over on Reddit - one user who was getting a particularly high frequency of crashes (usually within ~20mins of starting a game) has reported that after disabling rumble, they were able to play an hour session without any crashes.
This is only a single data point from a short session at this point, but it's the most promising lead so far.
4 weeks ago
Thank you for your feedback. Regarding the in-game crashing issue, there could be many factors affecting it (drivers, game settings). Similar to what one user mentioned, many users encountered FSR issues in "Witcher." If the crashes continue to occur in the same game, please provide the following information via private message for further investigation:
Please enable the log recording feature in Armoury Crate SE before starting the game, and after the crash occurs, provide the log file for further analysis. Thank you.
【This is the file path for the log file, provided for your reference.】
In Armory Crate SE, navigate to" Settings">"General" and check the "About" page. Click on "App Diagnostics tool" and select "Log Files" to bring up the Privacy Policy statement. Once the user agrees to the statement, Armory Crate will start collecting diagnostic logs. You can click on "Generate Log Data" to create an encrypted log file (ASUS log file).
4 weeks ago - last edited 4 weeks ago
I don't have any logs handy right now as I haven't personally had a crash in a while now, but will pass that on.
Regarding the other questions, for my case:
Service version output:
Item Version
---- -------
Armoury Crate SE UWP App 1.5.11.0
ROG Live Service 2.4.15.0
Armoury Crate SE service 1.5.11
BIOS RC72LA.304
MCU Firmware GA80100.RC72LA.310
AMD Radeon Graphics 31.0.24028.3
ACConfig 1.0.5
Aura Service (Lighting Service) 3.07.50
Aura SDK 3.04.44
ASUS Aac_GmAcc HAL 1.0.12.0
ASUS Aac_NBDT HAL 2.5.40.0
ASUS Ambient HAL 3.4.0.0
ASUS Keyboard HAL 1.2.65.0
ASUS MB Peripheral Products 1.0.40
ASUS Mouse HAL 1.2.0.97
AacAudioHal 1.3.67.0
AacDisplay 1.2.36
3 weeks ago
Hi @nvera ,
Please continue to monitor the usage. If the issue occurs again, please provide the current system information, logs, and a video so that we can assist you with further verification. Thank you.
3 weeks ago - last edited 3 weeks ago
I will, for sure. Only one new user has reported a crash recently, and they specifically mentioned they hadn't updated to the latest BIOS nor GPU driver yet - another user has reported good results from the latest BIOS. No one has yet reported a crash specifically on BIOS 305. (Meanwhile, chat / email support are suggesting to RMA my device and seem uninterested in that it's a widespread problem...)
Personally, I haven't had a crash in a little while now, but it still always hangs in the back of my mind when I'm gaming that it could happen. So it'd be nice to get confirmation if BIOS 305 (or any other recent update) is indeed meant to fix it; whether that comes from ASUS or from community feedback. And I can't specifically speak for anyone else, but, I'm far more likely to consider ASUS again next time I need a new device, if the issue is acknowledged and openly addressed, than I am if a fix is just snuck out with no comment, even though I'm still going to be happy with the current device as long as a fix happens (regardless of how).
4 weeks ago - last edited 3 weeks ago
I could've sworn I posted my info (EDIT: huh, it wasn't showing up, but now it is showing again). 😕 I'll get that again later, but in the meantime - another user has unfortunately confirmed that they get the crashes even with Rumble turned off.