Dietmar

@Andalu The only idea that I have, is to put the debug acpi.sys and its debug acpi.pdb in W:\Symbols2 also Dietmar EDIT: And delete my path (whole folder) C:\NT\base..

@Mov AX, 0xDEAD Before, I always updated my acpi files by hand. This time for the first I use your patch. I noticed, that in bus.c you changed in status = PnpBiosResourcesToNtResources( ASSERT(NT_SUCCESS(status)); ==> //ASSERT(NT_SUCCESS(status)); Dietmar

@Andalu Put the new debug acpi.sys and its acpi.pdb into your folder W:\Symbols4 . This is my way Dietmar

@Andalu I think, that the problem is the double definition of a lot of devices in DSDT as @canonkong noticed. So, win7 gives the same Bsod. We can write a hack for this but better solution is a debug LOG, what is exact going on Dietmar

@Damnation Here is the fresh from @Mov AX, 0xDEAD via Patch compiled by me, acpi.sys v6 and its acpi.pdb for XP SP3 Dietmar https://ufile.io/6iesmav8 and here its Debug version https://ufile.io/7kciqjd2

@un user I have a german SP1 XP CD Pro. This CD I updated with the Service Packs to SP3. During such a lot of tests I noticed, that any XP build with this CD is more stable than with its german original XP SP3 CD Dietmar

@Mov AX, 0xDEAD I hope, that I understand your idea correct: I do all the steps. in "3) Look for changes in Device Manger after first reboot" I do this last reboot with the line in boot.ini with /ONECPU switch as before. cpu-z shows one core, one thread. And in Device Manager I can see for the 12600 cpu 10 times correct with friendly name 12600 and 2 times with "Intel Processor" Dietmar EDIT: Exact the same happens, when I take the normal line in boot.ini on second reboot. And: After next next reboot, all 12 cores are shown in Device Manager again with friendly name 12600, no matter if I choose 1 core in boot.ini or all.

@canonkong Can you please upload your unmodded and also the modded acpi tables for your Bios mod for the new processor definition Dietmar

@Mov AX, 0xDEAD Is there something, that I can test more? The very last free acpi.sys that you send to me, is it based on exact the same Source Code as the checked one Dietmar PS: I make another test. With the working free acpi.sys on this XP SP3, I delete all entries in registry about intelppm and also all entries in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\ACPI\GenuineIntel_-_x86_Family_6_Model_151 In Device Manager, then all processors are gone. On next reboot, always 10 cores are shown correct with their friendly name. The others as Intel Processor (2 for 12600 and 14 for 12900k). On next reboot, all get their correct friendly name on all boards and for the 12600 and the 12900k cpu.

@Mov AX, 0xDEAD Yesssa , with this free acpi.sys all cpu's are correct listed at once! I make a test before last reboot of XP GUI install on other compi, loading registry HIVE system. In ENUM for the Genuine Intel randomally some cores have friendly name and some not. But all have service intelppm Dietmar

@Mov AX, 0xDEAD Yes, with this modded Bios always at once all cpu's (12900k, 12600, on 3 boards) are listed correct in Device Manager. BUT: Only the power cores work, the E-cores are listed but just do nothing, in XP SP3, win7 SP1, win8.1 all 32 bit version, and win10 (bit64). I noticed the "notwork" of the E-cores from 12900k only via its power consumption (few Watt) against 25 Watt with all cores working at 0% load and about 30% less cpu power in different benchmarks Dietmar PS: Thanks for free acpi.sys . I just set up a brandnew original XP SP3 with it and will soon report.

@Mov AX, 0xDEAD I remember my tests with the acpi.sys from outerspace ) 6666. With Ryzen cpu's, that only all cores are enumerated correct in Device Manager happens there also sometimes only on second reboot. And all those Bios use the old processor definition. So, this is not a special problem of the new processor definition via 0007 device. This "not recognicing of all cpu's correct on first boot" happens at a different place Dietmar

@Mov AX, 0xDEAD Can you send me the acpi.sys FREE version from this new acpi.sys. I will test Dietmar

