12-11-2024 10:05 AM
I have been experiencing random restarts since I bought my ASUS ROG STRIX SCAR 17 (G733PYV). It seems many other people have experienced the same or similar issues with this and other ASUS models.
The restarts were completely random... sometimes after only a few minutes... sometimes after several hours. They didn't seem to be dependent on CPU or GPU load or temps. It didn't matter if I had no applications open and the system was idle or if I was in the middle of a game.
I've tried everything else I found in this forum and other places...
Uninstalled everything ASUS related including ArmouryCrate and all ASUS and Aura services.
Install GHelper
Updated all drivers to ASUS recommended drivers.
Updated BIOS to latest version
Disabled Fast-Boot
Disabled Bluetooth
etc., etc., etc...
I was frustrated and ready to return my new laptop and get a refund...
Finally, I came across this post:
https://rog-forum.asus.com/t5/gaming-notebooks/solved-random-freezes-and-reboots-asus-rog-strix-g17-...
SOLUTION
Control Panel -> Hardware and Sound ->Edit power plan (under Power Options) -> Change advanced power settings
In Power Options window, expand PCI Express and then expand Link State Power Management
Change settings to:
On battery: Moderate power savings
Plugged in: Off
After making this change, I have not had any further random reboots!!
The original post was closed but I wanted to post my experience and give thanks to EyePatch for posting the solution for others!
Hopefully this is helpful to someone else!
12-11-2024 01:12 PM - edited 12-11-2024 01:34 PM
Hi @Jeff5266 , as mentioned in DMs... Thanks again for not only referrencing my (automatically-closed) post but also continuing my it at ASUS Forums ( ASUS should really warn atleast 1 week prior before automatically closing posts, I had planned to share update of my status ).
I hope to hear positive updates from you in a month's time as well.
__________________________________________________________________
@asus @AsusAsus @ASUSD @asusg @ROG @RogRog @RogRogRog @Anbby_ROG ( Any of you who really represent ASUS / ROG ) : Kindly look into this issue as seems to have been resolved with this particular solution for people with similar models. This is an existing issue of more than 2 years, kindly look into it and give a final verdict while Also mentioning this solution and giving a proper explanation. This is a question of integrity of Support Team, and not the manufacturers ( as errors are necessary to reach an optimal solution ). 🚩
-------------------------------------------------
Now, I'll be sharing my update from my former post here:
> I intended to reply after a month but I was still observing some crashes 🟨 (though minor, the solution worked 90% for me 🟩), I was unable to decypher the cause.
> I had been using sleep/hibernate as well so was unsure of the cause bsod and reboots that were still happening, like the instances I observed were like:
NOTES:-
| | | | | | | |
SEPTEMBER 2024 ( WINDOWS )- Count Of Reboots/Crashes : 7
OCTOBER 2024 ( WINDOWS, FEDORA ) - Count Of Reboots/Crashes : 6
NOVEMBER 2024 ( WINDOWS ) - Count Of Reboots/Crashes : 4
________________________________
Hi @Yury_X16 ,
How've you been?
I hope it's been great for you.
Here's my update.
Kindly do share your experience as well, I pray for it to be positive and be contributeful for community.
Best Regards,
EyePatch
12-11-2024 06:47 PM
Hi @EyePatch ,
Thank you for your attention to this issue. According to your records, the BSOD phenomenon is still occurring.
Could you please use the AsLogDumpTool to capture system information and record the error codes and the time of occurrence after the BSOD happens?
Additionally, please provide the following information via private message so we can further investigate the issue. Thank you.
12-12-2024 01:39 AM
Understood @Anbby_ROG , can I follow back to you when my next BSOD / Reboot Occurs?
I'll reply with all these questions in both DM and as well as here in this Thread (for community to see as well).
Plus another question, how long does it take for ASUS ROG Post to automatically be closed when thread isn't active?
12-12-2024 11:20 PM
No problem! Please provide the relevant information, and I will forward it to our technical team for further investigation.
Additionally, if a thread remains inactive for more than 30 days, the system will automatically close the thread. Hope this information is helpful. Thank you!
12-12-2024 11:34 PM
Understood ,
Thanks alot for your support and information.
I'll get back to you with relevant information (when I get the reboot) in both Dm and here, as well as would keep this Thread Live until issue resolves.
12-12-2024 11:28 AM
Try this solution and share your experience as well. ( If works well, then reply in month's time with your observations ).
12-15-2024 01:24 AM
Hello everyone,
I have the issue.
I'm trying with the proposed fix but I don't believe that could work as I do have the same exact issue also with Linux.
I experienced an increase of random shutdowns (black screen -> laptop completely switched off) wiht the latest bios, is it possible to rollback the bios to a previous version?
For now I'm using with discrete gpu only and it seems not having the issue, the problem is that I need to use it in battery mode and the battery consumption was very high with integrated GPU disabled in bios.
I hope Asus can find a fix for this. This appears to me like an HW bug and maybe a fix does not exists.
PS: Removing armoury-crate does appear to alleviate the problem a bit.
12-15-2024 02:33 AM - edited 12-15-2024 02:34 AM
If you check the former post of mine ( Author shared the link)
There's someone who applied the same solution for Linux (Fedora) and had it resolved for 2 weeks atleast (that was his last update).
I tried the solution in my Linux Fedora ( as I also have Dual boot and same issue) but I'm unsure as was formerly getting 10% reboots eitherway...
(Tho I hope that by now there's a Bios update that fixed it... I intend to reply with what Asus Support ask me here when I get my next reboot)
Feel free to try and share your results.
And I agree, that technical aspect should be checked.