Nitro Sense Breaks After Reboot with MSI Afterburner/RTSS Installed in Nitro AN14-41

Options
Fliksyy
Fliksyy Member Posts: 2 New User
edited July 15 in Nitro Gaming

I decided to download MSI Afterburner and RTSS to benchmark my laptop, and it worked great.

However, after I rebooted my computer, NitroSense stopped working completely. It launches, but the window is blank. It shows no temps, no system info, and gives me no way to change performance modes or fan speeds. My laptop is now permanently stuck in the last mode I used (Turbo Mode with max fans).

I correctly suspected MSI Afterburner was the cause. Here's what I did to confirm:

  1. I uninstalled NitroSense completely using Revo Uninstaller.
  2. I rebooted the laptop.
  3. I reinstalled a fresh version of NitroSense and rebooted again.
  4. At this point, NitroSense worked perfectly, even after a reboot.
  5. Then, I opened MSI Afterburner and RTSS. NitroSense still worked.
  6. The moment of truth: I rebooted the laptop with Afterburner and RTSS having been run.
  7. The problem returned immediately. NitroSense was blank and non-functional again.

So, the conflict is definitely caused by running MSI Afterburner and RTSS. If I never start them, NitroSense survives a reboot just fine.

My question is: Why does this happen? Why do these specific programs conflict with NitroSense after a system restart, and is there a known way to configure them to work together?

Thanks for any help!

image.png

[Edited the thread to add model number to the title]

Answers

  • Fliksyy
    Fliksyy Member Posts: 2 New User

    also my laptop model is an14 41

  • Puraw
    Puraw ACE, Member Posts: 17,962 Trailblazer

    Hi, interesting how NitroSense breaks only after RTSS runs and the system reboots. Seems more like an EC-state or overlay polling conflict than anything ‘permanent.’ Might be worth reviewing boot injection sequences or embedded controller handshakes—especially since it’s reproducible without touching the hardware.

    Tools like RTSS might be interfering with initialization timings or polling queues that NitroSense relies on during startup. Would be curious to see what the EC logs show, assuming Acer ever made them readable.

  • magis
    magis Member Posts: 1 New User

    Yep, this is a known conflict ⚠️ MSI Afterburner/RTSS can interfere with NitroSense's sensors and overlays, especially after a reboot. Try disabling RTSS auto-start or use Afterburner without hardware monitoring. No perfect fix yet, just some trial and error 😅