Mov AX, 0xDEAD

v19041 doesn't have DEV_04D4 unsigned int __stdcall GigUndiDriverSupported() { unsigned int v0; int v2; memset(&v2, 0, 0x40u); GetDevicePciInfo(&v2); v0 = 0x80000003; if ( IsDeviceIdSupported(v2, SHIWORD(v2)) || IsLegacy1GServerDeviceIdSupported(v2, SHIWORD(v2)) || (_WORD)v2 == 0x8086u && (HIWORD(v2) == 0x1000 || HIWORD(v2) == 0x1001 || HIWORD(v2) == 0x1004 || HIWORD(v2) == 0x1008 || HIWORD(v2) == 0x1009 || HIWORD(v2) == 0x100C || HIWORD(v2) == 0x100D || HIWORD(v2) == 0x100E || HIWORD(v2) == 0x1015 || HIWORD(v2) == 0x1017 || HIWORD(v2) == 0x1016 || HIWORD(v2) == 0x101E || HIWORD(v2) == 0x100F || HIWORD(v2) == 0x1011 || HIWORD(v2) == 0x1026 || HIWORD(v2) == 0x1027 || HIWORD(v2) == 0x1028 || HIWORD(v2) == 0x1010 || HIWORD(v2) == 0x1012 || HIWORD(v2) == 0x101D || HIWORD(v2) == 0x1079 || HIWORD(v2) == 0x107A || HIWORD(v2) == 0x107B || HIWORD(v2) == 0x108A || HIWORD(v2) == 0x1099 || HIWORD(v2) == 0x10B5 || HIWORD(v2) == 0x1013 || HIWORD(v2) == 0x1018 || HIWORD(v2) == 0x1014 || HIWORD(v2) == 0x1078 || HIWORD(v2) == 0x1076 || HIWORD(v2) == 0x107C || HIWORD(v2) == 0x1077 || HIWORD(v2) == 0x1019 || HIWORD(v2) == 0x101A || HIWORD(v2) == 0x1075 || HIWORD(v2) == 0x105E || HIWORD(v2) == 0x105F || HIWORD(v2) == 0x1060 || HIWORD(v2) == 0x10D9 || HIWORD(v2) == 0x10DA || HIWORD(v2) == 0x10A4 || HIWORD(v2) == 0x10D5 || HIWORD(v2) == 0x10A5 || HIWORD(v2) == 0x10BC || HIWORD(v2) == 0x10B9 || HIWORD(v2) == 0x107D || HIWORD(v2) == 0x107E || HIWORD(v2) == 0x107F || HIWORD(v2) == 0x108B || HIWORD(v2) == 0x108C || HIWORD(v2) == 0x109A || HIWORD(v2) == 0x10D3 || HIWORD(v2) == 0x10F6 || HIWORD(v2) == 0x150C || HIWORD(v2) == 0x1096 || HIWORD(v2) == 0x1098 || HIWORD(v2) == 0x10BA || HIWORD(v2) == 0x10BB || HIWORD(v2) == 0x104C || HIWORD(v2) == 0x104D || HIWORD(v2) == 0x1049 || HIWORD(v2) == 0x104A || HIWORD(v2) == 0x104B || HIWORD(v2) == 0x1501 || HIWORD(v2) == 0x10BF || HIWORD(v2) == 0x10F5 || HIWORD(v2) == 0x10CB || HIWORD(v2) == 0x10BD || HIWORD(v2) == 0x10E5 || HIWORD(v2) == 0x294C || HIWORD(v2) == 0x10CC || HIWORD(v2) == 0x10CD || HIWORD(v2) == 0x10CE || HIWORD(v2) == 0x10DE || HIWORD(v2) == 0x10DF || HIWORD(v2) == 0x1525 || HIWORD(v2) == 0x10EA || HIWORD(v2) == 0x10EB || HIWORD(v2) == 0x10EF || HIWORD(v2) == 0x10F0 || HIWORD(v2) == 0x1502 || HIWORD(v2) == 0x1503 || HIWORD(v2) == 0x153A || HIWORD(v2) == 0x153B || HIWORD(v2) == 0x155A || HIWORD(v2) == 0x1559 || HIWORD(v2) == 0x15A0 || HIWORD(v2) == 0x15A1 || HIWORD(v2) == 0x15A2 || HIWORD(v2) == 0x15A3 || HIWORD(v2) == 0x156F || HIWORD(v2) == 0x1570 || HIWORD(v2) == 0x15B7 || HIWORD(v2) == 0x15B8 || HIWORD(v2) == 0x15B9 || HIWORD(v2) == 0x15D7 || HIWORD(v2) == 0x15D8 || HIWORD(v2) == 0x15E3 || HIWORD(v2) == 0x15D6 || HIWORD(v2) == 0x15BD || HIWORD(v2) == 0x15BE || HIWORD(v2) == 0x15BB || HIWORD(v2) == 0x15BC || HIWORD(v2) == 0x15DF || HIWORD(v2) == 0x15E0 || HIWORD(v2) == 0x15E1 || HIWORD(v2) == 0x15E2 || HIWORD(v2) == 0x10A7 || HIWORD(v2) == 0x10A9 || HIWORD(v2) == 0x10D6 || HIWORD(v2) == 0x10C9 || HIWORD(v2) == 0x10E6 || HIWORD(v2) == 0x10E7 || HIWORD(v2) == 0x10E8 || HIWORD(v2) == 0x1526 || HIWORD(v2) == 0x150A || HIWORD(v2) == 0x1518 || HIWORD(v2) == 0x150D || HIWORD(v2) == 0x150E || HIWORD(v2) == 0x150F || HIWORD(v2) == 0x1510 || HIWORD(v2) == 0x1511 || HIWORD(v2) == 0x1516 || HIWORD(v2) == 0x1527 || HIWORD(v2) == 0x438 || HIWORD(v2) == 0x43A || HIWORD(v2) == 0x43C || HIWORD(v2) == 0x440 || HIWORD(v2) == 0x1521 || HIWORD(v2) == 0x1522 || HIWORD(v2) == 0x1523 || HIWORD(v2) == 0x1524 || HIWORD(v2) == 0x1F40 || HIWORD(v2) == 0x1F41 || HIWORD(v2) == 0x1F45 || HIWORD(v2) == 0x1533 || HIWORD(v2) == 0x1536 || HIWORD(v2) == 0x1537 || HIWORD(v2) == 0x1538 || HIWORD(v2) == 0x157B || HIWORD(v2) == 0x157C || HIWORD(v2) == 0x1539 || HIWORD(v2) == 0xDEADu) ) { v0 = 0; } return v0; }

