Dietmar

@pappyN4 What exact should I test on Intel board? The power consumption goes down to a few Watt with the nice DSDT patch from @Damnation. If you have a problem with CPU under heavy load, make a test with running prime95 stress test with AVX (from Ramsey XP) enabled and in the same time CINEBENCH_11.529 few times. If the compi survives 20 min, you have no problem with temperature. I think, about 80% of compis fail this. Also after this you can run memtest for 4 hours. If this is also ok, the problem is not in memory and not in cpu and not in temperature Dietmar PS: XP has some problems with different kind of cpu cores. When you can disable the efficients cores, you can see if the crash is connected to them. For me interesting is, that a 9900k is much faster than a 12900k with disabled effiziency cores. EDIT: I just remember, that I have problems like you describe 3 years ago. This happens because of a bad Power supplier, even this was brandnew. Make test with another Power Source, just make sure that it can deliver the needed Watt.

Hi, I do not find the original Source, I think it was somewhere on the Maxthon Homepage. I think, that it was this one mx5.3.8.2000.exe for Bit 32 and XP SP3 https://ufile.io/rbfpwtzc No modd, this is the last version that works under XP. It has some big advantages, it uses multicores of cpu and can open any videos Dietmar

@reboot12 I have the same problem. But the Mypal browser from Feodor works and also the Maxthon 5 browser Dietmar

@Damnation Mostly everything works nice on z690 for XP. With the asl.exe DSDT patch, power consumption is now small as much as possible. Some boards have problems with their Bios and XP. Some programs have problems with the mix of power and not power cores, all browser crash on their shutdown, only Mypal from Feodor not. And the most most XP friendly board is the Asrock Extreme z690. The Fernando 1006 Sata driver crashes on most boards. The only Sata driver, that works on ALL z690 boards is the one from Kai Schtrom. Win10 bit 32 cant be installed on some z690 boards. All together you can make a machine with XP SP3 with a z690 board, that can be used for everything on daily work and it is ultrafast. I have the program Mathematica 5 from 1998, which also runs under win95. Under XP it is soso much faster than any newer Mathematica on Win10 (maybe 10 times faster) Dietmar

@Damnation Yes, but via this way about 100 unknown devices are shown in Device manager, because the ACPI0007 device is still there Dietmar

@Damnation Happy, that it works for you!!! I noticed, that your full DSDT is split in 3 parts. Normally, full DSDT.aml has a size up to 500 kB, but this part only about 27 kB. May be, that some information is needed from all the DSDT together Dietmar

@Damnation @Mov AX, 0xDEAD tries to do everything in one step. In my eyes this is a mistake. So, with his patcher you can also compile *.dsl files and vice versa with the 3 offered Iasl. And you can build a Diff file. You dont need most of the steps, because you can use your own compiled dsdt.aml etc. Dietmar

@Damnation The advantage of the @Mov AX, 0xDEAD DSDT patcher is, that you also dont need to install the Acpi files always new. But it loads each DSDT table really new at boottime. The asl.exe stores DSDT permanent in registry. With your cpu patched SSDT and grub2, can you now see your exact processor description at processors in Device Manager of XP Dietmar

@Damnation

@Damnation Have you tested the DSDT patcher at boottime from @Mov AX, 0xDEAD? He updated his Tutorial here at MSFN, now it is much more easier and it works, I tested Dietmar

@Damnation Make a new extract of all Acpi files under running Win10 from your compi. Do you have Bios 2.2? Because from the Asrock Webside I read, that with from Bios 2.10 upward enable AMD CPU fTPM in BIOS default. Can you disable fTPM in Bios? If not, you can go back to an older Bios, BUT ALWAYS RISK to change something in BIOS. And then try to upload its own dsdt.raw with the asl.exe tool under XP SP3. Later you can edit a little thing via dsdt.dsl and look, if it is still loaded after reboot with the asl.exe tool Dietmar

@jaclaz Hi Jaclaz, I noticed the same. The Browser from Feodor MyPal works under XP SP3 for the forum here, have a nice evening Dietmar https://github.com/Feodor2/Mypal68/ And the Maxthon 5 browser also for XP SP3 https://www.maxthon.com/mx5/

@Damnation Exact this happens to me, when I take the DSDT from the Bios and not from the running XP Dietmar

@Damnation Because it works for me on the Asrock z690 Extreme board and also on the Asrock z370 k6 gaming board, the only idea that I have is, that some settings on your Bios does not match for to upload those tables Dietmar

@Damnation Make sure, that Secure Boot is disabled in your compi Bios settings. With Microsoft I think, that then no Acpi Tables are taken from registry, only from Bios Dietmar

