Jump to content

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


Mov AX, 0xDEAD

Recommended Posts


I succeed to install Win7 bit32 on the HP 255 g6 with AMD 2E-9000e processor in Multiprocessor Acpi mode.

Now there are the 2 processors listed in the Device Manager.

I also succeed to install Reactos Life CD 0414, but also as single cpu without any acpi.

The succesful installation of win7 bit32 makes me think, that there is may be only 1 device in DSDT, that XP acpi does not like

and this gives Bsod 0x7B.

Any idea, how to look for this device

Dietmar

 

Link to comment
Share on other sites

I finally reached this stage, but the keyboard does not work at this stage Only the control + alt + delete keys work, which can be reset I went through F7

what do i do now?

setup_welcome.png

Link to comment
Share on other sites

19 minutes ago, SEDANEH said:

keyboard does not work

Try different USB ports, and, if all else fails, there's a PS/2 port on your MB, pretty much for this.

Link to comment
Share on other sites

@Mov AX, 0xDEAD

I succeed to build the XP Multiprocessor Acpi on another compi,

change after this the Sata driver to AMD  VEN_1022&DEV_7904 (crazy work), its the one from the HP 255 g6 E2-9000e.

And get now with Debug acpi.sys, Debug Ntos kernel and Debug Hal this via Lan Debug

*** Fatal System Error: 0x000000a5
                       (0x0000000D,0x8A776530,0x5244415F,0x00000000)

Break instruction exception - code 80000003 (first chance)

A fatal system error has occurred.
Debugger entered on first try; Bugcheck callbacks have not been invoked.

A fatal system error has occurred.

Connected to Windows XP 2600 x86 compatible target at (Sat Feb  3 19:17:42.156 2024 (UTC + 1:00)), ptr64 FALSE
Loading Kernel Symbols
.............................
Loading User Symbols

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A5, {d, 8a776530, 5244415f, 0}

Probably caused by : ACPI.sys ( ACPI!ACPIBuildProcessDevicePhaseAdrOrHid+4f )

Followup: MachineOwner
---------

nt!RtlpBreakWithStatusInstruction:
80ac37ec cc              int     3
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

ACPI_BIOS_ERROR (a5)
The ACPI Bios in the system is not fully compliant with the ACPI specification.
The first value indicates where the incompatibility lies:
This bug check covers a great variety of ACPI problems.  If a kernel debugger
is attached, use "!analyze -v".  This command will analyze the precise problem,
and display whatever information is most useful for debugging the specific
error.
Arguments:
Arg1: 0000000d, ACPI_REQUIRED_METHOD_NOT_PRESENT
    ACPI could not find a required method/object in the namespace
    This is the bugcheck that is used if a vendor does not have an
    _HID or _ADR present

Arg2: 8a776530, The ACPI Extension that ACPI needs the object for
Arg3: 5244415f, The (ULONG) name of the method ACPI looked for
Arg4: 00000000, Base Case

Debugging Details:
------------------


ACPI_EXTENSION:  8a776530 -- (!acpikd.acpiext 8a776530)

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xA5

PROCESS_NAME:  System

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

DPC_STACK_BASE:  FFFFFFFFBACC8000

LAST_CONTROL_TRANSFER:  from 80a30d7b to 80ac37ec

STACK_TEXT:  
bacc7b18 80a30d7b 00000003 bacc7e74 00000000 nt!RtlpBreakWithStatusInstruction
bacc7b64 80a319e6 00000003 8a776530 8a7764e0 nt!KiBugCheckDebugBreak+0x19
bacc7f44 80a31f77 000000a5 0000000d 8a776530 nt!KeBugCheck2+0x574
bacc7f64 ba739821 000000a5 0000000d 8a776530 nt!KeBugCheckEx+0x1b
bacc7f8c ba73a4b2 00000000 00000000 80addf90 ACPI!ACPIBuildProcessDevicePhaseAdrOrHid+0x4f [c:\acpi\acpi_sp1\base\busdrv\acpi\driver\nt\buildsrc.c @ 2901]
bacc7fb0 ba73b29e ba781768 ba77c288 bacc7fe0 ACPI!ACPIBuildProcessGenericList+0x52 [c:\acpi\acpi_sp1\base\busdrv\acpi\driver\nt\buildsrc.c @ 4851]
bacc7fc8 80ae3f59 ba781720 00000000 00000000 ACPI!ACPIBuildDeviceDpc+0xe2 [c:\acpi\acpi_sp1\base\busdrv\acpi\driver\nt\buildsrc.c @ 661]
bacc7ff4 80ae3a3b bacc3108 00000000 00000000 nt!KiRetireDpcList+0x7e
bacc7ff8 bacc3108 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2b
WARNING: Frame IP not in any known module. Following frames may be wrong.
80ae3a3b 00000000 00000009 0081850f bb830000 0xbacc3108


