Mov AX, 0xDEAD

@George King This way you'l get another v6666 from 2018....

storpor8.sys is emulator of some new functions for win7's storport.sys I have experimental ported win8.0 storport.sys, it has many manual injected calls to PoStartNextPowerIrp(), perfectly works with win8's storahci Me and Daniel chose win7's storport.sys as base for ported storage drivers because it was last version who stills call PoStartNextPowerIrp() at proper places

I don't have NVMe hardware and it is very bad emulated by vmware/virtualbox, all my attemps to make working NVMe under VM was failed. My answer - yes, Daniel made many storage drivers for x86 and x64.

I didn't ported any Win8.1 NVMe drivers

start with saving crashdumps to disk, it can show stacktrace before crash

IDA debugger has same GUI, as standalone Disassembler i dont have pre-install environment experience, debug config stored in BCD

Remote debug with IDA, first learn when AMLILoadDDB(check subprocedures) may produce error, set breakpoints. There is internal "acpi debugger", but i dont know how to use it at boot time

I would like to remind that "mindless" turn off checks in acpi.sys (v6666/v5048) can lead to the fact that part of the AML code will never be executed. Remember skipping error of AMLILoadDDB() or ValidateArgTypes() ? Once you took this short way....

USB\RESET_FAILURE - what is it ?

No, PDB not published for early vista betas, PDB exist since v5342, maybe earlier, but i not tested

You are very far to booting XP texmode."Setup is Starting Windows" means all drivers loaded as files to ram. Next stage is code execution, but it stops there (surprise)...

Question is - how many people using WinXP x64 on UEFI x64 with original ACPI 1.0 driver on modern PC? Answer - about zero, only few new motherboards has special acpi1.0 legacy support for WinXP. Of couse you can make heavy patch of your DSDT to isolate all acpi2.0 syntax and run with ACPI 1.0 driver. Or use acpi x64 driver from longhorn 5048 beta

No, i can't. it's your idea and only you must handle it

For export/use already existing funcs in kernel. Not best solution, but it works on standart MS kernels. Modders, just comment all KeBugCheckEx(0xDEADBEEFL, 5, 0, 0, XX) lines

1) You cannot PoSetPowerState without device_object, device_object will be created usb3 driver to present usb3 controller abstraction to Windows 2) PoSetPowerState used to inform windows about current power state, what you do next after windows marked device as D0 ? 3) Better reverse ms usb3 8.0 driver(use win10 usb3 sources as base), find place where controller is resetted, change wait time or inject your additional code 4) Think about why are some additional delays/power states - solution to the problem ? I have repeatedly written that the driver will reset the controller, you will reset it second time(or you - first, driver - second), and what will it give ?