I believe what is going on here is that you have hit a known issue with the way Nsight Systems does time synchronization. A workaround is given in the documentation known issues as we work on a fix:
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Nsys doesn't show cuda kernel and memory data | 10 | 175 | December 7, 2024 | |
| 'osrt_sum' stats report no data available | 4 | 236 | June 25, 2024 | |
| Sqlite does not contain CUDA kernel data | 12 | 3633 | April 28, 2023 | |
| [QuadDCommon::tag_message*] = No GPU associated to the given UUID | 24 | 952 | November 5, 2024 | |
| Nsight-system can't recognize the conda enviroment when profile the application | 4 | 1153 | March 2, 2023 | |
| Nsys is not collecting kernel data | 31 | 7512 | March 14, 2025 | |
| Profiling using Nsight compute CLI python script with Cupy | 3 | 2542 | July 13, 2023 | |
| Generating CUPTI_* tables with nsys | 25 | 1678 | January 12, 2023 | |
| Profiling Python code using sudo | 8 | 2153 | March 10, 2022 | |
| Nsight Systems does not collect CUDA events | 21 | 9093 | January 11, 2023 |