STACK_COMMAND:  kb

FOLLOWUP_IP:
ACPI!ACPIBuildProcessDevicePhaseAdrOrHid+4f [c:\acpi\acpi_sp1\base\busdrv\acpi\driver\nt\buildsrc.c @ 2901]
ba739821 894624          mov     dword ptr [esi+24h],eax

FAULTING_SOURCE_LINE:  c:\acpi\acpi_sp1\base\busdrv\acpi\driver\nt\buildsrc.c

FAULTING_SOURCE_FILE:  c:\acpi\acpi_sp1\base\busdrv\acpi\driver\nt\buildsrc.c

FAULTING_SOURCE_LINE_NUMBER:  2901

FAULTING_SOURCE_CODE:  
No source found for 'c:\acpi\acpi_sp1\base\busdrv\acpi\driver\nt\buildsrc.c'


SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  ACPI!ACPIBuildProcessDevicePhaseAdrOrHid+4f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ACPI

IMAGE_NAME:  ACPI.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  639267ed

IMAGE_VERSION:  5.1.2600.7777

FAILURE_BUCKET_ID:  0xA5_ACPI!ACPIBuildProcessDevicePhaseAdrOrHid+4f

BUCKET_ID:  0xA5_ACPI!ACPIBuildProcessDevicePhaseAdrOrHid+4f

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xa5_acpi!acpibuildprocessdevicephaseadrorhid+4f

FAILURE_ID_HASH:  {58890b9a-d3fd-b56d-86d9-787ef65b881a}

Followup: MachineOwner
---------

 

 

 

Edited by Dietmar
Link to comment
Share on other sites

And this I get with the Debug Ntoskrnl, Debug Hal and normal acpi.sys 7777

kd> g
MM: Loader/HAL memory block indicates large pages cannot be used for 80100000->8012777F
Thermal - Zone 8A781130 - 0:00:08.218 - Cpu 1 Above critical (b74 0)
PopCriticalShutdown: type 1
Thermal - Zone 8A781130 - 0:00:08.218 - Cpu 0 Above critical (b74 0)
PopCriticalShutdown: type 1
HALACPI:  The BIOS wants the OS to preserve 300000 bytes
MiSessionWideReserveImageAddress: NO Code Sharing on \SystemRoot\System32\drivers\dxg.sys, Address 0xbf9c3000
HvpGetCellMapped called after shutdown for Hive = E1037B60 Cell = 25020
HvpGetCellMapped called after shutdown for Hive = E1037B60 Cell = 25020
IO: Waiting for last chance shutdown of device object (8a6e8718) - (null)

Link to comment
Share on other sites

And with normal Multiprocessor Acpi ntoskernl and normal  Halmacpi.dll and normal acpi.sys 7777

now I come nearly to desktop, I can see the normal background with mouse for a second,

but then again this unknown crash

kd> g


Process.Thread : 000001AC.000001B0 (winlogon.exe) is trying to create key:
    ObjectAttributes = 0006FC84
The caller should not rely on data written to the registry after shutdown...


Process.Thread : 000001AC.000001B0 (winlogon.exe) is trying to create key:
    ObjectAttributes = 0006F5D4
The caller should not rely on data written to the registry after shutdown...


Process.Thread : 000001AC.000001B0 (winlogon.exe) is trying to create key:
    ObjectAttributes = 0006F584
The caller should not rely on data written to the registry after shutdown...


Process.Thread : 000001AC.000001B0 (winlogon.exe) is trying to create key:
    ObjectAttributes = 0006F584
The caller should not rely on data written to the registry after shutdown...


Process.Thread : 00000194.000001C0 (csrss.exe) is trying to create key:
    ObjectAttributes = BAA87920
The caller should not rely on data written to the registry after shutdown...


