I just had a bear of a weekend with my i3 NUC. The short version is that I do not believe that the latest drivers output "full range" correctly, and the registry switch does not appear to work (at least for me) with the most recent driver version. Setting quantization to full range in the drivers and with registry entry results in significantly elevated blacks, measured at 0.3cdm2 vs my televisions true calibrated black point of 0.045cdm2.
Interestingly, the drivers versioned 10.18.10.3958 (https://downloadcenter.intel.com/search?keyword=153330
) do not exhibit this behaviour, and do not have the "quantization range" setting in the control panel. The registry setting does however work and 0-255 output can be achieved via hdmi out with appropriate black levels.
The only way for me to get correct black and white levels out of the current drivers with my i3 nuc is to set drivers: limited, input range: limited, TV: limited. The desktop actually gets compressed down to 16-235 so there are not any crushed blacks or whites for desktop relative to video.
More importantly, I was also able to conclude that Intel's DXVA implementation is broken, and does not output correct colors relative to other rendering methods. Using my meter I observed that white and primary color outputs using DXVA decoding and rendering measured consistently and significantly different than the same video files decoded and rendered using XBMC Software, XBMC Pixel Shaders, and MadVR. Additionally, the latter 3 all agreed with same color measurements taken using HCFR GDI Image Generator, and png's in Firefox. Back when I had NVIDIA driving my htpc I did not have this problem.
For owners of Intel graphics who DIY/professionally calibrate their displays you must choose from a set of non-optimal scenarios.
1 - Calibrate your display using video files rendered via DXVA.
Pro: You are calibrating with the videochain you will be viewing media from
Con: Everything else will have varying levels of error in calibration
2 - Calibrate using any non-DXVA chain. Render and decode media files using, for example, XBMC with pixel shaders or software implementations
Pro: Consistent colors across all applications
Con: Software decoding is cpu heavy and causes my NUC fan to turn on, which is highly annoying.
3 - Chuck it and get hardware which works as advertised.
I went with 1 as I value silence, and am able to have a setup where all of my decoding goes through dxva. The error isn't large enough that I care or notice in system menus etc.
Hardware: Intel NUC D34010WYK, Samsung ES8000 LCD, Denon 2310 AVR
Software: Windows 7, XBMC (Kodi) 14