Nsight 3.0 local shader debugging causes the application and the graphics driver to crash when hitti

I am using Nsight 3.0 (build 3.0.0.13027) with Visual Studio 2010, GeForce GTX 680 (driver version 310.90), Windows 7 64 bits, DX11 Debug Layer is Application Controlled. I am using the release candidate version because it allows shader debugging locally with a single GPU.

The strange error I get is that, for some shaders, not all, whenever a breakpoint is hit, the application I am debugging and the graphics card driver crash

Error message from the app I am debugging: “ has stopped working”

Error message from the graphics card driver: “Display driver stopped responding and has recovered - Display driver NVIDIA Windows Kernel Model Driver, Version 310.90 stoped responding and has successfully recovered”

All shaders are compiled the same way, no warning when compiling, they work when running (well, except for the bugs I am trying to correct).

Any ideas would be appreciated.

Hi, tiago

The RC2 was just posted. Would you please try the new version and make sure to update your driver to 314.07 or later?

If issues persist, let us know.

Thanks.

Hi Xuan,

just installed Nsight RC2 and the latest nVidia driver (314.22), and now my application crashes every time I try to start a graphics debug session.

Going back to the RC1 for now…

If it helps, this is the error I get:

Problem signature:
Problem Event Name: APPCRASH
Application Name: DX11GIRenderer.exe
Application Version: 0.0.0.0
Application Timestamp: 515257ec
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7600.16915
Fault Module Timestamp: 4ec4b137
Exception Code: c0000005
Exception Offset: 00000000000515b0
OS Version: 6.1.7600.2.0.0.256.4
Locale ID: 1041
Additional Information 1: f2e7
Additional Information 2: f2e77f8da5c3f4feae19bfdbdca37193
Additional Information 3: 2567
Additional Information 4: 2567d19d540a489fc6cc5e92a8d082a1

Nsight 3.0 (final version) did the trick :)