I am a Graphics developer and I recently updated to new nvidia drivers (566.36) and I’m encountering some issues with the new drivers. the code that I’ve written works fine in previous versions but in this latest update its giving me some heap corruption errors in “nvrtum64.dll” which is part of the driver.
Specifically it the “CreateStateObject” function of DirectX 12 API, when I try to call it, it results in a heap corruption way down in call stack after calls to dx dlls and in “nvrtum64.dll”.
Why I’m almost sure it’s not my own fault because it works fine with two other driver versions that I had in my computer version 555.85 and 552.44 which both of them have been released in 2024 so it’s not very old.
I’ve also updated to windows 11 24h2 and I’m also encountering some issues from directx itself but they don’t cause crash or instability like this one, maybe the origin is from update 24h2, but since even in this win version older nvidia drivers don’t have that issue I’m presuming it most likely this new update from nvidia.
Alright after hours of effort I finally tracked down the problem, it seems nvidia driver developers forgot to consider 16-bit data types which was introduced in shaders by DX and VK months ago.
using them now causes memory corruption in new drivers.
please fix it sooner!
Hi there @ShahroozLeon,
thank you for bringing this up. I will pass it on to engineering.
It would help if you could share more details like your system configuration details, dxdiag output, call stack and ideally a minimal repro for the issue.
Hello sry for late reply
I ended up getting in contact with one of your development team member and I’m providing more details to him so better not inform them again cause he said they are already on it.
Thanks for the reply though I just wish it was quicker.
Please could we get an update regarding this instability issue? I have a system which was BSOD dpc_watchdog_violation instantly with certain GPU compute workloads and a 4090. I was pointed at this page as a probable cause. I need to diagnose whether the instability we see is likely to be caused by hardware or broken drivers.
Any update on this? My PC was rendering fine before the update now I can’t render any stereo files with the 566.36 driver. Can I go back to previous driver? I need this to work now. Thanks for your help!