@Dietmar kdnet.dll is same for W8.1 and W10 mini-driver W8.1: kd_02_8086.dll -> kdstub.dll W10: kd_02_8086.dll -> kdnet10.dll + special kdstub.dll(https://github.com/MovAX0xDEAD/KDNET/blob/master/kdstub.dll)

@pappyN4 I recommend wait for separate W2003 Acpi v2.0 source release, it based on leaked W2003 RTM sources, not XP

@Andalu https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/supported-ethernet-nics-for-network-kernel-debugging-in-windows-10 told about DEV_04D4 (Andalu's i219V chip) support for Windows 10, version 20H2 Build 19042 https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/supported-ethernet-nics-for-network-kernel-debugging-in-windows-10-2004 told about DEV_04D4 (i219V) not support for Windows 10, version 20H2 Build 19041 I send to you 19041 and 17763 version, so probably you just need very last version of kd_02_8086.dll renamed to kdnet10.dll

@Andalu, @Dietmar Seems mini-driver has problem with some new Intel LAN chips I have only Realtek and Atheros/Qualcomm chips and never has issue with 8.1 or 10 mini-driver To test Intel drivers i used VirtualBox and Vmware, they emulate Intel PRO/1000 LAN chip and no issues at all i recommend to use /PCI_ID= option for Intel because minidriver set variable buffer size depends on chip ID

Link to update v3 was updated, i don't know why previous was wrong

@Dietmar Show missed lines

@Damnation I don't want to waste time for making "frankenstein", you can do it yourself, see ACPIDevicePowerProcessPhase3() as example OR make remote kernel debug logs and i give solution at sources level

Any VBox works with original XP install CD, select IDE Controller at Storage setting Qemu.exe -M "pc" : emulates ACPI1.0 hardware with IDE controller Qemu.exe -M "q35" : emulates ACPI2.0 hardware with SATA controller All Qemu versions after v0.15 are incredible slow without HAX acceleration, but q35 emulation started since v2.x with HAX acceleration i never run XP succefull, it just hangs or crash

@Damnation I made list of unresolved issues at first post

@daniel_k ACPIBuildCompleteMustSucceed() :

i think i forgot about "C language" operator ! and & priority fixed: or second, more reliable (not tested, VBox doesn't have non-pci devices with IRQ) variant: ACPIInternalIsPci() itself set DEV_CAP_PCI and DEV_CAP_PCI_DEVICE so we can trust him

see PM

i can compile your irqarb.c without any errors 1>Linking Executable - nt\obj\i386\acpi.sys for i386 BUILD: Done

@daniel_k 1) New opcodes like concatenaterestemplate() used in_CRS, when you skip it -> wrong resource list returned to OS 2) My implementation/decompilation of new 13 acpi 2.0 commands is error-free :), we can use it same way as v.6666

