Teamviewer cpu usage while idle

[xello]

Hello, I'm having some weird phenomenon where teamviewer's cpu usage at seemingly random times while the pc is idle will jump to 6-7% and remain there permanently. (please note, this may seem like a trivial amount of usage but it is a large amount considering my cpu is an 8 core 16 thread i7 5960X, and it just has this effect of never letting the cpu never going into a fully idle state where it clocks down and consumes less power + temps lower etc)

I've taken some screenshots that hopefully a more technical person can use to diagnose the problem.

This is from Process Explorer, displaying the cpu usage, the thread causing the usage, and the stack window for  the thread. The stack window changes every time Refresh is clicked, i took a screen of one of the more 'busy' instances.

https://dl.dropboxusercontent.com/u/98455184/tv1.jpg

Unsure if this is related, but I can also see when I used Task Manager's 'Analyze Wait Chain' on TV there was this info:

https://dl.dropboxusercontent.com/u/98455184/Screenshot%202014-12-19%2001.44.53.png

Upon checking the relevant svchost process this was the info on it:

https://dl.dropboxusercontent.com/u/98455184/Screenshot%202014-12-19%2001.46.15.png

At this stage I tried ending that particular svchost process, and the TV process 'analyze wait chain' no longer displayed any info. The cpu usage however stayed 6-7%.

PC is running windows 8.1 x64 and otherwise is operating normally. I'm running TV 8 due to 9 and 10 breaking certain functionality which I can't do without.

thanks!

[xello]

Some more info, I remembered teamviewer keeps logs so i checked it out:

http://pastebin.com/uVyAVuVd

I matched the exact time that the cpu usage jumps to 7% to 18:42:39. If you go to this time in the log you can see a few error messages that I can't make sense of:

2014/12/20 18:42:39.847  3304  4132 S0!  CTcpProcessConnector::HandleRead(): ERROR_SEM_TIMEOUT
2014/12/20 18:42:39.847 10680 10676 G1   CTcpProcessConnector::HandleRead(): Connection broken (PID=0, Error=10054)
2014/12/20 18:42:39.847  3304  4132 S0   CTcpProcessConnector::HandleRead(): Connection broken (PID=0, Error=10054)
2014/12/20 18:42:39.847 10680 10676 G1   CTcpProcessConnector::CloseConnection(): PID=0
2014/12/20 18:42:39.847  3304  4132 S0   CTcpProcessConnector::CloseConnection(): PID=0
2014/12/20 18:42:39.847  3304  4132 S0   UpdateOnlineState newOnlineValue 1

[Admin]

Have you started a direct support ticket?
Also post this to their Facebook page as well if possible.
See the links at the top of the page.

[xello]

thanks i'll try that

[Admin]

it cant hurt, this is an "unsupported" forum in the sense that it is user run, not sanctioned by Teamviewer itself.  If you do get a response, please post it here so other may benefit.
Thanks

[xello]

Update:

After some back and forth with TV support we were unable to find a fix for this, it would appear to be an issue with using TV 8 on Windows 8.1 as it is only officially supported up to Windows 8, so that definitely would seem to point to some compatibility issue. I've updated to TV 10 and the previous issue which stopped me from using it seems to be resolved, so I'll stick with it and hopefully the cpu usage problem will be gone along with TV8.