Hello. I’m getting warning message when launching GPU trace.
ID,Origin,Source,Message
1,Target,GPU Trace,Ignoring non-NVIDIA adapter ‘NVIDIA GeForce RTX 3060’
And as a result data collection is not available.
I tried installing different driver version, but the problem is the same.
Note: GPU frame capture is working. Profiler permission is enabled for all users in NVIDIIA control panel. Nsight Graphics version is 2025.2.0
Which OS and nvidia driver are you on and which graphics API is the app using ?
OS: Windows 10 Pro 22H2 19045.5854
API: DX12
NVIDIA driver version: 576.52
Also I noticed that profiling in Nsight System doesn’t work. Error message:
An error occurred. C:\dvs\p4\build\sw\devtools\Agora\Rel\QuadD_Main\QuadD\Target\Daemon\EventSource\NvApiEventHandler.cpp(105): Throw in function bool __cdecl QuadDDaemon::EventSource::NvApiEventHandler::Serialize(const class FlatData::ConstObject &,class QuadDCommon::StrongType,class QuadDCommon::ProcessIdTag>,class FlatData::StringSerializer &,enum QuadDCommon::FlatComm::Nvtx::EventType,unsigned __int64,unsigned __int64,unsigned int,unsigned __int64,unsigned __int64,unsigned __int64,const class std::basic_string,class std::allocator > &) Dynamic exception type: struct boost::wrapexcept std::exception::what: InternalErrorException [struct QuadDCommon::tag_message * __ptr64] = Cannot find GPU by LUID: 4afc4, sub-device id
If this error persists, please restart the app and/or reboot the target.
Version information: NVIDIA Nsight Systems, 2025.3.1.90-253135822126v0 Windows-x64
Hi e.konks,
Please post the issue on the topic of ‘Nsight System’ for your ‘Nsight System’ related issue.
Did you also send a feedback email about this similar issue? Let us keep the topic here for not fork the thread.
Thanks
An
Yes, I sent a feedback email in both apps NVIDIA Graphics and NVIDIA Systems.
I tried clean driver reinstalling as you suggested in the email reply, but the problem still persists.
Well, I found a workaround. GPU trace works for cpp generated capture of the frame.
Hi e.konks,
That looks like sample specific issue, GPUTrace works on cpp generated capture but not the original native app.
Could you share your app to us for some inhouse reproduce?
Thanks
An
I don’t have a clear answer for this, but I have seen something similar recently, due (in my case) to the d3d12 runtime enumerating the adapter twice, with 2 different LUIDs, when the driver itself only lists the adapter once to the runtime.
Can you share the output of the DirectX Caps Viewer (the DXGI Devices node)? GitHub - microsoft/DxCapsViewer: DirectX Capabilities Viewer utility (dxcapsviewer.exe)
That tool presents all the devices the D3D12 runtime enumerates to the application. Is the nvidia adapter showing twice?
If it does list twice, can you modify your app to pick “the other one” and report if that solves the issue?
I believe the GPUs the nvidia driver enumerates are listed in the registry at Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DirectX
and in my case, I only see one entry for the nvidia adapter.
(I haven’t fully understood why it’s being enumerated twice by the runtime when it’s a single adapter yet, though it may be due to having multiple adapters on the system + accessing the system through remote desktop).
Yes, I have 3 devices in the “DXGI 1.1 Devices” tree. I also have 6 registry entries corresponding to RTX3060 (although 4 of them have AdapterLuid=0).
There is only one adapter on the system. Although I do change it occasionally. This started after I switched to an NVIDIA card after coming back from an AMD card. And I use RDP to connect to the computer.
EnumAdapterByGpuPreference gives me 4 adapters in descending order of performance, 3 NVIDIA and Microsoft Basic Render Driver. The first NVIDIA adapter, which is the default, does not work in GPU Trace. The other NVIDIA adapter works, so I can do profiling if the second adapter is explicitly specified.
Thanks for the help!
DirectX Caps Viewer (3.0 MB)