FaceTime warning in system.log (during heavy buffering) receivedNoPacketsForCallID

Question

OSX 10.8 to OSX 10.9.1 Facetime, both external Logitech 9000 cam.
Heavy buffering, broken connections, retry, freezing, sound dropping.
Plenty bandwith (60/6 at one side at least, other side no measured but fast connection over ethernet)
At every video freeze thes lines in system.log:
Feb  4 20:53:55 iMac-van-Hoek.local FaceTime[4703]: [Warning] !!!!!!!!!!!!################receivedNoPacketsForCallID:#################!!!!!!! !!!!!!!!! (callID:775023717, time:19.169389): <IMAVChatParticipantCallInfo: 0x600000130a40>:state = 3, isFinished = 0, isBeingHandedOff = 0, callID = 775023717, state = 3, inviteNeedsDelivery = 0
Feb  4 20:53:56 iMac-van-Hoek.local FaceTime[4703]: [Warning] !!!!!!!!!!!!################receivedNoPacketsForCallID:#################!!!!!!! !!!!!!!!! (callID:775023717, time:20.170416): <IMAVChatParticipantCallInfo: 0x600000130a40>:state = 3, isFinished = 0, isBeingHandedOff = 0, callID = 775023717, state = 3, inviteNeedsDelivery = 0
This is a Mac 9.1 (late 2009) 2.66 CoreDuo, so not the fastest, but with 4Gb DDR3 should not be problem.
Even with all apps/bowsers/windows closed no improvement.
Not sure when this started getting this bad, has been just a few weeks i think.
Internal cam doesn't do any better.
Would switch to google chat but that has a dreadfull distorted  echo.
The only thing i can find on the web on this system.log warning is the sourcecode..
Anyone know anything about this issue?

Answer 1

Whew.
I'm glad you had the spare supply; I usually recommend "trying before buying" anything, unless, of course, one has lots of cash to blow.
I also wanted to tell you that, if your 2.03 driver method doesn't work, try this:
Go to Start, Run, type in MSCONFIG, press Enter, press the Services tab, check the Hide All Microsoft Services box, press the Disable All button, select the Startup tab, press the Disable All button, Apply, OK, and Restart.
After the reboot, try your games again, and see what happens. If everything's ok, then go back and enable the startup services one at a time, and try playing again until you find the offending service. If all is ok, do the same with the Services tab, until you find the offending Service.
(I spent hours online with Microsoft on this a couple of months ago, and this method found that the intermittent crashing problem was caused by one of the nVidia services.)
So far, I have had four causes of this type of problem (BSOD, spontaneous reboot, freezing):
1) Corrupted OS/driver
2) Poor power
3) Bad RAM
4) Startup Service
Of course, #1 and #4 don't cost anything but time and effort to fix, and should be tried first, unless anything is grossly wrong, like an underrated supply, and/or ram which won't pass memtest, which one should replace anyway. (I've got a lifetime warranty on the RAM, and only had to return it for replacement.) So the only thing that cost me to repair this problem completely was the replacement of the PSU, and it was the very last thing I did.
Were I to do it over again, I would have replaced the PSU before I actually put the replacement RAM in, because I risked damaging the new RAM (and the old stick too) with my old 300W supply. (However, I was on a severe cost restriction which influenced my decision, making the "free fixes" the priority.)
Hope this helps.