Dietmar

Here is first try with windbg 8.1 via NET debug of the Asrock z690 extreme with the new acpi.sys V2 (debug version). It is an pure, original XP SP3 install without any extra drivers or programs. Microsoft (R) Windows Debugger Version 6.3.9600.17200 X86 Copyright (c) Microsoft Corporation. All rights reserved. Using NET for debugging Opened WinSock 2.0 Waiting to reconnect... Connected to target 192.168.2.103 on port 50000 on local IP 192.168.2.101. Connected to Windows XP 2600 x86 compatible target at (Tue Apr 5 14:15:08.765 2022 (UTC + 2:00)), ptr64 FALSE Kernel Debugger connection established. ************* Symbol Path validation summary ************** Response Time (ms) Location OK C:\Symbols ************* Symbol Path validation summary ************** Response Time (ms) Location OK C:\symbols OK C:\symbolss OK C:\symbolsss Symbol search path is: C:\symbols;C:\symbolss;C:\symbolsss Executable search path is: C:\Symbols Windows XP Kernel Version 2600 (Service Pack 3) MP (24 procs) Checked x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 2600.xpsp.080413-2133 Machine Name: Kernel base = 0x80a02000 PsLoadedModuleList = 0x80b019e8 Debug session time: Tue Apr 5 14:12:02.750 2022 (UTC + 2:00) System Uptime: 0 days 0:00:05.343 ************* Symbol Path validation summary ************** Response Time (ms) Location OK E:\binaries.x86fre\Symbols ************* Symbol Path validation summary ************** Response Time (ms) Location OK C:\Symbols ************* Symbol Path validation summary ************** Response Time (ms) Location OK C:\symbols OK C:\symbolss OK C:\symbolsss OK E:\binaries.x86fre\Symbols Deferred https://msdl.microsoft.com/download/symbols Deferred srv* 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 (Tue Apr 5 14:15:09.218 2022 (UTC + 2:00)), ptr64 FALSE Loading Kernel Symbols ......................... Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A5, {3, 8989dba4, c0140008, 494e495f} Probably caused by : ACPI.sys ( ACPI!ACPIBuildCompleteMustSucceed+31 ) Followup: MachineOwner --------- nt!RtlpBreakWithStatusInstruction: 80ac37ec cc int 3 23: 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: 00000003, ACPI_FAILED_MUST_SUCCEED_METHOD ACPI tried to run a control method while creating device extensions to represent the ACPI namespace, but this control method failed. Arg2: 8989dba4, The ACPI Object that was being run Arg3: c0140008, return value from the interpreter Arg4: 494e495f, Name of the control method (in ULONG format) Debugging Details: ------------------ ACPI_OBJECT: 8989dba4 DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0xA5 PROCESS_NAME: System ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre LAST_CONTROL_TRANSFER: from 80a30d7b to 80ac37ec STACK_TEXT: ba551858 80a30d7b 00000003 ba551bb4 00000000 nt!RtlpBreakWithStatusInstruction ba5518a4 80a319e6 00000003 897d2008 8979d000 nt!KiBugCheckDebugBreak+0x19 ba551c84 80a31f77 000000a5 00000003 8989dba4 nt!KeBugCheck2+0x574 ba551ca4 ba732b29 000000a5 00000003 8989dba4 nt!KeBugCheckEx+0x1b ba551cc0 ba75c355 8989dba4 c0140008 00000000 ACPI!ACPIBuildCompleteMustSucceed+0x31 [e:\software\windowssourcecode\microsoft.leaked.source.code.archive_2020-10-04\nt5src\source\xpsp1\nt\base\busdrv\acpi\driver\nt\buildsrc.c @ 431] ba551cf8 ba75a1b5 ba732af8 c0140008 00000000 ACPI!AsyncCallBack+0xe5 [e:\software\windowssourcecode\microsoft.leaked.source.code.archive_2020-10-04\nt5src\source\xpsp1\nt\base\busdrv\acpi\driver\amlinew\sync.c @ 82] ba551d1c ba75d133 c0140008 4556414c 8979d000 ACPI!RunContext+0x1f5 [e:\software\windowssourcecode\microsoft.leaked.source.code.archive_2020-10-04\nt5src\source\xpsp1\nt\base\busdrv\acpi\driver\amlinew\ctxt.c @ 649] ba551d44 ba75d25f 8979d000 00000000 ba77ab08 ACPI!InsertReadyQueue+0x15a [e:\software\windowssourcecode\microsoft.leaked.source.code.archive_2020-10-04\nt5src\source\xpsp1\nt\base\busdrv\acpi\driver\amlinew\sched.c @ 275] ba551d64 ba74e137 897d1ca8 00000000 89913020 ACPI!RestartCtxtPassive+0x54 [e:\software\windowssourcecode\microsoft.leaked.source.code.archive_2020-10-04\nt5src\source\xpsp1\nt\base\busdrv\acpi\driver\amlinew\sched.c @ 384] ba551dac 80bd81ac 00000000 00000000 00000000 ACPI!ACPIWorker+0xbf [e:\software\windowssourcecode\microsoft.leaked.source.code.archive_2020-10-04\nt5src\source\xpsp1\nt\base\busdrv\acpi\driver\nt\worker.c @ 302] ba551ddc 80ae4212 ba74e078 00000000 00000000 nt!PspSystemThreadStartup+0x34 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 STACK_COMMAND: kb FOLLOWUP_IP: ACPI!ACPIBuildCompleteMustSucceed+31 [e:\software\windowssourcecode\microsoft.leaked.source.code.archive_2020-10-04\nt5src\source\xpsp1\nt\base\busdrv\acpi\driver\nt\buildsrc.c @ 431] ba732b29 c7401802000000 mov dword ptr [eax+18h],2 FAULTING_SOURCE_LINE: e:\software\windowssourcecode\microsoft.leaked.source.code.archive_2020-10-04\nt5src\source\xpsp1\nt\base\busdrv\acpi\driver\nt\buildsrc.c FAULTING_SOURCE_FILE: e:\software\windowssourcecode\microsoft.leaked.source.code.archive_2020-10-04\nt5src\source\xpsp1\nt\base\busdrv\acpi\driver\nt\buildsrc.c FAULTING_SOURCE_LINE_NUMBER: 431 FAULTING_SOURCE_CODE: No source found for 'e:\software\windowssourcecode\microsoft.leaked.source.code.archive_2020-10-04\nt5src\source\xpsp1\nt\base\busdrv\acpi\driver\nt\buildsrc.c' SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: ACPI!ACPIBuildCompleteMustSucceed+31 FOLLOWUP_NAME: MachineOwner MODULE_NAME: ACPI IMAGE_NAME: ACPI.sys DEBUG_FLR_IMAGE_TIMESTAMP: 62486e15 IMAGE_VERSION: 5.1.2600.1106 FAILURE_BUCKET_ID: 0xA5_ACPI!ACPIBuildCompleteMustSucceed+31 BUCKET_ID: 0xA5_ACPI!ACPIBuildCompleteMustSucceed+31 ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0xa5_acpi!acpibuildcompletemustsucceed+31 FAILURE_ID_HASH: {141550c3-a033-a93c-6e89-8fd34ca9e403} Followup: MachineOwner ---------