@Mov AX, 0xDEAD First I try the patched SSDT from @Damnation . But with new Bios, this gives always Bsod. Infuscomus then put this patch into DSDT. I delete there all the now unnecessary entries for the 0007 device. This works. BUT: Via Benchmark tests and power consumption with this patched Bios, only the power cores where recogniced, even in win10. Here is the modded DSDT but your acpi.sys is better. It looks, as now it only needs one reboot and all is ok with cpu's in Device Manager Dietmar https://ufile.io/nh6xuban

@Mov AX, 0xDEAD When you compare genuine2 (error) with genuine3 (all ok) you see, that the entry "FriendlyName"="12th Gen Intel(R) Core(TM) i5-12600" is missed for cpu 8 and 9 only in genuine2 Dietmar

@Mov AX, 0xDEAD And here is the ENUM entry for working 12600 entries for all cpu after 3 reboot with connected Windbg Dietmar https://ufile.io/fhd4s0pv

@Mov AX, 0xDEAD For to understand, what is going on, I deleted all entries in registry services for intelppm. Also I delete the entry in ENUM for Intel processors. Voila, on next reboot with connected Windbg again only the cpu 1,2,3,4,5,6,7,10,11 have the correct entry in Device Manager 12600 and the 8,9 have the entry "Intel Processor". After reboot with Windbg connected, again all processors are shown correct as 12600. Here is the ENUM entry with the error "Intel Processor" Dietmar https://ufile.io/yg35vs8s

@Mov AX, 0xDEAD Something strange happened: I start this XP SP3 again on the MSI z690-A pro DDR4 and 12600 cpu with connected Windbg, but now only from breakpoint for acpi.sys driver entry (means without ed Kd_ACPI_Mask 0xFFFFFFFF). And then hit in KD line just g. Now, all 12 processors show the correct name 12600 in Device Manager. So, your way for to fix the names works on this compi. Also the message in registry for intelppm about INITSTARTFAILED is gone. The cpus are now listed there on both sides the same as 0,1,10,11,2,3,4,5,6,7,8,9 Dietmar Here is the wished reg entry, from now with working cpu names https://ufile.io/hxdbepgg

@Mov AX, 0xDEAD Here is the new acpi.sys log file. https://ufile.io/91peohe2 I noticed, that the cpu with number A,B have now their correct number 12600. But after the mix of numbers, now the 8,9 have the wrong name "Intel Processor". These new 8,9 are the old A, B. In registry for the intelppm there is also an entry INITSTARTFAILED with value 1 Dietmar

@XP4ever I have also an normal Lenovo x230 notebook. On this notebook I make the same experience as you. After I installed under XP SP3 the USB3 driver, it was impossible to work with it any longer. And this behavior cant be reverted by deinstalling the USB2,3 driver. Now I think, that the Intel chipset driver for USB2 and any USB3 driver are incompatible. You have to make a new install of XP on this notebook without any chipset driver. After this, use the AMD USB3 driver 145 from @daniel_k for this notebook, Dietmar

@Mov AX, 0xDEAD Here is the wished APIC table from the MSI z690-A Pro DDR4 board with Intel 12600 cpu Dietmar https://ufile.io/my1inpxm

@Mov AX, 0xDEAD Here is the full acpi Windbg log file until XP SP3 reaches Desktop. I make it on the MSI z690-A Pro DDR4 board with new acpi.sys, Debug version. It shows in Device Manager 0,1,2,3,4,5,6,7,8,9 correct as 12600 cpu but the last A, B as Intel Processor. This cpu has 6 cores and 12 threads Dietmar https://ufile.io/fzgm5xr7

@Damnation Here is the debug version of new acpi.sys Dietmar https://ufile.io/0kgtqohx

@canonkong Make some Benchmark tests, if really all cores work with modded Bios. After my Bios modd (for Intel cpu), only the power cores work, even ALL cores are listed in Device Manager Dietmar

@Mov AX, 0xDEAD I will do Windbg session for acpi. But I need help, how I should do this for to get the wished information. I remember last time, that you have even modded a Source-file for this acpi.sys for to produce enough output, thanks a lot Dietmar