Jump to content

Compiling ACPI v2.0 driver for Windows XP SP3 and Windows 2003 SP2 (x32/x64)


Mov AX, 0xDEAD

Recommended Posts

@Mov AX, 0xDEAD

For my AMD AM4 systems I've only ever seen the CrackPRT 7E BSOD that has already been solved.
 

Quote

 

 BSOD 0xA5 (0x0000000D, ..., ..., ...) duplicated/absence _HID/_UID method (AMD boards)

 BSOD 0xA5 (0x2001, 0x01,  0xC0000034, ...) failure to evaluate the _PIC method in NotifyHalWithMachineStates()

 

I have not seen either of these BSODs on my AMD systems.

When my new B550 build arrives I'll test it, I think it should be fine though.

Link to comment
Share on other sites


@Mov AX, 0xDEAD

I'm following this thread since the deleted topic about running XP on modern hardware on "the other forum", I don't know if it helps but I get 0xA5 on Windows 8.0 with default acpi.sys & Intel CPU from 2018,  BUT running a modded version of Windows 8.0 acpi.sys, I can boot it. 

Since you're talking about w8,0 maybe this acpi.sys version can help you with the XP modded acpi version? Just tell me and I will send you the modded version 

I'm interested too on running XP on modern hardware: NVME + GPT + UEFI + ACPI mod

This is also the latest available info about running XP on modern hardware:

TXT (99 KB, English) - https://yadi.sk/d/JCLixO6xixweRg
TXT (111KB, Russian) - https://yadi.sk/d/Xxq4IGOSOnVZqw

 

Edited by sonyu
Link to comment
Share on other sites

2 minutes ago, sonyu said:

I'm following this thread since the deleted topic about running XP on modern hardware on "the other forum", I don't know if it helps but I get 0xA5 on Windows 8.0 with default acpi.sys & Intel CPU from 2018,  BUT running a modded version of Windows 8.0 acpi.sys, I can boot it. Since you're talking about w8,0 maybe this acpi.sys version can help you? Just tell me and I will send you the modded version

@sonyu

This topic about XP/W2003 ACPI.SYS, if you have some BSOD A5 on XP with latest (pre-v4) compiled driver - this info can be helpfull, you don't need even install XP, just run any XP-based LiveCD/WinPE/Install ISO from USB with updated acpi.sys

Info about BSOD A5 on other windows is useless for XP because each windows has own acpi.sys.

 

Link to comment
Share on other sites

@Mov AX, 0xDEAD  Yes, I remember running w7 and w8 live usbs to test the acpi.sys mods 

Ok, I know it's about XP/2K3. Fastest OS until Windows 8.0 (which is the fastest NT6 OS & doesn't have any lag, no dpi problems, no memory compression, no video memory pagination the way it's happening on w10. But I don't want to go off-topic).

@Damnation talked about w8.0 acpi.sys A5 error  and immediately I thinked in my modded acpi.sys to run w8.0 on current hardware so I commented to say if the file can help to make the XP version the same way.

here 

 

Is there any live USB based on XP Integral edition?

Edited by sonyu
Link to comment
Share on other sites

@sonyu

I know the windows 8.0 acpi sys you're referring to, that acpi.sys just has a skip DDB error hack, the error I was having has been solved through debugging and @Mov AX, 0xDEAD's genius.

Seriously dude the whole XP enthusiast community can't thank you enough for all your hard work, without which none of this would be possible!

Sincerely, thanks a lot! @Mov AX, 0xDEAD much appreciation!

Link to comment
Share on other sites

2 hours ago, Mov AX, 0xDEAD said:

 BSOD 0xA5 (0x0000000D, ..., ..., ...) duplicated/absence _HID/_UID method (AMD boards)

 BSOD 0xA5 (0x2001, 0x01,  0xC0000034, ...) failure to evaluate the _PIC method in NotifyHalWithMachineStates()

I do not remember having those on mine.  Only 7E c0000005 and 05 0000011 with unmodified acpi.

XP 7777v4 looks good, updated to newest firmware, tested on Gigabyte, B450, with AGESA 1.2.0.6 B

Link to comment
Share on other sites

@genieautravail

Make try with to disable the HD3000 in Bios.

BUT may be risk, if the other graphikscard does not work at all,

that you dont see anything on screen from the moment(!) when you disable HD3000 in Bios

Dietmar

Edited by Dietmar
Link to comment
Share on other sites

diff patch updated to v4 in first post, includes two workarounds:

  1. BSOD 0xA5 (0x11, 0x08, ..., ...) error in _AMLILoadDDB() (zero lenght buffer)
  2. BSOD 0xA5 (0x11, 0x08, ..., ...) error in _AMLILoadDDB() (doubled device definition)
Edited by Mov AX, 0xDEAD
Link to comment
Share on other sites

  • Mov AX, 0xDEAD changed the title to Compiling ACPI v2.0 driver for Windows XP SP3 and Windows 2003 SP2 (x32/x64)

