This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi there,
I've had a Surface 2 Pro for a month or so. Haven't done anything funky with the display that I know of but recently I noticed some really bad things going on in the dark areas of images on the screen. This is a big deal to me as I use this computer for work in visual effects and photography.
There is severe banding in the dark areas of the image and more worryingly, the display does not seem to be showing any pixels with a brightness darker than 14 out of 255 in the sRGB scale. It just comes out black on the screen. That's 5% of the brightness range gone.
The most basic demonstration of this effect is to go to this page:
http://www.lagom.nl/lcd-test/black.php
For me, all the swatches from 1 to 13, instead of being many shades of grey, are all 100% jet black even with the screen on maximum brightness.
It is certain that the colours are there in the image itself. This can be demonstrated by plugging the signal from the Surface into a separate Dell monitor via HDMI. Presto - you can see all the shades of grey again. But on the screen of the Surface
I've tried fixing the problem by applying different ICC profiles etc. The sRGB IEC61966-2.1 profile gives the best image, but the best image is horrible as described above. There is severe banding when displaying this image (http://www.lagom.nl/lcd-test/gradient.php)
The most interesting fact is this. My workmate also has a Surface 2 Pro, bought months earlier at a different store. I asked him to check his display using the same web pages and he sees exactly the same errors as me. Lots of banding. All greys darker than 14 are crushed to black. Is this a systemic problem with the display driver? A LUT applied by the bios?
Problem might be the same as mentioned here http://www.surfaceforums.net/forum/microsoft-surface-pro-2/7270-recent-update-killed-video-quality.html
I have applied all Microsoft's recommended updates including the most recent one.
Look forward to any tips, hints, fixes, etc. Cheers,
Stuart
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.
Hi again all,
After rebooting my Surface, I noticed that all the banding is gone and my gradients look perfect again.
I believe the problem was that the display driver had crashed and somehow put the display into 16-bit color. Has anyone tried rebooting and checking the gradient again?
Mines still ugly. Hulu app very jagged since its all black and grey gadients
C'mon Microsoft, officially fix this!
The fact that the majority of people who have this issue had it fixed with new generic Intel drivers, which doesn't work for me, leads me to believe mine is a hardware issue. I have the same problem when booting to Ubuntu as well which pretty much seals it as a memory or firmware problem.
Whether or not the firmware release scheduled for the 14th of this month will fix it or not, who knows. I'm probably not going to wait to find out and will exchange mine at BB before then.
Speaking of firmware, those of you who had the issue solved with the newest Intel drivers, did you also get the December firmware update?
Thanks Suart, this fixed the problem for me too!
My Pro2 screen is born again!
Also, it almost solved the known Wacom precision problem at the upper corners of the screen..
Still there, but so much better.
C'mon Microsoft, officially fix this!
Matteo
I would prefer to get a full fix from Microsoft. Or to at least know they are aware and working on it.
Has Microsoft acknowledged this as a problem? It seems to affect only a small minority of us users from the forum posts I've read. I'm still not convinced it isn't just software, in that if we knew what registry entry to tweak it could be easily fixed.
