https://bugs.winehq.org/show_bug.cgi?id=41998
--- Comment #2 from Henri Verbeet hverbeet@gmail.com --- The patch lost the "device->d3d_initialized" condition, which could be problematic for ddraw applications. Restoring that seems likely to help.
For completeness, could you attach a +seh,+tid,+ddraw,+d3d log? What I expect to happen is that the application messes up its reference counting in some way, as ddraw applications are known to do, and then we make it worse by trying to clean up on ddraw unload.
44003456 is 0x29f7080, which looks suspiciously like a heap address. Does warn+heap make a difference?