Changing a K4000M with a K4100M in a HP Elitebook 8770w this what I got

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 @ijozic said, 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

 

Which Windows version are you using?

I know people updated their Ivy Bridge Dell Precisions with Maxwell cards so I wouldn't expect any incompatibility there.

 

Windows 10 Pro 64 Bits - Creators Update (Btw im in Insider Program)
EDIT: Should I try with windows 8.1, 8 and/or 7? I can test it next time i got time.

 

When I searched for the similar error with the watchdog dpc error, I ran into this post.

https://notesalongthepath.com/2013/...end-windows-8-dpc_watchdog_violation-crashes/

He mentions fast startup (a feature of Win 8 and I presume Win 10) gave him these problems. Perhaps you could try disabling it or installing Windows 7 to see if it would help.

I did upgrade my Windows 7 to Windows 10 on my Maxwell upgraded Ivy Bridge laptop, but only ran with it for a very short while to register for a free upgrade, after which I reverted back to the 7. I certainly didn't have the same error.

 

Well, ok, ill try removing fast boot in the BIOS and in windows, if it still gives me the same problem ill try with windows 7,

Fast Startup has been around since Windows 8 through latest Windows 10 Version.

 

Try looking through nvbli.inf for NVIDIA_Devices and find your laptop ID along with the device ID of your old k4000m take note of that section ID and try to reuse it along with your laptop ID and the device ID of K4100m


Edit: Removed quotes to decrease the chance of confusion

 

Isn't nvhmi.inf for HP devices?

 

both are for HP devices but nvbli.inf covers business notebooks while nvhmi.inf covers assorted other stuff

 

Alright. ill check it out,

 

Ah, I see, thanks. The only HP I had was the 8710W, but its FX-3600M GPU couldn't have really been upgraded as the vBIOS used by the laptop was in the system BIOS IIRC so I never got the chance to play with their inf files. Though, I'd at least expect an h or a p in the inf file name, though

 

Any luck?

 

Not sure it matters by this point, but I remember when I had my previous 8770w: Running it in UEFI mode after putting in a Dell-variant K5100M in it made it boot perfectly with everything working. In legacy boot mode, I got black screen. Not sure how the vBIOS operates in these different modes but its possible when UEFI is enabled, the system does not rely as much on the GPU vBIOS.