Skip to content

Troubleshooting

Jump to bottom
Serge edited this page May 22, 2024 · 11 revisions

NOTE: This section is not related to G-Helper anyhow, but since people often come to this repository asking about general problems with their laptops I have listed the most frequent troubleshooting advice that I can give.

Hardware reset / CMOS reset

Most of Asus laptops have an option to do a hardware reset that can be handy sometimes. It doesn't touch your data, but resets all main hardware-related things (enables your dGPU, wakes up wifi/bt adapter if it has hanged for some reason, etc.).

  1. Turn OFF laptop
  2. Press and hold the "power" button for 30-40 seconds
  3. Then boot normally (it will take a bit longer to boot)

Reinstalling Asus System Control Interface

This "driver" is needed for both G-Helper and Armoury to work. If it's installation is damaged by some reason, you can try to reinstall it.

  1. Open Windows Device Manager
  2. Right click on System Devices -> ASUS System Control Interface v3
  3. Click Uninstall Device and check Attempt to remove driver
  4. Download latest Asus System Control Interface from Asus website, and install normally

Resetting windows power plan to defaults

Copy and paste the command below into Windows Terminal or Powershell as Admininstrator. Avoid adding extra spaces in the end!

powercfg -restoredefaultschemes

Reinstalling GPU drivers

  • For AMD devices (including ones who use integrated graphics) you can use AMD official cleanup utility to completely uninstall existing drivers from safe mode. After that you can download and install latest official drivers from AMD website

  • For NVidia / Intel devices you can use the Display Driver Uninstaller app to completely uninstall existing drivers. After that you can download and install latest official drivers from Nvidia website

Repair corrupted system files

Run following commands in Windows Terminal or Powershell as Admininstrator

DISM.exe /Online /Cleanup-image /Restorehealth
sfc /scannow

Rebuilding WMI repository

If application refuses to run at all, it could be that you have corrupt WMI in Windows. You may do following steps in order to rebuild it.

  1. Click Start -> Type CMD -> Right click on CMD from the result -> Click Run as Administrator
  2. Type the command ‘net stop winmgmt’ and press enter
  3. Leave the command prompt open and click Start and type system32 -> Open the folder system32 from the result pane
  4. From the system32 folder open Wbem and look for the folder Repository
  5. Right click on Repository and click rename
  6. Change the folder name from Repository to Repository.old
  7. Switch back to command prompt and type net start winmgmt and hit enter to execute
  8. Close all the windows and reboot the computer and now try opening the system information
Clone this wiki locally