Nsight graphics crash on start

Hi,

Nsight crashes on start. It looks like there is something wrong with configuration but I don’t what. It doesn’t matter if I check autoconnect or not. It crashes on three different machines (all use 1070). Drivers are up-to-date. Dmp shows 0xC06D007E: Module not found (parameters: 0x000000D4CA4CF720) exception, but I don’t see which module it is. Callstack below:

KERNELBASE.dll!RaiseException() Unknown
Nomad.Injection.dll!00007ffe0a0f57ec() Unknown
Nvda.Graphics.Interception.dll!00007ffd98f9f2ab() Unknown
WW3-Win64-Shipping.exe!00007ff79df0fb70() Unknown

Best Regards,
Pawel

Hi Pawel,

Sorry for the late reply and sorry about this issue!

Could you potentially send us your crash dump? We could resolve the symbols and see what is going on.

Also, what OS and driver version? Additionally, could you try Nsight Graphics 2019.3 that shipped yesterday?

Thanks!
Seth

Seth,

Thank you for reply.
Checked with 2019.3 and I still see the issue. It is Windows 10, Driver 430.86. Dmp included.

Best Regards,
Pawel
7b082c90-eb03-4bba-9e24-e8205dd1ea56.7z (12.9 KB)

Thanks for the crash dmp! We will take a look and see if there is a smoking gun. If not, we may need the application you are trying to analyze to get a full repro.

Thanks,
Seth

Hello,

We took a look at the crash dump and it looks like the crash is in your application. Is the app crashing without Nsight attached?

Thanks,
Seth

This link may also be of some help: https://docs.nvidia.com/nsight-graphics/UserGuide/index.html#troubleshooting_debugging_your_application_with_a_debugger

Seth,

Thank for looking in it.
It doesn’t crash without Nsight and what is interesting NSight shows crash dmp window but game moves forward and start without any problems, but without NSight attached. It doesn’t matter if I autoconnect or not. On my side it looks like Nvda.Graphics.Interception.dll cause crash. Game is based on UE4 (4.19.2).

Best Regards,
Pawel

Run into the same issue.
Windows 10.0.17763.557, driver 430.86, 2080TI.

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: 0.0.0.0, 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.

Hey Pacu2y5n,

Based on that Unreal Engine Version, it’s probably the heartbeat thread causing the issue.

Can you try running your game with the option “-noheartbeatthread”

Let me know if the app still crashes after that!

Thanks,
Seth

Hi Tomz5rpy,

This looks like it might be a different issue than Pacu2y5n’s.

Would you mind creating a separate thread? (our admin tools are a bit limited on this platform)

Thanks!
Seth

Done.

Seth,

I am sorry for late response, but we were overwhelmed by prep for free week on Steam. Noheartbeatthread switch solved problem. Thank you!!!

Best regards,
Pawel

Great to hear Pawel! Good luck with free week on steam!