USB4 Driver differences between canary and stable?

Hi all,

I am an eGPU user using a USB4 dock (UT3G) connecting to my Windows handheld PC running stable 23H2.
This dock uses 64Gbps PCIe x4 4.0 over 40Gbps USB4v1 versus the standard 32Gbps PCIe x4 3.0 over 40Gbps TB3.

The problem is that every person with this dock has only ever gotten it to work in Canary. When trying to use the dock on stable 23H2, my event log gets an error that the "Miniport driver failed to start device...due to insufficient resources" from the DxgKrnl. That being said, the drivers install fine and Device Manager recognizes the device, but GPU-Z says its running at 1.1 speeds rather than 4, and any external monitors plugged in to the gpu do not work.

My question is, how can I find the differences in how Win 11 is handling the eGPU resource in stable vs canary? I was hoping something like ViVeTool could be used to enable features on the stable build once I can identify them.

valoomba said:

My question is, how can I find the differences in how Win 11 is handling the eGPU resource in stable vs canary?

Click to expand...

You're going to have to do parsing of your own from the SYSTEM hive. You should be able to find allocated resources for a particular device instance using:


The part highlighted in bold is the device instance path which you can find in device manager under the Details tab of the device.

Additional Info:

x BlueRobot said:

You're going to have to do parsing of your own from the SYSTEM hive. You should be able to find allocated resources for a particular device instance using:

Rich (BB code):

reg query HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI\VEN_1002&DEV_1637&SUBSYS_3E331E83&REV_00\4&20c24d55&0&0141\Control /v AllocConfig

Click to expand...

Hi! A total noob here, but trying to do some stuff related to the same eGPU dock (UT3G) problem with it not working with Nvidia cards on stable builds vs them working totally fine on Canary. I have a question, how do I identify the features that I would need to enable with ViVeTool (or at least try to) with output from this command here, and it being a long string of numbers? I mean, what is the connection between these two, how do I identify the features basing on this command? The output (numbers only) looks something like this:
010000000500000009000000010001000900000003018000000000DB000000000000000100000000810100000100000000000000000000000000000003018400000000207E00000000000010000000008101000001000000010000000000000000000000030184000000003E7E00000000000002000000008101000001000000030000000000000000000000000131018000000080000000000000000000000081010000010000000500000000000000000000000201030000000100C8FFFFFF0000000000000000 (sorry I don't know how to make a code format, it's my first post here)
And I totally don't know what to do with this. Like, at all. I tried checking on those sites mentioned by xBlueRobot, and the second comment on second website was looking promising, but the link is not working unfortunately... And also I don't understand what they're saying to be honest.
I would be very very very thankfull if someone could help me and teach me how to do that in simple language, since I'm a newbie with those things.

You can parse that registry value using Regedit, just view the properties of the registry value and you should see the IRQ assignment etc.

I'm not sure what ViveTool has to do with hardware resource assignment though? That's decided by the PnP Manager and the driver.

Okay, thank you. I don't really know what ViVeTool has to do with hardware resource assignment too, to be honest. I was just following the thought of person that wrote the original post. But I think, maybe other question would be suitable, since there is an idea, that with ViVeTool you can enable (correct me if I'm wrong) "features" in Windows Stable version, that are in Windows Canary, since Windows is updated... If, again, I understand correctly, a bit like, I don't know, let's say - like you have different parts of it, and you can update each part separately (of course there is a thing with dependencies too I guess or something...?). So like, you can tick the box and make your stable version of Windows have some features of Canary version, if I understand all correctly. And the question is: is there any possible way to check which of those features must be enabled in order for this USB4 eGPU UT3G dock to work correctly on Stable version on Windows? (I take full responsibility on that it may mess my Windows, I'll just reinstall it then I guess). I think that's what the person before me meant. So like, check which features are used with that eGPU on Canary, and then go back to Stable, enable them and play whatever game you want (since some of them don't work on latest Canary builds, like... at all).

No, ViVeTool isn't going to affect anything like that, really that tool has enables and disables some UI features like tabs in File/Windows Explorer.

I was just informing the OP of where they could check the resource assignment for that particular device and see if anything was different between the two builds. A canary build is inherently unstable and you can't expect it to work the same as a stable build.

Ahh, okay, thanks for correcting me then. So there is no way to make it work on stable build with nvidia cards... for now eh. But anyways, thanks for explaining me those things.