Damnation

@SEDANEH You need to run Options Menu.cmd to apply the patches to your XP install media first. They're not included by default. I would recommend options 1,2,3,5 and 6.

@SEDANEH No, the CPU doesn't cause this. Andalu posted that pic showing that it's possible to install XP on your motherboard, so your making a mistake somewhere in the process of making your XP installation media. Can you go through, step by step, how you're making your XP install media?

@Andalu Can't see the image you posted. @SEDANEH If you're running setup from USB then use WinsetupfromUSB to make your installation media. works much better for XP.

@George King PoFx functions were first implemented in Beta 8128, which is why I went for 8118 initially since it doesn't have those functions. @Dietmar has solved a 7E BSOD with a driver in the past with acpi.sys beta 5048, so it shouldn't be entirely out of the realm of possibility that he could do so again. Assuming dietmar's up for the challenge, I think he wants to solve the HP 255 G6 resetting in ACPI mode first though.

@Dietmar Sorry for the delay, here are the QC6000M ACPI tables. qc6000m_acpi_tables.7z

@George King What Incompatible Code did they push after 8056?

@SEDANEH You can use the Optional Patch Integrator script to do that. If you want to learn how to properly integrate ACPI manually you can open the script in a text editor to see what it's doing.

@Dietmar 8064 also 7E BSOD. It looks like storport 8064 and 8102 are identical.

@Dietmar Here is the E2-6110 GPU driver for XP https://easyupload.io/g6r2hj

@Dietmar I can confirm that storport.sys of windows 8.0 beta 8056 is working in textmode setup without BSOD, beta 8102 gives 7E BSOD, I still need to test 8064. storport_6_2_8056_test_works_dietmar.7z

@Dietmar Yes, The integrated graphics works in XP, but not in 98.

@Dietmar I have a desktop motherboard with an AMD E2-6110 CPU on it. An ASRock QC6000M. It's ACPI spec is 1.0a - so even acpi.sys of windows 98 will work on it. cheap on amazon. https://www.amazon.de/-/en/ASRock-QC6000M-Socket-FT3-Micro/dp/B087X2PCVH/ref=sr_1_1?crid=2DMOLEWZEL2UO&keywords=qc6000m&qid=1706854281&sprefix=qc6000m%2Caps%2C333&sr=8-1 Should I dump ACPI tables? also, did you try windows 7 on that laptop?

@Dietmar Processor declaration will likely be in its own SSDT table, not in DSDT.

@Dietmar What I meant is, If ACPI is disabling the SATA and USB ports, but it might not be disabling PCIe, so if there is a mini PCIe slot on the board it might work booting from a PCIe card. How does Windows 7 go with this machine? does it boot?

@Dietmar Try a PCIe SATA card with it, that might work. You can use one of those chinese mini pcie to PCIe adapters for this.

@Dietmar There might be a registry key in SETUPREG.HIV to disable auto restart on BSOD. I know Integral Edition at least won't restart on a 7B BSOD.

@Dietmar The problem might not necessarily be in the DSDT, it could be in another table. If you hook up a windbg session can you get it to a BSOD before it resets?

@Dietmar Got past the F7 BSOD to 7E BSOD now. storport_8102_7e.7z

@Dietmar Any luck with debugging this?

@Dietmar I'm starting to think that replacing security_cookie with random value as @Mov AX, 0xDEAD suggested on his github might not be sufficient to get passed F7 BSOD?

@K4sum1 Fair enough.

@K4sum1 Just use XP integral edition.

@Dietmar I was unable to find any PDB symbols for the 8118 beta build of storport, but I did find them for the earlier 8102 beta build. Can you debug this when you have the time? The F7 BSOD I'm sure is because of security_check_cookie function, but the subsequent 7E BSOD isn't so easy. I'm hopeful you will find a way to get passed it like you did with the ACPICrackPRT function before we had the source. storport_6_2_8102_test.7z

@Dietmar I got an F7 BSOD - I think I forgot to patch the security cookie.

@Dietmar@George King Hi Guys, I was wondering if either of you would be interested in testing out storport.sys of windows 8.0 beta 8118 in XP? I think this is the last version before PoFx functions got implemented. I added stub KseRegisterShim (just returns invalid parameter) and stub KeQueryUnbiasedInterruptTime (just returns KeQueryInterruptTime) to ntoskrnl extender for this. I was curious to see if we could get TRIM working over NVME with this or some other additional functionality. Assuming it doesn't BSOD. Any interest in testing this out? storport_6_2_8118_test.7z