@Mov AX, 0xDEAD

I think you can edit acpiosnt.rc like this to easily distribute current patch version

For XP (5.1)

 

#define VER_FILEVERSION              5,1,2600,7777
#define VER_FILEVERSION_STR         "5.1.2600.7777.4"
#undef VER_PRODUCTVERSION
#undef VER_PRODUCTVERSION_STR
#define VER_PRODUCTVERSION           5,1,2600,7777,4
#define VER_PRODUCTVERSION_STR      "5.1.2600.7777.4"
    
#define VER_FILETYPE            VFT_DRV
#define VER_FILESUBTYPE         VFT2_DRV_SYSTEM
#define VER_FILEDESCRIPTION_STR         "ACPI 2.0 Driver for NT"
#define VER_INTERNALNAME_STR            "ACPI.sys"
#define VER_ORIGINALFILENAME_STR        "ACPI.sys"

 

For Server 2003 / XP (5.2)

 

#define VER_FILEVERSION              5,2,3790,7777
#define VER_FILEVERSION_STR         "5.2.3790.7777.4"
#undef VER_PRODUCTVERSION
#undef VER_PRODUCTVERSION_STR
#define VER_PRODUCTVERSION           5,2,3790,7777
#define VER_PRODUCTVERSION_STR      "5.2.3790.7777.4"
    
#define VER_FILETYPE            VFT_DRV
#define VER_FILESUBTYPE         VFT2_DRV_SYSTEM
#define VER_FILEDESCRIPTION_STR         "ACPI 2.0 Driver for NT"
#define VER_INTERNALNAME_STR            "ACPI.sys"
#define VER_ORIGINALFILENAME_STR        "ACPI.sys"

acpi-Ver.png

 

 

Edited by George King
Link to comment
Share on other sites

@Mov AX, 0xDEAD

I'm trying the compiled ACPI v4 update on some intel boards. Until now it worked on GA-H470, Asus Prime Q370 and Lenovo IH110MS.

I got the BSOD 0xA5 (0x0000000D, ..., ..., 0x0) for the Asrock H310M-HDV also by installing XP from a pendrive.

Here the debug log:

https://anonfiles.com/p63dLbabyd/H310M_7z

 

Edit: luckily the asrock board has a realtek 8111 chipset controller :)

Edit2: the acpi V4 also works on Asus Prime B250 and Asrock B250M Pro4 (on the lattest the restart still doesn't work with a PS/2 keyboard connected but I noticed a little changing: the system no longer blocks now on the "windows is shutting down" message but the screen becomes black even if the system is still ON and blocked).

Edited by Andalu
Link to comment
Share on other sites

1 hour ago, Andalu said:

@Mov AX, 0xDEAD

I'm trying the compiled ACPI v4 update on some intel boards. Until now it worked on GA-H470, Asus Prime Q370 and Lenovo IH110MS.

I got the BSOD 0xA5 (0x0000000D, ..., ..., 0x0) for the Asrock H310M-HDV also by installing XP from a pendrive.

This is BSOD I was asking about on prev page :)

Quote

        // At this point, we are hosed. We have two different devices with the
        // same PNP id, but no UIDs. Very bad

        //
        ACPIDevPrint( (
            ACPI_PRINT_FAILURE,
            DeviceExtension,
            "ACPIDetectDuplicateHID - matches with %08lx\n",
            childExtension
            ) );
        KeBugCheckEx(
            ACPI_BIOS_ERROR,
            ACPI_REQUIRED_METHOD_NOT_PRESENT,
            (ULONG_PTR) DeviceExtension,
            PACKED_UID,
            0
            );

I think PDRC conflict with GPI0, PDRC has _UID, GPI0 doesn't have

if GPHD =1, PDRC will set _HID = PNP0C02, but without any _UID

Quote

 

97eca899: {
97eca899: Return("PNP0C02")
97eca8a3: }
AMLI: 97f52408: \_SB.PCI0.GPI0._STA()
97EC7980 ACPI\PNP0C02 ACPIBuildProcessDevicePhaseHid: Status = 00000103

 

Quote

Device (PDRC)
        {
            Name (_HID, EisaId ("PNP0C02") /* PNP Motherboard Resources */)  // _HID: Hardware ID
            Name (_UID, One)  // _UID: Unique ID

Quote

Device (GPI0)
        {
            Method (_HID, 0, NotSerialized)  // _HID: Hardware ID
            {
                If (GPHD == One)
                {
                    Return ("PNP0C02")
                }

                If (PCHS == PCHH)
                {
                    Return ("INT3450")
                }

                Return ("INT34BB")
            }

Again, error in DSDT, no _UID method inside device

Dietmar has similar board, his "otto2" logfile has same device definition mistake, but without BSOD
 

1 hour ago, Andalu said:

Edit: luckily the asrock board has a realtek 8111 chipset controller :)

cheap = good, thanks to asrock :)

Edited by Mov AX, 0xDEAD
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...