TBS6909X V2 — Bluescreen with SYSTEM_SERVICE_EXCEPTION error

[betasat]

Hi all,

I have a TBS6909X V2 running on a PC with Windows 10 and trying to use crazycat's BDADataEx program (version 1.1.4.16) for signal monitoring. The PC would bluescreen randomly (e.g. anywhere between about 20 minutes and three hours) with the following error:

Code: Select All Code

SYSTEM_SERVICE_EXCEPTION
Failed component: tbs6909x.sys

Using EBSpro (version 18.0.0.4) also exhibits this symptom and is more likely to crash the system than compared to BDADataEx. I've tried with at least two driver revisions (v1.0.0.3 and v3.0.0.8) and the symptom is the same on both. The tuner card is set to Mode 0 (multiswitch) and only has LNB2/Input 2 connected, as I'm only accessing horizontal transponders on the Ku band currently.

Both the signal statistics logging from BDADataEx and EBSpro would often show strange and sometimes bizarre readings like the ones below:

Lock: 1, Level: 54, Quality: 57, SNR: 429496719.60dB, BER: 0.000000, RFLevel: -44 dBm
Lock: 1, Level: 53, Quality: 52, SNR: 10.40dB, BER: 0.000000, RFLevel: 50 dBm

Has anyone else experienced this issue and know of a fix?
Many thanks.

[smile]

Hello
Could you try update to the latest libs for Crazyscan?

Best Regards

[crazycat]

Using EBSpro (version 18.0.0.4) also exhibits this symptom and is more likely to crash the system than compared to BDADataEx. I've tried with at least two driver revisions (v1.0.0.3 and v3.0.0.8) and the symptom is the same on both. The tuner card is set to Mode 0 (multiswitch) and only has LNB2/Input 2 connected, as I'm only accessing horizontal transponders on the Ku band currently.

See streamreader.log from EBSPro. Look like hw failure - no i2c answer from stid135 chip and finally driver crash (IRQ handler and etc)

[betasat]

Hello
Could you try update to the latest libs for Crazyscan?

Best Regards

Hi smile,

Unfortunately, we had a storm over the weekend and no longer have reception as the dish is likely knocked out of alignment; probably won't be able to do further testing until that is resolved.

See streamreader.log from EBSPro. Look like hw failure - no i2c answer from stid135 chip and finally driver crash (IRQ handler and etc)

Hi crazycat,

I've had a look at StreamReader's log from EBSpro and haven't found any errors relating to hardware failures. The log would end abruptly just before a bluescreen like in the following excerpt:

Code: Select All Code

11:00:57 - 10/04/2025 StreamReaderEx BDA Ver:1.2.5.202-commited (Nov  5 2024, 20:14:46)
…
11:29:12 - 10/04/2025 SignalInfo()
11:29:13 - 10/04/2025 Statistic()
11:29:13 - 10/04/2025 Signal   Present = 1   Locked = 1
11:29:13 - 10/04/2025    Level = 52%   Quality = 46%
11:29:13 - 10/04/2025 GetSignalExEx()
11:29:14 - 10/04/2025 Signal   Present:1   Locked:1   RFLevel = -47dBm   SNR = 9.400000dB   BER = 0.000000
11:29:14 - 10/04/2025 SignalInfo()
11:29:15 - 10/04/2025 Statistic()
11:29:15 - 10/04/2025 Signal   Present = 1   Locked = 1
11:29:15 - 10/04/2025    Level = 51%   Quality = 46%
11:29:15 - 10/04/2025 GetSignalExEx()
11:29:15 - 10/04/2025 Signal   Present:1   Locked:1   RFLevel = -48dBm   SNR = 9.200000dB   BER = 0.000000
11:29:15 - 10/04/2025 SignalInfo()
11:29:16 - 10/04/2025 Statistic()
11:29:16 - 10/04/2025 Signal   Present = 1   Locked = 1
11:29:16 - 10/04/2025    Level = 52%   Quality = 46%
11:29:16 - 10/04/2025 GetSignalExEx()
11:29:16 - 10/04/2025 Signal   Present:1   Locked:1   RFLevel = -47dBm   SNR = 9.300000dB   BER = 0.000000
11:29:16 - 10/04/2025 SignalInfo()
11:29:17 - 10/04/2025 Statistic()
11:29:17 - 10/04/2025 Signal   Present = 1   Locked = 1
11:29:17 - 10/04/2025    Level = 51%   Quality = 46%
11:29:17 - 10/04/2025 GetSignalExEx()
11:29:18 - 10/04/2025 Signal   Present:1   Locked:1   RFLevel = -48dBm   SNR = 9.300000dB   BER = 0.000000
11:29:18 - 10/04/2025 SignalInfo()
11:29:19 - 10/04/2025 Statistic()
11:29:19 - 10/04/2025 Signal   Present = 1   Locked = 1
11:29:19 - 10/04/2025    Level = 51%   Quality = 46%
11:29:19 - 10/04/2025 GetSignalExEx()
11:29:19 - 10/04/2025 Signal   Present:1   Locked:1   RFLevel = -48dBm   SNR = 9.300000dB   BER = 0.000000
11:29:19 - 10/04/2025 SignalInfo()
11:29:20 - 10/04/2025 Statistic()
                                                                                                                                                                                                                                                                                                                       


