vkCmdBindDescriptorSets access violation in nvoglv64.dll
I’ve ensured all inputs to this function are correct, used Aftermath attempting to catch a gpu dump, however no gpu crash actually occurs, so this seems to be a regular crash - inside the driver ?
Vulkan Validation is fully enabled, with additional gpu assisted options and no messages or validation errors are reported before this specific function is called at render time in any instance of its usage.
Need I mention that this issue does not occur on a AMD Radeon 290, where it does now with a new NVIDIA Geforce 3060
Latest Studio Drivers (516.59)
Using Vulkan.SDK 18.104.22.168
Hello @carandiru666 and welcome to the NVIDIA developer forums!
Thank you for bringing this to our attention. I will forward the information to engineering and they might ask for more details in the future.
In the meantime, do you happen to have a minimal reproduction application that you could share for us to reproduce the issue in-house?
I found the problem., this is what caused the issue. It was a execution access violation afterall. I suppose that vkCmdBindDescriptorSets uses dynamic code? Disabling the code below fixes the issue.
// setup zero dynamic code execution
//policy.ProhibitDynamicCode = 1;
//SetProcessMitigationPolicy(ProcessDynamicCodePolicy, &policy, sizeof(PROCESS_MITIGATION_DYNAMIC_CODE_POLICY));
Thank you for sharing your solution!
I am not familiar enough with our Vulkan implementation, but it might very well be that it uses dynamic code.
Best of success with your project!
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.