Jump to content

Search the Community

Showing results for tags '8770w'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Forum Introduction & Feedback
    • Site Announcements, Rules & New Member Intros
    • TechInferno Forum Feedback
  • Tech News & Reviews
    • News & Reviews
  • Notebook Discussion
    • General Notebook Discussions
    • Notebook OEM Subforums
    • What Notebook Best Fits My Needs?
    • Legacy Articles
  • Desktop & General Hardware
    • General Desktops Discussion
    • Desktop Hardware
    • Overclocking, Cooling & Build Logs
  • Software, Networking & Gaming
    • PC & Console Gaming
    • Video Driver Releases & Discussion
    • Networking
    • General Software Discussion
  • Everything Else
    • Off Topic
  • Legacy Section (Not Actively Supported)
    • DIY e-GPU Projects

Categories

  • SVL7 & Klem VBIOS Mods
    • AMD
    • Alienware M11x R3
    • Alienware M14x R2
    • Alienware M17x R4
    • Alienware M18x R1
    • Alienware M18x R2
    • Kepler VBIOS
    • Lenovo Y400-Y500
    • Lenovo Y410p-Y510p
    • Lenovo Y580-Y480
    • Legacy BIOS/VBIOS
    • Maxwell VBIOS
    • Sony Vaio SVS13 / SVS15 series
  • BAKED BIOS Mods
    • Clevo
  • Utilities

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Steam


AIM


MSN


Website URL


Yahoo


Jabber


Skype


Location


Interests


Occupation

Found 5 results

  1. 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") 80.4.33.0.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? To summarize: 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) K4000M.zip
  2. Hello, I'm new here and heard this was the place to go for help. I've got an HP 8770w that came with the Firepro M4000 originally. I bought a Nvidia K4100M and the corresponding heat sink as a replacement. I've installed it but get a black screen at startup. It almost seems like it tries to start and then the light on my mouse goes out and it tries again. I was going to delete the old drivers and install the new ones after it started up. Should I install drivers first or am I missing something else? I can easily do the disassembly/reassembly stuff but my knowledge is limited when it comes to software. Any help you guys can give me is greatly appreciated!
  3. 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.
  4. Well, after my ZBook died because of faulty bios (hardware related) and it had a K4100M (OC) with HP vBios, i wanted it to be on my old 8770w, but it just gave me no screen output (laptop screen) only on VGA (didn't test on DP cuz i got no DP Monitor nor cable) and i liked how the K4100M had better performance than the K4000M (Well the oc made the bandwidth go from the original 102 GB/s, to 200 GB/s [Not stable at all in some games like Rust, or Heavy iray rendering] vs the K4000M 89 GB/s [BTW I couldn't find any SAFE way to oc it] So I decided to make some research and testing,, Long ago before I started searching on how to do this change of gpu i found out that people had 980m in their 8770w and also k5100m without any errors, just by modifying the drivers, i tried so and failed. This is my laptop Specs: HP EliteBook 8770w Quadro K4000M Intel i7 3820mq 2x500GB WD Blue (Only ones i had around empty in my inventory) 20GB of ram (I know its not "correct" but i used 3x4GB and 1x8GB RAM sticks) 1080p Screen Non-Dreamcolor Windows 10 Pro 64 Bits - Creators Update (Btw im in Insider Program) Notes: This laptop has no Optimus support as far as i know, I havent tested on more vbios, only on 1 OC Dell Vbios I didnt test video output on DP, Beacuse i have no DP Monitor nor a cable, and i dont need it, at all. The laptop didnt give any video on integrated screen, only on vga with OC HP vbios and aswell Original (Backed up) vbios, only with the Dell vbios made successful output to laptop screen. There was video going on at VGA without nvidia drivers, if i installed the drivers the screen had artifacts like random colors then the laptop freezes and shutdowns with errors, even with dell vbios. GPU temp was higher than usual, even when it wasn't on high load. I was able to run Besiege at 5 fps without a driver (Only with Microsoft Display adapter). So by some hours of testing this were the results: I replaced the K4000M with the K4100M, I used windows recovery thing at startup (since the nVidia drivers from K4000M bugged the hell out the screen output) then I selected the CMD option, did cd to the folder where i had nvflash, flashed my gpu from there, with a OCed DELL vbios, (link), and then restarted my laptop, I was so excited because i made it make video output through the laptop screen, and then i loaded windows normally and the drivers started to bug the screen and then windows crashed after 4m every time i logged to windows (even without logging in), it said Video tcp failure (or something) and Watchdog_DPC_violation, So i used a fresh windows install (from a HDD i had around), it did give 1080p video output to laptop screen and i didnt test anything at all, so then installed Normal Nvidia drivers (from nvidia not hp neither dell) and then it started to bug again, And well, Then i tried using Ubuntu (17) and the screen give 1080p output without problems, i was going to install nvidia drivers but it was too difficult for the short time i had to test, so i didn't finished up testing with Ubuntu, As some dude told me at other forums that it might be an Optimus driver bug or something, so later on ill try testing with modified drivers. Also the GPU temp was high, i didn't check out the temp, but the laptop was too hot for normal use and used too much battery life (i found out when i was playing around with Ubuntu at my couch). And months before, I found out that in Nvidia page it said that the K4100M worked only on Haswell Generation (4th gen), and not Ivy Bridge, now it says that supports Shark Bay, which is kinda new, since that "option" wasn't there before. This is what ill do next time i make another test: I'll use another vbios a not OC one, just a normal one, Modify nVidia Drivers to try removing optimus (if posible) Finish testing up in Ubuntu Try to use older Drivers to see if anything happens. Post the pics of the Artifacts and a video of besiege running with Default video Driver
  5. 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... PS I am sorry if my English is not very good, it's not my native language.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.