P.S. Not sure if this is useful but here's another excerpt from the log of StreamReader under CrazyScan, which exhibits the same behaviour where the log abruptly ends just before the bluescreen:

Code: Select All Code

09:01:40 - 24/04/2025 StreamReaderEx BDA Ver:1.2.5.207-commited (Apr 13 2025, 18:37:32)
09:01:40 - 24/04/2025 Log level = 1
09:01:40 - 24/04/2025 DLL_PROCESS_ATTACH hModule = 6BE10000
09:01:40 - 24/04/2025 CheckForDVBEx(0x00D79890)
09:01:40 - 24/04/2025 Power-off LNB on exit: ENABLED
09:01:40 - 24/04/2025 SendDiSEqC use 2 repeats
09:01:40 - 24/04/2025 Default modulation: AUTO
09:01:40 - 24/04/2025 Default spectral inversion: AUTO
09:01:40 - 24/04/2025 Default pilot: AUTO
09:01:40 - 24/04/2025 Default rolloff: AUTO
09:01:40 - 24/04/2025 Preffered BDA device type: AUTO
09:01:40 - 24/04/2025 Allowed IF Freq 950-2150 Mhz
09:01:40 - 24/04/2025 Inverted LOF<6000 and >21000 Mhz
…
09:01:40 - 24/04/2025 StartDVBEx(5)
09:01:40 - 24/04/2025 Device_ID: 5
09:01:40 - 24/04/2025 Use Device 5
09:01:40 - 24/04/2025    Tuner filter: TBS 6909x DVBS/S2 Tuner 1
09:01:40 - 24/04/2025    Capture filter: TBS 6909x DVBS/S2 Capture 1
09:01:40 - 24/04/2025 Input num 1
09:01:42 - 24/04/2025 Frontend/demod IC: STiD135 (rev 2.1)
09:01:42 - 24/04/2025 Chip temperature: 56°C
09:01:42 - 24/04/2025 TBS STiD135 direct control used !
09:01:42 - 24/04/2025 Force DVB-S2 BBframe mode (Encapsulated in TS, PID 270) !
09:01:42 - 24/04/2025 Turbosight (Lattice FPGA based) BDA extension used !
09:01:42 - 24/04/2025 + Turbosight I2C access support
09:01:42 - 24/04/2025 + Turbosight SignalEx support
09:01:42 - 24/04/2025 + Turbosight SignalInfo support
09:01:42 - 24/04/2025 + Turbosight MIS filtering support
09:01:42 - 24/04/2025 + Turbosight PLS control support
09:01:42 - 24/04/2025 + Turbosight MODCODE filtering support
09:01:42 - 24/04/2025 + Turbosight BBFrame streaming support
09:01:42 - 24/04/2025 + Turbosight fast LNB control support
09:01:56 - 24/04/2025 StopDVB()
09:01:56 - 24/04/2025 LNB power-off ok !
09:01:56 - 24/04/2025 StartDVBEx(4)
09:01:56 - 24/04/2025 Device_ID: 4
09:01:56 - 24/04/2025 Use Device 4
09:01:56 - 24/04/2025    Tuner filter: TBS 6909x DVBS/S2 Tuner 3
09:01:56 - 24/04/2025    Capture filter: TBS 6909x DVBS/S2 Capture 3
09:01:56 - 24/04/2025 Input num 3
09:01:58 - 24/04/2025 Frontend/demod IC: STiD135 (rev 2.1)
09:01:58 - 24/04/2025 Chip temperature: 55°C
09:01:58 - 24/04/2025 TBS STiD135 direct control used !
09:01:58 - 24/04/2025 Force DVB-S2 BBframe mode (Encapsulated in TS, PID 270) !
09:01:58 - 24/04/2025 Turbosight (Lattice FPGA based) BDA extension used !
09:01:58 - 24/04/2025 + Turbosight I2C access support
09:01:58 - 24/04/2025 + Turbosight SignalEx support
09:01:58 - 24/04/2025 + Turbosight SignalInfo support
09:01:58 - 24/04/2025 + Turbosight MIS filtering support
09:01:58 - 24/04/2025 + Turbosight PLS control support
09:01:58 - 24/04/2025 + Turbosight MODCODE filtering support
09:01:58 - 24/04/2025 + Turbosight BBFrame streaming support
09:01:58 - 24/04/2025 + Turbosight fast LNB control support
09:03:51 - 24/04/2025 MISSel(0,0x00,0x00)
09:03:51 - 24/04/2025 PLSSel(0,0x01)



