Created attachment 47056 [details]
winedbg backtrace

This was tested with the GOG.com version of the game, no demo version has been released.
The game comes with the following native dlls placed in the game directory: msvcp100, msvcp100d, msvcr100, msvcr100d. The problem doesn't occur when using native msvcr100.dll.

If I use Wine's built-in msvcr100 the game freezes when I start a new game from the menu. The screen is not refreshing but menu music is still playing. The 'Dracula4.exe' process and wineserver consume only 1-2% CPU all the time. At this point in-game videos should be played. The same freezing occurs if I choose <Prologue> from the main menu.

Now comes the tricky part that makes debugging complicated (at least for me):
-if I run the game under winedbg (wine winedbg Dracula4.exe), then starting a new game is working, the videos are playing, but the game crashes as soon as the last video ends.
- the same scenario happens if I start the game normally, but redirect the output to a file: 'wine Dracula4.exe >dracula.log 2>&1). Just like when running under winedbg, the game gets past the videos and crashes when the videos end.
- if I start the game with debug channels enabled, e.g. 'WINEDEBUG=+msvcrt,+tid wine Dracula4.exe >>msvcrt.log 2>&1', then the game doesn't crash at all, it plays the videos and the game continues normally after the videos.
- if I start the game normally, let it freeze and attach winedbg to the already hung Dracula4.exe process, then I receive a backtrace as can be seen in the attached log file.

Plain terminal output doesn't show anything interesting except for a
>fixme:heap:HeapSetInformation (nil) 1 (nil) 0

Fedora 19 x86
wine-1.7.9-143-g33132ce