Cannot profile A100 on Windows with Nsight Systems

Developer Tools Nsight Systems Profiling x86 Windows Targets
1

OS: Windows Server 2022 21H2
Device and driver info:

+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 560.94                 Driver Version: 560.94         CUDA Version: 12.6     |
|-----------------------------------------+------------------------+----------------------+
| GPU  Name                  Driver-Model | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA A100 80GB PCIe        TCC   |   00000000:00:0C.0 Off |                    0 |
| N/A   38C    P0             44W /  300W |      10MiB /  81920MiB |      0%      Default |
|                                         |                        |             Disabled |

Nsight System 2025.2.1
CUDA SDK: 12.5.1
Commands used for profiling:

nsys.exe profile --trace=cuda,nvtx ./cuda_prog.exe

The program unexpectedly terminates when being profiled by nsight system.
When not profiled, the program runs normally.
The generated report file cannot be opened by nsight system GUI.
report1 (1).zip (2.2 MB)

On my other windows machine with A4000 GPU, nsight system can profile the program without issue.

2

@dofek can you take a look at this.

3

Hi @apt-init2020 , I can open the report file with the upcoming new Nsight Systems release 2025.3.1 (scheduled to be released shortly).
As for the target application crash, can you please activate the Nsight Systems log, reproduce the crash and upload the log file? Instructions below.

  1. Please copy the file C:\Program Files\NVIDIA Corporation\Nsight Systems 2025.2.1\host-windows-x64\nvlog.config.template to the folder where your target application is located and rename the new file to “nvlog.config”.
  2. Edit line 11 in the file to direct the output log file to a folder of your choice, e.g. $ c:\temp\nsys-ui.log
  3. Rerun nsys-ui and trace your application.
  4. A log file named nsys-ui.log should appear in the output folder that you specified in step 2 above. Please upload this file or send it to devtools-support@nvidia.com if you’re uncomfortable loading the file to this forum.