http://bugs.winehq.org/show_bug.cgi?id=6505
------- Additional Comments From the3dfxdude@gmail.com 2006-31-10 12:41 ------- Not abandoned, but kind of useless.
You really ought to determine whether this is caused by the wined3d backend. To me it looks like so. If that is the case, we know where to look. It could also be a sound bug or a thread priority bug. But this is what it appears like. Not enough information is given.
The idea of "random crashes" is really difficult to approach. Like describing two bugs in one report, reporting more than one crash at a time is the same thing. We can't really properly address both. Just focus on one and try to reproduce it, then dig out the information we need, and then we can clean up the description of the bug. This bug could be for example: "WoW crash after character selection screen" with component of wined3d, but I can't make that change because I don't know.
You might want to look here for more debugging techniques. (The first three sections) http://www.winehq.com/site/docs/winedev-guide/index