ASUS TUF F15 Windows 11 standby freeze

I currently have my asus laptop for a while, probably close to 3 years now. It has been working fine until a week ago specifically since 18-03-2026.

I have been experiencing freezes during standby or when lid closed. It has been occurring basically every time that my laptop goes into standby for over an hour both plugged in and on battery. The only way to solve it is force shutting down by long pressing power button and then restarting manually. There is no blue screen as the display is just black not an arrow nothing and the light bulb indicator is solid white with I think depending on if the charger is plugged in the battery icon also solid white or off and the disk light is off. Also tried getting a crash dump by enabling it in windows but in the exact directory that is should be it is just empty. So I think it crashes even before it can create a dump.
Thing is I think it does not crash until waking up. As the lights are slowly blinking on off indicating standby, but then as soon as I either use my mouse click a keyboard key or open the lid if closed, the constant on lights happen. What is intereesting for me is that the disk light stays of, but why that happens I don't know, as I have checked.

I have already tried many things, like chkdsk /f /r to check the disk, also crystaldiskmark shows condition is good. It has the original SSD. All seems fine, also sfc /scannow and dism. All did not indicate anything bad or fix the problem. Furthermore I tried memory diagnostic using windows built in tool which also resulted in no errors found.

I have tried disabling fast startup in windows as well as fast boot in the BIOS.

I have already looked into S states and disabled hibernation. which did not seem to do anything, I have of course tried windows update I am fully up to date.
Tried updating Intel Management Engine which was older than it should have before, possibly 2023 or 2024 driver, but now updated to the latest but did not fix.

Tried DDU both intel and nvidia graphics drivers, also again updating back to latest drivers. Tried multiple pc profiles for GPU, eco, standard optimized. all same behavior. I normally use ghelper but also tried closing that and using armoury crate only from fresh install. Not the solution.

I do seem to get almost everytime exactly as last log information the following entry

The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well. For this I tried unregistering and reregistering/starting time service which I found online but does not seem to fix the freezing or logging.

It sometimes also seems to continue logging during the freeze. For example reliability history shows an entry with date 19-03 10:03 as that is when I tried to start and force rebooted the pc. but the previous shutdown is put at 15:54 (18-03), while the windows system log shows many entries after that 15:54 and before 10:03 the next day.
So I have no clue what is causing this, but tried a lot. One thing that I am not super sure about but has popped up recently, I had to reenter my bitlocker key using my microsoft account. I have never really needed to do this, although I saw a windows update that seemed to suggest this was going to happen. If so could bitlocker have anything to do with this?
Already tried reinstalling chipset and serial drivers to original asus support versions.
Also reset some drivers that seemed to link to some entries in the windows log, but this also did not make a difference.

The only two windows update entries on 18-03 if they are connected/casuing this are: Windows defender updates KB2267602 (versie 1.445.601.0) and KB2267602 (versie 1.445.603.0). And KEK secure boot key update on 18-03 also.

If anyone could guide to me to help debug or try possible solutions that I did not mention yet please let me know!

I have not yet tried and inplace upgrade, but if no other causes are identified that might be my next try.

I have tried a lot, so possibly I have forgotten some fixes I tried if I remember I will respond or update the post.
Added attachments are a log of the non information entries of the past 30 days and the reliability history showing when exactly the broken wakes/freezes happen as well as some install/uninstall info of course.

About all I could suggest is to see if your system log files give any indication of the problem. Gather your logfiles per these instructions. Put them all in a folder, zip the folder, and upload the zipped folder to any cloud provider. Post a SHARE link to the shared folder here. When @zbook comes online he can analyze then for you. BSOD - Posting Instructions

1) Run the V2 log collector > post a share link






2) Add WMIC:

DISM /Online /Add-Capability /CapabilityName:WMIC~~~~






3) Enable regback:






4) Run tuneup_plus_log.bat > post a share link








5) Create a new restore point:





6) Open event viewer > system and application > post share links

Run administrative command prompt: > post share links

wevtutil epl Application "%userprofile%\Desktop\application.evtx"

wevtutil epl System "%userprofile%\Desktop\system.evtx"

@zbook I have done all steps
v2log is attached -> ASUS-...

tuneup_plus_log gives: tuneup.log

For step 6, I am not sure what you mean? I have added the evtx files from the exports if that is what you mean. Proton Drive

I suspect that the culprit is G-Helper. I would never use such an app on this type of Laptop.

Normally the manufacturer supplies various Power profiles for certain scenarios with their particular hardware configuration.

Therefore look to your Power Plans:
Control Panel > Power Options

On mine there are 3 from the manufacturer, plus the standard MS balanced one.

On the left menu is "Choose what closing the lid does" should be about 4 choices: Do nothing, Sleep, Hibernate, Shut down.
You have not said what you have actually configured(and saved), the lid, power button etc, when the problem occurs.

My Laptop is a different brand but probably almost identical hardware. Has exactly the same Windows updates as yours, except the forced Graphics driver updates, an 3rd party uninstaller, G-Helper which I don't use.

Settings > System > Advanced > Virtual Workspaces > Everything there is Off.

Helmut said:

I suspect that the culprit is G-Helper. I would never use such an app on this type of Laptop.

Normally the manufacturer supplies various Power profiles for certain scenarios with their particular hardware configuration.

Therefore look to your Power Plans:
Control Panel > Power Options

