Our Windows 11 laptop has intermittent mouse stutter, sluggish desktop interaction and periods of loud fan noise. It eased yesterday, then felt slow again today, 10 October 2026. We are documenting what we measured and asking others for comparable experiences. We have not identified a single root cause.
The setup and symptoms
The machine is a Dell Precision 5550 with an Intel Core i7-10850H (six cores, twelve threads), 32 GB RAM, Intel integrated graphics and an NVIDIA Quadro T1000. DisplayLink USB display devices are part of the setup. Moving the wireless mouse receiver from the dock directly to the laptop did not eliminate the stuttering. That test did not remove the DisplayLink display path.
We were using desktop AI tools during the investigation. The user reports using the ChatGPT app today; yesterday’s trace also contained processes named ChatGPT. The app name is an observation, not proof that the app causes the mouse stalls. Ambient heat is another possibility, but we have not measured room temperature or compared controlled hot and cool conditions.
9 October: several sources of load, rather than one clear culprit
An early sample showed roughly 86–99% CPU use and only about 2.6 GB of available RAM, with heavy paging. We initially wondered about a memory leak. Short samples did not establish one: high memory use alone is insufficient, and driver memory pools were not showing an obvious upward trend.
Process Monitor exposed repeated Git activity across a large development workspace. We removed its redundant outer repository metadata while preserving the individual project repositories. A later sample was substantially calmer, but the workload was not identical, so this is not a controlled benchmark or a proven universal fix. Removing repository metadata also removes its history; it is not a general troubleshooting recommendation.
Another busy period included thirteen compiler processes building ESPHome firmware on a twelve-thread CPU. Firefox and ChatGPT processes also used CPU. Once the build finished, a short sample fell to about 13% CPU. This explained part of the observed saturation without establishing why every mouse stutter occurred.
Temperature and the kernel trace
We used LibreHardwareMonitor readings and a Windows Performance Recorder kernel trace to look beyond Task Manager averages. Immediately after the later capture, CPU package temperature was 67–71°C, CPU load averaged about 30%, reported core clocks were around 2.8–3.6 GHz and package power averaged about 22 W. An earlier full-load period measured 65–73°C with reported clocks around 1.9–2.4 GHz. These snapshots do not establish thermal throttling or a power-limit cause.
- In the first 30 seconds of the trace, two ChatGPT processes accounted for about 37% of recorded CPU samples.
- A Windows user-mode driver host accounted for about 9%; sampled execution included DisplayLink’s
dlidusb4.dlland NVIDIA graphics code. The installed DisplayLink DLL identified version 11.5.6200.0. - Defender accounted for about 4% of recorded samples. It was active, but was not the largest sampled CPU consumer.
- The longest recorded deferred driver call was about 0.94 ms, and the longest interrupt routine about 0.29 ms.
Those percentages are shares of recorded CPU samples, not whole-machine CPU utilisation. The full trace lost 474 events, and we did not mark the exact moment of a perceived mouse stall. Scheduling-ready latency and symbol-resolved call stacks have not yet been analysed. The trace therefore cannot rule out every brief stall or attribute the symptom to a particular driver. We are keeping raw traces private because they can contain process and file metadata.
10 October: slow again, without sustained CPU saturation in our sample
The next day the laptop felt slow again. A fresh five-second sample averaged about 8.3% CPU, with roughly 12 GB of available RAM and about 1.2 page inputs per second. It did not capture yesterday’s sustained saturation. We have no new temperature reading for this recurrence, so we cannot say whether ambient heat explains it. Yesterday the fan also dropped noticeably after a busy period, but we did not establish whether mouse smoothness changed at the same time.
Similar reports online: useful leads, not confirmation
A July 2022 Microsoft community question describes Windows 11 cursor freezes across multiple USB ports and pointing devices. It is a user’s report, not a Microsoft diagnosis of our machine.
A Windows 11 Logitech community thread discusses animation settings and later moving the receiver away from USB 3 equipment. Its follow-up reports vary, including recurrence after an apparent fix. That makes it a source of test ideas rather than a reliable universal solution.
The closest match to our direct-mouse test comes from an older, November 2016 Windows 10 DisplayLink forum discussion: a user reported driver-host CPU spikes despite plugging the mouse into the laptop, with the issue disappearing when the dock was disconnected. It predates Windows 11 and cannot establish a current regression.
Plugable’s docking-station troubleshooting guidance also describes wireless input lag around USB docking equipment. Input radio interference and delayed display rendering are different mechanisms; we need tests that distinguish them.
The next useful comparisons
- Disconnect the DisplayLink dock completely and use the laptop screen with the mouse connected directly.
- Compare a wired mouse and the built-in touchpad with the wireless receiver, without changing the rest of the workload.
- Compare the same workload with the ChatGPT desktop app open and fully exited, after saving work.
- Record room temperature, CPU temperature, clock readings and power during a recurrence, and mark the exact stall time for another short trace.
- Record the Windows build, display refresh rates, dock model and driver versions before changing settings.
Have you experienced something similar?
We would like to hear from other Windows 11 users seeing intermittent cursor stutter, sluggish desktop interaction or unexpectedly loud fans. Please share your laptop and dock models, Windows build, graphics and DisplayLink driver versions, display arrangement, whether it follows sleep/wake, and whether disconnecting the dock or exiting a particular app reliably changes it. If you have a fix, tell us how long it stayed fixed. CPU and room-temperature readings are especially useful.
Please use the comments below or contact TekOnline. This is an open investigation, not a claim that Windows 11, DisplayLink, Defender or ChatGPT is defective.