This a followup to the automated response for more detailed info:
- HP laptop Intel Quad Core i7 processor w/ latest BIOS
- 17.3-in, WVA full high-definition (FHD), LED, AntiGlare (1920×1080, 6 mm) display; typical brightness: 300 nits
- Mobile Intel® HM55 Express Chipset
- ATI Mobility Radeon HD 5850 discrete graphics with 1024-MB of GDDR5 dedicated video memory (32 MB × 32 MB × 8 PCs); Supports BD and or HD-DVD playback with HD decode, and DX11 support and HDMI support Chipset Graphics
- GPU has 1xVGA + 1xDP 1.1 + 1xHDMI 1.2 ports
- Original build with windows 7 64bit
- CCC ver 15.7.1 WHQL certified
These laptops were among the early releases by HP using ATI CCC software with eyefinity. They functioned perfectly outputting to my 3 x 1920x1080 75Hz Dell monitors at 5760x1080.
Everything went sideways after upgrading to windows 10 64bit but I did have eyefinity work for some time until windows update/event changed something. It was not stable thereafter. A clean install of windows made no difference.
Kingfish you are more likely correct that I should look at what windows drivers that were loaded for the Intel integrated graphics chipset. I assumed windows would have got it right since they are so anal with WHQL certified drivers.
I need to find where/how to reload the intel HM55 chipset drivers to see if that rectifies the problem. I know the VGA port on the discrete GPU is not being identified correctly with no EDID info showing in CCC therefore, not allowing for proper GPU scaling. When setting up the desktop properties in CCC I have to go into the VGA Properties screen to deselect the EDID box and reset the resolution to 1920x1080 otherwise it defaults to 1600x900. You would then think that 3 monitors all set to 1920x1080 for 5760x1080 would work....but no. The GPU scaling takes a 5760x1080 images and displays it at 5760x900 I suspect, which is somewhat odd scaling.
So having said all that I will need to investigate what is happing with the VGA graphics port driver info that CCC is using. Again more than likely the intel chipset driver has something to do with it.
Thanks for your advice Kingfish, I will let you know if that is the solution.
