Does a laptop experience stuttering when a 34-inch external monitor is connected?
Does a laptop experience stuttering when a 34-inch external monitor is connected?
Hi all, I’m facing issues with my daughter’s Alienware M15 R7 laptop that has an RTX 3070 Ti and 32GB RAM.
When I connect the external monitor via HDMI, the performance is extremely poor with stuttering.
Once the monitor is unplugged, the laptop responds instantly and runs smoothly.
The display model is a LC Power M34-UWHQ.
I’ve had no issues with the older HP E243 Office Monitor in 1080p.
What I’ve tried so far:
- Updated GPU and other drivers
- Changed resolution from 1440p to 1080p
- Adjusted refresh rate between 100Hz and 60Hz
- Tried different HDMI cables
- Reinstalled Alienware Command Center
- Reset the monitor settings on the device
- Disabled the GPU
- Reset display settings through CTRL+Shift+Win+B
I also tested the monitor on another laptop, which ran perfectly.
Since the monitor works well with other notebooks and Alienware supports multiple displays, it seems there might be a compatibility issue between the Alienware and this specific monitor.
I’m running out of solutions and have been struggling for weeks… 😓
Maybe someone has a better idea…
The monitor is a 2K ultrawide model with 3440x1440p resolution.
In terms of pixels, it renders 4953600 for 2K and 2073600 for 1080p.
That’s roughly twice as many pixels to process on the LG compared to the HP. This difference might be the key factor here.
Keep in mind that the laptop GPU is significantly weaker than the desktop version of the same GPU.
For example, an RTX 3070 Ti in a laptop performs like an RTX 2070 Super on a desktop.
See the comparison here: https://gpu.userbenchmark.com/Compa...pt...7879vs4048
As per my tasks, I lowered the resolution from 1440 to 1080p, particularly for the 1920x1080 display on the monitor, but this didn’t resolve the issue. The monitor previously worked smoothly, yet the PC would stutter suddenly one day. Also, my 2070S on my desktop runs better at higher resolutions, such as a 32:9 49” from Samsung. My office laptop with an Intel Iris GPU on the CPU can handle this monitor without stuttering, even when plugged in instantly. The problem only appears with the gaming laptop, while the potato office notebook functions well.
You can lower the resolution as well (downscale), though it doesn’t reduce the number of pixels needed to display. The monitor still shows nearly 5 million pixels. Unless you’re only using two-thirds of the screen in 1080p resolution—like the comparison shown here [compare 2K ultrawide (purple) and 1080p (red)]—then there’s likely something else at play. If adjustments are necessary, it might be a software problem; starting from a fresh page would help. This would remove all software conflicts, bloatware, and malware (except firmware rootkits). It’s the simplest and quickest solution. The only drawback is that all personal data on the OS drive will be lost during the format process. Backing up data beforehand is recommended. Creating a new, clean Windows installation is another troubleshooting step, especially since your laptop still stutters even after a fresh OS setup, suggesting a hardware issue.
Solution: cleaned up the operating system
After reinstalling the OS, the laptop performed much better. The monitor no longer had issues and ran smoothly. This confirmed it was a software issue.
There were no stutters or delays on the external display, and I achieved 120 FPS during gaming.
Win needs consistent attention to function properly. There are specific programs available that demand proper understanding of procedures. However, relying solely on the OS without maintenance will eventually lead to problems—such as BSoD or total corruption—making it impossible to boot.
In a similar way, a car can be driven for many years if well-maintained; otherwise, components will fail and the vehicle becomes unusable.
The matter is, I've taken care of the system, updated everything, removed unused programs and always considered software before installing it. I really can't picture what the issue was, perhaps related to G-sync or something similar, but I also can't recall making any changes. Anyway, it's now running. Thanks for your support!