NSight 5.4 / Visual Studio 2017 causes crashes + restart on exit
NSight QtCoreNvda.dll causes a crash when exiting VS2017 resulting in an automatic restart of VS. From windows event logs: [code] Name of faulty application: devenv.exe, version: 15.0.26730.15, time stamp: 0x59b6fbe8 Name of the faulty module: Qt5CoreNvda.dll, version: 5.7.0.0, time stamp: 0x5811baa1 Exception code: 0xc0000005 Error offset: 0x001b0cd5 ID of the faulty process: 0x3628 Start time of faulty application: 0x01d3310194d271db Path of corrupted application: C: \ Program Files (x86) \ Microsoft Visual Studio \ 2017 \ Professional \ Common7 \ IDE \ devenv.exe Path of the faulty module: C: \ Program Files (x86) \ NVIDIA Corporation \ Nsight Visual Studio Edition 5.4 \ Host \ Common \ Qt5CoreNvda.dll Reporting code: c21cc907-ed05-48dc-92cd-d49b1d62e483 Full name of the corrupted package: Application ID that is relative to the failed package: [/code] Before, the following warning is generated: [code] The NVIDIA OpenGL driver has encountered an out of memory error. This application might behave inconsistently and fail. (skipped 60 previous events of this type) [/code] HW: Razer Blade 14" / GTX1060 / driver 385.28 / Windows 10 15063.608
NSight QtCoreNvda.dll causes a crash when exiting VS2017 resulting in an automatic restart of VS.

From windows event logs:
Name of faulty application: devenv.exe, version: 15.0.26730.15, time stamp: 0x59b6fbe8
Name of the faulty module: Qt5CoreNvda.dll, version: 5.7.0.0, time stamp: 0x5811baa1
Exception code: 0xc0000005
Error offset: 0x001b0cd5
ID of the faulty process: 0x3628
Start time of faulty application: 0x01d3310194d271db
Path of corrupted application: C: \ Program Files (x86) \ Microsoft Visual Studio \ 2017 \ Professional \ Common7 \ IDE \ devenv.exe
Path of the faulty module: C: \ Program Files (x86) \ NVIDIA Corporation \ Nsight Visual Studio Edition 5.4 \ Host \ Common \ Qt5CoreNvda.dll
Reporting code: c21cc907-ed05-48dc-92cd-d49b1d62e483
Full name of the corrupted package:
Application ID that is relative to the failed package:


Before, the following warning is generated:
The NVIDIA OpenGL driver has encountered
an out of memory error. This application might
behave inconsistently and fail.
(skipped 60 previous events of this type)


HW: Razer Blade 14" / GTX1060 / driver 385.28 / Windows 10 15063.608

#1
Posted 09/19/2017 09:37 AM   
Hi, I'm sorry for the problem you met, can we have your sample to do some local repro, then we can identify the crash quickly? Thanks, Letitia
Hi,

I'm sorry for the problem you met, can we have your sample to do some local repro, then we can identify the crash quickly?

Thanks,
Letitia

#2
Posted 09/20/2017 05:48 AM   
Hi, i dont actually have to use nsight to get that crash. It's just installed/loaded lying dormant while i load and work with any of my solutions. Then after i while i close Vs and a few secs later it shows a messagebox that it crashed and will be restarted. I tried to attach windbg to devenv.exe, but it didnt catch the crash. The logs above are from windows event logging.
Hi,

i dont actually have to use nsight to get that crash. It's just installed/loaded lying dormant while i load and work with any of my solutions. Then after i while i close Vs and a few secs later it shows a messagebox that it crashed and will be restarted.
I tried to attach windbg to devenv.exe, but it didnt catch the crash. The logs above are from windows event logging.

#3
Posted 09/20/2017 05:54 AM   
I get this same issue too, with and without using nsight during my VS2017 session. I'm not sure of a reliable repro for this but I get crashes on close with this error shown in the windows event logging more than 50% of the time.
I get this same issue too, with and without using nsight during my VS2017 session. I'm not sure of a reliable repro for this but I get crashes on close with this error shown in the windows event logging more than 50% of the time.

#4
Posted 10/04/2017 05:14 AM   
Same behavior for me, happens regularly. In the most recent case, I opened a VS2017 solution that manages Latex files. I did not use NSight 5.4 or even the C/C++ compiler. The crash happened for multiple versions of VS2017. I am running latest version 15.4.1. It is also happened for different versions of Windows 10. I am running latest (version 1709) and it happened also on version 1706. I have NSight 5.4 integration into VS2015 and do not get crashes, so this appears to be an interaction between NSight 5.4 and VS2017. The Event Viewer has field P7 of c0000005, which is the type of error you see on an access violation when you attempt to dereference a null pointer. The Windows Error Reporting file (Report.wer) associated with the event does not appear to contain much more useful information other than what modules are loaded and items about the OS. Event Viewer log below. Fault bucket 109209153934, type 1 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: devenv.exe P2: 15.0.27004.2005 P3: 59e69397 P4: Qt5CoreNvda.dll P5: 5.7.0.0 P6: 5811baa1 P7: c0000005 P8: 001b0cd5 P9: P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9FBB.tmp.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB856.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB852.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB872.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_devenv.exe_c4412e98b79b792aeaa4aea9afec25a56c070a7_706139d6_2993cf36 Analysis symbol: Rechecking for solution: 0 Report Id: 116e290d-9864-4872-abdd-f225a22bc7dc Report Status: 268435456 Hashed bucket: 538b5f7d845209fe170bdc05716cb167
Same behavior for me, happens regularly. In the most recent case, I opened a VS2017 solution that manages Latex files. I did not use NSight 5.4 or even the C/C++ compiler. The crash happened for multiple versions of VS2017. I am running latest version 15.4.1. It is also happened for different versions of Windows 10. I am running latest (version 1709) and it happened also on version 1706. I have NSight 5.4 integration into VS2015 and do not get crashes, so this appears to be an interaction between NSight 5.4 and VS2017.

The Event Viewer has field P7 of c0000005, which is the type of error you see on an access violation when you attempt to dereference a null pointer. The Windows Error Reporting file (Report.wer) associated with the event does not appear to contain much more useful information other than what modules are loaded and items about the OS. Event Viewer log below.

Fault bucket 109209153934, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: devenv.exe
P2: 15.0.27004.2005
P3: 59e69397
P4: Qt5CoreNvda.dll
P5: 5.7.0.0
P6: 5811baa1
P7: c0000005
P8: 001b0cd5
P9:
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9FBB.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB856.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB852.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB872.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_devenv.exe_c4412e98b79b792aeaa4aea9afec25a56c070a7_706139d6_2993cf36

Analysis symbol:
Rechecking for solution: 0
Report Id: 116e290d-9864-4872-abdd-f225a22bc7dc
Report Status: 268435456
Hashed bucket: 538b5f7d845209fe170bdc05716cb167

#5
Posted 10/27/2017 12:38 AM   
Hi, Thanks for your information. I've created an internal bug to track the issue. Thanks, Letitia
Hi,

Thanks for your information.
I've created an internal bug to track the issue.

Thanks,
Letitia

#6
Posted 11/08/2017 10:03 AM   
Scroll To Top

Add Reply