http://bugs.winehq.org/show_bug.cgi?id=25472
--- Comment #6 from Erik Dalina edgy.dalina@yahoo.de 2011-04-27 09:52:44 CDT --- Well, I tried to play it another few times and once it didn't even crash in the prison (i.e. cell) but after going through the hole in the wall (after the first assault), killing the rat and heading to the skeleton with the bow. This I actually tried it four or five times more (different routes, sneaking, running, with weapon in/out, with torch) and everytime it crashed (as far as my uncertainty in perceptive measurement is to be trusted) after crossing the same "invisble line". But also one time before entering the hole.
The back trace in the terminal gave -- as I think, logically not out of experience -- two possible causes where one could also be the consequence of the prior one:
The first would have to do with my graphics driver (I have to use the alpha/beta/whatever Catalyst 11.4 because of 11.3 not being compatible with Xorg 1.10) because one of the last lines sais something with "... in fglrx ...".
The other one would be: the very last line asks whether a timer is still running. I already googled it and found out it is supposed to be a generic WINE error. But here I suppose the WINE error only follows the other one ... or otherwise many(?) others would expierience a similar problem.
That all was some time ago and in the meantime I'm playing Oblivion -- being depressed about having to dual boot -- happily and without any crashes on the inferior OS. I surely will give it another try when the next stable driver is released!
BTW, I don't have any CPU usage increases during dialogues of any kind.
I hope this is at least a bit useful as I'm not doing bug reports, usually.