NSight graphics on capturing OpenGL4 (frame debug or profile)

Run into an issue.
Windows 10.0.17763.557, driver 430.86, 2080T, OpenGL 4.5 context.

Crash indeed happens in the application, but not in the application module. Applications performs normally until you try to use the capture functionality. Got the stack trace by connecting to the process from VS after Nsight launched it. No symbols, just addresses ;)

Project is using GL4.5 (simple prototype) . Start up Nsight Graphics, launch (frame debugging), working directory is specified, bring up the HUD, press space (or click capture in Nsight)

Exception thrown at 0x00007FFEDC152488 (Nvda.Graphics.Interception.dll) in tech2.exe: 0xC0000005: Access violation reading location 0x0000000000000000.

Nvda.Graphics.Interception.dll!00007ffedc152488() Unknown
Nvda.Graphics.Interception.dll!00007ffedc42c618() Unknown
Nvda.Graphics.Interception.dll!00007ffedd0a5481() Unknown
Nvda.Graphics.Interception.dll!00007ffedd0a300d() Unknown
Nvda.Graphics.Interception.dll!00007ffedce16234() Unknown
Nvda.Graphics.Interception.dll!00007ffedce7598f() Unknown
Nvda.Graphics.Interception.dll!00007ffedce75c4d() Unknown
Nvda.Graphics.Interception.dll!00007ffedce760a5() Unknown
Nvda.Graphics.Interception.dll!00007ffedce75eef() Unknown
Nvda.Graphics.Interception.dll!00007ffedd6c1ab3() Unknown
Nvda.Graphics.Interception.dll!00007ffedd78461c() Unknown
kernel32.dll!00007fff3ccd7974() Unknown
ntdll.dll!00007fff3ce2a271() Unknown

Windows event log entry:

Faulting application name: tech2.exe, version:, time stamp: 0x5d06f9f4
Faulting module name: Nvda.Graphics.Interception.dll, version: 2019.3.0.0, time stamp: 0x5cddc4cb
Exception code: 0xc0000005
Fault offset: 0x0000000000d72488
Faulting process ID: 0x8e8
Faulting application start time: 0x01d524d82c3425ec
Faulting application path: D:\dev\tech2\x64\ProfilingNS\tech2.exe
Faulting module path: C:\Program Files\NVIDIA Corporation\Nsight Graphics 2019.3.0\target\windows-desktop-nomad-x64\Nvda.Graphics.Interception.dll
Report ID: 42f3bbbe-06af-422a-a260-280e48062963
Faulting package full name:
Faulting package-relative application ID:

Let me know if i can assist more. I can make the binary and/or source available if needed.

Hi Tom,

Sorry that you are running into this issue! Looking at the trace, nothing particularly stands out.

If you were able to provide a binary and/or source, that would be extremely helpful to getting a solid repro!


No problem. How can i provide a binary package? I am working on a 64k demo (WIP), so the source will be eventually published, but i don’t want to make it available for the general public. I can invite you to my private bitbucket repo.

Or i can upload it to google drive & share privately - or if post attachments here can be private?

Hi Tom,

Your best bet would to be to put it on your private google drive or dropbox and send me a link over private message.


I am preparing it.

Message sent - with a video. Not hard to reproduce, its 10/10 on W10 & 445.75 and NSight Graphics 2020.2 (and the visual studio edition even crashes VS 2019 16.5)

Also added a VS dump. @sschneider

Update? I can forward the repro, crash dump and test case to someone else if needed.

Is anyone looking at this? I’ve sent a repro, a minidump, even video on youtube on how to repro it.

Hi tomz5rpy – we just released 2020.3, and within this release and within this release we did process the minidump crashes we saw in 2020.2 and solved as many of them as proved conclusive. I’d suggest trying again with 2020.3. If that release does not work, I would suggest sending another minidump and please include your contact information if you do so that we can contact you directly to discuss it more.

No problem, thanks for coming back. It happens with 2020.3 too. I will reproduce and upload the artifacts tomorrow (I am in the UK).

I’ve uploaded a new dmp, Rar compressed DMP

Maybe you should close this as User == 1D10T. I did not notice that the nvtx headers have changed, after updating them and recompiling the crash went away.

I don’t remember reading this in the release notes, though. Maybe i was not reading the right docs?

I’m glad to hear that you were able to find a cause for the issue, especially as the crash dump you offered didn’t show anything particularly conclusive, likely coming from some corruption that might have happened.

Regarding the NVTX changes – which version had you been using previously? I don’t know of any specific NVTX changes other than v3 becoming header only whereas v2 was library based, but I could be missing a detail.

I think the code still had the old v2 libs - well before nsight graphics came out.

Can’t say more at the moment that it works - visual studio crashes the moment i click the timeline view. Different bug, apparently.

And nsight graphics does not seem to have a mode that displays nvtx events alongside gpu ones for multiple frames (for OpenGL). Seems to work with nsight systems, but the times are suspicious. I will investigate and open a different topic if necessary.

Best, T.