Dietmar

@ward201185 Make a try with disabling your HD sound driver from your graphikcard in Device Manager Dietmar

@geeb21 I think it is enough, to disable all UEFI in Bios and to disable "Fast Boot" in Bios Dietmar

@geeb21 In Patches\ACPI drivers change the acpi.sys 7777 -> acpi.sys 6666 version from the folder.

@geeb21 Make a try with the other acpi.sys 6666 Dietmar PS: This Bsod because of acpi.sys is strange, because before you dont get. Set in Bios everything to "Legacy", no UEFI at all. Disable "Fast Boot" in Bios.

@geeb21 Do you use the last XP SP3 from Ramsey from 9 September 2022? On which compi you try to install XP now? Make a photo of the acpi.sys blue screen Bsod Dietmar

@geeb21 Try the XP SP3 from Ramsey with settings 1, 3, 5, 6, A, C, D, E Dietmar

@geeb21 Only MBR works for now with XP. Use Firadisk install as described in https://www.zone94.com/ together with this nice XP SP3 from Ramsey Dietmar https://ufile.io/qz4e1an9

@geeb21 This compi has the Intel cpu N3000 with graphik HD 400. The Bios has CSM, so you will be able to install XP but no 3D graphik for HD 400 under XP Dietmar

@dizzydevil Just look on left side above in Core Temp https://www.alcpu.com/CoreTemp/ how much the power consumption is with 0% cpu load. It should be less than 20 Watt, then all is ok Dietmar

@dizzydevil Just put this modified intelppm.sys into windows\system32\drivers of your XP from an outstanding OS Dietmar https://ufile.io/908ky4hm

@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

@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

@Damnation You just forget 5 funktions in ntoskrn8.sys EtwSetInformation MmMapIoSpaceEx ExQueryWnfStateData ExSubscribeWnfStateChange ExUnsubscribeWnfStateChange Dietmar

@Mov AX, 0xDEAD On XP SP3 when doing dxdiag.exe, the "Input" fails. It depends on USB. When I disable all usb on any z690 board, no crash happens. I try a Windbg session for to look at this crash. The only information I get is LPC[ 270.2fc ]: csrss.exe Attempted ReplyWaitReceive to Thread 89ab2468 (dxdiag.exe) LPC[ 270.2fc ]: failed. MessageId == 12669 Client Id: 9d4.9d8 LPC[ 270.2fc ]: Thread MessageId == 0 Client Id: 9d4.9d8 Do you have an idea, how to get more information about this crash from dxdiag or do you have an idea, why this happens Dietmar

@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

@Andalu I remember a check from @Mov AX, 0xDEAD, and he noticed, that with this tool no trim at all was done on any nvme device. But at this time he has not the Silicon driver, so who knows Dietmar

@Andalu This "frozen" happens, when you use an nvme device, that has been used for some time (or formatted(!)). So, trim your nvme device and do not use "format" under XP, because this shortens the lifetime. The nvme device can be "trimmed" for example under win8.1 (tools for disk). When you use an nvme device under XP, until now I do not know a tool, that can trim an nvme device under xp and so this "frozen" happens. It goes away after one time "trim" Dietmar

@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

@pappyN4 Only the Microsoft nvme driver version 2.0 works without problems Dietmar

@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.

@pappyN4 Yepp, also on the Asus WS z390 Pro XP does not like 128 Gbyte ram, only 64 Gb Dietmar

@Damnation Nice would be a generic USB3 driver from win8.1 The USB3 driver from win8.0 shows some problems on newer compis, stops data transfer suddently because of "not enough memory" or just ignores USB devices. This does not happen for example with the USB3 driver from Asmedia. Maybe it is worth a try to modd this Asmedia USB3 driver for other USB ports also Dietmar

@Damnation From that, what @Mov AX, 0xDEAD wrote, from storport win8.0 and later a crashdump can be get only via the win8 etc. Kernl. And the !analyze -v command cant work, because Windbg does not react on the "break" command, meaning that it crashes. By the way I notice, that the Sata driver from Kai Schtrom is the only driver from all the drivers in the package "Patch", that works with this storport.sys from win8.1, all other driver fail Dietmar PS: What will be better with a storport.sys from win8.1? A lot of driver work with the modded storport.sys from win8.0 from @Mov AX, 0xDEAD, but not all, for example the Microsoft stornvme.sys v2.0 from @daniel_k only likes the modded win7 storport.sys.

@Damnation I get Windbg over Lan to work with storport.sys from win8.1 6.3.9600.17383 (winblue_r4.140924-1541) and the Sata driver from Kai Schtrom. Problem is, that I do not succeed to catch this Bsod 0x9F. This Bsod happens only on shutdown, on running XP everything seems to work ok. But exact at this shutdown, windbg hangs, reacts to nothing, shows no Bsod. XP shows this Bsod 0x9F with blue screen and message DRIVER_POWER_STATE_FAILURE May Be, that @Mov AX, 0xDEAD has an idea how to catch this Bsod with windbg or has an idea, how to overcome this Dietmar PS: From github Storport.sys from Windows 7 more compatible with Windows XP/2003 because it still call required PoStartNextPowerIrp when processing power IRPs. Microsoft removed calls to PoStartNextPowerIrp in Windows 8's storport.sys, without this call Windows XP/2003 kernel cannot finish current power IRP and start next IRP => it generate BSOD (0x0000009F).

@Damnation I set up an Ramsey XP with your Patch Integrator 332New_stornvme81. It contains an storport.sys from 28 August 6.3.9600.17383 (winblue_r4.140924-1541). With this I build an XP with the Sata from Kai Schtrom, settings 4,C,E,G. I notice, that for this storport.sys there is no storport.pdb only storpor8.pdb and ntoskrn8.pdb. At the end of copying files during TXT Setup of XP, direct for reboot to GUI Setup I get Bsod 0x9F, (0x500, 0x02, yyy, zzz). But after reboot Gui Setup starts. Soon I set up there an Debug Session with Lan Debug with the files from @Mov AX, 0xDEAD Dietmar Dietmar