100% CPU Load

[dfdario]

Sorry, I really cant see anything. It looks fine.

I still think its probably just something buggy with the drivers of the HVR cards.

Sorry I don't want be misundertood since I'm trying to help you finding where the problem is. If you look better you'll see that in the file GBPVRRecordingService.exe-native.log there's something wrong (in my opinion):

00:10:46.968 VERBOSE BDARecorder::StartRecording() finished
00:11:26.750 VERBOSE BDARecorder::StopRecording()
00:11:47.468 VERBOSE BDARecorder::StopRecording()
<-------- HERE it should stay "VERBOSE BDARecorder::StopRecording() finished" --------->
01:30:00.468 VERBOSE BDARecorder::StopRecording()
01:39:39.468 VERBOSE BDARecorder::StopRecording() finished

in fact the try icon stays in recording state...

[dfdario]

More infos
Drivers should be the same as Nova-T cards.
Yesterday I rolled back to v. 2.1 drivers that were working better than newer.

[sub]

Sorry I don't want be misundertood since I'm trying to help you finding where the problem is. If you look better you'll see that in the file GBPVRRecordingService.exe-native.log there's something wrong (in my opinion):

00:10:46.968 VERBOSE BDARecorder::StartRecording() finished
00:11:26.750 VERBOSE BDARecorder::StopRecording()
00:11:47.468 VERBOSE BDARecorder::StopRecording()
<-------- HERE it should stay "VERBOSE BDARecorder::StopRecording() finished" --------->
01:30:00.468 VERBOSE BDARecorder::StopRecording()
01:39:39.468 VERBOSE BDARecorder::StopRecording() finished

in fact the try icon stays in recording state...

It probably means the driver crashed while stopping. I have seen this in the past with an older version of the Twinhan drivers for my DVB-S card.

This BDARecorder::StartRecording() function just stops the graph, which behind the scenes stops the BDA filters (drivers) for this device.

[dfdario]

OK
Thanks Sub for the help. I'll try to find the reason and a workaround.

[dfdario]

Before throw in the towel
Are you interested in these files? (see attach)
There is also a GBPVRRecordingService.exe.hdmp (dump) but is 15 megs long.

When hanged restarting RecordingService solve the problem.

[sub]

Server=watson.microsoft.com
UI LCID=1040
Flags=1672016
Brand=WINDOWS
TitleName=GBPVRRecordingService.exe
DigPidRegPath=HKLM\Software\Microsoft\Windows NT\CurrentVersion\DigitalProductId
ErrorText=Se si sta eseguendo un'operazione, è possibile perdere i dati su cui si sta lavorando.
Stage1URL=
Stage1URL=/StageOne/GBPVRRecordingService_exe/1_0_2243_24818/MpgMux_ax/5_0_0_727/00018fcc.htm
Stage2URL=
Stage2URL=/dw/stagetwo.asp?szAppName=GBPVRRecordingService.exe&szAppVer=1.0.2243.24818&szModName=MpgMux.ax&szModVer=5.0.0.727&offset=00018fcc
DataFiles=C:\DOCUME~1\PVR\IMPOST~1\Temp\WER733b.dir00\GBPVRRecordingService.exe.mdmp|C:\DOCUME~1\PVR\IMPOST~1\Temp\WER733b.dir00\appcompat.txt
Heap=C:\DOCUME~1\PVR\IMPOST~1\Temp\WER733b.dir00\GBPVRRecordingService.exe.hdmp
ErrorSubPath=GBPVRRecordingService.exe\1.0.2243.24818\MpgMux.ax\5.0.0.727\00018fcc
DirectoryDelete=C:\DOCUME~1\PVR\IMPOST~1\Temp\WER733b.dir00

The fault is occuring inside the Cyberlink mux. Try a later version. Use the forum search feature to search for "5.0.1307"

[dfdario]

You are always the greatest!
I'll do and give you a feedback!!

F E E D B A C K
IT WORKED!

THANKS AGAIN SUB!!!

[jaws316]

I have the problem, but I am not following this post. I have a haupaug 500 tuner running the latest version of gbpvr as of 10/18/06

can anyone help?

[sub]

It wont be the same cause. His problem was caused by Cyberlink mux filter, which is only used for digital cards, so not relevent with your PVR500.

What process is using the CPU for your problem?