With neumoDVB (and Crazyscan) on satellites

[satesco]

Eutelsat 12 West G @ 12.5° W

I scanned Eutelsat 12 West G with neumoDVB (and Crazyscan) using the 6909x card on the first visit to 12.5W.
Unlike the Windows app, neumoDVB also found and locked two muxes (11191 V,17143 and 11209 V,17142) that were not detected by Crazyscan.

 

[satesco]

I've encountered situations when, with 6909x/(6903x) cards, the frequencies in the upper band were copied from 10950-11200 HV both under Windows and Linux.
This time, it happened the same: at 60.0E, Crazyscan (Windows) and neumoDVB (Linux) found the same frequencies from the lower band to the upper band.
I wonder if this situation is a problem with the IBU lnb used, a bug in the applications/drivers used, or a card construction error.
Why does this error occur?

 

[satesco]

Express-103 @ 96.5° E

Even though these low positions on the arc can only be reached by those with an unobstructed opening and, of course, if they are interested, I think it is worth posting what I am getting at 96.5E in my area.
As usual, neumodVB finds more spikers even with a stid135(6909x) card than with Crazyscan, but the bottom line is that they both lock about the same number of muxes.
This is not an advantage for those looking for TV/radio programs, but they are targets for dxers and all satellites with only Data muxes.