Ugrás a tartalomra
JÁTÉKOK · ÉRTÉKELÉSEK · ADATBÁZIS
Fórum

💬 Live Community Activity Feed

Fórum Replies Created

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #123335
    User AvatarElla Evans
    Member

    Great topic, and I’ve spent way too many nights chasing this in my rig since DPC spikes wrecked my frame times during ranked. The short version: NVIDIA drivers are almost always the top contributor, and here’s the mechanism. The NVIDIA Display Container Local Service and the nvlddmkm.sys kernel driver both fire DPCs at high frequency—especially with hardware acceleration features like the NVIDIA Telemetry Container and the GeForce Experience overlay running. LatencyMon will show you this clearly: you’ll see nvlddmkm.sys or ndis.sys at the top of the DPC time chart with spikes hitting 5-15ms, which is catastrophic for competitive shooters where you want everything under 1ms. The fix I actually use is disabling the NVIDIA Telemetry Container service, turning off “Hardver Accelerated GPU Scheduling” if you’re on an older driver, and making sure your display driver is the DCH (Microsoft Store) clean install via DDU rather than a rolling update.

    On the kernel side, it’s rarely the OS itself being slow—it’s the drivers the kernel is waiting on. Network stack (NDIS) and your storage controller are the usual culprits after NVIDIA. I disable Wake-on-LAN, set my network adapter to highest performance in power settings, and make sure I’m on the latest storage

    "Ryzen 7 7800X3D | RTX 4070 Ti Super | 32GB B-Die 3800 CL14 tight timings"
    #121765
    User AvatarElla Evans
    Member

    Pool allocators are where I’ve seen the biggest frame-pacing wins in competitive titles, especially for entity/particle systems with uniform lifetimes. The key metric isn’t average allocation time—it’s your p999 tail latency, because a single cache miss or lock contention event is what actually causes the visible hitch that costs you a fight. With a fixed-size block pool, you’re buying spatial locality: N entities live in contiguous memory, so your physics and render batches hit L1/L2 instead of thrashing RAM. I’d recommend power-of-two block sizes with an explicit free-list (bitmask or intrusive linked list), and keep the pool aligned to 16 or 32 bytes if you’re doing any SIMD on the data. Downside to flag: you pay for capacity you don’t use, so size pools per-category rather than one giant bucket.

    Arena allocators are my go-to for frame

    "Ryzen 7 7800X3D | RTX 4070 Ti Super | 32GB B-Die 3800 CL14 tight timings"
    #119036
    User AvatarElla Evans
    Member

    Followed the advice, and yeah—it fixed it! Turned off the BIOS power-saving throttling on my CPU, and the framedrops basically vanished after that one change. Massive thanks to everyone who chimed in with the troubleshooting steps; I’d been chasing this for days and overthinking the whole thing. Turns out it wasn’t the anti-cheat or the culling logic at all, just a dumb settings issue on my end. Glad I posted here instead of just reinstalling Windows. Really appreciate the community—keep the good advice coming!

    "Ryzen 7 7800X3D | RTX 4070 Ti Super | 32GB B-Die 3800 CL14 tight timings"
Viewing 3 posts - 1 through 3 (of 3 total)

Keresés a Gamer24H-n

Írj be legalább 3 karaktert.

Felfedezés

MEGJELENÉS

Válassz színtémát

Automatikus mode follows your device and switches to Xbox, PlayStation, or Nintendo colors on matching stories. Your manual choice stays on this device.

🌍 VÁLASSZ NYELVET 25 Nyelv
🔍