No FPS gaming possible

[LaggyTyp]

I want to believe it, but I can't quite. Our distribution box on the street is fiber optic compatible (FTTC). Only the 100 meters into the house are copper cables. Why should that be a problem? I have an 8ms latency to the AWS gaming server. Why would it be any better with FTTB/FTTH? Incidentally, friends with FTTH keep having the same or similar problems.

I had the program configured incorrectly. The interval was set to 0.0 seconds instead of 1.

https://ibb.co/MDys7f7K

[darkbebe]

your problem is from isp & you're probably right switching from fttb ftth etc won't change anything , plus your friend get the same problem ! even with vdsl it should be really great if the isp was good. they are so focused on managing ping / download speed / TV & phone service. they neglect udp packet management for fps games .
the fact that starlink is perfect proves that there is nothing to do with your hardware or software
i'm looking at a cs 2 video of brazilian playing with starlink and it looks a dream for me . the hit register is so great ! sadly we can't have good starlink connection quality yet on my island https://www.youtube.com/watch?v=sOlRl12y8Wc

[LaggyTyp]

VDSL + Telekom = Horror (Peering)
DOCSIS + Vodafone = Horror (Dual-Stack)
DOCSIS + O2 = Double Horror (DS-Lite)
VDSL + O2 = Sometimes maybe good, sometimes maybe shit
StarLink = Very Good (but only ~180° line of sight)

My neighbor is moving a few houses down (same street) and has fiber to the home (FTTH) right to his office.

5000 Mbps download and 2500 Mbps upload

LatencyMon

When I disable settings on my network card, such as FlowControl or Interrupt Moderation, it doesn't improve as expected, but actually gets worse.

My thought is: You're disabling options, so your CPU has to work harder...

LatencyMon reports terrible performance. Since I moved my (external) NIC (TPLink TX201 with an RTL8125B chip) and GPU to other cores, the values ​​seem to have improved significantly, and Battlefield 6 also runs better (Hitreg). No, not perfectly, but better.

It's like a puzzle.

Approximately 5 hours (watching Twitch/YouTube, working and playing BF6)

Screenshot (1245).png (47.27 KiB) Viewed 274 times

Screenshot (1246).png (60.46 KiB) Viewed 274 times

Screenshot (1247).png (94.72 KiB) Viewed 274 times

_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be suitable for handling real-time audio and other tasks without dropouts.
LatencyMon has been analyzing your system for 4:46:03 (h:mm:ss) on processors 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14 and 15.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DIRECTOR
OS version: Windows 11, 10.0, version 2009, build: 26100 (x64)
Hardware: System Product Name, ASUS
BIOS: 2204
CPU: GenuineIntel 12th Gen Intel(R) Core(TM) i9-12900KF
Logical processors: 24
Processor groups: 1
Processor group size: 24
RAM: 32613 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed (WMI): 320 MHz
Reported CPU speed (registry): 3187 MHz

Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.


_________________________________________________________________________________________________________
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_________________________________________________________________________________________________________
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.

Highest measured interrupt to process latency (µs): 370,90
Average measured interrupt to process latency (µs): 3,662634

Highest measured interrupt to DPC latency (µs): 256,40
Average measured interrupt to DPC latency (µs): 1,637087


_________________________________________________________________________________________________________
REPORTED ISRs
_________________________________________________________________________________________________________
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

Highest ISR routine execution time (µs): 218,190775
Driver with highest ISR routine execution time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation

Highest reported total ISR routine time (%): 0,004787
Driver with highest ISR total time: Wdf01000.sys - Kernelmodustreiber-Frameworklaufzeit, Microsoft Corporation

Total time spent in ISRs (%) 0,004945

ISR count (execution time <250 µs): 9050921
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-1000 µs): 0
ISR count (execution time 1000-2000 µs): 0
ISR count (execution time 2000-4000 µs): 0
ISR count (execution time >=4000 µs): 0


_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

Highest DPC routine execution time (µs): 539,105742
Driver with highest DPC routine execution time: ntoskrnl.exe - NT Kernel & System, Microsoft Corporation

Highest reported total DPC routine time (%): 0,012797
Driver with highest DPC total execution time: Wdf01000.sys - Kernelmodustreiber-Frameworklaufzeit, Microsoft Corporation

Total time spent in DPCs (%) 0,016265

