Debugging OpenGL program, only crashes on win10 fall creators update
Specs and versions: GTX1060 I3-6100 Nvidia Driver: 388.31 Updated Nsight Problem: When launching the graphic debugging to debug an external program (openGL) which crashes. I'm not sure if it's a problem with the application (it seems to be program specific) but I would like some clarification to what's exactly wrong or to hear if someone else is experiencing this. Also, if my stack trace guess is to be believed, KiUserExceptionDispatcher could be the problem here. It's a known compatibility issue with this program and the Windows 10 fall creators update. Inform me when I missed some information, thanks! Logs (monitor and host): Monitor log: [url]https://pastebin.com/ciHdjUyR[/url] VSIP/Host log: [url]https://pastebin.com/49ujGd6U[/url] Thanks for looking into this, hopefully there's a solution.
Specs and versions:
GTX1060
I3-6100
Nvidia Driver: 388.31
Updated Nsight

Problem:
When launching the graphic debugging to debug an external program (openGL) which crashes. I'm not sure if it's a problem with the application (it seems to be program specific) but I would like some clarification to what's exactly wrong or to hear if someone else is experiencing this. Also, if my stack trace guess is to be believed, KiUserExceptionDispatcher could be the problem here. It's a known compatibility issue with this program and the Windows 10 fall creators update. Inform me when I missed some information, thanks!

Logs (monitor and host):
Monitor log: https://pastebin.com/ciHdjUyR
VSIP/Host log: https://pastebin.com/49ujGd6U

Thanks for looking into this, hopefully there's a solution.

#1
Posted 11/19/2017 04:15 PM   
Hi, I'm sorry for the problem you met, can you please provide more information? - OS, Visual Studio, Nsight version - Did the issue happen when started graphics debugging or performance analysis? - Did the issue only happen with the specific sample? If it is, can we have your sample please? - The steps to reproduced the issue. Thanks, Letitia
Hi,

I'm sorry for the problem you met, can you please provide more information?
- OS, Visual Studio, Nsight version
- Did the issue happen when started graphics debugging or performance analysis?
- Did the issue only happen with the specific sample? If it is, can we have your sample please?
- The steps to reproduced the issue.

Thanks,
Letitia

#2
Posted 11/20/2017 03:53 AM   
I'm also experiencing crashes on Win10 fall creators update. Both VS2015 and VS2017 are affected. This happens on a Dell Precision M4800 with Quadro K2100M (dGPU only, it's a QHD+ config) I've managed to extract some relevant information: The crash occurs inside Nvda.Graphics.Interception.dll when any of the intercepted functions GetExtensionsStringARB or GetExtensionsStringEXT are called by pointers (other functions might be affected as well). Stack trace: https://pastebin.com/fzMsJQPs Any sample program from the GLFW project ('boing' in this case) crashes in the same way Regards, Sergey
I'm also experiencing crashes on Win10 fall creators update. Both VS2015 and VS2017 are affected.