Process.Thread : 00000194.000001C0 (csrss.exe) is trying to create key:
    ObjectAttributes = BAA87920
The caller should not rely on data written to the registry after shutdown...


Process.Thread : 00000194.000001C0 (csrss.exe) is trying to create key:
    ObjectAttributes = BAA87920
The caller should not rely on data written to the registry after shutdown...


Process.Thread : 00000194.000001C0 (csrss.exe) is trying to create key:
    ObjectAttributes = BAA87928
The caller should not rely on data written to the registry after shutdown...


Process.Thread : 000001AC.000001B0 (winlogon.exe) is trying to create key:
    ObjectAttributes = 0006F790
The caller should not rely on data written to the registry after shutdown...
SXS: BaseSrvSxsGetActivationContextGenerationFunction: LdrLoadDll(C:\WINDOWS\system32\sxs.dll) failed 0xc0000142
SXS: BasepCreateActCtx() Calling csrss server failed

 

Link to comment
Share on other sites

After a year of trying to install Windows XP on Asus Z790 motherboard, today I announce that the XP installation project has completely failed.

im tried with cd drive

im tried with usb drive

im change any boot to legacy

im tried with  wintosetup

im tried witheasy2boot

im tried with rufus

im tried with nlite

im tried with evrythings

but :0X000000A5 then pres F7 :0X000000B7 then boot with easy2boot then press F6,F7 :windows cant find a hard drive and.......

I'm tired, no matter how much the last attempt failed

Link to comment
Share on other sites

@SEDANEH

Have you burned a real CD-Rom with my xp.iso? Is this burned CD in a Sata CD Rom, connected to a Sata slot on the Asus z790?

No acpi Bsod is possible, when you hit via this CD install F5, F7, F8 in the very first beginning of Setup and then choose

"Standard PC"

Dietmar

Link to comment
Share on other sites

5 minutes ago, Dietmar said:

@SEDANEH

Have you burned a real CD-Rom with my xp.iso? Is this burned CD in a Sata CD Rom, connected to a Sata slot on the Asus z790?

No acpi Bsod is possible, when you hit via this CD install F5, F7, F8 in the very first beginning of Setup and then choose

"Standard PC"

Dietmar

i borned this windows xp 2023 to cd and boot with dvd rw but see A5 when i press F7 see B7 or windows cant find hard drive

Link to comment
Share on other sites

And the same in Safe Mode F8 for to go to commandline on the HP 255 g6 gives this

kd> g
SAFEBOOT: skipping device = Cdrom.SYS(SCSI CDROM Class)
SAFEBOOT: skipping device = mnmdd.SYS(Video Save)
SAFEBOOT: skipping device = RDPCDD.SYS(Video Save)
SAFEBOOT: skipping device = RasAcd.SYS(Streams Drivers)
SAFEBOOT: skipping device = IPSec.SYS(PNP_TDI)
SAFEBOOT: skipping device = Tcpip.SYS(PNP_TDI)
SAFEBOOT: skipping device = NetBT.SYS(PNP_TDI)
SAFEBOOT: skipping device = AFD.SYS(TDI)
SAFEBOOT: skipping device = NetBIOS.SYS(NetBIOSGroup)
SAFEBOOT: skipping device = Serial.SYS(Extended base)
SAFEBOOT: skipping device = intelppm.SYS(Extended Base)
SAFEBOOT: skipping device = WS2IFSL.SYS(Group)
SAFEBOOT: skipping device = Rdbss.SYS(Network)
SAFEBOOT: skipping device = MRxSmb.SYS(Network)
SAFEBOOT: skipping device = Fips.SYS(Group)


Process.Thread : 00000004.00000034 (System) is trying to create key:
    ObjectAttributes = BACFFB98
The caller should not rely on data written to the registry after shutdown...

*** Fatal System Error: 0xc000021a
                       (0xE12BD490,0xC000009A,0x00000000,0x00000000)


STOP: c000021a {Schwerer Systemfehler}
Der Systemprozess Session Manager Initialization wurde unerwartet beendet. Status 0xc000009a (0x00000000 0x00000000).
Das System wurde heruntergefahren.
Break instruction exception - code 80000003 (first chance)

A fatal system error has occurred.
Debugger entered on first try; Bugcheck callbacks have not been invoked.

A fatal system error has occurred.