@Mov AX, 0xDEAD Interesting is also, what the acpi.sys from W2003 RTM sources tells to XP SP3 Dietmar PS: misc.c in base\busdrv\acpi\driver\amlinew for XP SP1 and Win2003 RTM and there with the Definition of ValidateArgTypes(POBJDATA pArgs, PSZ pszExpectedTypes) is exact the same.

@George King Your hack works exact as mine. But now other BSOD appears 0x000000A5 (0x00000002, xxx, 0x00000001, yyy) The "1" in this BSOD means: 1 : ACPI cannot convert the BIOS' resource list into the proper format. This probably represents a flaw in the BIOS' list encoding procedure. Dietmar

@George King Can you send to me the "free" 2.0 acpi.sys for tests Dietmar

@George King Can you please compile a "free" version of acpi.sys ver2.0 ? Because with dirty hack, the acpi.sys "Debug" version shows always BSOD 0x7E (0x80000003,..) meaning that a Breakpoint is reached Dietmar

On the new z690 Asrock extreme board, the new Vers 2.0 acpi.sys gives BSOD 0x000000A5 (0x00000003, 0x98E1DBA4, 0xC0140008, 0x494E495F) so until now manual hack in acpi.sys with IDAPro is needed also Dietmar PS: _ValidateArgTypes was called with 2nd arg = pointer to string with "H" char inside at winxp_5512 exist C, I, O, A, B, D, .. but not "H"

@Mov AX, 0xDEAD @George King I just test the new acpi.sys on the Asrock z370 Fatalty k6 board with 32 Gbyte ram. It works, nicccceeeeeeee!!!!!!!!! Interesting, that the Acpi error about mistake in DDB 0x000000A5 (0x00000011, 0x00000008, xxx, yyy) is not longer shown without any mod Dietmar

@Dave-H Without a 3 times checked whole Bios copy via EEpromer I would not do anything with Bios on the Flex 10. I for myself had the situation also with the Flex 10, that after modding the Bios it looks like dead. And in this case the only possibility is reflash original Bios via EEpromer. For DSDT the situation is a little bit other. You can upload an DSDT on the fly even in XP without any mod in Bios. But I never succeed with this Dietmar

Hi Dave, in this case your only chance is to mod your DSDT. Can you send me your DSDT form your Flex 10, extracted from Bios via iasl.exe Dietmar

