Nice! You are a bulldog!
Monitor stuck on displayport with 640x480
Hi all.. Today after I updated my surface pro, my monitor is stuck in a 640x480 resolution. Which is no good with a 49 inch Samsung monitor. If I plug in the HDMI, it works, but, resolution is not that good like it was on the Displayport. Any tips or tricks to get it working again? For some reason it shows 'Flat Panel, 640x480' when using display port, but the samsung drivers when using HDMI.
I am using the surface dock as well. I tried the displayport of the monitor with other computers and it's working fine. Not with surface. Really need help with this one!
Surface | Surface Pro | Install and update
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
315 answers
Sort by: Most helpful
-
Anonymous
2021-11-23T18:51:15+00:00 -
Anonymous
2021-11-23T04:38:24+00:00 Just a monthly update.
In my frustration I posted a snail mail addressing to Panos Panay to 1 Microsoft Way, with a link and QR code to this thread.
After a few weeks, I was contacted by a nice gentleman from Tier 3 Support, who, together with his colleagues, have been trying to troubleshoot the problem over the past month via emails and phone calls.
Unfortunately, no solution aside from rolling back the driver still.
I'll keep you posted if there's something new.
Cheers.
P.S. My problem is a little bit different from this thread's subject in that newer driver isn't making my screen 640x480, but simply blank/black/undetected/whatsoever.
-
Anonymous
2021-10-26T15:55:10+00:00 Yes, we know the Dock is related. But somehow the driver plays a part as well as we've found out.
Unfortunately, MS ain't going to take the Docks back and refund us, nor are they fixing the driver.
I guess it's different when you're institutional...
-
Anonymous
2021-10-24T17:07:22+00:00 Not sure if related to outdated driver, but occasionally this fuzzy/shaking occurs on mine...
-
Anonymous
2021-10-24T12:37:58+00:00 For some reasons the driver was "upgraded" today without manual intervention.
So I had to revert, again.
Sigh.