Dietmar

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

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)

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

@SEDANEH Burn my xp.iso to a real CD and boot from it via an Sata CD-Rom drive Dietmar

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

crazy

@SEDANEH I already integrated this acpi.sys into the xp.iso, that I send to you. The only thing that you have to do, is to burn a CD from this xp.iso and start Setup Dietmar

@Damnation Can you please send to me this graphik driver for XP also, thanks Dietmar

@Damnation Yes, please send me all the ACPI tables. I found this board on Amazon and just order. Does the integrated graphik card work? Thanks a lot Dietmar

@SEDANEH I just install the xp.iso, that I send to you, on a Asus B760-A D4 works at once Dietmar

@SEDANEH You have post Dietmar

Via this way, you get same Bsod on next reboot. Put this acpi.sys into the Ramsey folder, that i show you. Burn the new Build Ramsey iso to a real CD-Rom. Dont use any external programs Dietmar

Into Windows XP Professional SP3 x86 - Integral Edition 2023.11.26\Patch Integrator v4.0.1\Patches\ACPI drivers

Into Windows\system32\drivers or just change it in Ramsey XP acpi folder Dietmar

@SEDANEH Make a try with this acpi.sys Dietmar https://ufile.io/6l9k08lg

But may be it has to look like this Scope (_PR) { Processor (C000, 0x00, 0x00000410, 0x06){ Name (_HID, "ACPI0007") } }

@Mov AX, 0xDEAD Hi, in DSDT I find this Scope (_PR) { Processor (C000, 0x00, 0x00000410, 0x06){} Processor (C001, 0x01, 0x00000410, 0x06){} Processor (C002, 0x02, 0x00000410, 0x06){} Processor (C003, 0x03, 0x00000410, 0x06){} }

I notice, that no Processor entry is in Device Manager. It is an AMD cpu e2-9000e. And maybe no entry for processor in DSDT, so only 1 cpu ist recogniced, without any acpi Dietmar

This will not help. I succeed to boot XP from USB this crazy HP 255 g6. And get 2 entries in Device-Manager: For Standard PC and Acpi Multiprocessor. But only with Standard PC it boots, Bsod 0x7B with Acpi Multiprocessor. So, there must be something in Bios, what disrupted the arcpath to any boot device, when you choose any acpi on this notebook.

On the HP 255 g6 with any XP SP3 ACPI install, the compi seems to loose any contact to the boot device, no matter if Sata or USB. Independend from the underlying boot device driver. And because of this comes the Bsod 0x7B Dietmar

1 3 5 A C F with ramsey Dietmar

@Mark-XP 1.) Edit Hal entry in registry via regedit to this Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\ACPI_HAL\0000] "ConfigFlags"=dword:00000000 "Legacy"=dword:00000000 "DeviceReported"=dword:00000001 "Service"="\\Driver\\ACPI_HAL" "HardwareID"=hex(7):61,00,63,00,70,00,69,00,61,00,70,00,69,00,63,00,5f,00,6d,\ 00,70,00,00,00,00,00 "CompatibleIDs"=hex(7):44,00,45,00,54,00,45,00,43,00,54,00,45,00,44,00,49,00,\ 6e,00,74,00,65,00,72,00,6e,00,61,00,6c,00,5c,00,41,00,43,00,50,00,49,00,5f,\ 00,48,00,41,00,4c,00,00,00,44,00,45,00,54,00,45,00,43,00,54,00,45,00,44,00,\ 5c,00,41,00,43,00,50,00,49,00,5f,00,48,00,41,00,4c,00,00,00,00,00 "Capabilities"=dword:00000000 "ClassGUID"="{4D36E966-E325-11CE-BFC1-08002BE10318}" "Class"="Computer" "Driver"="{4D36E966-E325-11CE-BFC1-08002BE10318}\\0000" "Mfg"="(Standardcomputer)" "DeviceDesc"="ACPI-Multiprocessor-PC" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\ACPI_HAL\0000\LogConf] [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\ACPI_HAL\0000\Control] "DeviceReported"=dword:00000001

@Damnation My problem is, that the HP 255 g6 shows Bsod 0x7B with acpi, means that the arcpath cant be found to the boot device. So, no information about the reason for this Bsod during debug. But it depends on acpi, because with "Standard PC" setup of XP works. This is such a strange behavior, because I can see my harddisk for a second at XP-Setup, but then compi shuts down Dietmar

@Mov AX, 0xDEAD Do you have an idea, what XP SP3 acpi.sys not likes in this DSDT from HP 255 g6 Dietmar https://ufile.io/6fb5w13l

@Mov AX, 0xDEAD I also test the brandnew acpi.sys from George King. Exact the same behavior. I can make a try to debug this BSOD via Lan from you, Mov AX, 0xDEAD, possible because it has a supported Realtek Lan chip. But this will be hard work, because I have no working XP SP3, so that I can boot from this XP for to fetch the Bsod.