Nsight 5.4 fails to Start Graphics Debugging

Developer Tools Nsight Visual Studio Edition
1

This is the message I am getting:

Attaching the Graphics Debugger to process ‘blah.exe’ on machine ‘blah_blah’ failed. Operation not supported. Unknown Error:
0x80004005

Here’s my system info:

Name Intel(R) Core™ i7-4790K CPU @ 4.00GHz
Architecture x64
Frequency 3,998 MHz
Number of Cores 8
Page Size 4,096
Total Physical Memory 32,706.00 MB
Available Physical Memory 25,371.00 MB
Hybrid Graphics Enabled False
Version Name Windows 10 Pro
Version Number 10.0.15063
Nsight Version 5.4.0.17240
Nsight Edition Standard
Visual Studio Version 14.0

GPU Devices:
Driver Version 388.13
Driver Model WDDM
CUDA Device Index 0
GPU Family GP104-A
Compute Capability 6.1
Number of SMs 20
Frame Buffer Physical Size (MB) 8192
Frame Buffer Bandwidth (GB/s) 320.32
Frame Buffer Bus Width (bits) 256
Frame Buffer Location Dedicated
Graphics Clock (Mhz) 904
Memory Clock (Mhz) 5005
Processor Clock (Mhz) 1809
RAM Type GDDR5X
Attached Monitors 2

2

Hi,

I’m sorry for the problem you met, please provide more information for investigating the problem:

  • Nsight version
  • I’m a little confused about the steps that caused the failure. Did you launch the sample without nsight, then try to attach the process with nsight? Can you please provide detailed steps about the failure?
  • Can we have your sample to repro the issue then we can identify the issue quickly?

Thanks,
Letitia

3

Hello,

I’m having the same issue.

-The version is 5.4, build number 5.4.0.17240.
-The steps are that I simply went to Nsight menu → Start graphics debugging.
-I can provide you with the whole project if necessary. But for simplicity I only link DxDiag output: [url]https://pastebin.com/FqrUKHWD[/url] . I noticed in the Diagnostics part of the text file there are few issues like this:

Windows Error Reporting:
+++ WER0 +++:
Fault bucket 129549941657, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: Nsight.Monitor.exe
P2: 5.4.0.17240
P3: 59a4cb5a
P4: Nvda.Messaging.Interop
P5: 5.4.0.17240
P6: 59a4cafb
P7: de
P8: 0
P9: System.NullReferenceException
P10:

It worked few weeks ago. Since then I think I updated Nsight, Visual studio (15.4.4) and also I’m now using a second monitor. I tried turning it off and using only the main one. The graphics debugging then worked for the first time. But next tries were unsuccessful as before.

Thanks,
Pavel

4

Hi dareback1,

I’m sorry I have no access to the DxDiag link.
Can you provide more information please?

  • OS, driver, Visual Studio info
  • Can we have your sample please?

Thanks,
letitia

5

EDIT: I found out how to attach the files directly to this post, hope you can access it now.

Ok, here is the sample: File Dropper - Online file sharing .
Visual studio version 15.4.4 as stated in previous post. I don’t know what other info about VS is relevant, so just tell me if you need any other.
I’m wondering why you cannot access the DxDiag, but whatever. I will write some info then.

Operating System: Windows 10 Education 64-bit (10.0, Build 15063) (15063.rs2_release.170317-1834)
Processor: Intel(R) Core™ i5-4570 CPU @ 3.20GHz (4 CPUs), ~3.2GHz
Memory: 16384MB RAM
Available OS Memory: 16336MB RAM
Card name: NVIDIA GeForce GTX 1060 6GB
Driver Name: C:\WINDOWS\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_2e7fa54192fe16d0\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_2e7fa54192fe16d0\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_2e7fa54192fe16d0\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_2e7fa54192fe16d0\nvldumdx.dll
Driver File Version: 23.21.0013.8813 (English)
Driver Version: 23.21.13.8813
Driver Attributes: Final Retail
Driver Date/Size: 10/27/2017 1:00:00, 945072 bytes
Driver Strong Name: oem0.inf:0f066de38c1ebff8:Section136:23.21.13.8813:pci\ven_10de&dev_1c03
Rank Of Driver: 00D12001

