@66cats
This is all the acpi.sys files as far as i know, including the newest acpi.sys I have.
https://ufile.io/xl07mr8a
@Dietmar might have a newer one though.
@Dietmar
Can you run a debug on storport 8.0 beta 8102 to find the cause of this storport 7E BSOD?
(remember to restore original XP SP3 HAL and acpi.sys before running debug this)
dietmar_storport_8102_7e.7z
@SFMG
I'd say your best option would be to get a cheap Nvidia GT 710 or 730 and run it along side your RX580 in a lower PCIE slot.
Nvidia kept XP support up to GTX 980 whereas AMD dropped support around the R7 270.
@Mov AX, 0xDEAD
I know this isn't related to ACPI, but I got my hands on some windows 10 private symbols and was wondering if you could use them to make an NDIS_emu extender using them like how you did for ntoskrnl?
@Dietmar
I noticed that ACPI 5112, which still has XP RSDT find function in it. also gives this 7E BSOD.
So I think I can narrow down the cause of the BSOD to either HalGetInterruptTargetInformation or HalGetMessageRoutingInfo in my HAL and not my ACPI table finding code.
@Dietmar
It seems like that's the case, I wonder why microsoft did it that way.
I'm going to go through vista beta acpi.sys and see which version is first to BSOD.
@George King
Can you run H2testw on it to confirm that it is legit? I'll be genuinely surprised if it is as these are usually scams.
https://h2testw.org/
A video showing H2testw in action.
https://youtu.be/SI0m7nVn2Tk?t=444
@SEDANEH
If this is for the integrated motherboard GPU your only option in XP is a generic 2D only driver.
http://bearwindows.zcm.com.au/vbempk.zip
If it's for an nvidia or AMD card you can just get the drivers from their websites.
@user57
PCI DeviceID's are more useful than names when looking for drivers.
A PCI device might have the same name as another but be of a different hardware revision, which is why you should look for the DeviceID.