08-09-2024 04:22 PM
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.
12-10-2024 03:53 PM
any way you can elaborate more on the ASU control interface? Not sure what that is
12-10-2024 03:57 PM
So I’m not entirely sure myself, I was advised by someone on the Reddit discussion on all of this,
if you go into device manager, click system devices near the bottom, and uninstall the above mentioned, then reinstall here : https://www.asus.com/support/faq/1047338/
in the section for V3 it says click here to install it, that’s what I followed to reinstall (forget about the instructions just sift through to find the install link)
12-10-2024 04:15 PM
Thanks a bunch for the quick reply.
12-10-2024 04:55 PM
No problem! We’re all in this together, we just want our £800 ally x’s to work! XD
Do let me know how you get on please!
12-11-2024 09:26 AM
Any luck?
12-15-2024 04:43 PM
Nope, nada. I updated to the beta bios and also nothing. I tried to run the dump tool they wanted me to use but the Ally doesn't let me says it's not for my PC lol
12-11-2024 09:14 PM
I think now it not fair for us who have this problem. this black screen occur more than 100 days until now i can see Asus support here just do by gathering information only 100 days ? and release bios that can't fix the problem and ignore to find and solve this problem or offer refund every customer who have this problem it so expensive handheld but asus only do like this it so unfair.Asus must conference all with technical and find cause urgently but until now still no clear information why it still happen . It not fair for Rog all x customer.
a month ago
Any updates to this situation having issues with mine as well. I see theres a 310 Bios? Could I get a link for it to try it myself but seems like it didn't solve everyones issues.
a month ago
I got provided it via DM by one of the customer service reps active on this forum, but sadly didn’t solve a thing for me. Hopefully they’ll get this worked out soon coz it’s getting really frustrating now not knowing when it’s gonna crash. I have a temporary workaround by mapping Y to M2 and not had a crash since, but that’s obviously not a permanent solution.
4 weeks ago
I waited for abit before replying to test this out but you're right mapping Y to M2 solves the issue entirely.
I was DMed by a service rep and provided with the 310 Bios. However, it didn't solve the Y issue for me either provided the .win infomation hopefully they can resolve this issue soon.