I’ve been using Nsight on a laptop with an RTX 4080 laptop GPU, testing it with the HelloTriangle example (an official Microsoft sample). The Frame Debugger launches successfully; however, when I switch to GPU Trace Profiler, the process gets stuck at the “Tracing” stage without generating any results. All Nsight settings are left at their default values. I’ve updated the GPU drivers and Windows 11, but this didn’t resolve the issue. Could someone help me identify what might be causing this problem ? Thank you
*I can launch both Frame debugger and GPU trace profiler successfully with the same example on RTX 3070 Ti laptop GPU.
Thank you for using Nsight Graphics and providing your feedback. I just tried the similar process as yours, but I can do Frame Debugger and GPUTrace as expected on D3D12HelloTriangle sample.
Could you try these?
Update your driver to latest
Make sure you already have the privilege to get the access to the GPU performance counters
Open your driver’s control panel, enable Enable Developer Settings under 'Desktop` menu
Change the options under Developer → Manage GPU Performance Counters.
Thank you for your reply. My current GPU driver version is 561.09 (the latest available on NVIDIA’s website), and the Developer Settings are enabled. Unfortunately, the GPU Trace still gets stuck at the “Tracing” stage.
Additionally, I’ve noticed that after pressing F11, the D3D12HelloTriangle.exe begins allocating a large amount of memory before crashing (note that the HelloTriangle source code is unmodified). This issue has not occurred on other devices. I hope this information is helpful in diagnosing the problem. Thank you !
That’s weird, the sys memory will also increase in my machine, but it will decrease back to original level, and it will not increase to such high value. My peak sys mem is ~300M, and yours is ~9G, maybe you meet some kind of Out of memory issue.
It’s hard for me to say anything right now. Are you using release build or debug build (just take some try, both release and debug build work fine in my side), is this reproduce-able on another machine?
In fact, I’ve only encountered this issue on this laptop with the 4080 GPU, while all other devices work fine.
The good news is that I tried resetting the laptop (reinstalling Windows and all other programs), and now GPU Trace is functioning properly (although the exact cause of the issue is still unclear…).
I sincerely appreciate your assistance and the time you’ve taken to respond !
