I had to unexpectedly upgrade my HTPC this week when my old hardware refused to boot at all. I took this opportunity to upgrade to the latest hardware and software. Now that I have everything up and running I am now having problems with ProgDVB.

Hardware:
MB: Gigabyte GA-Z170X-UD5 TH
CPU: Intel Core i7-6700 8M Skylake Quad-Core 3.4 GHz LGA 1151 65W
RAM: G.SKILL Ripjaws V Series 16GB (2 x 8GB) 288-Pin DDR4 SDRAM DDR4 3000 F4-3000C15D-16GVR
GFX Card: Still my old ATI 4600 series, it gets the job done. :-/
TV Tuner: WinTV-HVR-2250
Sat Tuner: TBS 6925 S2 Tuner
eSATA Card: StarTech PEXESAT322I for my external HD enclosure.

Software:
Windows 10 Pro x64
ProgDVB x86 7.12.03
WinTV 8
PowerDVD 8 Ultra for the codecs
VLC 2.2.1 for playback of recorded video

My old x86 Vista Basic system ran flawlessly with ProgDVB. Since I've moved to Windows 10 Pro x64 I have had a lot of problems with ProgDVB.

ProgDVB crashes when I try to scan transponders on a satellite.

I have a lot of pops and glitches in the audio and random blocks and smeared rows of blocks in the video similar to having a low signal but I don't have a low signal, I'm using a 1.2 meter dish on Galaxy 19 ku and have a signal of L: 80 Q:98, same as before on my old system when I had flawless operation.

Codecs
MPEG-2: MainConcept
H.264/AVC: CoreAVC
WMV: WMVideo Decoder DMO
MPEG4: Mpeg4 DMO
MPEG43: Mpeg43
MPEG4s Mpeg4s
H.263: None
VP6: None
H.265/HVEC: None

MPEG: CyberLink Audio Decoder (PDVD8)
AC3: Hauppauge AC3 Decoder
AAC: CyberLink Audio Decoder (PDVD8)
WMA: WMAudio Decoder DMO
MP3: MP3 Decoder DMO
Vorbis: None

Same setting as on my previous system with flawless operation.

Any insight on the crashes and audio pops/glitches with random blocks and smears on the video?

Thanks

Please send me logs of problem channels (Options->Debug->Logs)

Prog wrote:Please send me logs of problem channels (Options->Debug->Logs)

I deleted the channels I had this morning and re-scanned Galaxy 19, it crashed again part way through scanning the ku band channels. I have attached the logs. I'm not sure if the logs capture information related to the audio and video glitches I'm having, I'm guessing probably not.

Thanks

But this log of scan. Not crash...

Prog wrote:But this log of scan. Not crash...

That was all that was in the Logs folder. ProgDVB must not have crashed then, it just shut down in the middle of scanning. It did ask if I wanted to start it with the last known good configuration, which is what I thought happened after a crash.

I just re-scanned G19 to try again, ProgDVB didn't shutdown this time. The only thing I can think of that I did different this time was that I deleted the channels then closed ProgDVB, restarted it then scanned G19. I think before, if I remember correctly, I deleted the channels then immediately tried to re-scan G19.

I'm wondering if my audio and video problems are caused by the codecs or ProgDVB itself? I tried using my PowerDVD 8 MPEG2 codec for the video but it was VERY slow and the video would freeze every few seconds, I would have thought it would have given the best quality.

Thanks

You can send me logs without restart.

Prog wrote:You can send me logs without restart.

Okay, i deleted the channels and immediately tried re-scanning without closing the program. It crashed again. I have zipped up the entire log directory. Hopefully it will have more than a record of the channel scan.

FYI for update purposes I believe I have fixed the audio and video glitches I was having with my satellite card. It wasn't the codecs causing the problems it was the slot I had the card plugged into. I installed a Samsung 950 Pro 256GB SSD m.2 drive on the motherboard when I rebuilt my HTPC with new hardware. The SSD drive which sits right in front of the last PCIe 1X slot on the motherboard where I had my satellite card plugged into must be sharing some of the same circuit paths and was probably disrupting the data going into and out of the 1x slot causing the random squares and streaks of squares on the screen and the pops and glitch sounds in the audio.

I read that when you plug an m.2 SSD into the slot it disables the last PCIe 4x slot on the board but apparently it also disrupts the last PCIe 1x slot as well.

I moved my 1x satellite card over to the PCIe 8x slot, it's a major waste of an 8x slot but I probably wasn't going to use it anyway. My other two 1x slots on either side of my graphics card are occupied with my WinTV card and my eSATA card. I just hope I won't need another 1x or 8x slot for something else.

Check File->Input traffic->packet lost.

And your log of scan. Do you have problem in scanning time?

ps: Usually stability not depended from DVB device.

Prog wrote:Check File->Input traffic->packet lost.

And your log of scan. Do you have problem in scanning time?

ps: Usually stability not depended from DVB device.

I am seeing "Minimal lost:" 0 bytes

I didn't have any problems in scanning time.

That mean problem not in DVB part (not in DVB card or cables)