http://bugs.winehq.org/show_bug.cgi?id=10343
--- Comment #2 from jvlad dmda@yandex.ru 2007-11-08 17:45:31 --- I created test case (even two) and was unable to replicate the problem.
Then I went deeper into the original faulting application and found out that there was a conflict between ID I used for the application main window timer and ID returned by SetTimer with zero hWnd. So the window's timer that triggers quite frequently was recognized as an application-wide timer so I thought that the timeout value I set for it had no effect.
I'm not sure if you can fix this problem in any other way but use quite high values for returning from SetTimer when zero hWnd is supplied like Windows does. Windows always returns IDs somewhere from 0x7d00 and higher. Wine returned 0x1 and it's what I use :) for my main window.