I've not heard of nor experienced this before. I'm afraid the problem description is a little light on details, so not much I can do to diagnose from the above.
If the game crashes, Windows usually dumps information about the crash, including the EIP value (Extended Instruction Pointer), which shows the crash location, and hopefully part of the stack as well. If it does, paste that here.
If the game hangs without crashing, you can try running it under a debugger, and then pausing it when it hangs. The debugger should display the current state of the program. Look in the registers pane for the EIP value. That should indicate what part of the code it is stuck in. If it's hung, it might help to run and pause it a few times to get a few sample EIP values. A dump of the stack pane might also help, especially if EIP was an unusable value, such as 0. A good free debugger is
OllyDbg.
As an aside, maybe we should work on some kind of crash dump auto reporting module for the game. Would be more difficult to handle hangs though.