On mine there are 3 from the manufacturer, plus the standard MS balanced one.

On the left menu is "Choose what closing the lid does" should be about 4 choices: Do nothing, Sleep, Hibernate, Shut down.
You have not said what you have actually configured(and saved), the lid, power button etc, when the problem occurs.

My Laptop is a different brand but probably almost identical hardware. Has exactly the same Windows updates as yours, except the forced Graphics driver updates, an 3rd party uninstaller, G-Helper which I don't use.

Settings > System > Advanced > Virtual Workspaces > Everything there is Off.

Click to expand...

Dear Helmut,

Thank you for your reply.
I have already fully disabled g-helper and before that have used it for a long time. Nothing suggest g-helper being the issue. I am not sure if you see it back in the log. And like I said I did a full reinstall of armoury crate if that had anything to do with it.
For me there is balanced and asus profile I currently have it on balanced and I think it has often been at that, but like other things, I have not changed or used control panel to go into those settings for months.
I had for choose what lid does -> standby both power and battery, but now as a workaround do nothing as not going into sleep is the only way to not crash, which is not really usable if you understand for a laptop espessially. It does not matter how it gets to standby either way it crashes on wakeup.

I have never been in the virtual workspaces menu but platform for virtual machines was on It has now been turned off only windows hypervisor is not greyed out and was already off. The rest is greyed out. I don't really use virtual machines but I will check if it helps by restarting and then standby.

If you have any other suggestions please let me know as I am reallly annoyed and frustrated by this issue and already tried so much.
Do you think a windows in-place upgrade could help?

The log files were in a foreign language and could not be scanned.

Please temporarily us English as the default language so that files can be scanned an read.







Run administrative command prompt: > post share links

wevtutil epl Application "%userprofile%\Desktop\application.evtx"

wevtutil epl System "%userprofile%\Desktop\system.evtx"

(Look on the desktop for new files) > report the method used



In case the above commands produce error messages then comment into the thread and:

open event viewer:
open event viewer:

a) system > post a share link

b) application > post a share link









Please make sure that files are not cleaned during the troubleshooting: Glary Utilities, Ccleaner, disk cleanup. etc.

zbook said:

The log files were in a foreign language and could not be scanned.

Please temporarily us English as the default language so that files can be scanned an read.

Add, Remove, and Change Display Language in Windows 10

How to Add or Remove Language Packs and Change Display Language in Windows 10

www.tenforums.com

Change Display Language in Windows 10

How to Change Display Language in Windows 10

www.tenforums.com

Run administrative command prompt: > post share links

wevtutil epl Application "%userprofile%\Desktop\application.evtx"

wevtutil epl System "%userprofile%\Desktop\system.evtx"

(Look on the desktop for new files) > report the method used



In case the above commands produce error messages then comment into the thread and:

open event viewer:
open event viewer:

a) system > post a share link

b) application > post a share link

How to Export Windows Event Logs | Dell US

Code:

Event[5103]
  Log Name: System
  Source: EventLog
  Date: 2026-03-18T14:54:14.3230000Z
  Event ID: 6008
  Task: Geen
  Level: Fout
  Opcode: N/A
  Keyword: Klassiek,
  User: N/A
  User Name: N/A
  Computer: PaulsASUS
  Description:
De vorige afsluiting van het systeem om 14:46:20 op ?18-?3-?2026 is onverwacht gebeurd.

Code:

Event[9794]
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2026-03-25T14:16:31.8760000Z
  Event ID: 41
  Task: N/A
  Level: Kritiek
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: PaulsASUS
  Description:
Het systeem is opnieuw opgestart zonder eerst correct te zijn afgesloten. Deze fout is mogelijk veroorzaakt doordat het systeem niet meer reageert of is vastgelopen of doordat de stroom is uitgevallen.

Click to expand...

You did not say that I needed to get in in EN, I assumed the log file wasn't in a language specific. The dell link you showed only exports the same as your command, but don't result in English exports. Not sure if I needed to use it for something else.
I did not see how to export in english besides trying to click use language english in the export but this did not seem to actually show English logs.
I have set my system language to English and exported, and opening it seems to show English logs, but I cannot guarantee if for some reason logs have been made in NL, then, maybe they still will show in NL not EN.
see Proton Drive again but click the NON NL variants.

For the specific log entries you showed they say the previous shutdown was unexpected and the system has been restarted without proper shutdown, might have been caused by freeze/crash or power failure. Which is true because I force shutdown after the freeze. But they don't show any insight in the before and why.

The computer had at least two recent BSODs:

11/14/25
01/12/26
01/26
01/29
02/03
02/10
02/18


1) Read this link on Windows Driver Verifier (WDV):

Enable and Disable Driver Verifier in Windows 10




2) Create a new restore point





3) Learn the methods to recover from BSOD caused by WDV by booting into safe mode and running one or more of these commands:

verifier /reset

verifier /bootmode resetonbootfail



(option nine and seven)





4) Plan to run the tool with various customized test settings.

a) Test all non-Microsoft drivers

b) Test no Microsoft drivers

c) For the first run of WDV select the 3 customized tests displayed in the TF tutorial






5) Whenever the WDV tool is started if there is no immediate BSOD then open administrative command prompt and copy and paste:

verifier /querysettings

Post a share link.



Customized tests will then be posted for the next run of WDV.



WDV can run continuously during the testing.



For any BSOD post a new V2 share link into the newest post.