@Damnation They are both in this acpi.reg file: DSDT and SSDT2. It should work. My compi refuses to boot, after I offered him this acpi.reg file, which simple means, that it is loaded. The only problem that I had before was, when I take the DSDT direct out of the Bios. With the acpi tables taking from running windows, all is nice now. Everything works for me, even with acpi.reg from other compi Dietmar PS: By the way I noticed, that RWEverything reads out the loaded ACPI tables and not them from Bios. So, with RW Everything you can make a very quick check, if the tables are loaded.

@Damnation Here it is. Be careful, because your XP will not longer start if something goes wrong Dietmar https://ufile.io/ummtcs4q

@Damnation Only the needed tables, that you can see the processors in XP. No garantie that it will work, but I try. Before you click on the acpi.reg file, make sure, that you have a rescue copy of the whole folder system32 of your XP Dietmar

@Damnation I mean, that I make from your Acpi tables a single acpi.reg file and that file I send back to you. So you can test, if my hack for to load any acpi tables on any XP works without any tool, without any asl.exe, just by hand Dietmar PS: By the way, the asl.exe tool works also for newer versions of Windows. May be, that my hack of registry works there also and even on pure UEFI machines, oh, this would be a nice virus.. Via this way you should load up ANY Acpi tables on any Windows PC. Anyway we have now a 4. methode, for to upload any Acpi tables and may be, that this is the most universal.

@Damnation Send me your wished tables, which you want to upload. I upload them to my Registry and make an *.reg file from them. Only risk for you can be, that your XP installation may be destroyed after, when you install this *.reg file. For to overcome this risk, make from an outstanding Windows a copy of your system32 folder and rename this copy to system32rett. When something went wrong, you just choose this system32rett, delete damaged system32, and rename it system32rett to system32 Dietmar

@Damnation Where is limit in the sky, I just succeed to upload a different DSDT without any asl.exe to registry , and indeed THIS new DSDT is loaded from XP SP3 after reboot, and stays there until I delete it by hand from registry.. Dietmar EDIT: This overcomes any signing limits or versions limit of the DSDT. I also "succeed" to upload the DSDT and SSDT from the z690 Asrock Extreme board to the z370 Asrock gaming k6 board a, only mistake I see then is, that suddently the i8700k cpu of the Asrock k6 board has 24 cores^^..

@Damnation Here is the compare of HKLM from XP SP3 without ASL (named ORI) and with ASL. You can see, that asl.exe does a very simple job. Some is there with Cryptographie, which I dont understand. But mostly asl.exe puts the table DSDT in this key [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\ACPI\Parameters\DSDT\ALASKA\A_M_I_\01072009] So, any with asl.exe uploaded DSDT and also SSDT comes into ControlSet001\Services\ACPI\Parameters\DSDT ControlSet001\Services\ACPI\Parameters\SSDT Dietmar https://ufile.io/v4btld4z

@Damnation Oh, soso much fun. With a ram boot XP I extract the whole registry HKLM. Editor needs even in ram some time for to open this 52 Mbyte *.reg file. And then I let asl.exe upload its tables and read again whole HKLM out. Before reboot I compare both registries then with Beyond Compare 2 Dietmar

@Damnation I think, even without the asl.exe tool you can add the acpi tables by hand to registry. This I will try now. My only problem in this is, how to translate the Hex *.reg outread from Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\HARDWARE\ACPI\DSDT because this outread contains "," and linebreaks instead of pur hex code Dietmar

@Damnation The asl.exe has a BIG downside: ALWAYS test your dsdt.aml files with another methode before!!! Because when your DSDT or SSDT has an error, asl.exe uploads this fatal table also to the Registry of your XP and makes XP unbootable Dietmar From Microsoft: Using the Microsoft ASL compiler's ACPI-table-load feature During system development, it is useful to have a way to simulate various ACPI BIOS constructs and test them on the development system. The Windows operating system allows certain ACPI tables to be loaded from the Windows registry instead of from the PC's BIOS ROM. Use of this feature requires administrator privileges, and also requires that test signing be enabled on the system. For systems that support UEFI Secure Boot, test signing cannot be enabled, and the compiler's table-load feature cannot be used unless UEFI Secure Boot is disabled or the Windows Debug Policy is installed on the system. To use the table-load feature, the ACPI table to be overloaded must meet the following requirements: The table to be overloaded must already be present in the system's BIOS ROM. For instance, the DSDT can be overloaded; however, if the machine does not have an SSDT, you cannot force an SSDT to be loaded from this registry override mechanism. The table must contain AML code that is normally consumed by the Windows ACPI interpreter (the Acpi.sys driver). The table with the highest version number will be loaded. The table loaded into the registry for testing must have a higher version number than the same table in the BIOS ROM. The table to be loaded must be in compiled (AML) format and loaded into the registry in the correct location, with the correct parameters specified. The mechanism described herein is designed to handle all aspects of loading the table and configuring the registry.