HP Z1 G2 AIO MXM Upgrade - Quadro RTX 3000 / T1000 Code 43, 0 MB VRAM, Driver Won't Initialize

[Alpine_B]

I'm looking for help getting newer MXM GPUs working in an HP Z1 G2 AIO workstation and some other MXM systems

 

Below is a detailed explanation of everything I have tried, at this point I am leaning towards using nvflashk (patched version of NVFLASH) to try flashing a different VBIOS. My reasoning is that the HP VBIOS is preventing these card from initializing. 

 

Any recommendations for a good generic Nvidia / OEM VBIOS for either the HP RTX 3000 or T1000 (both Type-B) ? I posted numerous screenshots and phots of the cards below

System

• HP Z1 G2 AIO and HP USDT 800 G1 (Dell Precision 7720 is next) 
• Windows 11 x64
• UEFI enabled
• MXM Type-B Card (RTX 3000 & T1000) 

 

Problem Cards

I now have two HP ZBook MXM cards that exhibit the same behavior:

1. Quadro RTX 3000 MXM (TU106)
2. Quadro T1000 MXM

Both are HP OEM Type-B MXM modules removed from HP ZBooks.

RTX 3000 Details

Hardware ID:

PCI\VEN_10DE&DEV_1F36&SUBSYS_860E103C

GPU-Z identifies:

• TU106
• HP Subvendor
• Original HP VBIOS
• Samsung GDDR6

The card displays video and can function as the primary display adapter.

Symptoms

With both the RTX 3000 and T1000:

• Driver installs successfully
• Device Manager identifies the card correctly
• Screen flickers/blanks during installation
• Device Manager shows Code 43
• GPU-Z reports:
  • Memory Size = 0 MB
  • Bus Width = Unknown
• NVIDIA-SMI fails with:

"NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver"

The cards POST and output video normally (HP Z1 does not have Optimus, so the card for sure is being used as primary display adapter and initially shows as "Microsoft Basic Display Adapter - VGA Capable Adapter" 

 

 

Troubleshooting Performed

• Verified original HP VBIOS on RTX 3000
• Tried multiple NVIDIA driver versions
• Used DDU between installs
• Used NVCleanInstall
• Tried numerous subsystem IDs and INF entries
• Tested HP, Dell, Lenovo, Acer RTX 3000 entries
• Tried:
  • nvblwi.inf
  • nvmiwi.inf
  • nvdmwi.inf
  • nvltwi.inf
  • nvcawi.inf
  • nv_dispwi.inf
• Exact HP subsystem entry installs but still results in Code 43

Working Card

I have a Quadro P4000 MXM that is now fully working in this system.

When I first installed the P4000, it showed symptoms very similar to what I am seeing now:

• Code 43
• 0 MB VRAM
• Bus Width Unknown
• Driver would install but not initialize

Eventually I got the P4000 working by experimenting with different INF entries in NVCleanInstall. I do not remember the exact entry that finally worked, but the first several attempts failed before one finally initialized properly.

Once working:

• NVIDIA drivers loaded normally
• Native 1440p resolution returned
• VRAM was detected correctly
• GPU-Z reported normal specs
• Card became fully functional

Questions

1. Has anyone successfully run an HP RTX 3000 MXM (1F36.860E.103C) in an HP Z1 G2 AIO or other systems like laptops? I have a few MXM laptops and SFF systems (HP USDT, HP Z1 AIO, and Dell Precision 7710/7720)  I'd like to use these in. Seeing how you guys are pushing the limits of using unsupported MXM cards in Alienware/Clevo laptops, I am hoping someone knows.
2. Is there a known Turing limitation on the Z1 G2 that does not affect Pascal cards like the P4000?
3. Are there specific INF sections known to work for RTX 3000 MXM upgrades?
4. Has anyone seen both T1000 and RTX 3000 fail with:
   • Code 43
   • 0 MB VRAM
   • Unknown Bus Width
5. Could this indicate a missing MXM signal or platform compatibility issue specific to Turing GPUs?
6. What VBIOS is everyone using to get HP RTX 3000 working on unsupported systems? 

 

Any advice from people who have upgraded Alienware MXM rigs or SFF workstations or Z1 AIO systems would be greatly appreciated- thanks for your work keeping these systems in service!