as i wrote before, this is not "best", we don't know how acpi driver set Flags for all devices, DEV_CAP_PCI_DEVICE may be not setted for all pci like devices, best ways: 1) using additional call to isPciDevice() instead direct flag check, isPciDevice look for _ADR method and parent bus, return FALSE if not 2) add AMDI0030 (and similar non-pci devices) to table AcpiInternalDeviceFlagTable[] to set flag DEV_CAP_ISA or new flag #define DEV_CAP_EXCLUDEFROMPRT 0x0000010000000000 add check for this flag to AcpiArbCrackPRT()

@daniel_k i dont understand idea, if you want keep original acpi 1.0b driver and patch instead tables - I'm not interested

this better: in both cases we must be 100% sure about configured flags for all devices, need additional debug print i already did it partialy, but not inside AcpiArbCrackPRT(), check Dietmar's logfile:

@daniel_k Bad idea, GPIO is not pci device and have fixed IRQ Vector Problem is bugged acpi code, it should not call AcpiArbCrackPRT() for non-pci devices, or have check for non-pci inside AcpiArbCrackPRT() at least

i already wrote how to avoid BSOD and keep running AcpiArbCrackPRT() see https://msfn.org/board/topic/183464-compiling-acpi-v20-driver-for-windows-xp-sp3-x32-only/?do=findComment&comment=1216379

@daniel_k Sorry, i don't understand DSDT enough, only INTEL knows how this crap works C3 is ACPI hardware, as i remember anything after 110 chipset has disabled acpi's power-saving part

@daniel_k no BSOD description/log - no workaround port 60 emulation is bios SMM hack, i think problem in bios code

First record about calling AcpiArbCrackPRT(): PGS_ - internal ACPI device object you did't !devobj 8A545038 end of log tell about devnodes: so AcpiArbCrackPRT was called for AMDI0030 (GPIO) before loading pci.sys as Daniel said before after quick analyzing DSDT i see this: GPIO connected to SystemBus directly and have _CRS method to inform about claimed IRQ GPIO is not under usual _SB.PCI0. path - i think this is problem description of AcpiArbCrackPRT(): but inside AcpiArbCrackPRT no check for non-pci device *facepalm* only strange check:

@Dietmar Check PM for custom acpi.sys if you still interested what wrong on amd board 1) ed Kd_ACPI_Mask 0xFFFFFFFF 2) AcpiArbCrackPRT() has additional output, look for "Adding allocation for IRQ" string: .... Adding allocation for IRQ b for device 81B7F7E0 0x81b7f560 0x69635030 0xf99afb98 0x0 `ї╖Б 0Pci Ш√Ъ∙ PCI Device 81B7F7E0 had _ADR of 5 ... Adding allocation for IRQ f for device 81B82170 0x0 0x0 0x81bacf38 0x81b82170 8╧║Б p!╕Б Referencing vector f : 0 0 3) get details of devices: !devobj 81B7F7E0 Device object (81b7f7e0) is for: NTPNP_PCI0005 \Driver\PCI DriverObject 81b69900 Current Irp 00000000 RefCount 0 Type 00000022 Flags 00001040 Dacl e140fd5c DevExt 81b7f898 DevObjExt 81b7f960 DevNode 81b85a68 ExtensionFlags (0000000000) Characteristics (0x00000100) FILE_DEVICE_SECURE_OPEN AttachedDevice (Upper) 81adc3e8 \Driver\HDAudBus !devobj 81B82170 Device object (81b82170) is for: PciIde0Channel1-1 \Driver\PCIIde DriverObject 81bacf38 Current Irp 00000000 RefCount 0 Type 00000004 Flags 00001040 Dacl e140fd5c DevExt 81b82228 DevObjExt 81b822e0 DevNode 81bd6dc8 ExtensionFlags (0000000000) Characteristics (0x00000100) FILE_DEVICE_SECURE_OPEN AttachedDevice (Upper) 81bd0030 \Driver\atapi

OK, let assume this bsod was random From my old list there are still some left 1) 0xA5 (0x0000000D, ..., ..., ...) duplicated _HID method for AMD boards 2) 0xA5 (0x11, 0x08, ..., ...) unknow error in _AMLILoadDDB() 3) 0xA5 (0x2001, 0x01, 0xC0000034, ...) Failure to evaluate the _PIC method NotifyHalWithMachineStates() and more binary patches to acpi.sys from Daniel/Dietmar/Daniel/Infuscomus and Patch Integrator