This happens on a Dell Precision M4800 with Quadro K2100M (dGPU only, it's a QHD+ config)

I've managed to extract some relevant information:
The crash occurs inside Nvda.Graphics.Interception.dll when any of the intercepted functions GetExtensionsStringARB or GetExtensionsStringEXT are called by pointers (other functions might be affected as well).

Stack trace: https://pastebin.com/fzMsJQPs

Any sample program from the GLFW project ('boing' in this case) crashes in the same way

Regards,
Sergey

#3
Posted 11/22/2017 06:37 PM   
Hi sergey1980, I'm sorry for the problem you met, can you provide more information please? - Was the OS Win10 x64 RS4? - Can we have your sample please? or tell us how to get the samples. - the steps to reproduce the issue. Thanks, Letitia
Hi sergey1980,

I'm sorry for the problem you met, can you provide more information please?
- Was the OS Win10 x64 RS4?
- Can we have your sample please? or tell us how to get the samples.
- the steps to reproduce the issue.

Thanks,
Letitia

#4
Posted 11/23/2017 03:41 AM   
Thanks for responding everyone. I can't really provide a sample as it's an external program and I don't have the source code for it. The sample that sergey1980 is referring can be found here: [url]https://github.com/glfw/glfw/tree/master/examples[/url]. I'm glad that there's another program/sample is affected. I can confirm that I can graphically debug it on Windows 10 [b]non[/b] fall creator's update. I used the newest cmake and Visual Studio Version 15.4.3 aka 2017. My windows 10 [b]non[/b] fall creator's update OS is Windows 10 OS Version 10.0.15063 Build 15063. I'm using the latest Nsight (5.4) on this system. I can't currently test it on my other machines due to reasons. Geforce drivers are also updated to V. 388.31. Use cmake to get project files, opened boing.vcxproj, build the project, ran the exe with Nsight [b]externally[/b] debugging the project, so only used the compiled exe. I've provided an exe in the attachments so you can skip the building part. Tell me if I need to provide more information, I'd gladly provide it.
Thanks for responding everyone. I can't really provide a sample as it's an external program and I don't have the source code for it. The sample that sergey1980 is referring can be found here:
https://github.com/glfw/glfw/tree/master/examples. I'm glad that there's another program/sample is affected. I can confirm that I can graphically debug it on Windows 10 non fall creator's update. I used the newest cmake and Visual Studio Version 15.4.3 aka 2017. My windows 10 non fall creator's update OS is Windows 10 OS Version 10.0.15063 Build 15063. I'm using the latest Nsight (5.4) on this system. I can't currently test it on my other machines due to reasons. Geforce drivers are also updated to V. 388.31.

Use cmake to get project files, opened boing.vcxproj, build the project, ran the exe with Nsight externally debugging the project, so only used the compiled exe. I've provided an exe in the attachments so you can skip the building part.

Tell me if I need to provide more information, I'd gladly provide it.
Attachments

boing.7z

#5
Posted 11/23/2017 11:35 AM   
Hi Crementif, I tested the sample - the attached sample with an internal nsight build, the configuration as below: - Visual Studio 2017 - bothe win10 15063 RS2 and win10 16299 RS3 - driver 388.30 the sample ran smoothly with nsight, no crash. BTW, after the sample was launched with nsight, it showed error message if pressed ctrl+z+space to capture the frame, for some APIs are unsupported. please click the menu nsight->pause and capture frame, click "OK" button on the popped window, then the frame was captured. But if you still met the problem, please wait for the release build and check it again. Regards, Letitia
Hi Crementif,

I tested the sample - the attached sample with an internal nsight build, the configuration as below:
- Visual Studio 2017
- bothe win10 15063 RS2 and win10 16299 RS3
- driver 388.30

the sample ran smoothly with nsight, no crash.
BTW, after the sample was launched with nsight, it showed error message if pressed ctrl+z+space to capture the frame, for some APIs are unsupported. please click the menu nsight->pause and capture frame, click "OK" button on the popped window, then the frame was captured.

But if you still met the problem, please wait for the release build and check it again.

Regards,
Letitia

#6
Posted 11/24/2017 03:22 AM   
Letitia, Thanks for the answer, In my case it was Windows 10 1709 RS3 with the latest updates, NSight 5.4.0.17240 and Quadro drivers 385.12 and 385.90. Rolling Windows back to RS2 has fixed the problem.
Letitia,

Thanks for the answer,

In my case it was Windows 10 1709 RS3 with the latest updates, NSight 5.4.0.17240 and Quadro drivers 385.12 and 385.90.
Rolling Windows back to RS2 has fixed the problem.

#7
Posted 11/24/2017 02:22 PM   
Hi, I'm glad that the problem is fixed after rolling back to WIN10 RS2. Please wait for the release build which might support WIN10 RS3. Thanks, Letitia
Hi,

I'm glad that the problem is fixed after rolling back to WIN10 RS2.
Please wait for the release build which might support WIN10 RS3.

Thanks,
Letitia

#8
Posted 11/27/2017 03:07 AM   
I can confirm that the changes suggested above (Rolling back to Win10 RS2) fixed the issue for me. One caveat is that I had to reinstall nsight for it to have it working.
I can confirm that the changes suggested above (Rolling back to Win10 RS2) fixed the issue for me.
One caveat is that I had to reinstall nsight for it to have it working.

#9
Posted 11/29/2017 08:01 AM   
Im having this exact problem. After fall creators update cant start graphics debugging. I use the nsight menu "start graphics debugging" it connects to localhost, shows a console window associated with my opengl windows program and then throws up an nsight crash dialog to file a report. NSight 5.4 (5.4.0.17240) Driver 388.31 Visual Studio 2015 and 2017 Windows Version 1709 (Build 16299.125)
Im having this exact problem. After fall creators update cant start graphics debugging.
I use the nsight menu "start graphics debugging" it connects to localhost, shows a console window associated with my opengl windows program and then throws up an nsight crash dialog to file a report.

NSight 5.4 (5.4.0.17240)
Driver 388.31
Visual Studio 2015 and 2017
Windows Version 1709 (Build 16299.125)

#10
Posted 12/17/2017 05:05 AM   
Hi NumberXaero, I'm sorry for the problem you met. Did the issue also happen on WIN10 RS2 platform? Thanks, Letitia
Hi NumberXaero,

I'm sorry for the problem you met.
Did the issue also happen on WIN10 RS2 platform?

Thanks,
Letitia

#11
Posted 12/18/2017 03:17 AM   
I cant roll back to confirm, but before the fall creators update would be around the last time I remember using it without a crash.
I cant roll back to confirm, but before the fall creators update would be around the last time I remember using it without a crash.

#12
Posted 12/18/2017 05:42 AM   
Hi NumberXaero, Please wait for the release build which might support WIN10 RS3 platform and then check it again. Nsight 5.4 doesn't support WIN10 RS3 platform. Regards, Letitia
Hi NumberXaero,

Please wait for the release build which might support WIN10 RS3 platform and then check it again.
Nsight 5.4 doesn't support WIN10 RS3 platform.

Regards,
Letitia

#13
Posted 12/18/2017 05:56 AM   
"Nsight 5.4 doesn't support WIN10 RS2 platform." You mean RS3?
"Nsight 5.4 doesn't support WIN10 RS2 platform."

You mean RS3?

#14
Posted 12/18/2017 09:45 AM   
Hi NumberXaero, Nsight 5.4 doesn't support WIN10 RS3 platform. sorry for my mistake. Regards, Letitia
Hi NumberXaero,

Nsight 5.4 doesn't support WIN10 RS3 platform.
sorry for my mistake.

Regards,
Letitia

#15
Posted 12/18/2017 09:48 AM   
Scroll To Top

Add Reply