@Dave-H Hi, here is my modded Bios for 64 Bit for the Flex 10 with n2806 cpu. https://ufile.io/taqxqvhl It has a working DSDT table inside for full Acpi XP SP3 and the ahci harddisk. Also I deleted the Whitelist in this Bios, so you can install every device that you want. This is the full 8Mbyte Bios, I think it can be only installed with an EEpromer. Make sure, that you have the Flex 10 version with n2806 cpu. There exist another, 32 bit Flex 10 with n2805 cpu. This n2805 is NOT compatible with my Bios! Make sure, that you make (read out) three valid copies of your Original Bios and compare them, that they are identic. I use the very best EEpromer REVELPROG IS via Ebay, costs about 150 Euro. Have a nice day Dietmar PS: I desolder the Bios chip from the Lenovo Flex 10 board. But do this only, if you are good in soldering:)).

Fresh XP pic from Corona Lab in Ingelheim in germany on 4 January 2022^^ Dietmar

@Dave-H Crazy hard work, to get XP SP3 to work on the Flex 10 board. At the end I get everything to work, only not the graphik driver. After loong searching in the dark I noticed, that ALL the problems of this board belongs to its DSDT table in Bios. Intel did all for the Baytrail chipset, that XP and even Win7 and Win8 do not run on it. After I changed DSDT in Bios (also crazy procedure, because I can do this only with EEPROMER), the problems are gone Dietmar PS: Now I am in Ukraine until 8 of January. Only at home I have this ready modded Bios.

@FantasyAcquiesce Do you get the Radeon x1300 to work under Win98? I tried x1400 on a Thinkpad T60 without success Dietmar

Yesssssssssssssssssssssaaaaaaaaaaaaaaaaaaa all USB3 on XP SP3 on Intel chipset on full ACPI Multiprocessor https://www.win-raid.com/t4035f45-Windows-XP-SP-bit-and-modern-PC-parts-86.html#msg84052 Dietmar

Now USB 3.0 works also on Intel chipset under XP SP3 Yesssssssssssssssssssssssssssssssssssaaaaaaaaaaaaaaaaaaaaaaaa:))))))))))))))))))!!!!!!!!!!!! Dietmar https://www.win-raid.com/t4035f45-Windows-XP-SP-bit-and-modern-PC-parts-82.html#msg83830

I succeed with USB 3.1 for USB boot XP SP3, Kanguru USB stick works fantastic, even write protected Dietmar https://www.win-raid.com/t4035f45-Windows-XP-SP-bit-and-modern-PC-parts-19.html#msg68271

Yessssssssssssssssssssssssssssssaaaaaaaaaaaaaaaaaa, I got all USB 3.0 3.1 3.2 drivers to work under XP SP3 !!!!! https://www.win-raid.com/t4035f45-Windows-XP-SP-bit-and-modern-PC-parts-72.html#msg83048

@~♥Aiko♥Chan♥~ The problem for me is, how to test acpi.sys for XP SP3 there because I do not have this board. But because it is sold in the time when XP was still spported, there a good chances for success, Dietmar PS: May be it can be done easy with fixed DSDT table. What is the exact BSOD 0xA5 (...)? Make a copy of this DSDT table using RW everything (XP, win7, win8, win10) and send it to me. With the nice program asl.exe the DSDT table is modded one time and stays in registry. This can be done without any ACPI, from "Standard PC". I have tested, works for XP SP3 without any need for modified acpi.sys or hacking Bios.

XP SP3 runs in full ACPI mode with nearly all drivers on Ryzen 3700x https://www.win-raid.com/t4035f45-Windows-XP-SP-bit-and-modern-PC-parts-68.html#msg82490 Dietmar

makecab acpi.sys is enough, gives you acpi.sy_ Dietmar

Best is, to make a new *.iso install CD for XP SP3 with nlite. And in installationsfolder, just change acpi.sys against new version via makecab.exe Dietmar PS: I tested this on 2 AM4 boards, asrock fatal1ty ab350 gaming k4 and asus prime b350 plus and a lot of newer Intel boards, works everywhere.

New acpi.sys I make which works until now on any XP SP3. AMD, Intel, new, old boards, all languages. Please test test test and tell results Dietmar acpi.rar

XP works on Ryzen https://www.win-raid.com/t4035f45-Windows-XP-SP-bit-and-modern-PC-parts-51.html#msg80487 Dietmar

Vista 32 bit does not work on B350 chipset (Ryzen). Only the 64 bit legacy Vista version works. On the Asrock fatal1ty ab350 gaming k4 it is impossible to have any kind of Vista 32 bit, because there is no APIC mode in Bios, only PIC. And because of this you get BSOD "no Acpi compatible Bios", no matter if you install Vista or use it from another compi (I try Vista 32 bit from AM3+ board) Dietmar

Hi, I am happy, when all AMD Ryzen users can make a quick test via rw-everything, if there is a MPS table on their board. For this, just click MPS on top of the RW-everything window Dietmar PS: I do not succeed to install Vista 32 bit on any Ryzen board. It is, because APIC mode is not enabled via Bios, and so ACPI fails.