DD crashes after PC resumes from sleep

[kukuku]

Hi,

I found this while testing the SageTV network encoder module with DD. I start DD in renderless mode, put the PC to sleep, hit power to resume pc later, then windows tells me DD crashed, and needs to close the program. Tried a few times with repeatable results. I am using Vista 32bit.

Does this happen to everybody or is it specific to my setup?

Thanks!

[genpix]

Are you serious?

TS data streaming thread has Time_Critical priority.
Surely, this thread gets busted when you go into sleep/wake-up mode.
As well as many other threads which don't want to be interrupted.

PS: PC goes into sleep mode, while SkyWalker-1 is left in the active mode. It still trying to pump the data into "dead" PC.

[kukuku]

I figured is has something to do with DD constantly tuning to a channel. When PC is suspended and resumed, the TS stream is interrupted and DD cannot handle it and crashes. Is that correct?

[genpix]

start DebugView before go into sleep mode, then wake up.
Then look into debug messages

[hdnow]

and yet genpix, when I was running 1.4h on wxp pro, hibernation used to be flawless: just hit hibernate with dd up and running, PC goes to sleep, then restart with remote, it'll catch up in couple of seconds on the same channel it was left at with video and audio. Not anymore with 1.4i.

cheers,
hdnow

Are you serious?

TS data streaming thread has Time_Critical priority.
Surely, this thread gets busted when you go into sleep/wake-up mode.
As well as many other threads which don't want to be interrupted.

PS: PC goes into sleep mode, while SkyWalker-1 is left in the active mode. It still trying to pump the data into "dead" PC.

[kukuku]

DebugView log of sleep/wakeup:

00000000 0.00000000 [5404] genpix 8PSK: WaitForXfer() timed out buffer = 19 ***********
00000001 0.00009247 [5404] - STOP mpeg stream
00000002 0.02145049 [5404] +START mpeg stream
00000003 0.02151111 [5404] genpix 8PSK: WaitForXfer() timed out buffer = 0 ***********
00000004 0.02157146 [5404] - STOP mpeg stream
00000005 0.04223693 [5404] Error -
00000006 0.04229504 [5404] RtlWerpReportException failed with status code :-1073741772. Will try to launch the process directly
00000007 0.04234058 [5404]

[rel]

moving to "bug reports"

[kukuku]

My windows is set to go to sleep after a certain time of inactivity. DvbDream would prevent windows from going to sleep even when it is in renderless mode and minimized. This becomes a problem when I want to use DD as a backbone program for other HTPC programs such as SageTv, because DD now has to run 24/7.
Please consider fixing this bug for next release. Highly appreciated!!

[KlausWolter]

Hi Gents and Ladies,

Since I updated to version 1.4i I have the same problem. Once the computer went to sleep in Standby DD is not anymore able to start a channel. It keeps to stay in a condition where CPU usage is permanently in range of 50% and task manager shows that that is kernel most likely use. The Channel is chosen and the signal quality and strength bars are placed. By that it might be of interest that after booting the computer DD runs without any problem. Only if there was a standby before this hanging occurs and it is not of interest if DD had run after fresh booting or not. Means: After standby and boot new...

Added: For me it seems to be that the way to the video output is shortcut, because the program DD can be operated as normal. I am able to change channels, change properties and so on. Only the way out is blocked...

[KlausWolter]

Now some more informations:
Because I am not happy with the situation, I tried again some variations. The result:

I installed version 1.4h after my computer awoke from standby. And with that fresh installation it was also not possible to get some signal. During channel scan no transponder answered with a content only the amplitude of the scanned transponder was signaled. Then after a reboot all was fine...

Then I tested with 1.4i - if you believe or not: the same result!!!

I can say now, that the problem seems to be, that the transponder is seen but the transport stream of the entire transponder is blocked after one time standby.

Maybe that helps a little bit.


I hope there will be a solution

[KlausWolter]

A step forward!

After entering the failure status I tried something I did not before: I deactivated my Pinnacle driver in the Windows hardware manager and activated again. After that DD started with no failure and worked perfect.



p.s.
I just found a Microsoft document that might be of interest:

download.microsoft.com/download/9/c/5/9c5b2167-8017-4bae-9fde-d599bac8184a/DriverHangVerification.doc

[KlausWolter]

Hi my dear fellowships!

Microsofts program devcon.exe used in command line syntax "devcon restart *DEV_0878* restarts 'Pinnacle PCTV Sat TS' after suspend... And no problem anymore.

Bye bye