gbpvr.exe cpu spikes

[Pexcer]

Mostly I use gbpvr only as an mvp server, I don't use the recording features at all or watch videos on the pc using gbpvr.

Often times part way through watching a video, after the point where the transcoding to mpg is finished, it will suddenly freeze for a few seconds, then start, then freeze etc. If I push pause it will pause after a several second delay (10 - 15 ), if I leave it for awhile then come back and resume it will play normally.

I finally discovered that when this is happeneing GBPVR.exe is spikeing to around 30% cpu on a very fast cycle, about a second. I've tried killing all other programs that might be interfering, I do have nod32 but I've done the fixes for that and many times just shut it off anyway.

I have some verbose log files taken the last time it was doing it, then some from afterwards when it was running smoothly and the cpu spikes had stopped.

Ok, I didn't make an exact note of the time but I'm pretty sure that the first part of that log file is during the time it was spiking, the last part I beleive it had stopped spiking. I'm not sure when the change happened or if I have normal operation in there for sure, I do know for sure that at least some of that log file is during the cpu spikes. The spikes last for several minutes.

I installed a patch I found in the survival guide post, I'm not sure if it's the same problem but seemed in the same ball park at least I'll have to see if it happens again.

I noticed a strange series in the middle of that log excerpt where it kept saying something about disabling the hauppauge screensaver over and over, not sure if that's normal.

Appreciate any help

[sub]

At the beginning of that log you were paused while watching a video, and it was having to send an updated OSD graphics to the MVP once a second. I would expect this to be pretty CPU intensive (ie, every second it would be generating screen, then converting colour space for every pixel from RGB to YUY2, then zipping up the screen data and sending it across the network with the MVP).

I also recommending leaving the 'force miminal OSD for MVP' setting enabled (the default), since its a lot easier on the system with the OSD is not needing to be sent to the MVP as often.

[Pexcer]

I may have grabbed the log at the wrong time then because when the problem started it wasn't paused. I paused when the video started freezing up and the cpu spikes started.

I'll try the minimal OSD and try to get a more accurate log if it happens again.