If possible, the next time that you see something like this happen -- assuming that ClockBlocker's main process is still working properly. I'd like for you both to do three things for me, this would be a great help in figuring out exactly what's happening. (so that I can narrow this down and get it fixed) -Check the color of the tray-icon, if it's reverted to yellow or still red. -tray-icon right-click > Misc > Dump to TXT > "Log" and "Settings" (run them both and save the resulting files somewhere) -Open a Task-Manager and look for if you see any helper modules running. If you can attach those files (or put the contents in a code block in a post) and let me know the result of the tray-icon, etc, that'll be a huge help in figuring out at least what part of ClockBlocker this is happening in. Also fine to PM them to me on the forums, but in a reply to the thread is fine too. --Also, when you close ClockBlocker to restart the program, do you have to manually terminate a helper-container? Or do you just need to close it from the tray-icon and re-launch ClockBlocker? (this will hint if the helper process is completely hosed or not) EDIT: One last question: Did you have anything happen at the same time as the game-crash indicated in the Windows Event Viewer (system events) such as a TDR or other driver recovery? -Basically so that I know if this is a typical program crash or something more. And thanks! That should hopefully be enough to get me started.