Diagnostics

Windows Error Reporting:
+++ WER0 +++:
Fault bucket 129549941657, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: Nsight.Monitor.exe
P2: 5.4.0.17240
P3: 59a4cb5a
P4: Nvda.Messaging.Interop
P5: 5.4.0.17240
P6: 59a4cafb
P7: de
P8: 0
P9: System.NullReferenceException
P10:

+++ WER1 +++:
Fault bucket 129549941657, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: Nsight.Monitor.exe
P2: 5.4.0.17240
P3: 59a4cb5a
P4: Nvda.Messaging.Interop
P5: 5.4.0.17240
P6: 59a4cafb
P7: de
P8: 0
P9: System.NullReferenceException
P10:

+++ WER2 +++:
Fault bucket 129549941657, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: Nsight.Monitor.exe
P2: 5.4.0.17240
P3: 59a4cb5a
P4: Nvda.Messaging.Interop
P5: 5.4.0.17240
P6: 59a4cafb
P7: de
P8: 0
P9: System.NullReferenceException
P10:

+++ WER3 +++:
Fault bucket 129549941657, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: Nsight.Monitor.exe
P2: 5.4.0.17240
P3: 59a4cb5a
P4: Nvda.Messaging.Interop
P5: 5.4.0.17240
P6: 59a4cafb
P7: de
P8: 0
P9: System.NullReferenceException
P10:

+++ WER4 +++:
Fault bucket 129549941657, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: Nsight.Monitor.exe
P2: 5.4.0.17240
P3: 59a4cb5a
P4: Nvda.Messaging.Interop
P5: 5.4.0.17240
P6: 59a4cafb
P7: de
P8: 0
P9: System.NullReferenceException
P10:

+++ WER5 +++:
Fault bucket 129549941657, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: Nsight.Monitor.exe
P2: 5.4.0.17240
P3: 59a4cb5a
P4: Nvda.Messaging.Interop
P5: 5.4.0.17240
P6: 59a4cafb
P7: de
P8: 0
P9: System.NullReferenceException
P10:

+++ WER6 +++:
Fault bucket 129549941657, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: Nsight.Monitor.exe
P2: 5.4.0.17240
P3: 59a4cb5a
P4: Nvda.Messaging.Interop
P5: 5.4.0.17240
P6: 59a4cafb
P7: de
P8: 0
P9: System.NullReferenceException
P10:

+++ WER7 +++:
Fault bucket 129549941657, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: Nsight.Monitor.exe
P2: 5.4.0.17240
P3: 59a4cb5a
P4: Nvda.Messaging.Interop
P5: 5.4.0.17240
P6: 59a4cafb
P7: de
P8: 0
P9: System.NullReferenceException
P10:

+++ WER8 +++:
Fault bucket 129549941657, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: Nsight.Monitor.exe
P2: 5.4.0.17240
P3: 59a4cb5a
P4: Nvda.Messaging.Interop
P5: 5.4.0.17240
P6: 59a4cafb
P7: de
P8: 0
P9: System.NullReferenceException
P10:

+++ WER9 +++:
Fault bucket 125730739576, type 5
Event Name: PerfWatsonVS12Data
Response: Not available
Cab Id: 0

Problem signature:
P1: PerfWatsonTcdb
P2: 0
P3: 0
P4: 0
P5: 0
P6:
P7:
P8:
P9:
P10:

DxDiag.txt (77.9 KB)
project1_test.zip (38.8 MB)

6

Hello again,

any update on the situation?

7

Hi dareback1,

Sorry for delay.
I tested your sample with an internal Nsight build on WIN10 RS2 platform, it worked fine with nsight.
Can you please update the driver to the latest version and then try it again?
If the issue still happened, please wait for the release build and then check it again.

Thanks,
Letitia

8

Hello letitia,

Today I’ve tried updating the driver, updating Nsight and reinstalling nsight. None of that worked. However, I uninstalled the 5.4 version of Nsight and installed 5.3. Now it works again. Thank you for your willingness.

Happy new year :)

9

Hi dareback1,

Please wait for the release build and then check it again. And please tell us if the issue still happened.

Thanks,
Letitia