I have a device and driver that works fine on some computers and fails to load properly on other computers. On the computer which the driver fails a Code 10 appears in device manager on the device node. The device appears fine in device manager before the driver is loaded. After the driver is installed the device is properly named and added to the correct node in device manager. This is the point at which the code 10 appears on the device node.
Upon investigation I discovered that on machines which experience this issue the AddDevice routine is not getting called.
Searching setupapi.dev.log I found the error message CM_PROB_FAILED_START. The msdn page about CM_PROB_FAILED_START (https://docs.microsoft.com/en-us/windows-hardware/drivers/install/cm-prob-failed-start) but it doesn’t say much.
It did however key me into looking at the IRP_MN_START_DEVICE (https://docs.microsoft.com/en-us/windows-hardware/drivers/kernel/irp-mn-start-device) page. I don’t fully understand everything this page says. I can say that the hardware does have a reverse bridge on it. I was initially having issues with the bridge. Windows would come up a code 10 was appearing on a PCI-to-PCI bridge node in device manager. Again, this issue is on some PCs. An eeprom was added to the bridge and now I am at the point described above.
What are other steps I can take to trouble shoot the cause of this issue?