Shader Debugger Configuration Fails with Two Dedicated NVIDIA GPUs (RTX 4060 + RTX 5060 Ti, No Integrated GPU)

Hi everyone,

I’m encountering an issue with Nsight Graphics (tested with versions 2025.3 and older version, not sure which ones exactly) on my Windows 10 Pro 10.0.19045 offline system. I have two dedicated NVIDIA GPUs installed:

  • GeForce RTX 4060
  • GeForce RTX 5060 Ti

Both GPUs are recognized correctly by the system and seem to work fine generaly. I have the latest NVIDIA Studio Driver 576.52 installed.

However, when I try to use the Shader Debugger in Nsight Graphics, it attempts to configure for both GPUs and reports enabling mshybrid mode for both cards. From what I understand, mshybrid is typically associated with systems that have an integrated GPU (iGPU) alongside a dedicated one (dGPU), for power-saving purposes. My system does not have an integrated GPU. If I try the configuration anyway (as the only other option is to cancel completely), it fails with the message “Failed to configure target for shader debugging.” I guess it cannot enable mshybrid mode.

According to the Nsight Graphics documentation, the Shader Debugger should support systems with two dedicated NVIDIA GPUs, and there’s even an example in the documentation that uses this configuration as a stated as being a correct setup. I also reached out to NVIDIA email support before, when I was testing with a 4060 + older AMD card (which understandably didn’t work), and they specifically recommended using two NVIDIA GTX/RTX cards that work on the latest drivers. This led me to get the 5060 Ti, where I am now hung on this problem.

Has anyone successfully used the Shader Debugger in Nsight Graphics with a dual NVIDIA GPU setup without an integrated GPU involved? Could this be a bug or a configuration issue?
Any help, insights, or suggestions would be greatly appreciated.

Thanks in advance!

Hi dinopron,

Thanks for the question about the shader debugger. Sorry for the confusion, but we do use MSHybrid in order to accomplish debugging on a local system. In this case, one of your discrete GPUs is taking the place of the integrated GPU. Note that when you get this set up, the one you want to run your application on needs to have the monitor unplugged from it, which will have it function like a true dGPU in a laptop. Only have a monitor plugged into the GPU that will run the Nsight Graphics host.

Jeff@NVIDIA

Hi Jeff,

thank you for the reply. I have two monitors connected, both to the RTX 4060. So no monitors are connected to the RTX 5060 Ti.

However, I cannot even start the Shader Debugger. It fails already on trying the configuration. This is what it stated beforehand:

"The following settings will be configured:
- Enable MsHybrid on the following adapters: NVIDIA GeForce RTX 4060 (host) and NVIDIA GeForce RTX 5060 Ti (target).

Would you like us to configure your system?"

If I click on Yes to start the configuration, it fails with the message:

“Failed to configure target for shader debugging.”

So it seems to me that it fails to enable MsHybrid mode. I guess because my system does not have an integrated GPU installed, which apparently is needed to set this mode to be enabled. Is there a way to do this manually? How is Nsight Graphics querying this mode?

If it helps, I use a “Dell Precision 5820 Tower X-Series”.

Thank you very much!

Hi dinopron,

OK, so my next question would be: are you running as Administrator? We have to make modifications to the registry and require admin privs in order to do that.

Jeff@NVIDIA

Hi Jeff,

thanks for the reply. Yes I am running as administrator. So this is also not the problem. I think it is related to the msHybrid mode as it is what it wants to configure before failing the configuration.

If I do not, I get a completely different error message (a note that I need to run as administrator).

Is there any information about how msHybrid is configured? Maybe I can do these steps manually and see where it fails.

The error message from Nsight Graphics does not contain any information about why it failed.

I finally solved it, so if other people might have the same issue:

I changed the CPU/Mainboard. So it seems it is just not compatible with this “Dell Precision 5820 Tower X-Series (LGA 2066 Socket)” hardware.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.