This is Nvidia's fault all the way. It generally happens with older cards on the latest drivers, which isn't entirely surprising given the wide range of hardware NV now has to support from one codebase. More to the point, reverting MAME versions has no effect, while reverting the Nvidia drivers always does.
> At first, I was pointing the finger of blame at Nvidia, but I've become curious as to > exactly which version of MAME this started in. Is it possible that MAME code is doing > something wrong with D3D that's causing the crashes?
As per my devquote, MAME is about as close to a reference D3D app as you're going to get. With HLSL off it uses a hilariously tiny amount of the resources of any GPU made in the last 5 years - during normal gameplay without artwork it draws 2 triangles at 60 frames per second. 2. If that's crashing your graphics drivers, they have problems MAMEdev can't help you with
|