# Nsight VS crashes on driver crashes... **URL:** \ **Category:** Nsight Visual Studio Edition\ **Created:** [March 11, 2018, 7:23pm UTC](https://forums.developer.nvidia.com/t/nsight-vs-crashes-on-driver-crashes/59018 "2018-03-11T19:23:42Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![ShadowCam](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@ShadowCam](https://forums.developer.nvidia.com/u/ShadowCam)\ **Post date:** [March 11, 2018, 7:23pm UTC](https://forums.developer.nvidia.com/t/nsight-vs-crashes-on-driver-crashes/59018/1 "2018-03-11T19:23:42Z")
Basically, I would have thought the using Nsight would allow devs to see why something is crashing, but, instead, Nsight crashes as well. This is a openGL program, and Aftermath only works on DX, so, how do we proceed here? The same code was tested on both intel & AMD gear, and it works fine, so, it sure looks like a Nvidia openGL driver bug here… ```auto EXCEPTION_PARAMETER1: 00000008 EXCEPTION_PARAMETER2: 00020052 WRITE_ADDRESS: 00020052 FOLLOWUP_IP: nvoglv32+83afb6 58d3afb6 ?? ??? FAILED_INSTRUCTION_ADDRESS: +83afb6 00020052 ?? ??? FAULTING_THREAD: 00003ac8 BUGCHECK_STR: APPLICATION_FAULT_SOFTWARE_NX_FAULT_INVALID PRIMARY_PROBLEM_CLASS: SOFTWARE_NX_FAULT_INVALID DEFAULT_BUCKET_ID: SOFTWARE_NX_FAULT_INVALID LAST_CONTROL_TRANSFER: from 58d3afb6 to 00020052 STACK_TEXT: WARNING: Frame IP not in any known module. Following frames may be wrong. 07a6dc70 58d3afb6 00008246 00008250 00020052 0x20052 07a6dc74 00000000 00008250 00020052 00009147 nvoglv32+0x83afb6 STACK_COMMAND: ~5s; .ecxr ; kb SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nvoglv32+83afb6 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvoglv32 IMAGE_NAME: nvoglv32.dll DEBUG_FLR_IMAGE_TIMESTAMP: 5a4d6882 FAILURE_BUCKET_ID: SOFTWARE_NX_FAULT_INVALID_c0000005_nvoglv32.dll!Unknown BUCKET_ID: APPLICATION_FAULT_SOFTWARE_NX_FAULT_INVALID_BAD_IP_nvoglv32+83afb6 ``` ---
**Author:** ![AYan](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/ayan/32/256893_2.png) [@AYan](https://forums.developer.nvidia.com/u/AYan)\ **Post date:** [March 12, 2018, 3:56am UTC](https://forums.developer.nvidia.com/t/nsight-vs-crashes-on-driver-crashes/59018/2 "2018-03-12T03:56:01Z")
Hi ShadowCam, Sorry for the crash you meet, but from your words, you mean your app also crash even without Nsight, right? I am sorry that Nsight doesn’t support a app that will crash. Thanks An ---
**Author:** ![ShadowCam](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@ShadowCam](https://forums.developer.nvidia.com/u/ShadowCam)\ **Post date:** [March 12, 2018, 4:27am UTC](https://forums.developer.nvidia.com/t/nsight-vs-crashes-on-driver-crashes/59018/3 "2018-03-12T04:27:25Z")
Hi, well, the app don’t crash per se, the driver is crashing (nvoglv32.dll). I thought Nsight was used for debugging GPU code? Is there another tool I can use to help debug the driver crashing? ---
**Author:** ![AYan](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/ayan/32/256893_2.png) [@AYan](https://forums.developer.nvidia.com/u/AYan)\ **Post date:** [March 12, 2018, 7:35am UTC](https://forums.developer.nvidia.com/t/nsight-vs-crashes-on-driver-crashes/59018/4 "2018-03-12T07:35:47Z")
Hi ShadowCam, I am not very understand your meaning, do you mean the app runs smoothly, and nvoglv32.dll will crash? Which process does the crash happen? Thanks An ---
**Author:** ![ShadowCam](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@ShadowCam](https://forums.developer.nvidia.com/u/ShadowCam)\ **Post date:** [March 12, 2018, 5:48pm UTC](https://forums.developer.nvidia.com/t/nsight-vs-crashes-on-driver-crashes/59018/5 "2018-03-12T17:48:18Z")
Yes, the program doesn’t crash on intel & AMD, only on Nvidia’s driver, nvoglv32.dll. This is why we are using Nsight to try and debug why it only crashes in nvoglv32.dll, however, when the driver crashes, so does Nsight. I would have thought Nsight would tell us the calls right before the crash so we can narrow it down. ```auto Access Violation at location 00020052 Writing to location 00000000. Registers: eax=00000000 ebx=1886fd38 ecx=00000000 edx=00000001 esi=00008246 edi=00000001 eip=00020052 esp=15c8df28 ebp=00008250 iopl=0 nv up ei pl nz na pe nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010202 Call stack: 00020052 5B35AFB6 C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5601d21ccd639df9\nvoglv32.dll:5B35AFB6 5B35B0E6 C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5601d21ccd639df9\nvoglv32.dll:5B35B0E6 5B35B095 C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5601d21ccd639df9\nvoglv32.dll:5B35B095 5B567EBF C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5601d21ccd639df9\nvoglv32.dll:5B567EBF DrvPresentBuffers 5B634D71 C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5601d21ccd639df9\nvoglv32.dll:5B634D71 DrvPresentBuffers 5ABDF7D9 C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5601d21ccd639df9\nvoglv32.dll:5ABDF7D9 5ABCA741 C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5601d21ccd639df9\nvoglv32.dll:5ABCA741 5B635456 C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5601d21ccd639df9\nvoglv32.dll:5B635456 DrvPresentBuffers 5B63666E C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5601d21ccd639df9\nvoglv32.dll:5B63666E DrvPresentBuffers 5B63546A C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5601d21ccd639df9\nvoglv32.dll:5B63546A DrvPresentBuffers 5B55A71A C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5601d21ccd639df9\nvoglv32.dll:5B55A71A DrvPresentBuffers 5B564A30 C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5601d21ccd639df9\nvoglv32.dll:5B564A30 DrvPresentBuffers 5B580669 C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5601d21ccd639df9\nvoglv32.dll:5B580669 DrvPresentBuffers 5B63082E C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5601d21ccd639df9\nvoglv32.dll:5B63082E DrvPresentBuffers 5B637E24 C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5601d21ccd639df9\nvoglv32.dll:5B637E24 DrvPresentBuffers 5ABC5B89 C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5601d21ccd639df9\nvoglv32.dll:5ABC5B89 5B5335DF C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5601d21ccd639df9\nvoglv32.dll:5B5335DF DrvValidateVersion 5B618EB7 C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5601d21ccd639df9\nvoglv32.dll:5B618EB7 DrvPresentBuffers 5B607CE1 C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5601d21ccd639df9\nvoglv32.dll:5B607CE1 DrvPresentBuffers 5B60762F C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5601d21ccd639df9\nvoglv32.dll:5B60762F DrvPresentBuffers 5B541A51 C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5601d21ccd639df9\nvoglv32.dll:5B541A51 DllMain 5B541B9C C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5601d21ccd639df9\nvoglv32.dll:5B541B9C DllMain 5B5419D2 C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5601d21ccd639df9\nvoglv32.dll:5B5419D2 DllMain 5B541590 C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5601d21ccd639df9\nvoglv32.dll:5B541590 DllMain 5B52E3B5 C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5601d21ccd639df9\nvoglv32.dll:5B52E3B5 DrvSwapLayerBuffers 5B54348A C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5601d21ccd639df9\nvoglv32.dll:5B54348A DllMain 5B3D19F4 C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5601d21ccd639df9\nvoglv32.dll:5B3D19F4 5B3D1864 C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5601d21ccd639df9\nvoglv32.dll:5B3D1864 5B5379E7 ``` ---
**Author:** ![AYan](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/ayan/32/256893_2.png) [@AYan](https://forums.developer.nvidia.com/u/AYan)\ **Post date:** [March 13, 2018, 4:17am UTC](https://forums.developer.nvidia.com/t/nsight-vs-crashes-on-driver-crashes/59018/6 "2018-03-13T04:17:37Z")
Hi ShadowCam, Sorry, but I think Nsight doesn’t support a app that will crash. It’s better to ask for support from driver team, IMO. Thanks An