https://bugs.winehq.org/show_bug.cgi?id=41998
--- Comment #8 from Henri Verbeet hverbeet@gmail.com --- (In reply to Fabian Maurer from comment #7)
Created attachment 56498 [details] Crash log with path
Sadly not. The issue seems to go deeper.
Right, at the core the issue is that ddraw releases the wined3d device before all the corresponding resources are released. That's what the "Device released with resources still bound ..." messages is about, and it's not a new issue. The "acceptable" in that message may be a bit misleading at this point.
I had hoped avoiding the issue in device_resource_released() would have been enough to fix this for 2.0, but it looks like there are more issues.