Weird stuttering across all OS

Occasional Visitor

Hi!

 

I have this weird issue that causes stuttering and slowdowns in entire system: mouse become jumpy, sound's cracking, animations are jerky. Things that triggers this issue:

- scanning for new devices via device manager

- installing or updating some drivers (network, audio)

- launching some games (Apex Legends) though it happens randomly few times a month

- rarely happens randomly on it's own.

Stuttering persist until I restart PC. Also reboot take a lot of time when it occurs. Happens in all versions of Windows 10 since two years ago. It's also present in Windows 11.

 

Things I've already tried:

- scannow

- clean install

- removing periferals

- disabling devices

- updating drivers and BIOS

- disabling XMP profiles

- temps are OK

 

My specs:
CPU: AMD Ryzen 5 3600
RAM: 16,0GB
Motherboard: Micro-Star International Co. Ltd B450 GAMING PLUS MAX
Graphics: 4095MB NVIDIA GeForce RTX 2060 SUPER 

Storage: 931GB PNY CS3030 1000GB SSD 
Audio: NVIDIA Virtual Audio Device

Network: Realtek PCIe GbE Family Controller

 

1 Reply
Specs:
- Ryzen 5 3600X
- Crucial 32GB kit (4x8GB)
- ROG Strix GTX 960
- Crucial P5 256GB NVMe PICe3.0
- MSI MAG B550 TOMAHAWK (MS-7C91)

Issue:
exactly what's described above, only Windows freezes for half a second every like 10/15 seconds when audio is playing (YouTube, etc), and every like THREE seconds when I try to play Osu!

Failed trials:
- firstly started experiencing the issue on my "normal" Windows installation, then tried
- reinstalling Windows 10 21H2 completely fresh
- updating everythin possible on the fresh install
- reinstalling all the latest drivers on the completely fresh install
- reinstalling the main drivers (Wacom tablet, GPU, Corsair keyboard (iCUE), Razer Mouse (Synapse)) to a known "good" version (pretty much à là "go older than 1yo and you're safe because the most recent the more sh**y it seems they be")
- reinstalling of course Osu! but that obviously isn't the cause
- not gonna even try to contact Microsoft, their b*crap will probably not gonna help like they always do

Maybe a community post like more than half a year later after this one had received literally zero interest, is gonna change something?
Doubt it.
We'll see (a whole lot of nothing and another whole lot of zero consideration again for another half a year or more when somebody in the next major Windows release still has this stupid **bleep** issue).