Damnation

@cyberluke Yeah I read it, they select the MPS HAL in this case which means this threads ACPI driver irrelevant as it's not used by that HAL.

@Dietmar @geeb21 IIRC This acpi.sys 7E BSOD happened because an ISA GPIO device was being treated as PCI by mistake, unless I'm mistaken.

@Brickedandroid Try windows 7 instead of Vista.

@Brickedandroid Unfortunately I don't think ntoskrnl extender will help for something like this - ntoskrnl extender just resolves missing exports. Maybe try the XP driver on Vista, see if that works.

@cyberluke Not quite, to disable ACPI you'll also need a type of HAL that specifically ignores ACPI. Multiprocessor ACPI HAL is the best HAL for modern hardware, the other HALs might not even work.

@geeb21 I think you lost USB Input in this case, so you'll need to use the optional patch integrator to integrate USB 3.0 drivers before you can continue with setup.

@Brickedandroid What bug are you referring to?

@MrMateczko you could try this - https://github.com/JHRobotics/patcher9x

@Dietmar Thanks, So this message means 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?

@Dietmar Whoops! OK new version. https://ufile.io/mkr85nmw

@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

@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

@pappyN4 I've never had this problem. but then I don't try to have more than 1 OS on each drive, so maybe try just having XP on the drive without any other windows installed.

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.

@Dietmar I'm not sure why this BSOD is happening, I'm not using checked builds.

@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

@Dietmar OK, I'll focus on porting 8.1 USB 3.0 driver instead.

@Dietmar Ah, so no crashdump or live debug is possible for this storport then? I chose windows 8.1 storport simply because it was newer than 8.0 - From my testing storport 8.0 will also have this 9F BSOD problem.

@Dietmar You could maybe debug with a crashdump? i.e https://www.sysnative.com/forums/threads/how-to-debug-a-driver-power-state-failure-bugcheck-0x9f-when-1st-param-0x3.27871/ Has XP given a crashdump for this BSOD?

@Dietmar From this page - https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x9f--driver-power-state-failure Try kd>!analyze -v

@Dietmar 332New_stornvme81 has free build of storport 8.1 not checked, but if checked is not working then use that. Here is the PDB symbols for that storport.sys https://ufile.io/pt4kq3fc

@Dietmar OK, Can you debug with just 8.1 storport & storahci please? It should give a 9F BSOD when the system tries to restart.

@Dietmar This 8.1 storport.sys is from checked 8.1 debug ISO, so I think checked XP ntoskrnl/hal is needed?

@Dietmar You're welcome! If you have the time, can you debug the 9F BSOD I encountered trying to port windows 8 storport.sys and post in the thread I made?

@Dietmar First lets try just adding the Processors onto the end of your DSDT table and leave the other ACPI tables untouched. This seems to work fine on my B550 steel legend, although it also leaves the duplicate ACPI0007 Devices in place doing nothing. https://ufile.io/l72v8ae3