Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash on TUF a16 kernel event 41 #3409

Open
2 tasks done
boiledorigin opened this issue Nov 25, 2024 · 13 comments
Open
2 tasks done

Crash on TUF a16 kernel event 41 #3409

boiledorigin opened this issue Nov 25, 2024 · 13 comments
Labels
question Further information is requested

Comments

@boiledorigin
Copy link

boiledorigin commented Nov 25, 2024

Rules

  • I made myself familiar with the Readme, FAQ and Troubleshooting.
  • I understand that, if insufficient information or no app logs will be provided, my issue will be closed without an answer.

What's wrong?

My laptop crashes on first boot when on battery during the first boot after being plugged in on optimized mode really irritating when im in class and it restarts when im supposed to be taking notes

edit -only happens when optimized mode was in standard when it was plugged in then when it boots it is unplugged and switches to Eco works for a minute freezes then crashes

How to reproduce the bug?

  1. boot system after it being charged
  2. open apps such as Firefox and note taking app
  3. wait a minute or two
  4. crash to automatic reboot
  5. event id 41 and event id 6008 found in event viewer

Logs

log.txt

Device and Model

Asus tuf a16 FA617NT

Additional information.

No response

Armoury Crate

Uninstalled

Asus Services

7

Version

0.197

OS

Windows 11 24H2

@boiledorigin boiledorigin changed the title Crash on TUF a16 Kernal event 41 Crash on TUF a16 kernel event 41 Nov 25, 2024
@seerge
Copy link
Owner

seerge commented Nov 26, 2024

@boiledorigin hello,

I don’t think that crash is related to G-Helper as it’s not a driver and is not running your system in real time.

Event 41 is the kernel power, if i remember correctly. So most likely it’s some underlying issue with windows /drivers or firmware/hardware.

  • Try to do a clean reinstall of all NVidia drivers from official nvidia website (and check Reset to Factory defaults during installation)
  • Try to check “Enable GPU on shutdown” in G-Helper’s Extra settings (it helps with some driver issues)

@seerge seerge added the question Further information is requested label Nov 26, 2024
@boiledorigin
Copy link
Author

hey seerge thank you for the suggested fix however i do not appear to have that option as of 0.197.0 idk if its a thing with raedeon gpus on ghelper or what but I will reinstall the Raedeon drivers though sorry i should have mentioned that

@seerge
Copy link
Owner

seerge commented Nov 26, 2024

@boiledorigin ah, sorry. I didn’t realise you have all AMD model (same as me btw, with G14 2022).

Then try to do a clean reinstall of AMD drivers from AMD website (and also tick Factory Reset during install), to see if it helps?

@boiledorigin
Copy link
Author

Tried that in the crash happened again I have a video of it. I coach Steam and then it happened again I’ll keep it on standard when I’m in class then toy with it over break to see what I can do and to see if it won’t restart.

@seerge
Copy link
Owner

seerge commented Nov 26, 2024

@boiledorigin may be device just don’t behave well when GPU is turned off?

Does same happen if you would just boot in Standard mode and then manually set Eco (this is same as Optimized does)?

Does performance mode (like Silent or Balanced) make any difference?

@boiledorigin
Copy link
Author

Performance mode doesn’t make a difference, however I’ve noticed that it behaves perfectly fine on Eco or standard when I manually set them. Maybe it has something to do with optimized itself. I don’t know. But thank you for helping me out with the issue I had.

@seerge
Copy link
Owner

seerge commented Nov 26, 2024

@boiledorigin the one and only thing Optimized mode does is just automatically sets Eco on battery and Standard when plugged.

So it’s strange that when you select Eco manually - it’s ok.

May be just try to use Eco for a while and see if something pops up?

@seerge
Copy link
Owner

seerge commented Dec 8, 2024

@boiledorigin hello, do you have any updates or did you made any new observations over last time? Does it work fine if you just use Eco?

@icedterminal
Copy link

I have the same model, TUF A16 (FA617NT). I can indeed reproduce identically.

  1. With system powered on and plugged in, set mode to "Optimised"
  2. Shutdown system.
  3. Power on system.
  4. Give the system a moment to load.
  5. Open Firefox (or any gpu based task)
  6. Observe system freeze and instant reboot.

A cold/clean shutdown (discard both sessions), hibernate (keep user and kernel session), or fast startup (keep kernel session, discard user session) makes no difference. As long as you repeat the steps above, it happens every time. I believe this particular issue is not something that seerge can fix. This seems like a driver or ASUS issue with implementation at the firmware level. Something about "Optimised" does not work well on this model.

@seerge
Copy link
Owner

seerge commented Dec 17, 2024

@icedterminal hello, as mentioned above the only thing Optimized does is just automatically sets Eco on battery and Standard when plugged in. It doesn't do anything else besides that.

This also includes situation when you boot laptop in a state different from one that should be based on current power source (i.e. you boot in Eco and laptop is plugged in). If you would boot in Standard when plugged - no changes would happen.

The toggle happens pretty much as soon as G-Helper starts (which is usually couple of seconds after you log in to windows).


I can suggest you to try following : delay all automated actions for a few seconds to see if it makes any difference.

Quit app and add following line to %appdata%\GHelper\config.json. Then start app again as explained in power-user settings:

"charger_delay" : 2000,

That would delay toggle for 2 seconds.

Thanks

@seerge
Copy link
Owner

seerge commented Dec 29, 2024

@icedterminal hello, do you have any updates here ? Does adding 2 second delay for all automated actions (including GPU toggle) make any difference for you ?

@icedterminal
Copy link

Adding a delay doesn't change the outcome. It still hangs and suddenly reboots.

@seerge
Copy link
Owner

seerge commented Jan 2, 2025

@icedterminal ok,

As I understand it happens to you only if device booted with GPU being ON (i.e. in Standard) and then it's being disabled by Optimized cause it's unplugged as soon as windows loads ?

Can you try to keep laptop in Standard but set Eco manually as soon as possible after boot? Does it have same effect ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants