The blue screen error I get when using G Helper...

[cristianoronaldinho2009-svg]

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?

I'm an Asus ROG Strix SCAR RTX 5080 user. Although I couldn't pinpoint the exact cause, I was constantly getting an error that caused a reboot loop. The error message was: "Your device ran into a problem and needs to restart. VIDEO_DXGKRNL_FATAL_ERROR(0x113)". Even after performing several clean installations, the same error kept reappearing. Finally, I wondered if the error might be caused by Ghelper, so I stopped using it. The number of errors decreased dramatically. But I really like this program, and that's why I want to report this error. I'm also attaching the minidump files in case they're useful.

How to reproduce the bug?

It usually happened in eco mode or when switching between modes. Sometimes it would occur when Windows first started. Rarely, simply navigating the desktop could cause this error, which would lead to a restart loop.

Logs

020526-13750-01.dmp
020526-14125-01.dmp

020826-12765-01.dmp
020826-13609-01.dmp
020826-13625-01.dmp
020826-13812-01.dmp

Device and Model

Asus Rog strix scar 16 rtx 5080 G635LW

Additional information.

No response

Armoury Crate

Uninstalled

Asus Services

No response

Version

0.239.0

OS

windows 11 pro 25h2

[seerge]

@cristianoronaldinho2009-svg hello,

G-Helper is not a driver and it's not interacting with hardware in realtime. But you could have some underlying hardware / firmware issue that pops up only in certain settings or mode. Especially considering that issues still appear even without G-Helper.

• Can you upload app log from %appdata%\GHelper?
• What settings did you use ? Did you overclock GPU or undervolt CPU ?
• What do you mean under "stopping using G-Helper". What do you use now and with what settings (again)?

To tackle it :

• I have seen few devices that were crashing on "Best Power Efficiency" Power Mode in windows settings. Try to set it to "Balanced" or "Best Performance" (under Fans + Power).
• Try to disable power link management in windows power plan. It's enabled by default there for energy saving.

Thanks

[seerge]

@cristianoronaldinho2009-svg any updates here ?

[frps]

I can confirm the same issue: VIDEO_DXGKRNL_FATAL_ERROR (0x113).
ROG Zephyrus M16
Intel 11800H, Nvidia RTX 3050 Ti, Windows 11

I'm using ECO mode 100% of the time.

Possible pre-error signals are:

1. the fans starting to spin
2. the notebook getting hot

Therefore, I guess the mode switches spontaneously from ECO mode to Standard.
At least, it is set to Standard after a post-error reboot.

My guess is that it is similar to this:
"The fix that worked: I didn't need to open the laptop or reinstall Windows. I just had to stop the laptop from 'switching' graphics cards."
https://www.reddit.com/r/techsupport/comments/1n3a47f/facing_frequent_blue_screen_of_death_video/

There were no errors before I upgraded G-Helper from the August 2025 version to the latest 0.239.0 a few days ago.
I'll try downgrading the app and see if anything changes.

[seerge]

@frps hello. I don't think it's related.

Modes don't "switch" by themselves :) it's a specific firmware handled action that completely disables or enables GPU.

It is likely some underlying driver / hardware issue with Intel iGPU in your case since you have dGPU completely disabled. I would suggest to do a clean intel driver reinstall using DDU as windows might have updated something there.

In the link you post on reddit - it's not even Asus device there :)

[frps]

Hi Seerge, thank you for your reply.

Modes don't "switch" by themselves

That's just a guess, since Standard mode was active after the post-error reboot

it's not even Asus device there

Indeed. But it might be video card switching problem, intel/nvidia and not related to specific mobo.

System updates are currently paused. The system had not been updated for at least a month prior to the error, and no driver changes were made during that time.
Firefox may have updated automatically. It was running during both BSOD incidents, and video playback (hardware decoding) was active shortly beforehand.

For now, I’ve rolled back to 0.222 and will report back after a week or after the first BSOD — whichever comes first.

If the BSOD occurs with the older version, I will follow your recommendations. For now, I would like to test without modifying the drivers, specifically to determine whether the issue disappears when the hardware is managed by the older version of G-Helper.