Large CPU load from background processes?

[rnslucas]

Hi,
Have been running GBPVR version 92.11 very successfully for some time. However, a power supply blow up, meant hard disk corruption, and I've had to reinstall everything. We also took the opportunity to upgrade the sound card.
I've now installed version 94.13, and when GBPVR is running (not just the Recording Service) it does something every 5-7 seconds which takes up to 50% of the processor power.
When running Windows Media Player at the same time, this causes a huge stutter and distortion in the music. You don't necessarily notice what's it's doing to other programs, but I'm sure it never used to do this.
Can you tell us what GBPVR is doing (nothing gets written to the logs) and confirm that it is more recent that 92.11.
I still have the msi for 92.11 and am thinking of reverting back to it, to make sure there's no conflicts with the new sound card.
Cheers.

[sub]

Can you tell us what GBPVR is doing (nothing gets written to the logs) and confirm that it is more recent that 92.11.

Doesnt ring any bells for me. It doesnt do this on my setup.

[nkh]

I've now installed version 94.13, and when GBPVR is running (not just the Recording Service) it does something every 5-7 seconds which takes up to 50% of the processor power.

Do you have any panels on the main screen that accesses the DB every now and then?

[wtg]

Hi,
I've now installed version 94.13, and when GBPVR is running (not just the Recording Service) it does something every 5-7 seconds which takes up to 50% of the processor power.

I believe the Next Recording panel on the main gbpvr screen queries every 5 seconds. I haven't noticed a problem with this in the gbpvr client, but when I had this panel enabled with my MVPs, the CPU required to regen and transmit the new MVP screens every 5 seconds was too much of a burden for my wee little 1.1 GHz Celeron and it'd introduce a stutter into any video I was watching on the PC itself.

You can easy disable the Next Recording panel (or is it Now Recording... I can't recall) in the skin file, I believe by setting it's Visible attribute to False.

[capone]

Just to offer a troubleshooting idea, when does this happen? When watching TV, on a menu screen, a particular screen, or all the time?

[rnslucas]

Hi folks,
Thanks for all the advice. However, it turned out to be an IRQ conflict with the new sound card, and all is now happy bunnies.
Out of interest, the distortion occurred at the same time as a CPU spike from GBPVR.exe, but was not purely due to processor power, because other processes taking large amounts of power did not cause the problem. It had to be something accessing somewhere at the same time.
I changed the decoder settings (endlessly), and this lowered the CPU usage, but the fault still occurred.
Finally, we moved the sound card - hey presto!
Hope this report is of help to anyone with similar difficulties.

[justlivin']

I am having a similar problem. My cpu load spikes to 99 to 100% when useing gbpvr.exe. This is not the norm. After the spike gbpvr freezes and I have to ctrl+alt+del to end it. I am not using the new recording panel or any plugins. Can anyone stop the spike?

Oh and I dont have any conflicts in my device manager. I have a celeron 2.0 ghz with 384mb. Gbpvr is the only program running.

[justlivin']

no anti-v only hardware firewall, the firewall that is supplied by a d-link router

[justlivin']

so far so good. thankyou tipstir. the system restore trick realy helped. Just to make sure it stays this way how do i disable offline sync?

[MarkD]

I have the same problem with a spike, but shutting down services still isn't doing enough to help my poor old 800Mhz Dell....
I'm using it as a home theater to feed the TV display, and would like it to shut down (hibernate) after a period of low cpu activity. The spikes prevent this from happening. On my system, they reach 40%; if I set the machine to hibernate at this level, it will do so while recording.

The spikes only happen on the main screen, and stop if I disable the "next recording" field. When I tried to follow the thread, it appears to be caused by mscoree.dll (I have .net 1.1).

Any chance of limiting the resources for the "next recording" display, or should I just plan on shutting it off?