Streaming on new PC resulting in majority dropped packets

[Skully_B]

I've been using a 12 year old PC (Intel I5, AMD Radeon HD 1800, 16Gb DDR3 RAM, Windows 10) to stream at 1080p with ~5Mbps uplink without issue for the past 10 years.

Unfortunately I needed a new PC because I can't upgrade to Win11 due to too old hardware.

So I've set up a new PC with reasonable parts (Intel I7, NVidia RTX 5060Ti, 32Gb DDR5 RAM, Windows 11) and then I tried to match the settings that I had used previously. The settings are slightly different due to a different GPU so the GPU encoding option is different along with the options that show up after selecting it.

When I try to stream with my new PC, ~70% of the packets are dropped with the upload rate fluctuating but rarely getting about 1000kbps, the stream is unviewable. If I drop the bitrate down from 5000kbps to 1000kbps then it's a bit more stable for a few minutes but eventually drops.

I had tried the things in the thread involving "dropped frames/disconnecting/lag" and did see from the tool linked there that, although I'm based in the UK, I had a more solid connection to other places in the UK. So I tried those places but the behaviour was exactly the same.

Given that the old PC is still able to stream without issue, it doesn't seem like it's simply a network issue? As I tested using the exact same Ethernet cable.

I created a log from a quick test on the old PC: https://obsproject.com/logs/1gCIkBoS7tFUCbcb and on the new PC: https://obsproject.com/logs/qMVG7JAMVOHBPj3x

I appreciate any help/advice people are able to give on why my newer PC might be struggling like this and what I can do to fix it.

 

[Skully_B]

So while trying to make sure I had all the info, I saw in the "OBC Analyzer" it mentioning about "HAGS" and how to disable it.
So I tried that and... that seems to have resolved the issues? My stream is now not dropping any frames.

So this thread can be closed - Sorry!

 

[rockbottom]

HAGS only?
14:27:04.252: Output 'adv_stream': Number of dropped frames due to insufficient bandwidth/connection stalls: 6911 (46.4%)

The Killer Suite was known to cause dropped frames. I'm not sure if that still holds true or if you have it installed but going with the driver only install was the way to go in the past. Keep an eye on stats while & check your logs after streaming, some of that 46.4% probably remains.

On another note, the BenQ & any additional monitors added down the road should be connected to the 5060 for best performance. Leave the mobo/iGPU connector empty.

14:18:12.508: Adapter 1: Intel(R) Graphics
14:18:12.508: Dedicated VRAM: 134217728 (0.1 GiB)
14:18:12.508: Shared VRAM: 19199868764 (17.9 GiB)
14:18:12.508: PCI ID: 8086:7d67
14:18:12.508: HAGS Status: Disabled (Default: No, Driver status: Unsupported)
14:18:12.509: Driver Version: 32.0.101.6737
14:18:12.509: output 0:
14:18:12.509: name=BenQ XL2420T
14:18:12.509: pos={-1080, -638}
14:18:12.509: size={1080, 1920}
14:18:12.509: attached=true
14:18:12.509: refresh=60
14:18:12.509: bits_per_color=8
14:18:12.509: space=RGB_FULL_G22_NONE_P709

 

[Skully_B]

HAGS only?
14:27:04.252: Output 'adv_stream': Number of dropped frames due to insufficient bandwidth/connection stalls: 6911 (46.4%)

The Killer Suite was known to cause dropped frames. I'm not sure if that still holds true or if you have it installed but going with the driver only install was the way to go in the past. Keep an eye on stats while & check your logs after streaming, some of that 46.4% probably remains.

On another note, the BenQ & any additional monitors added down the road should be connected to the 5060 for best performance. Leave the mobo/iGPU connector empty.

14:18:12.508: Adapter 1: Intel(R) Graphics
14:18:12.508: Dedicated VRAM: 134217728 (0.1 GiB)
14:18:12.508: Shared VRAM: 19199868764 (17.9 GiB)
14:18:12.508: PCI ID: 8086:7d67
14:18:12.508: HAGS Status: Disabled (Default: No, Driver status: Unsupported)
14:18:12.509: Driver Version: 32.0.101.6737
14:18:12.509: output 0:
14:18:12.509: name=BenQ XL2420T
14:18:12.509: pos={-1080, -638}
14:18:12.509: size={1080, 1920}
14:18:12.509: attached=true
14:18:12.509: refresh=60
14:18:12.509: bits_per_color=8
14:18:12.509: space=RGB_FULL_G22_NONE_P709

Thanks for your reply, it did in fact appear to be related to the Killer Suite rather than HAGS.

I tried to stream today and was dismayed to see the exact same behaviour appear, even though I had disabled HAGS.

It turned out that I had accidentally switched to using Wifi rather than Ethernet during my successful test yesterday and so attributed it to disabling HAGS.

I'm confused about exactly what the issue with the Killer Suite is. I intended to uninstall it all, as recommended, but only did so with the "Remove Programs" functionality where I could see and uninstall a couple of "Killer" programs. However I still had an internet connection after doing that and realised that I hadn't actually uninstalled the Ethernet driver.

However, before doing that, I just tried streaming anyway and to my surprise, without needing to install anything new (only removing those extra programs), the stream appears to now be working as expected (0 dropped packets) over Ethernet (as well as Wifi still being fine).

I'll be trying again tomorrow in case it again decides not to work...

Also I appreciate the point about having all my monitors going through my GPU. I'm not currently able to as my new GPU has only a single HDMI and then 3 Display Ports and I've only got a bunch of HDMI cables. It doesn't seem to be a problem at the moment, but it is something I'll rectify later on.

Thanks again for your reply and fingers crossed it finally behaves tomorrow.

 

[rockbottom]

YW!

It's been years since I had to deal with Killer but the app is designed to improve game traffic while basically killing everything else, like RTMP.