Connected to Windows XP 2600 x86 compatible target at (Sat Feb  3 21:44:04.109 2024 (UTC + 1:00)), ptr64 FALSE
Loading Kernel Symbols
................................................
Loading User Symbols
..
Loading unloaded module list
.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C000021A, {e12bd490, c000009a, 0, 0}

unable to get nt!KiCurrentEtwBufferOffset
unable to get nt!KiCurrentEtwBufferBase
Probably caused by : ntkrpamp.exe ( nt!KiFastCallEntry+fc )

Followup: MachineOwner
---------

nt!RtlpBreakWithStatusInstruction:
8052b5dc cc              int     3
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WINLOGON_FATAL_ERROR (c000021a)
The Winlogon process terminated unexpectedly.
Arguments:
Arg1: e12bd490, String that identifies the problem.
Arg2: c000009a, Error Code.
Arg3: 00000000
Arg4: 00000000

Debugging Details:
------------------

unable to get nt!KiCurrentEtwBufferOffset
unable to get nt!KiCurrentEtwBufferBase

ERROR_CODE: (NTSTATUS) 0xc000021a - {Daten wurden nicht akzeptiert}  Der TDI-Client konnte die empfangenen Daten nicht verarbeiten.

EXCEPTION_CODE: (NTSTATUS) 0xc000021a - {Daten wurden nicht akzeptiert}  Der TDI-Client konnte die empfangenen Daten nicht verarbeiten.

EXCEPTION_PARAMETER1:  e12bd490

EXCEPTION_PARAMETER2:  c000009a

EXCEPTION_PARAMETER3:  00000000

EXCEPTION_PARAMETER4: 0

ADDITIONAL_DEBUG_TEXT:  Session Manager Initialization

BUGCHECK_STR:  0xc000021a_smss.exe_c000009a_PoShutdown

DEFAULT_BUCKET_ID:  DRIVER_FAULT

PROCESS_NAME:  smss.exe

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

LAST_CONTROL_TRANSFER:  from 804f8df9 to 8052b5dc

STACK_TEXT:  
bad774e8 804f8df9 00000003 bad77844 00000000 nt!RtlpBreakWithStatusInstruction
bad77534 804f99e4 00000003 c000021a 0000004c nt!KiBugCheckDebugBreak+0x19
bad77914 804f9f33 0000004c c000021a bad779b0 nt!KeBugCheck2+0x574
bad77934 805c7192 0000004c c000021a bad779b0 nt!KeBugCheckEx+0x1b
bad77970 806573e1 00000001 0000004c c000021a nt!PoShutdownBugCheck+0x5c
bad77b28 80614110 c000021a 00000004 00000001 nt!ExpSystemErrorHandler+0x511
bad77cd4 80614691 c000021a 00000004 00000001 nt!ExpRaiseHardError+0x9a
bad77d44 8054161c c000021a 00000004 00000001 nt!NtRaiseHardError+0x16b
bad77d44 7c91e4f4 c000021a 00000004 00000001 nt!KiFastCallEntry+0xfc
0015feec 7c91d9ac 48589b39 c000021a 00000004 ntdll!KiFastSystemCallRet
0015fef0 48589b39 c000021a 00000004 00000001 ntdll!ZwRaiseHardError+0xc
0015ff1c 48589d9f 0015ff4c 00000005 00162395 smss!SmpTerminate+0x45
0015ffa8 4858ad97 00000001 00162340 00162348 smss!main+0x20b
0015fff4 00000000 7ffde000 000000c8 00000188 smss!NtProcessStartup+0x1d2


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!KiFastCallEntry+fc
8054161c 8be5            mov     esp,ebp

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  nt!KiFastCallEntry+fc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4802516a

IMAGE_VERSION:  5.1.2600.5512

FAILURE_BUCKET_ID:  0xc000021a_smss.exe_c000009a_PoShutdown_nt!KiFastCallEntry+fc

BUCKET_ID:  0xc000021a_smss.exe_c000009a_PoShutdown_nt!KiFastCallEntry+fc

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xc000021a_smss.exe_c000009a_poshutdown_nt!kifastcallentry+fc

FAILURE_ID_HASH:  {417dd63c-79a4-27bd-b22b-d067a8d08de8}

Followup: MachineOwner
---------

 

 

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
×
×
  • Create New...