After spending significant time and effort to obtain "DC" screen for 8770w (which is essentially a regular IPS panel with fancy board that converts 8bpc LVDS to 10bpc DP), I have finally got and installed one. All works great, except of the one problem...
It has pretty bad banding / posterization in lower shadows. I have tried profiling it in different modes (full range, sRGB, rec709) - issue persists, and it indeed shows only in the lowest part of the characteristic curve. Mids and highlights are represented fine and show low deviation from reference values.
GPU is HP K4000M, Nvidia drivers installed "as it is", video-card is identified without a hitch.
Banding was not present with the original TN panel using the same GPU.
While checking a software side, I have noticed that Win10 has bit depth set to 8-bit...
My initial reaction was, - "Easy, let's change it in `nvidia-settings` and we're all set":
...but that would be too easy, right? After selecting 10bpc and clicking "Apply" screen went off and back on, only to show that depth stayed at 8bpc. Repeating the above few times yielded exactly the same result and I'm not in a hurry to meet a cliched (and laymen) definition of insanity.
Let's check GPU-Z. So far so good, nothing unusual. Notice the highlighted BIOS version and subvendor string:
Time to delve into other tabs. We are running WDDDM v2.4 which supports GPU dithering, but hey... BIOS version has changed!
Briefly back to `nvidia-settings` to check what is reported by vendor's own utility:
So far, we have two strings for BIOS version:
80.04.5A.00.02 (let's call it an "A") 22.214.171.124.37 (let's call it a "B")
Notice how 2nd one seems to not follow hexademical notation. Lastly, "NVIDIA BIOS" drop-down, reports "A" version:
...and monitor section which confirms that rig is indeed capable of 10bpc, but currently running at mere 8bpc:
Windows "Adapter settings", reports version "B". It's 2019, diversity is a must.
"NVidia inspector" is of the same opinion:
Now, let's use some seriously legit tools and check-in exported BIOS file in `nvflash`:
Here we have two three interesting findings:
Reported vendor is Dell, not an HP. See this link for details. BIOS version is back to "A". Have I already mentioned diversity? MXM module uses MX25L2005 flash storage in WSON-8 packaging. If things go real nasty, we should be able to rescue a patient via Pomona clip and external programmer.
Loading the same file in "Kepler BIOS tweaker" confirms the facts:
EDID settings, courtesy of NVidia Control Panel. Hex dump can be found at the bottom of this post.
...Shall I be worried about "60.02Hz" refresh rate?
Why two different BIOS versions are reported? Anything to do with UEFI (e.g. HP is sideloading its own during boot)?.. Why two different vendors reported? As far as I remember, this is branded HP GPU. Where to get "clean" BIOS of K4000M for future experiments? Ideally from 8770w equipped with "DreamColor" panel from a factory.
Link to the dumps, BIOS ROM and monitor EDID: https://mega.nz/#F!zGgRmQIL!9q2QFZtHuK2RQ-WHXMA4Mg (also attached to this post)
Would really like some help with this.
I Have a HP 8770W Elitebook Workstation.
its powered by an Intel Core i7-3630QM, 32GB RAM and an Nvidia Quadro K4000M.
the Quadro's stock clock is 600 MHz- Core/ 700 MHz- Memory.
its currently overclocked 736 MHz (+135 MHz)- Core/ 1050 MHz (+750 MHz)/ 1100 MHz (+800 MHz)- Memory.
The GPU temps stay fairly decent in summer ( between 70-75 Degrees Celsius) while loaded and CPU around 5 degrees higher. In winter the drop to the mid/high 60's so i believe there is still some space there to push it a bit harder.
The problem is nor Nvidia Inspector nor MSI Afterburner allow me to overclock the core over 135 MHz, the memory i know is maxed out because anything over just bugs out.
Is there anything i can do that would allow me to go over that threshold of 135 MHz.
Hi, does anyone have an HP EliteBook with Dreamcolor display and HP DreamColor Calibration Solution B1F63AA?
If yes, then I would really appreciate if you guide me through the calibration process, cause either I am doing something very stupid or something is really wrong with my software or hardware...
I am sorry if my English is not very good, it's not my native language.