http://bugs.winehq.org/show_bug.cgi?id=12964
--- Comment #109 from Henri Verbeet hverbeet@gmail.com 2013-01-23 13:21:55 CST --- (In reply to comment #108)
0026:trace:d3d_surface:wined3d_surface_create flags 0x1, parent 0x14d7f0, parent_ops 0x7e518d6c. 0026:trace:seh:raise_exception code=c0000005 flags=0 addr=0x7bc49bfe ip=7bc49bfe tid=0026 0026:trace:seh:raise_exception info[0]=00000000 0026:trace:seh:raise_exception info[1]=000010d9 0026:trace:seh:raise_exception eax=000010e1 ebx=7bcb6000 ecx=00110088 edx=000008e8 esi=00008018 edi=00110000 0026:trace:seh:raise_exception ebp=00e8e008 esp=00e8dfb0 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00010206
That's a slightly different crash from the one before. The traces aren't enough to narrow down the exact line where it crashes, but going by the eip and the critical section timeouts, it's probably inside some HeapAlloc() call. That suggests some kind of memory corruption. That kind of thing can be pretty hard to debug remotely, and it doesn't look like there's any useful output from warn+heap, although I suppose there's a small chance there's something in the part of the log you cut.