Windows 10 64-bit Home.

I've used shares before to quit cgminer in a batch file and loop it to restart after it quits. Say 500,000 acceptable shares then timeout for 300 seconds then start again.

--shares       Quit after mining N shares (default: unlimited)

I have a lot of respect for what @sidehack and @vh do. It is almost magic to me what they can do in terms of hardware and driver/cgminer software programming. I'm just guessing it is some sort of memory or CPU load issue and haven't fully isolated it. Just asking if anyone here has experienced the same. If so, it is worth investigating and isolating so we can report it for a solution. The workaround of restarting is not a bad hack, but it isn't a good long-term solution.