DPC count (execution time <250 µs): 14706364
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 32
DPC count (execution time 1000-2000 µs): 0
DPC count (execution time 2000-4000 µs): 0
DPC count (execution time >=4000 µs): 0


_________________________________________________________________________________________________________
REPORTED HARD PAGEFAULTS
_________________________________________________________________________________________________________
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.

NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.

Process with highest pagefault count: svchost.exe

Total number of hard pagefaults 4477
Hard pagefault count of hardest hit process: 942
Number of processes hit: 14


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 203,395661
CPU 0 ISR highest execution time (µs): 218,190775
CPU 0 ISR total execution time (s): 1,530103
CPU 0 ISR count: 949566
CPU 0 DPC highest execution time (µs): 325,886727
CPU 0 DPC total execution time (s): 42,357743
CPU 0 DPC count: 3555708
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 101,274090
CPU 1 ISR highest execution time (µs): 201,165359
CPU 1 ISR total execution time (s): 18,840577
CPU 1 ISR count: 8101355
CPU 1 DPC highest execution time (µs): 539,105742
CPU 1 DPC total execution time (s): 19,217175
CPU 1 DPC count: 8365789
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 48,896196
CPU 2 ISR highest execution time (µs): 0,0
CPU 2 ISR total execution time (s): 0,0
CPU 2 ISR count: 0
CPU 2 DPC highest execution time (µs): 99,904612
CPU 2 DPC total execution time (s): 1,074041
CPU 2 DPC count: 834879
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 42,789048
CPU 3 ISR highest execution time (µs): 0,0
CPU 3 ISR total execution time (s): 0,0
CPU 3 ISR count: 0
CPU 3 DPC highest execution time (µs): 104,148415
CPU 3 DPC total execution time (s): 0,307495
CPU 3 DPC count: 259856
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 43,609038
CPU 4 ISR highest execution time (µs): 0,0
CPU 4 ISR total execution time (s): 0,0
CPU 4 ISR count: 0
CPU 4 DPC highest execution time (µs): 532,368685
CPU 4 DPC total execution time (s): 0,314797
CPU 4 DPC count: 110383
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 46,385484
CPU 5 ISR highest execution time (µs): 0,0
CPU 5 ISR total execution time (s): 0,0
CPU 5 ISR count: 0
CPU 5 DPC highest execution time (µs): 537,946031
CPU 5 DPC total execution time (s): 0,319090
CPU 5 DPC count: 203017
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 45,227736
CPU 6 ISR highest execution time (µs): 0,0
CPU 6 ISR total execution time (s): 0,0
CPU 6 ISR count: 0
CPU 6 DPC highest execution time (µs): 94,118607
CPU 6 DPC total execution time (s): 0,336651
CPU 6 DPC count: 154530
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 45,327588
CPU 7 ISR highest execution time (µs): 0,0
CPU 7 ISR total execution time (s): 0,0
CPU 7 ISR count: 0
CPU 7 DPC highest execution time (µs): 91,304675
CPU 7 DPC total execution time (s): 0,307675
CPU 7 DPC count: 158445
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 55,841612
CPU 8 ISR highest execution time (µs): 0,0
CPU 8 ISR total execution time (s): 0,0
CPU 8 ISR count: 0
CPU 8 DPC highest execution time (µs): 536,625353
CPU 8 DPC total execution time (s): 0,411459
CPU 8 DPC count: 135011
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 46,560131
CPU 9 ISR highest execution time (µs): 0,0
CPU 9 ISR total execution time (s): 0,0
CPU 9 ISR count: 0
CPU 9 DPC highest execution time (µs): 529,981801
CPU 9 DPC total execution time (s): 0,419263
CPU 9 DPC count: 140042
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 48,696955
CPU 10 ISR highest execution time (µs): 0,0
CPU 10 ISR total execution time (s): 0,0
CPU 10 ISR count: 0
CPU 10 DPC highest execution time (µs): 530,185755
CPU 10 DPC total execution time (s): 0,339418
CPU 10 DPC count: 136256
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 46,654353
CPU 11 ISR highest execution time (µs): 0,0
CPU 11 ISR total execution time (s): 0,0
CPU 11 ISR count: 0
CPU 11 DPC highest execution time (µs): 106,588328
CPU 11 DPC total execution time (s): 0,286082
CPU 11 DPC count: 100439
_________________________________________________________________________________________________________
CPU 12 Interrupt cycle time (s): 48,798580
CPU 12 ISR highest execution time (µs): 0,0
CPU 12 ISR total execution time (s): 0,0
CPU 12 ISR count: 0
CPU 12 DPC highest execution time (µs): 528,672733
CPU 12 DPC total execution time (s): 0,402768
CPU 12 DPC count: 150904
_________________________________________________________________________________________________________
CPU 13 Interrupt cycle time (s): 42,706727
CPU 13 ISR highest execution time (µs): 0,0
CPU 13 ISR total execution time (s): 0,0
CPU 13 ISR count: 0
CPU 13 DPC highest execution time (µs): 535,899278
CPU 13 DPC total execution time (s): 0,262770
CPU 13 DPC count: 120082
_________________________________________________________________________________________________________
CPU 14 Interrupt cycle time (s): 47,283577
CPU 14 ISR highest execution time (µs): 0,0
CPU 14 ISR total execution time (s): 0,0
CPU 14 ISR count: 0
CPU 14 DPC highest execution time (µs): 535,093505
CPU 14 DPC total execution time (s): 0,332686
CPU 14 DPC count: 189617
_________________________________________________________________________________________________________
CPU 15 Interrupt cycle time (s): 43,956575
CPU 15 ISR highest execution time (µs): 0,0
CPU 15 ISR total execution time (s): 0,0
CPU 15 ISR count: 0
CPU 15 DPC highest execution time (µs): 126,584562
CPU 15 DPC total execution time (s): 0,312759
CPU 15 DPC count: 91438
_________________________________________________________________________________________________________

