Dell actually made a firmware verison that address it and people reported that it indeed fixed it. But guess what? You cannot download it! The only way to get newer FW was to buy a monitor from a newer production batch.
No you can't have the firmware update. You can exchange it for a refurbished monitor and "should" get the new firmware.
There's a 53 page Dell forum thread about that disaster of a monitor: https://www.dell.com/community/Monitors/UP3214Q-UP2414Q-1-2-...
Amazing that nearly 10 years later they still can't update monitor firmware in the field.
If it's going to need firmware updates, it should be able to get firmware updates.
I found a forum thread on Dell's forums about it ages ago, I remember people sharing the refresh rate override fix, but I wasn't aware that Dell did eventually "fix" it in a later batch of monitor.
That monitor did actually die for me literally 2 months ago(and just few months out of warranty, typical) but I was very glad to replace it with something else.
Before high refresh rate screens, I was one of those people that would turn off v-sync in games because the additional input lag bugged me just enough, JUST on the edge of perception. I wasn't even a competitive player or particularly good, but it felt....mushy. Similar problem with playing old NES games on modern LEDs.
For many years I had a mechanical keyboard I loved, but slowly and subtly over time the enter key would miss a keystroke. It was like 1 out of 300 times maybe, but it was just often enough for me to start doubting my own fingers. Finally couldn't take it anymore and just bought a new keyboard.
Just goes to show that very subtle problems in a computer interfaces can have a big impact.
I have to flip it between 59.95Hz and 60 Hz in the windows advanced settings, changing that setting basically makes the monitor re-initialize and then everything is fine. It happens every time I wake the monitor from sleep (ie: my computer rarely, if ever goes to sleep, but the monitors will turn off after 10 minutes of inactivity)
This only really happens with games. DirectX or Vulcan doesnt matter. Doesnt affect things like youtube, plex etc.
But any game in fullscreen or borderless windows on that screen, i have to basically just change that setting back and forth to keep my sanity.
It worked and sounded great in Windows; it also worked and sounded great in Linux, with one exception: the card supported ISA PNP, which was great, but the kernel module for the sound card wouldn't load unless I did `cat /proc/isapnp` first.
I had no idea why, and it took a few reboots and trial-and-error to narrow it down to this janky workaround, but it worked so I just configured modprobe to run `cat /proc/isapnp > /dev/null` before trying to load the module and I never had to worry about it again.
Technology sure is weird sometimes.
Every other boot, the BIOS would fail to initialize the controller, leaving the computer stuck at a "non-bootable device" error until I could manually reboot it.
My solution? A perpetually plugged-in USB flash drive with a small boot loader that would simply reboot the machine again, set to a lower boot priority than the SATA RAID controller.
It was pretty stupid, but if it's stupid and it works...
Open-source is the best worst-thing ever.
Would probably need to use Custom Resolution Utility to define a refresh rate that you really want.
right click on desktop>Display Settings>scroll to bottom>Advanced Display Settings
Then select your monitor in the drop down and the refresh rate. Which is negotiated by the monitor and the video card. I suppose unplugging and pluggin the cable back in may help. But ive changed cables, bought new ones, tried adapters to change the type (ie: hdmi to DP etc).
Its just something with the display. And Im too lazy to bend over and unplug/plug it in, so i just do the refresh rate trick.
I've had it happen on more than one phone, and I'd also note that my Sony headphones don't skip.
You could splice cable DDC lines to I²C EEPROM programmed with patched EDID data.
All I can figure is that it might have some motion blur or other interpolation feature and it's holding frames back after receiving them and displaying them from an internal buffer at 60Hz. In this case, you'll get occasional (but rare) tearing/stuttering no matter what since the computer's clock and the LCDs hypothetical clock are not syncronized.
The easy and lazy solution is to generate your own clock signal at the rate you want, and then to buffer the data from their closeish-clock to your own. Obviously this has the downside of an extra frames latency and the occasional dropped frame when the clocks drift.
Even so, the anti-ghosting compensation algorithms typically only work at one rate.
To save you the story of weeks-long debugging efforts - the problem turned out to the monitor. It was a Dell Ultrasharp 25", and (as I now know) they all had an issue where the monitor would freeze roughly every 20 seconds for a frame, because the monitor was advertising the refresh rate to windows as 59.95Hz but it was actually refreshing at 60Hz internally - the timing would get out of sync pretty much exactly every 20 seconds, causing the monitor to "pause" and freeze - which looked like stutter when playing games. The solution was using some kind of program(forgot the name now) which basically overrode the refresh information being sent from the monitor and forced windows to refresh at exactly 60Hz and no less - then it worked fine. But of course if you used it with a PS4 then you didn't have any way to do that and just had to suffer this stutter every 20 seconds.