DXGI debugging: Microsoft put me on a list
7 comments
·September 21, 2025Pannoniae
georgemcbay
Its also not surprising to anyone who spent time reading Raymond Chen's The Old New Thing blog posts back in the day, a lot of them were about these rather absurd hoops Microsoft was always jumping through to increase backward and forward compatibility with these sorts of tricks.
It may have lead to an unfortunate situation for this developer in this one very niche corner case, but overall it has been wildly beneficial for users over the years (decades even).
HeliumHydride
TrickNvidiaDriversForPerformance_javaw.exe.minecraft.exe
ramijames
When I read about stuff like this it makes me feel lucky never having had to do Windows development.
pjmlp
No worries, the same experience can be done with OpenGL or Vulkan, depending on the specific OS flavour and OEM drivers.
toast0
> It only happens when the program is called SS14.Loader.exe.
Could you have a SS14.Loader.arm.exe for arm? Then the exe name wouldn't match and it woildn't trigger the crash?
gregschlom
You could. The fix is easy. The problem was the painfully long debugging in order to find the root cause of the issue.
The title is a bit clickbait but nice article ;) This is widespread in API-level software, from OSes to GPU drivers. I'm not sure how documented this is but you can find interesting stuff by renaming your exe to Quake, or FIFA, or Minecraft or whatever.