Damnation Posted September 4, 2022 Share Posted September 4, 2022 @Dietmar Here is my 1st attempt at getting USBXHCI of 8.1 in XP. Currently it gives a 7E BSOD in usbxhci.sys - please debug when you have time. https://ufile.io/mzsc3dq9 patch integrator 3.1.1.6 with 8.1 usbxhci Link to comment Share on other sites More sharing options...
Damnation Posted September 5, 2022 Author Share Posted September 5, 2022 @Dietmar I'm not sure why this BSOD is happening, I'm not using checked builds. Link to comment Share on other sites More sharing options...
Dietmar Posted September 5, 2022 Share Posted September 5, 2022 @Damnation BSOD 0x7E 0x80000003 If exception code 0x80000003 occurs, a hard-coded breakpoint or assertion was hit Dietmar PS: Today I do have not much time but on Wednesday. Link to comment Share on other sites More sharing options...
Damnation Posted September 5, 2022 Author Share Posted September 5, 2022 15 minutes ago, Dietmar said: BSOD 0x7E 0x80000003 If exception code 0x80000003 occurs, a hard-coded breakpoint or assertion was hit Unfortunately, I don't know where in the file this occurred, so I'll have to wait for you to debug to get more information. Link to comment Share on other sites More sharing options...
DrunkenTanker Posted September 6, 2022 Share Posted September 6, 2022 I tried to know what is it and found links only about BSOD. Link to comment Share on other sites More sharing options...
DrunkenTanker Posted September 6, 2022 Share Posted September 6, 2022 21 hours ago, Damnation said: I'm not sure why this BSOD is happening Do you have a dump? Link to comment Share on other sites More sharing options...
Damnation Posted September 6, 2022 Author Share Posted September 6, 2022 @DrunkenTanker @Dietmar I think the files on the Windows 8.1 RTM ISO are checked builds. So I switched to Windows 10 RTM (1507) no more 7E BSOD, but I even though I no longer get a BSOD I get code 31 in device manager for the USB 3.0 controller, so it's not yet functional. here's a patch integrator you can try https://ufile.io/gb0fevux Link to comment Share on other sites More sharing options...
Dietmar Posted September 6, 2022 Share Posted September 6, 2022 @Damnation There exist a checked version of win8.1 and I have. The same to win8.0 You can compare the file size, the checked version always produce bigger files Dietmar Link to comment Share on other sites More sharing options...
Dietmar Posted September 7, 2022 Share Posted September 7, 2022 @Damnation I test via windbg the usbxhci from win8.1, which you send to me. Here is result Dietmar USBXHCI: Controller enumeration failure in WdfEvtDevicePrepareHardware Break instruction exception - code 80000003 (first chance) USBXHCI!Controller_WdfEvtDevicePrepareHardware+0xe7: b95b32a9 cc int 3 4: kd> g Unloaded modules: b8073000 b807d000 WppRecor.sys b4588000 b45cb000 USBXHCI.SYS b455d000 b4588000 ucx01000.sys b49bb000 b49cf000 Parport.SYS b650b000 b650e000 DumpDrv.SYS b57af000 b57ba000 imapi.sys b57bf000 b57ce000 redbook.sys b5d70000 b5d75000 Cdaudio.SYS b5be7000 b5bf7000 cdrom.sys b6523000 b6526000 Sfloppy.SYS b5bf7000 b5c03000 Flpydisk.SYS b5d78000 b5d7f000 Fdc.SYS ba318000 ba322000 WppRecor.sys b9585000 b95c8000 USBXHCI.SYS b92a0000 b92cb000 ucx01000.sys DevNode 0x8a1eb6d8 for PDO 0x8a1f0340 InstancePath is "PCI\VEN_8086&DEV_A2AF&SUBSYS_A2AF1849&REV_00\3&11583659&0&A0" ServiceName is "USBXHCI" State = DeviceNodeRemoved (0x312) Previous State = DeviceNodeStartCompletion (0x306) Problem = CM_PROB_FAILED_START Failure Status 0000000000 Link to comment Share on other sites More sharing options...
Damnation Posted September 7, 2022 Author Share Posted September 7, 2022 @Dietmar Thanks, Can you do a debug with these files too? No BSOD with these but it will fail in device manager. https://ufile.io/lqmpvf6h Link to comment Share on other sites More sharing options...
Dietmar Posted September 11, 2022 Share Posted September 11, 2022 (edited) @Damnation You just forget 5 funktions in ntoskrn8.sys EtwSetInformation MmMapIoSpaceEx ExQueryWnfStateData ExSubscribeWnfStateChange ExUnsubscribeWnfStateChange Dietmar Edited September 11, 2022 by Dietmar Link to comment Share on other sites More sharing options...
Damnation Posted September 11, 2022 Author Share Posted September 11, 2022 @Dietmar Whoops! OK new version. https://ufile.io/mkr85nmw Link to comment Share on other sites More sharing options...
Dietmar Posted September 11, 2022 Share Posted September 11, 2022 @Damnation Here is result for the win10 usb3 driver: 0: kd> !devnode 8a8ab6d8 DevNode 0x8a8ab6d8 for PDO 0x8a861710 Parent 0x8a861db8 Sibling 0x8a8ab5a8 Child 0000000000 InstancePath is "PCI\VEN_8086&DEV_A2AF&SUBSYS_A2AF1849&REV_00\3&11583659&0&A0" ServiceName is "USBXHCI" State = DeviceNodeRemoved (0x312) Previous State = DeviceNodeInitialized (0x302) StateHistory[08] = DeviceNodeInitialized (0x302) StateHistory[07] = DeviceNodeAwaitingQueuedRemoval (0x30f) StateHistory[06] = DeviceNodeInitialized (0x302) StateHistory[05] = DeviceNodeUninitialized (0x301) StateHistory[04] = DeviceNodeRemoved (0x312) StateHistory[03] = DeviceNodeInitialized (0x302) StateHistory[02] = DeviceNodeAwaitingQueuedRemoval (0x30f) StateHistory[01] = DeviceNodeInitialized (0x302) StateHistory[00] = DeviceNodeUninitialized (0x301) StateHistory[19] = DeviceNodeRemoved (0x312) StateHistory[18] = DeviceNodeInitialized (0x302) StateHistory[17] = DeviceNodeAwaitingQueuedRemoval (0x30f) StateHistory[16] = DeviceNodeInitialized (0x302) StateHistory[15] = DeviceNodeUninitialized (0x301) StateHistory[14] = DeviceNodeRemoved (0x312) StateHistory[13] = DeviceNodeInitialized (0x302) StateHistory[12] = DeviceNodeAwaitingQueuedRemoval (0x30f) StateHistory[11] = DeviceNodeInitialized (0x302) StateHistory[10] = DeviceNodeUninitialized (0x301) StateHistory[09] = DeviceNodeRemoved (0x312) Flags (0x000022f0) DNF_ENUMERATED, DNF_IDS_QUERIED, DNF_HAS_BOOT_CONFIG, DNF_BOOT_CONFIG_RESERVED, DNF_RESOURCE_REQUIREMENTS_NEED_FILTERED, DNF_HAS_PROBLEM CapabilityFlags (0x00002000) WakeFromD3 Problem = CM_PROB_FAILED_ADD Here is the whole Windbg output Dietmar https://ufile.io/k6dxz0kn Link to comment Share on other sites More sharing options...
Damnation Posted September 11, 2022 Author Share Posted September 11, 2022 @Dietmar Thanks, So this message means Quote 'This Device Manager error message indicates that the function driver for the device returned an error from its AddDevice routine. But I'm unsure which AddDevice routine failed in USBXHCI there seems to be more than one - can you see if loading PDB symbols gives more info? Link to comment Share on other sites More sharing options...
Dietmar Posted September 11, 2022 Share Posted September 11, 2022 (edited) @Damnation All *.pdb are loaded. I make a test with the usbxhci.sys and usbhub3.sys from the Ramsey XP together with all your files from win10. They work via this way. I think, that this message mean, that usbxhci from win10 cant work together with the other files Dietmar Edited September 11, 2022 by Dietmar Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now