http://bugs.winehq.org/show_bug.cgi?id=11749
--- Comment #22 from Fredrick Lockert fredricklockert@gmail.com 2008-10-08 06:12:09 --- Since no one has said anything yet, this problem is solved by adding a native dxdiagn.dll
The problem is probably caused by the builtin dxdiagn, (kinda logical though).