12-11-2025 12:38 PM
I've got a 2025 Flow Z13 laptop/tablet. (windows 11) When I leave it, or put it in sleep mode to turn off the screen, and stop driving two external screens, it eventually goes into a state, I think it's hibernation and it won't come back awake. I went through CS and they had a script to recover whereby I do a hard power reset, then can restart. This is clearly not a standard state, yet the CS people reassured me that it was necessary to do a hard power reset after "leaving it" in sleep mode for a set period. After recovery, all hibernation state is lost and it's like a full reboot.
Is this really a glitch with this particular model? The CS agents really have no technical knowledge to discuss anything technical, they just walk through a script for a particular symptom. When I insist that this is not normal, they say I can send the laptop in. I really don't want to take my laptop out of service for 3-4 weeks, risk losing all setttings and data. (yes, you know the first thing they'd do is full OS re-install because, well, why not?)
Is there a workaround for this? I've tried to stop hibernation from device manager settings but I'm not even sure it's hibernation mode because it does not recover state.
12-11-2025 09:45 PM
@Pabloman
Please confirm whether the BIOS version and system version of your laptop have been updated to the latest.
Also, please check the version of the graphics card driver you are using.
If the graphics driver was not downloaded from our official website but from the graphics chip manufacturer’s site,
we recommend uninstalling it and then downloading and installing the appropriate graphics driver from our official download section.
Additionally, please test whether the laptop can wake up normally from sleep mode without an external monitor connected, to determine if the issue is caused by the external display path.
Thank you.
12-12-2025 07:36 AM - edited 12-12-2025 06:25 PM
1. BIOS is uptodate: BIOS Version/Date American Megatrends International, LLC. GZ302EA.311, 8/1/2025
2. It's an AMD 8060S graphics card. I have not changed the drivers for it. The driver date is 8/1/2025 same as BIOS.
3. The hang issue is not directly tied to attached external monitors. It hangs while no external devices attached.
More importantly, your CS agents seem to have a known script for this issue, identifying the hard power reset as an acceptable solution. That tells me this is a known issue, without any available fix, at least not a software/driver fix. The first time it happened (first day I had the laptop) I thought it was bricked - it never dawned on me to hard power reset.
Having no hibernation is a major drawback to having a laptop so turning hibernation off (another suggestion from CS agents) is not a long term solution. Doing hard power resets every morning carries risk to data as well.
Agent suggested that by leaving it in sleep mode long enough to trigger hibernation, it will get into this state requiring hard power reset. Is that a known thing for this laptop? (this happens while power adapter is plugged in, or on battery so it's not related to a power saving reaction).
Thanks for your response on this.
by the way, am I the only one that finds that image based CAPTCHA on every post to be a huge pain, given the grainy low resolution images where I can't really see if that is a bus? Is this really necessary?
12-14-2025 10:27 PM
@Pabloman
Our website provides the graphics card driver version V32.0.12074.5 for the GZ302EA model.
https://rog.asus.com/laptops/rog-flow/rog-flow-z13-2025/helpdesk_download/
If the installed graphics card driver is not this version, we recommend uninstalling it and then downloading and installing the correct driver from our website to check if the issue improves.
If the problem persists, to rule out system faults, we suggest backing up your data and restoring the system before further verification.
We apologize for any inconvenience caused and appreciate your understanding.
[Windows 11/10] How to Reset (Reinstall) the Operating System
12-15-2025 06:55 AM
AMD Radeon(TM) 8060S Graphics
Driver Version: 32.0.12079.1014
Driver Date: 8/1/2025
The version that ASUS installed on this machine and delivered to me is a later version than what you referenced.
MORE IMPORTANTLY: I mentioned this in previous note and you just ignored it. YOUR AGENTS told me that the device needs to be hard power reset if I leave it in Sleep Mode and it goes into hibernation. IS THIS TRUE??? IF SO THIS IS A KNOWN ISSUE.
1. Is this a known issue (locking in hibernation requiring a hard power reset)?
2. Are you suggesting that despite 1., I need to install an older graphics driver to solve this specific problem? The agent did not suggest this, in fact they asked me to make sure I had the LATEST drivers.
3. If you have no idea what the problem is (evidence suggests YOU DO KNOW OF THIS PROBLEM) why on earth would I go through the trouble of doing a full system restore (massive pain in the a$$) on a lark?
4. This is not an intermittent problem. Like your agent suggested, it happens reliably when I put the system in sleep mode, overnight for example. My experience is that EVERY MORNING I need to restart my laptop with a full power reset, and I have lost all hibernation state (duh, I am restarting the laptop). Can you please go back to look at the agent interatction I had where they recoreded my issue and gave me advice. Talk to the agent to understand the issue they were advising me on.
If you'd like to provide me with a technically competent agent on the phone to go through some tests, I'd be happy to do that to help ASUS troubleshoot a known severe problem with the ROG Flow 13. But just throwing out "reinstall your OS and hope" or "install an older driver because our driver list is out of date" is a waste of my time. (it would be all MY TIME wasted). This problem existed on day one with the OS you installed. Your agents ARE AWARE OF IT AND HAVE A KNOWN SET OF STEPS TO RECOVER THE LAPTOP (BUT NOT FIX THE PROBLEM).
12-15-2025 10:04 PM
@Pabloman
In my response, I recommended that you install the graphics driver version provided in our official download section, rather than the latest driver from AMD, because the drivers on our website have been fully validated for the specific model to ensure system stability. Based on the issue you described, which has existed since day one of use, I suggest performing a system restore and installing the ASUS official driver to verify whether the problem persists in a controlled and validated environment. We apologize for any inconvenience caused.
a month ago
I enumerated the questions so you couldn't avoid answering the most obvious and pertintent issue - YOUR AGENTS ARE AWARE OF THIS HANGING ISSUE AND HAVE A SCRIPT TO RECOVER FROM IT BUT NO FIX.
Yet you refuse to address that point.
Instead, you make up some garbage related to the device driver for the display. Is there any cause/effect to relate a hibernation hanging issue to the display drivers? NO. There is no connection. Yet your advice is to spend 4 hours doing a system restore and installing an old driver. Why? Because you have no idea what you're doing and you don't want to address THE KNOWN ISSUE.
Maybe I should throw salt over my shoulder, then reboot while holding the mouse button down for four hours?
The issue existed on day one, with the software ASUS delivered. I'm assuming you delivered this $3500 machine with software that was tested? Yes? Well then maybe this is a known issue with how ASUS hardware handles hibernation? It appears the call agents know of this, but you haven't bothered to look into it. Why bother when you can just tell the customer to spend 4 hours doing some frivilous steps, and hope they give up?
If you're not going to help, please let some other technically skilled agent take over this issue? Please?
a month ago
Resume from hibernate isn’t just “Windows wakes up.” The display path has to be re-initialised by the graphics kernel. You're berating support whilst not fully understanding the power stack. By all means, be annoyed the device is misbehaving, but blaming support for giving you a relevant troubleshooting step is just shooting the messenger.
Perhaps post this "script", so it's clearer what exactly it is, as it's possible you're not fully understanding what it does.
a month ago - last edited a month ago
Apparently, your agents don't understand the "power stack" either, otherwise they could articulate why they think my display device driver is blocking the wake up process that works properly in billions of computers around the world. But there are hundreds of aspects of a hibernation restore, why not tell me to replace something else,....anything else?
The script, is what your agents walk me through when I say my new laptop is bricked. They seem to be aware of this "can't return from hibernation" state that Asus QA folks failed to test before delivering my laptop and many more laptops. The script involved two paths - one to just unbrick the new laptop with a power reset, and one to try to avoid the hang state by turning off hibernation altogether.
After 5 or 6 interactions with your agent, they fail to even acknowledge that their support team knows of this issue and has steps to recover from it (not fix it). You as well, choose to suggest I'm dumb and don't understand the power stack to conclude, without a shred of evidence, that one of the many aspects of restoring from a hibernation image is the root cause.
It is akin to me going to a doctor, saying I have a headache, and the doctor tells me to replace all my blood. When I question the extreme measure, the doctor "berates" me - don't you know fool, that blood runs through your head? Sure, if you did a blood test and found something in my blood that could trigger a headache, sure, maybe replace my blood. You have absolutely no evidence to suggest doing a system restore would solve a specific issue. Or perhaps you do have a knowledge base with correlating data but you sure have not provided ONE BIT of data to me about the cause. Instead, you read from your "script", the one that you pimp out to everyone when you don't know what's going on..."do a system restore". Forget how intrusive it is to do a system restore - that's not your problem, right?
So yes, I've paid a lot for the laptop and despite a serious problem requiring a fix, I get agents who prefer to just waste my time rather than trying to understand why other agents share a known fact, that your Asus computers hang when going from sleep state to hibernation state.
I told Falcon on the first exchange that this happens without external displays attached. I asked them to research the KB to understand if the collection of customer issues has lead to any specific causes for this hang, and you, he just ignore that question and provide me with a littany of time wasting steps. I'm a software engineer. We both know that "system restore" is equivalent to "reboot the computer" is equivalent to "clear your cookies" and is what you tell customers to do when you have no idea.
This is a known problem. Please research your KB. The system clean from your factory had the issue so system restore won't work. Hardware replacement won't work either and is an even more invasive step.
If your agent feels offended by a customers' frustration, they should look for another line of work. If you want to put the person respnsible for this bug on the phone, they I could direct my frustration at them, but your CS strategy is to put someone without knowledge or accountability on the support lines to shield those responsible. Take that up with your boss.
4 weeks ago - last edited 4 weeks ago
@Pabloman wrote:
I enumerated the questions so you couldn't avoid answering the most obvious and pertintent issue - YOUR AGENTS ARE AWARE OF THIS HANGING ISSUE AND HAVE A SCRIPT TO RECOVER FROM IT BUT NO FIX.
Yet you refuse to address that point.
Instead, you make up some garbage related to the device driver for the display. Is there any cause/effect to relate a hibernation hanging issue to the display drivers? NO. There is no connection. Yet your advice is to spend 4 hours doing a system restore and installing an old driver. Why? Because you have no idea what you're doing and you don't want to address THE KNOWN ISSUE.
No disrespect, but comments like this are precisely why it's best to follow procedure and not presume.
Service suggested you try a validated driver, but you then wanted to berate them, insinuating the display path couldn't possibly be related to this problem. In reality, it can be directly involved in hibernation/resume hangs because the GPU/display stack must fully tear down and re-initialise during the resume sequence. So it's naive not to at least attempt these steps.
Ultimately, if you're going to go after service for something, at least be half right. I think that's fair to say? It's a bit like your own Dr analogy. All that happens is the thread gets derailed, and you impede further escalation. Please answer anything and attempt the diagnostic steps provided; they're not claiming it will resolve the problem.
For my own curiosity, can I ask if this behaviour happens both with the AC connected and whilst on battery?
Thanks