Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 1033421" data-attributes="member: 82144">With the BSOD... I wonder if the tuner doesn't like being tuned to the same transponder over and over again (when it is already tuned to that transponder). Long shot maybe, but I don't know the history with the 6984. What happens if you delete the now defunct U and Prime channels/tuning-details - does that only delay the BSOD?How frequent are the BSODs?Okay, this is good - different manifestation of a similar problem with really clean logs. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite24" alt="(y)" title="Thumbs Up&nbsp; &nbsp; (y)" loading="lazy" data-shortname="(y)" />Looks like the problem runs back to 00:41 on the 13th:Similar to the other thread I linked recently, we see that it looks like TsWriter stopped but something else prevented the graph from fully stopping. As I understand it a filter graph is stopped starting at the renderer(s) and moving back up the filter chain, so something upstream probably failed to stop.If we look further back in that TsWriter log we see the BSOD occurred during the previous tune. I can't help but wonder if the hardware was still not happy after the reboot (presumably you didn't do a full power-off and power on?).[edit: I note that the presence of MD filters in the graph... well it isn't ideal from a support/policy perspective. This is one situation where they really could potentially be causing issues. Any chance you can live without Sky for a few days and see if the BSODs and &quot;no free cards&quot; keep coming?]</blockquote>

[QUOTE="mm1352000, post: 1033421, member: 82144"] With the BSOD... I wonder if the tuner doesn't like being tuned to the same transponder over and over again (when it is already tuned to that transponder). Long shot maybe, but I don't know the history with the 6984. What happens if you delete the now defunct U and Prime channels/tuning-details - does that only delay the BSOD? How frequent are the BSODs? Okay, this is good - different manifestation of a similar problem with really clean logs. (y) Looks like the problem runs back to 00:41 on the 13th: Similar to the other thread I linked recently, we see that it looks like TsWriter stopped but something else prevented the graph from fully stopping. As I understand it a filter graph is stopped starting at the renderer(s) and moving back up the filter chain, so something upstream probably failed to stop. If we look further back in that TsWriter log we see the BSOD occurred during the previous tune. I can't help but wonder if the hardware was still not happy after the reboot (presumably you didn't do a full power-off and power on?). [edit: I note that the presence of MD filters in the graph... well it isn't ideal from a support/policy perspective. This is one situation where they really could potentially be causing issues. Any chance you can live without Sky for a few days and see if the BSODs and "no free cards" keep coming?] [/QUOTE]

Verification