Perhaps your eagle eyes will spot something?

[LaggyTyp]

Screenshot (1248).png (102.29 KiB) Viewed 274 times

[Slender]

that is not pc, that is not windows, that is not network.
say u understand.
say it, say it!!!

[darkbebe]

Screenshot (1248).png

stop killing yourself with computer settings bro focus on internet . They way you're describing your problem it looks like exactly the same as mine , maybe you can do more test with your neighbour about starlink ! if he has more view from his home on the starlink's satellite & sky , lend him your material & put his adress on your account to test at his house. if it's working too , it will end your suffering of research & you'll know it's 100% the isps.

[LaggyTyp]

First off: I appreciate your contributions and your interest in my problem.

Yes, this issue is really driving me crazy, but I can't accept it like this.

Let's just say it's due to O2's VDSL. Okay. But then it has to be possible to make it VISIBLE and TRACEABLE. It has to be visible, measurable, and documented.

[MK92]

Why it would be traceable? In what metrics? The problems due to electrcity, for example, are also not really measurable as all software and hardware tests would be perfectly fine, but the problem would still be there.

As long as you don't test your PC & monitor at other house, preferably the one with fiber optics and different ISP, all "fixes" are just useless. Only AFTER you test that you can start fixing the issue, because guess what, I bet that at other house (not on the same street - try it somewhere at least 2-3 km away) would be working fine.

And then you will have only one option - move to another house, because your house simply has a combination of bad routing, bad coax cable, maybe also bad and old electrcical installation, and some kind of EM/RF interference, which can even travel through the air, not just cables - and this can also be caused by old and faulty coax copper cables by the way.

[LaggyTyp]

Here's the thing...

I took a picture of my Telekom wall socket (TAE socket) and posted it in a forum. The response was that the cable wasn't connected correctly because it wasn't connected with a special tool, which apparently is how it has to be connected.

I bought the tool and re-clipped the cable yesterday.

Then this happened:

According to the DSL info on my Asus router, two things changed:

1) The download bandwidth increased by about 7 Mbps.

2) My INP increased from 63 (download) and 30 (upload) to 63 (download) and 34 (upload).

Since this, gaming has become significantly worse again, and I started complaining in the forum again.

I reinstalled the cable again today. I shortened it a bit and clipped it in properly.

Now my router is showing me an INP of 63 (download) and 30 (upload) again, and gaming is better again.

Screenshot 2025-12-26 at 12-26-22 ASUS WLAN-Router DSL-AX82U - DSL-Report.png (227.34 KiB) Viewed 81 times

Could this be related? Because the gaming performance degradation started immediately after that and disappeared just as quickly.

Background: The cable was slightly smeared with wall paint at the clip point.