Would the STid135's chip temperature be of concern? I've had a minimum of 28°C and maximum of 75°C with typical readings of 60°C under load.

[betasat]

I've noticed some seemingly random and odd behaviour when sweeping the upper Kᵤ band with RFScan in CrazyScan. I don't have reception currently as the dish is still out of alignment, so the tuner is only picking up noise, although the LNB is present on the line as far as I'm aware.

Sometimes a somewhat legible and continuous sweep is produced, while it would be erratic at other times as per attached screenshot. The PC tends to bluescreen especially during the erratic sweeps. I then realised there was a scheduled recording running in the background via DVBViewer during the erratic sweeps.

I'm wondering if simultaneously using two different applications on the tuner card is causing it to crash and whether it would be possible to do so without it crashing.

For example:

• Tuner 3 — BDADataEx
• Tuner 6 — DVBViewer

[DVB]

Check this post by crazycat: viewtopic.php?f=176&t=26010#p57570

[betasat]

Check this post by crazycat: viewtopic.php?f=176&t=26010#p57570

Hi DVB,

I've tried setting HWControl=0 in StreamReader.ini as suggested by @crazycat, but cannot FFTScan across any of the 8 tuners. It also appears to disable the BlindScan capability? With HWControl=1, Tuners 0, 1, 2 and 3 can scan as expected. Am I missing something?

Given the integrated nature of the STiD135's narrow band demodulators, would it still be possible to arrange them as virtual tuners with StreamReaderEx-BDA?

[crazycat]

Only first four virtual demods have FFT cell, sо support FFTScan

I'm wondering if simultaneously using two different applications on the tuner card is causing it to crash and whether it would be possible to do so without it crashing.

This fantastic Only one StreamReaderEx-based app can be used with 6903x/6909x

[betasat]

Only first four virtual demods have FFT cell, sо support FFTScan

I'm wondering if simultaneously using two different applications on the tuner card is causing it to crash and whether it would be possible to do so without it crashing.

This fantastic Only one StreamReaderEx-based app can be used with 6903x/6909x

I see; thanks @crazycat for clarifying. I had suspected the integrated nature of the STiD135 does not support running multiple applications simultaneously.

Is it possible to use a single instance of StreamReaderEx-BDA to access all 8 demods at the same time for signal monitoring and route their traffic via RTSP or similar to other applications like DVBViewer for recording?

[crazycat]

you can use BDADataEx for signal monitoring + DVBViewer for streaming with all 8 demods