http://bugs.winehq.org/show_bug.cgi?id=22745
--- Comment #1 from default_357-line@yahoo.de 2010-05-17 21:34:30 --- Somebody changed the component to directx-d3d; it would be good to know the reasoning behind that given that the crash happens in ntdll's memory management - one would think who calls those routines would be immaterial to the fact that they're being faulty.