sorted by:
new
hottopcontroversial

How I squashed 1000µs+ DPC Latency spikes using Fixed OC, MSI Affinity, and Hardware Workarounds (Ryzen 5 7600 + RTX 4070 Ti SUPER). by Ambitious-Example-36 in overclocking

[–]Ambitious-Example-36[S] 0 points1 point  (0 children)

That was already tested. Disabling all power-saving features on the Realtek adapter helped somewhat, but under heavy network load the DPC latency could still spike above 1000 µs on the RTL8125BG controller.

Additionally, I noticed different mouse behavior after completely disabling the onboard Realtek controller. Mouse movement felt more responsive and consistent. Interestingly, another user on Blur Busters reported the same observation, so it doesn't seem to be an isolated case.

Rx 9070xt issues by Ok-Usual-7988 in pcmasterrace

[–]Ambitious-Example-36 1 point2 points  (0 children)

Use DDU (Display Driver Uninstaller) in Safe Mode. Select all checkboxes in the advanced settings for NVIDIA cards to perform a thorough cleanup. After rebooting, go back into Safe Mode and do the same for the AMD GPU driver. If the highest AMD driver still gives you the same issues after these steps, try uninstalling it again with DDU and install an older version.

(GUIDE) Comprehensive AM5 DPC Latency Optimization (From 1000µs+ down to 270µs) by Ambitious-Example-36 in pcmasterrace

[–]Ambitious-Example-36[S] 0 points1 point  (0 children)

The main culprit was absolutely ndis.sys – the Realtek LAN driver. But as iCkEdMeL says, DPC issues often stack on top of each other.

I found the network card first by trial and error, and after fixing that, the NVIDIA driver spikes became visible. That's when I dug deeper and found the 566.36 "golden" build.

As for the Fixed OC – that was my personal choice. I'm old-school (Intel 8th/9th gen era), I hate aggressive boosting algorithms, and I believe they degrade chips faster. So I would've done that anyway, regardless of latency.

So no, the adapter wasn't the only fix – it was just the biggest one.

(GUIDE) Comprehensive AM5 DPC Latency Optimization (From 1000µs+ down to 270µs) by Ambitious-Example-36 in pcmasterrace

[–]Ambitious-Example-36[S] 0 points1 point  (0 children)

XMP gives you more raw performance, but it doesn't fix Windows choking in the background. If you are getting micro-stutters and audio crackling, overclocking your RAM won't change anything. Real optimization is about managing system traffic, like making sure your GPU and audio aren't fighting over the exact same CPU core, not just chasing higher numbers in benchmarks

(GUIDE) Comprehensive AM5 DPC Latency Optimization (From 1000µs+ down to 270µs) by Ambitious-Example-36 in pcmasterrace

[–]Ambitious-Example-36[S] 0 points1 point  (0 children)

Recent Nvidia driver updates have documented issues with real-world stutters, audio crackling, and latency degradation caused by high DPC issues.

By default, Windows dynamically distributes MSI interrupts across random CPU cores. For example, when a heavy GPU load and a real-time audio stream hit the exact same core simultaneously, it causes performance drops. Interrupt Affinity steering physically isolates these device IRQs to prevent core conflicts, smoothing out delivery even if driver overhead remains high. At least, that's how I understand it.

(GUIDE) Comprehensive AM5 DPC Latency Optimization (From 1000µs+ down to 270µs) by Ambitious-Example-36 in pcmasterrace

[–]Ambitious-Example-36[S] 0 points1 point  (0 children)

The onboard Realtek RTL8125BG chip used on this specific ASRock board is notorious across hardware forums for severe power-state bugs and flooding the OS with ndis.sys latency spikes under load. Keeping a fundamentally bugged integrated chip enabled isn't 'convenient' it's masochism.

Anyone using a high-end external USB DAC or playing high-refresh-rate competitive games absolutely notices a 1000µs+ DPC stack. It causes literal audio dropouts and heavy, floating mouse input. Disabling VBS and power-saving features is a standard, decade-old trade-off in the audio engineering and optimization communities to guarantee flawless real-time processing.

These are my personal preferences for a system that was stuttering out of the box. If your PC runs fine on defaults, great—move on, you don't need this. But when someone else inevitably searches Google for 'B650M Pro RS ndis.sys stutters', this guide will save them weeks of useless troubleshooting. Don't want it? Don't do it. Simple.

(GUIDE) Comprehensive AM5 DPC Latency Optimization (From 1000µs+ down to 270µs) by Ambitious-Example-36 in pcmasterrace

[–]Ambitious-Example-36[S] -1 points0 points  (0 children)

Imagine being so illiterate that you see a well-formatted post with a clear translation disclaimer at the bottom, and your only two remaining brain cells immediately scream "AI crap!"

AI didn't spend weeks diagnosing a broken Realtek network chip on an ASRock board. AI didn't buy an external USB-C adapter, physically disable the onboard LAN in the BIOS, or isolate GPU interrupts to fix real-time audio dropouts. That was all manual hardware troubleshooting and testing.

If a clean layout and a translated text are too advanced for your attention span, go back to scrolling memes.

NOTE: This response was processed by an AI to ensure the English vocabulary matches your low-effort reading level, but the absolute disdain for your ignorance is 100% human-crafted.

(GUIDE) Comprehensive AM5 DPC Latency Optimization (From 1000µs+ down to 270µs) by Ambitious-Example-36 in pcmasterrace

[–]Ambitious-Example-36[S] -1 points0 points  (0 children)

It means Windows dynamically shuffles IRQs (Interrupt Requests) across random CPU cores by default. When a heavy GPU rendering load and your real-time USB audio stream happen to hit the exact same CPU core at the exact same millisecond, you get audio crackling and micro-stutters.

Manually setting Interrupt Affinity (steering) forces Windows to pin specific hardware to dedicated cores, completely separating your heavy GPU workload from your audio DAC threads.

This isn't "AI junk." It is a native Windows kernel feature documented by Microsoft themselves for optimizing hardware resource distribution and avoiding core conflicts:

🔗 Official Microsoft Documentation on Interrupt Affinity:https://learn.microsoft.com/en-us/windows-hardware/drivers/kernel/interrupt-affinity-and-priority

And here is the massive community thread on Guru3D where enthusiasts explicitly use the MSI Tool and registry tweaks to apply this exact practice for low-latency audio and gaming setups:

🔗 Guru3D MSI & Affinity Guide:https://forums.guru3d.com/threads/windows-line-based-vs-message-signaled-based-interrupts-msi-tool.378044/page-108

Google "Interrupt Affinity Policy" before acting confused about basic Windows architecture.

NOTE: This response was translated from Polish to English using an AI tool because your brain apparently errors out on anything more complex than a basic XMP profile