It's not driver specific bug. I should have followed the hint that there is a registry entry to workaround this problem with wined3d. It turns out that this registry entry is specifically for this bug. The analysis and possible solutions could be found here: https://bugs.winehq.org/show_bug.cgi?id=34052#c42 Also, this bug is also tracked at: https://github.com/iXit/Mesa-3D/issues/312