Dietmar

@Mov AX, 0xDEAD With new XP SP1 Sources I can compile acpi.sys. My acpi.sys, compiled under XP SP3, is a little bit smaller than yours but shows the same output in Windbg, and same Bsod. 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.104 on port 50000 on local IP 192.168.2.101. Connected to Windows XP 2600 x86 compatible target at (Wed Apr 13 04:02:38.046 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:\symbolssss Symbol search path is: C:\symbolssss Executable search path is: C:\Symbols Windows XP Kernel Version 2600 MP (1 procs) Checked x86 compatible Built by: 2600.xpsp.080413-2133 Machine Name: Kernel base = 0x80a02000 PsLoadedModuleList = 0x80b019e8 System Uptime: not available ************* 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:\symbolssss OK C:\symbols OK C:\symbolss OK C:\symbolsss OK E:\binaries.x86fre\Symbols Deferred https://msdl.microsoft.com/download/symbols Deferred srv* Closing open log file otto7 Opened log file 'ottoPCI' Break instruction exception - code 80000003 (first chance) nt!DbgBreakPoint: 80ac37e0 cc int 3 kd> g MM: Loader/HAL memory block indicates large pages cannot be used for 80100000->8012777F MM: Loader/HAL memory block indicates large pages cannot be used for 810A6000->8258AFFF MM: Disabling large pages for all ranges due to overlap *** Assertion failed: PciInterfacesInstantiated *** Source File: c:\nt\base\busdrv\acpi\driver\nt\irqarb.c, line 3514 Break repeatedly, break Once, Ignore, terminate Process, or terminate Thread (boipt)? i i *** Assertion failed: pciInterface *** Source File: c:\nt\base\busdrv\acpi\driver\nt\irqarb.c, line 3520 Break repeatedly, break Once, Ignore, terminate Process, or terminate Thread (boipt)? i i PS: Unhandled Kernel Mode Exception Pointers = 0xBACC69DC Code c0000005 Addr BA6CABFC Info0 00000000 Info1 00000010 Info2 00000010 Info3 8A4EB2F8 *** Fatal System Error: 0x0000007e (0xC0000005,0xBA6CABFC,0xBACC6E90,0xBACC6B8C) 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 (Wed Apr 13 04:02:50.218 2022 (UTC + 2:00)), ptr64 FALSE Loading Kernel Symbols .................................... Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7E, {c0000005, ba6cabfc, bacc6e90, bacc6b8c} *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 Probably caused by : ACPI.sys ( ACPI!AcpiArbCrackPRT+110 ) Followup: MachineOwner --------- nt!RtlpBreakWithStatusInstruction: 80ac37ec cc int 3 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: c0000005, The exception code that was not handled Arg2: ba6cabfc, The address that the exception occurred at Arg3: bacc6e90, Exception Record Address Arg4: bacc6b8c, Context Record Address Debugging Details: ------------------ *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung "0x%08lx" verweist auf Speicher bei "0x%08lx". Die Daten wurden wegen eines E/A-Fehlers in "0x%081x" nicht in den Arbeitsspeicher bertragen. FAULTING_IP: ACPI!AcpiArbCrackPRT+110 [c:\nt\base\busdrv\acpi\driver\nt\irqarb.c @ 3537] ba6cabfc ff5610 call dword ptr [esi+10h] EXCEPTION_RECORD: bacc6e90 -- (.exr 0xffffffffbacc6e90) ExceptionAddress: ba6cabfc (ACPI!AcpiArbCrackPRT+0x00000110) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 00000000 Parameter[1]: 00000010 Attempt to read from address 00000010 CONTEXT: bacc6b8c -- (.cxr 0xffffffffbacc6b8c;r) eax=bacc7070 ebx=00000000 ecx=0000bb40 edx=00000056 esi=00000000 edi=8a4a8b10 eip=ba6cabfc esp=bacc6f58 ebp=bacc70a0 iopl=0 nv up ei ng nz na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286 ACPI!AcpiArbCrackPRT+0x110: ba6cabfc ff5610 call dword ptr [esi+10h] ds:0023:00000010=???????? Last set context: eax=bacc7070 ebx=00000000 ecx=0000bb40 edx=00000056 esi=00000000 edi=8a4a8b10 eip=ba6cabfc esp=bacc6f58 ebp=bacc70a0 iopl=0 nv up ei ng nz na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286 ACPI!AcpiArbCrackPRT+0x110: ba6cabfc ff5610 call dword ptr [esi+10h] ds:0023:00000010=???????? Resetting default scope PROCESS_NAME: System ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung "0x%08lx" verweist auf Speicher bei "0x%08lx". Die Daten wurden wegen eines E/A-Fehlers in "0x%081x" nicht in den Arbeitsspeicher bertragen. EXCEPTION_PARAMETER1: 00000000 EXCEPTION_PARAMETER2: 00000010 READ_ADDRESS: 00000010 FOLLOWUP_IP: ACPI!AcpiArbCrackPRT+110 [c:\nt\base\busdrv\acpi\driver\nt\irqarb.c @ 3537] ba6cabfc ff5610 call dword ptr [esi+10h] BUGCHECK_STR: 0x7E DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre DPC_STACK_BASE: FFFFFFFFBACCC000 LOCK_ADDRESS: 80afd6c0 -- (!locks 80afd6c0) Resource @ nt!IopDeviceTreeLock (0x80afd6c0) Shared 1 owning threads Threads: 8a528da8-01<*> 1 total locks, 1 locks currently held PNP_TRIAGE: Lock address : 0x80afd6c0 Thread Count : 1 Thread address: 0x8a528da8 Thread wait : 0xd1 LAST_CONTROL_TRANSFER: from 80a30d7b to 80ac37ec STACK_TEXT: bacc70a0 ba70af2a 8a4a8b10 bacc70cc bacc70e0 ACPI!AcpiArbCrackPRT+0x110 [c:\nt\base\busdrv\acpi\driver\nt\irqarb.c @ 3537] bacc70d4 ba71a367 ba700f00 bacc70f0 e134c934 ACPI!AcpiArbAddAllocation+0x9d [c:\nt\base\busdrv\acpi\driver\nt\irqarb.c @ 1474] bacc7158 ba709c7d e1359d50 e134c934 ba700f00 ACPI!ArbBootAllocation+0xf5 [d:\xpsp1\base\ntos\arb\arbiter.c @ 1406] bacc716c ba71a3de ba700f00 e134c934 e134c934 ACPI!AcpiArbBootAllocation+0x49 [c:\nt\base\busdrv\acpi\driver\nt\irqarb.c @ 1850] bacc7188 80b6c111 ba700f00 00000009 bacc71a8 ACPI!ArbArbiterHandler+0x52 [d:\xpsp1\base\ntos\arb\arbiter.c @ 1562] bacc71c4 80b6d093 bacc71b8 00000000 80afd1c0 nt!IopBootAllocation+0xbb bacc7208 80b6d80b 00000004 e1359d00 e1350ef8 nt!IopAllocateBootResourcesInternal+0xc5 bacc7228 80d38c8b 00000004 8a4a8b10 e1350ef8 nt!IopAllocateBootResources+0x75 bacc724c 80b5653a 00000004 8a4a8b10 e1350ef8 nt!IopReportBootResources+0x65 bacc727c 80b5cb93 8a4bec78 800005f8 00000001 nt!PiQueryAndAllocateBootResources+0x150 bacc736c 80b5d26d 8a4bec78 00000000 00000000 nt!PipProcessNewDeviceNode+0xc9d bacc75c4 80a2cff0 8a4f1828 00000000 00000000 nt!PipProcessDevNodeTree+0x1bd bacc7608 80a2d2fb 00000000 00000000 80091178 nt!PipDeviceActionWorker+0xc4 bacc7620 80d37f53 00000000 00000006 00000000 nt!PipRequestDeviceAction+0x13b bacc7684 80d341f1 80085000 bacc76a0 00034000 nt!IopInitializeBootDrivers+0x39b bacc7830 80d31940 80085000 00000000 8a528da8 nt!IoInitSystem+0x82d bacc7dac 80bd81ac 80085000 00000000 00000000 nt!Phase1Initialization+0xb12 bacc7ddc 80ae4212 80d30e2e 80085000 00000000 nt!PspSystemThreadStartup+0x34 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 FAULTING_SOURCE_LINE: c:\nt\base\busdrv\acpi\driver\nt\irqarb.c FAULTING_SOURCE_FILE: c:\nt\base\busdrv\acpi\driver\nt\irqarb.c FAULTING_SOURCE_LINE_NUMBER: 3537 FAULTING_SOURCE_CODE: 3533: &classCode, 3534: &subClassCode, 3535: &parent, 3536: &routingToken, > 3537: &flags); 3538: 3539: if (!NT_SUCCESS(status)) { 3540: return STATUS_NOT_FOUND; 3541: } 3542: SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: ACPI!AcpiArbCrackPRT+110 FOLLOWUP_NAME: MachineOwner MODULE_NAME: ACPI IMAGE_NAME: ACPI.sys DEBUG_FLR_IMAGE_TIMESTAMP: 62562bdf IMAGE_VERSION: 5.1.2600.1106 STACK_COMMAND: .cxr 0xffffffffbacc6b8c ; kb FAILURE_BUCKET_ID: 0x7E_ACPI!AcpiArbCrackPRT+110 BUCKET_ID: 0x7E_ACPI!AcpiArbCrackPRT+110 ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x7e_acpi!acpiarbcrackprt+110 FAILURE_ID_HASH: {a86b27ef-d17a-5a94-e401-dcba315598cf} Followup: MachineOwner --------- 0: kd> lm start end module name 80070000 80080a80 pci (deferred) 80100000 80127780 HAL3 (deferred) 80128000 80150000 kdcom (deferred) 80150000 8017a000 KDSTUB (deferred) 80a02000 80da3000 nt (pdb symbols) C:\Programme\Windows Kits\8.1\Debuggers\x86\sym\ntkrpamp.pdb\5B9E8A586D3D49D98927B5D5117577231\ntkrpamp.pdb ba448000 ba461b80 Mup (deferred) ba462000 ba48e980 NDIS (deferred) ba48f000 ba51b600 Ntfs (deferred) ba51c000 ba579000 UsbHub3 (deferred) ba579000 ba5be000 USBXHCI (deferred) ba5be000 ba5d4880 KSecDD (deferred) ba5d5000 ba5e6f00 sr (deferred) ba5e7000 ba606b00 fltMgr (deferred) ba607000 ba61c000 amd_sata (deferred) ba61c000 ba635000 storport (deferred) ba635000 ba646000 storahci (deferred) ba646000 ba66ba00 dmio (deferred) ba66c000 ba68ad80 ftdisk (deferred) ba68b000 ba6ba000 ucx01000 (deferred) ba6ba000 ba724b00 ACPI (private pdb symbols) C:\Programme\Windows Kits\8.1\Debuggers\x86\sym\acpi.pdb\4FEAB1D79A7443328F0D6EC5860CB1131\acpi.pdb ba725000 ba7a7000 WDF01_W8 (deferred) ba8a8000 ba8b6000 WDFLDR8 (deferred) ba8b8000 ba8c1300 isapnp (deferred) ba8c8000 ba8d2000 WppRecorder (deferred) ba8d8000 ba8e2580 MountMgr (deferred) ba8e8000 ba8f5200 VolSnap (deferred) ba8f8000 ba903000 amd_xata (deferred) ba908000 ba910e00 disk (deferred) ba918000 ba924180 CLASSPNP (deferred) ba928000 ba931000 USBD_W8 (deferred) bab28000 bab2e800 firadisk (deferred) bab30000 bab34d00 PartMgr (deferred) bacb8000 bacbb000 BOOTVID (deferred) bacbc000 bacbef80 ACPIEC (deferred) bada8000 bada9100 WMILIB (deferred) badaa000 badab700 dmload (deferred) bae70000 bae70d80 OPRGHDLR (deferred) 0: kd> !devnode 0 1 Dumping IopRootDeviceNode (= 0x8a4f1828) DevNode 0x8a4f1828 for PDO 0x8a4f1970 InstancePath is "HTREE\ROOT\0" State = DeviceNodeStarted (0x308) Previous State = DeviceNodeEnumerateCompletion (0x30d) DevNode 0x8a54ac30 for PDO 0x8a54ad90 InstancePath is "Root\ACPI_HAL\0000" State = DeviceNodeStarted (0x308) Previous State = DeviceNodeEnumerateCompletion (0x30d) DevNode 0x8a4eb4d0 for PDO 0x8a5465d8 InstancePath is "ACPI_HAL\PNP0C08\0" ServiceName is "ACPI" State = DeviceNodeStarted (0x308) Previous State = DeviceNodeEnumerateCompletion (0x30d) DevNode 0x8a5448a8 for PDO 0x8a4bf3d0 InstancePath is "ACPI\PNP0C14\AWW" ServiceName is "WmiAcpi" State = DeviceNodeInitialized (0x302) Previous State = DeviceNodeUninitialized (0x301) DevNode 0x8a544778 for PDO 0x8a545f18 InstancePath is "ACPI\PNP0A08\0" ServiceName is "pci" State = DeviceNodeInitialized (0x302) Previous State = DeviceNodeUninitialized (0x301) DevNode 0x8a4beed8 for PDO 0x8a4a8f18 InstancePath is "ACPI\PNP0C0C\aa" State = DeviceNodeDriversAdded (0x303) Previous State = DeviceNodeInitialized (0x302) DevNode 0x8a4beda8 for PDO 0x8a4bc7e0 InstancePath is "ACPI\PNP0103\2&daba3ff&0" State = DeviceNodeInitialized (0x302) Previous State = DeviceNodeUninitialized (0x301) DevNode 0x8a4bec78 for PDO 0x8a4a8b10 InstancePath is "ACPI\AMDI0030\0" State = DeviceNodeInitialized (0x302) Previous State = DeviceNodeUninitialized (0x301) Problem = CM_PROB_DISABLED DevNode 0x8a4beb48 for PDO 0x8a4bbee8 State = DeviceNodeUninitialized (0x301) Previous State = Unknown State (0x0) DevNode 0x8a4bea18 for PDO 0x8a544288 State = DeviceNodeUninitialized (0x301) Previous State = Unknown State (0x0) DevNode 0x8a4ecb18 for PDO 0x8a4a8d90 State = DeviceNodeUninitialized (0x301) Previous State = Unknown State (0x0) DevNode 0x8a4ec9e8 for PDO 0x8a4eb6f8 State = DeviceNodeUninitialized (0x301) Previous State = Unknown State (0x0) DevNode 0x8a4ec8b8 for PDO 0x8a4f41f8 State = DeviceNodeUninitialized (0x301) Previous State = Unknown State (0x0) DevNode 0x8a4ec788 for PDO 0x8a545278 State = DeviceNodeUninitialized (0x301) Previous State = Unknown State (0x0) DevNode 0x8a4ec658 for PDO 0x8a4ec170 State = DeviceNodeUninitialized (0x301) Previous State = Unknown State (0x0) DevNode 0x8a4ec528 for PDO 0x8a4bb4f0 State = DeviceNodeUninitialized (0x301) Previous State = Unknown State (0x0) DevNode 0x8a479ed8 for PDO 0x8a4bb3d0 State = DeviceNodeUninitialized (0x301) Previous State = Unknown State (0x0) DevNode 0x8a479da8 for PDO 0x8a4bb218 State = DeviceNodeUninitialized (0x301) Previous State = Unknown State (0x0) DevNode 0x8a479c78 for PDO 0x8a4bb0f8 State = DeviceNodeUninitialized (0x301) Previous State = Unknown State (0x0) DevNode 0x8a479b48 for PDO 0x8a4a92c0 State = DeviceNodeUninitialized (0x301) Previous State = Unknown State (0x0) DevNode 0x8a479a18 for PDO 0x8a4a91a0 State = DeviceNodeUninitialized (0x301) Previous State = Unknown State (0x0) DevNode 0x8a4798e8 for PDO 0x8a4a9690 State = DeviceNodeUninitialized (0x301) Previous State = Unknown State (0x0) DevNode 0x8a4e5008 for PDO 0x8a4a9570 State = DeviceNodeUninitialized (0x301) Previous State = Unknown State (0x0) DevNode 0x8a4e5848 for PDO 0x8a4a9450 State = DeviceNodeUninitialized (0x301) Previous State = Unknown State (0x0) DevNode 0x8a4e5718 for PDO 0x8a544c48 State = DeviceNodeUninitialized (0x301) Previous State = Unknown State (0x0) DevNode 0x8a4e55e8 for PDO 0x8a544b28 State = DeviceNodeUninitialized (0x301) Previous State = Unknown State (0x0) DevNode 0x8a4e54b8 for PDO 0x8a544a08 State = DeviceNodeUninitialized (0x301) Previous State = Unknown State (0x0) DevNode 0x8a54a8b8 for PDO 0x8a54aa18 InstancePath is "Root\dmio\0000" ServiceName is "dmio" State = DeviceNodeInitialized (0x302) Previous State = DeviceNodeUninitialized (0x301) DevNode 0x8a54a660 for PDO 0x8a54a7c0 InstancePath is "Root\firadisk\0000" ServiceName is "FiraDisk" State = DeviceNodeInitialized (0x302) Previous State = DeviceNodeUninitialized (0x301) DevNode 0x8a54a408 for PDO 0x8a54a568 InstancePath is "Root\ftdisk\0000" ServiceName is "ftdisk" State = DeviceNodeInitialized (0x302) Previous State = DeviceNodeUninitialized (0x301) DevNode 0x8a54a1b0 for PDO 0x8a54a310 InstancePath is "Root\LEGACY_AFD\0000" ServiceName is "AFD" State = DeviceNodeStarted (0x308) Previous State = DeviceNodeEnumerateCompletion (0x30d) DevNode 0x8a4f0ed8 for PDO 0x8a4f0038 InstancePath is "Root\LEGACY_BEEP\0000" ServiceName is "Beep" State = DeviceNodeStarted (0x308) Previous State = DeviceNodeEnumerateCompletion (0x30d) DevNode 0x8a4f0c80 for PDO 0x8a4f0de0 InstancePath is "Root\LEGACY_CPUZ135\0000" ServiceName is "cpuz135" State = DeviceNodeStarted (0x308) Previous State = DeviceNodeEnumerateCompletion (0x30d) DevNode 0x8a4f0a28 for PDO 0x8a4f0b88 InstancePath is "Root\LEGACY_DMBOOT\0000" ServiceName is "dmboot" State = DeviceNodeStarted (0x308) Previous State = DeviceNodeEnumerateCompletion (0x30d) DevNode 0x8a4f07d0 for PDO 0x8a4f0930 InstancePath is "Root\LEGACY_DMLOAD\0000" ServiceName is "dmload" State = DeviceNodeStarted (0x308) Previous State = DeviceNodeEnumerateCompletion (0x30d) DevNode 0x8a4f0508 for PDO 0x8a4f0668 InstancePath is "Root\LEGACY_FIPS\0000" ServiceName is "Fips" State = DeviceNodeStarted (0x308) Previous State = DeviceNodeEnumerateCompletion (0x30d) DevNode 0x8a4f02b0 for PDO 0x8a4f0410 InstancePath is "Root\LEGACY_GPC\0000" ServiceName is "Gpc" State = DeviceNodeStarted (0x308) Previous State = DeviceNodeEnumerateCompletion (0x30d) DevNode 0x8a549008 for PDO 0x8a4f01b8 InstancePath is "Root\LEGACY_HTTP\0000" ServiceName is "HTTP" State = DeviceNodeStarted (0x308) Previous State = DeviceNodeEnumerateCompletion (0x30d) DevNode 0x8a549db0 for PDO 0x8a549f10 InstancePath is "Root\LEGACY_IPNAT\0000" ServiceName is "IpNat" State = DeviceNodeStarted (0x308) Previous State = DeviceNodeEnumerateCompletion (0x30d) DevNode 0x8a549b58 for PDO 0x8a549cb8 InstancePath is "Root\LEGACY_IPSEC\0000" ServiceName is "IPSec" State = DeviceNodeStarted (0x308) Previous State = DeviceNodeEnumerateCompletion (0x30d) DevNode 0x8a549900 for PDO 0x8a549a60 InstancePath is "Root\LEGACY_KSECDD\0000" ServiceName is "ksecdd" State = DeviceNodeStarted (0x308) Previous State = DeviceNodeEnumerateCompletion (0x30d) DevNode 0x8a5496a8 for PDO 0x8a549808 InstancePath is "Root\LEGACY_MNMDD\0000" ServiceName is "mnmdd" State = DeviceNodeStarted (0x308) Previous State = DeviceNodeEnumerateCompletion (0x30d) DevNode 0x8a549450 for PDO 0x8a5495b0 InstancePath is "Root\LEGACY_MOUNTMGR\0000" ServiceName is "mountmgr" State = DeviceNodeStarted (0x308) Previous State = DeviceNodeEnumerateCompletion (0x30d) DevNode 0x8a5491f8 for PDO 0x8a549358 InstancePath is "Root\LEGACY_NDIS\0000" ServiceName is "NDIS" State = DeviceNodeStarted (0x308) Previous State = DeviceNodeEnumerateCompletion (0x30d) DevNode 0x8a4efed8 for PDO 0x8a4ef038 InstancePath is "Root\LEGACY_NDISTAPI\0000" ServiceName is "NdisTapi" State = DeviceNodeStarted (0x308) Previous State = DeviceNodeEnumerateCompletion (0x30d) DevNode 0x8a4efc80 for PDO 0x8a4efde0 InstancePath is "Root\LEGACY_NDISUIO\0000" ServiceName is "Ndisuio" State = DeviceNodeStarted (0x308) Previous State = DeviceNodeEnumerateCompletion (0x30d) DevNode 0x8a4efa28 for PDO 0x8a4efb88 InstancePath is "Root\LEGACY_NDPROXY\0000" ServiceName is "NDProxy" State = DeviceNodeStarted (0x308) Previous State = DeviceNodeEnumerateCompletion (0x30d) DevNode 0x8a4ef7d0 for PDO 0x8a4ef930 InstancePath is "Root\LEGACY_NETBT\0000" ServiceName is "NetBT" State = DeviceNodeStarted (0x308) Previous State = DeviceNodeEnumerateCompletion (0x30d) DevNode 0x8a4ef578 for PDO 0x8a4ef6d8 InstancePath is "Root\LEGACY_NULL\0000" ServiceName is "Null" State = DeviceNodeStarted (0x308) Previous State = DeviceNodeEnumerateCompletion (0x30d) DevNode 0x8a4ef320 for PDO 0x8a4ef480 InstancePath is "Root\LEGACY_PARTMGR\0000" ServiceName is "PartMgr" State = DeviceNodeStarted (0x308) Previous State = DeviceNodeEnumerateCompletion (0x30d) DevNode 0x8a548008 for PDO 0x8a4ef228 InstancePath is "Root\LEGACY_PARVDM\0000" ServiceName is "ParVdm" State = DeviceNodeStarted (0x308) Previous State = DeviceNodeEnumerateCompletion (0x30d) DevNode 0x8a548db0 for PDO 0x8a548f10 InstancePath is "Root\LEGACY_RASACD\0000" ServiceName is "RasAcd" State = DeviceNodeStarted (0x308) Previous State = DeviceNodeEnumerateCompletion (0x30d) DevNode 0x8a548b58 for PDO 0x8a548cb8 InstancePath is "Root\LEGACY_RDPCDD\0000" ServiceName is "RDPCDD" State = DeviceNodeStarted (0x308) Previous State = DeviceNodeEnumerateCompletion (0x30d) DevNode 0x8a548900 for PDO 0x8a548a60 InstancePath is "Root\LEGACY_RWDRV\0000" ServiceName is "RwDrv" State = DeviceNodeStarted (0x308) Previous State = DeviceNodeEnumerateCompletion (0x30d) DevNode 0x8a5486a8 for PDO 0x8a548808 InstancePath is "Root\LEGACY_TCPIP\0000" ServiceName is "Tcpip" State = DeviceNodeStarted (0x308) Previous State = DeviceNodeEnumerateCompletion (0x30d) DevNode 0x8a548450 for PDO 0x8a5485b0 InstancePath is "Root\LEGACY_UCX01000\0000" ServiceName is "UCX01000" State = DeviceNodeStarted (0x308) Previous State = DeviceNodeEnumerateCompletion (0x30d) DevNode 0x8a5481f8 for PDO 0x8a548358 InstancePath is "Root\LEGACY_VGASAVE\0000" ServiceName is "VgaSave" State = DeviceNodeStarted (0x308) Previous State = DeviceNodeEnumerateCompletion (0x30d) DevNode 0x8a4eeed8 for PDO 0x8a4ee038 InstancePath is "Root\LEGACY_VOLSNAP\0000" ServiceName is "VolSnap" State = DeviceNodeStarted (0x308) Previous State = DeviceNodeEnumerateCompletion (0x30d) DevNode 0x8a4eec80 for PDO 0x8a4eede0 InstancePath is "Root\LEGACY_WANARP\0000" ServiceName is "Wanarp" State = DeviceNodeStarted (0x308) Previous State = DeviceNodeEnumerateCompletion (0x30d) DevNode 0x8a4eea28 for PDO 0x8a4eeb88 InstancePath is "Root\LEGACY_WDF01_W8\0000" ServiceName is "WDF01_W8" State = DeviceNodeStarted (0x308) Previous State = DeviceNodeEnumerateCompletion (0x30d) DevNode 0x8a4ee7d0 for PDO 0x8a4ee930 InstancePath is "Root\MEDIA\MS_MMACM" ServiceName is "audstub" State = DeviceNodeInitialized (0x302) Previous State = DeviceNodeUninitialized (0x301) DevNode 0x8a4ee578 for PDO 0x8a4ee6d8 InstancePath is "Root\MEDIA\MS_MMDRV" ServiceName is "audstub" State = DeviceNodeInitialized (0x302) Previous State = DeviceNodeUninitialized (0x301) DevNode 0x8a4ee320 for PDO 0x8a4ee480 InstancePath is "Root\MEDIA\MS_MMMCI" ServiceName is "audstub" State = DeviceNodeInitialized (0x302) Previous State = DeviceNodeUninitialized (0x301) DevNode 0x8a547008 for PDO 0x8a4ee228 InstancePath is "Root\MEDIA\MS_MMVCD" ServiceName is "audstub" State = DeviceNodeInitialized (0x302) Previous State = DeviceNodeUninitialized (0x301) DevNode 0x8a547db0 for PDO 0x8a547f10 InstancePath is "Root\MEDIA\MS_MMVID" ServiceName is "audstub" State = DeviceNodeInitialized (0x302) Previous State = DeviceNodeUninitialized (0x301) DevNode 0x8a547b58 for PDO 0x8a547cb8 InstancePath is "Root\MS_L2TPMINIPORT\0000" ServiceName is "Rasl2tp" State = DeviceNodeInitialized (0x302) Previous State = DeviceNodeUninitialized (0x301) DevNode 0x8a547900 for PDO 0x8a547a60 InstancePath is "Root\MS_NDISWANIP\0000" ServiceName is "NdisWan" State = DeviceNodeInitialized (0x302) Previous State = DeviceNodeUninitialized (0x301) DevNode 0x8a5476a8 for PDO 0x8a547808 InstancePath is "Root\MS_PPPOEMINIPORT\0000" ServiceName is "RasPppoe" State = DeviceNodeInitialized (0x302) Previous State = DeviceNodeUninitialized (0x301) DevNode 0x8a547450 for PDO 0x8a5475b0 InstancePath is "Root\MS_PPTPMINIPORT\0000" ServiceName is "PptpMiniport" State = DeviceNodeInitialized (0x302) Previous State = DeviceNodeUninitialized (0x301) DevNode 0x8a5471f8 for PDO 0x8a547358 InstancePath is "Root\MS_PSCHEDMP\0000" ServiceName is "PSched" State = DeviceNodeInitialized (0x302) Previous State = DeviceNodeUninitialized (0x301) DevNode 0x8a4eded8 for PDO 0x8a4ed038 InstancePath is "Root\MS_PSCHEDMP\0001" ServiceName is "PSched" State = DeviceNodeInitialized (0x302) Previous State = DeviceNodeUninitialized (0x301) DevNode 0x8a4edc80 for PDO 0x8a4edde0 InstancePath is "Root\MS_PSCHEDMP\0002" ServiceName is "PSched" State = DeviceNodeInitialized (0x302) Previous State = DeviceNodeUninitialized (0x301) DevNode 0x8a4eda28 for PDO 0x8a4edb88 InstancePath is "Root\MS_PTIMINIPORT\0000" ServiceName is "Raspti" State = DeviceNodeInitialized (0x302) Previous State = DeviceNodeUninitialized (0x301) DevNode 0x8a4ed7d0 for PDO 0x8a4ed930 InstancePath is "Root\RDPDR\0000" ServiceName is "rdpdr" State = DeviceNodeInitialized (0x302) Previous State = DeviceNodeUninitialized (0x301) DevNode 0x8a4ed578 for PDO 0x8a4ed6d8 InstancePath is "Root\RDP_KBD\0000" ServiceName is "TermDD" State = DeviceNodeInitialized (0x302) Previous State = DeviceNodeUninitialized (0x301) DevNode 0x8a4ed320 for PDO 0x8a4ed480 InstancePath is "Root\RDP_MOU\0000" ServiceName is "TermDD" State = DeviceNodeInitialized (0x302) Previous State = DeviceNodeUninitialized (0x301) DevNode 0x8a546008 for PDO 0x8a4ed228 InstancePath is "Root\SYSTEM\0000" ServiceName is "swenum" State = DeviceNodeInitialized (0x302) Previous State = DeviceNodeUninitialized (0x301) DevNode 0x8a546db0 for PDO 0x8a546f10 InstancePath is "Root\SYSTEM\0001" ServiceName is "update" State = DeviceNodeInitialized (0x302) Previous State = DeviceNodeUninitialized (0x301) DevNode 0x8a546b58 for PDO 0x8a546cb8 InstancePath is "Root\SYSTEM\0002" ServiceName is "mssmbios" State = DeviceNodeInitialized (0x302) Previous State = DeviceNodeUninitialized (0x301)

@Mov AX, 0xDEAD Same Bsod as before, looks like a lot of more work Dietmar *** Assertion failed: PciInterfacesInstantiated *** Source File: c:\acpi\acpi_sp1\base\busdrv\acpi\driver\nt\irqarb.c, line 3514 Break repeatedly, break Once, Ignore, terminate Process, or terminate Thread (boipt)? i i *** Assertion failed: pciInterface *** Source File: c:\acpi\acpi_sp1\base\busdrv\acpi\driver\nt\irqarb.c, line 3520 Break repeatedly, break Once, Ignore, terminate Process, or terminate Thread (boipt)? i i PS: Unhandled Kernel Mode Exception Pointers = 0xBACC69D4 Code c0000005 Addr BA6C774A Info0 00000000 Info1 00000010 Info2 00000010 Info3 80AEBEFC *** Fatal System Error: 0x0000007e (0xC0000005,0xBA6C774A,0xBACC6E88,0xBACC6B84) 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 (Wed Apr 13 03:27:49.703 2022 (UTC + 2:00)), ptr64 FALSE Loading Kernel Symbols .................................... Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7E, {c0000005, ba6c774a, bacc6e88, bacc6b84} *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 Probably caused by : ACPI.sys ( ACPI!AcpiArbCrackPRT+142 ) Followup: MachineOwner --------- nt!RtlpBreakWithStatusInstruction: 80ac37ec cc int 3 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: c0000005, The exception code that was not handled Arg2: ba6c774a, The address that the exception occurred at Arg3: bacc6e88, Exception Record Address Arg4: bacc6b84, Context Record Address Debugging Details: ------------------ *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung "0x%08lx" verweist auf Speicher bei "0x%08lx". Die Daten wurden wegen eines E/A-Fehlers in "0x%081x" nicht in den Arbeitsspeicher bertragen. FAULTING_IP: ACPI!AcpiArbCrackPRT+142 [c:\acpi\acpi_sp1\base\busdrv\acpi\driver\nt\irqarb.c @ 3537] ba6c774a ff5710 call dword ptr [edi+10h] EXCEPTION_RECORD: bacc6e88 -- (.exr 0xffffffffbacc6e88) ExceptionAddress: ba6c774a (ACPI!AcpiArbCrackPRT+0x00000142) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 00000000 Parameter[1]: 00000010 Attempt to read from address 00000010 CONTEXT: bacc6b84 -- (.cxr 0xffffffffbacc6b84;r) eax=bacc7008 ebx=00000000 ecx=0000bb40 edx=00000056 esi=8a4be0f0 edi=00000000 eip=ba6c774a esp=bacc6f50 ebp=bacc70a0 iopl=0 nv up ei ng nz na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286 ACPI!AcpiArbCrackPRT+0x142: ba6c774a ff5710 call dword ptr [edi+10h] ds:0023:00000010=???????? Last set context: eax=bacc7008 ebx=00000000 ecx=0000bb40 edx=00000056 esi=8a4be0f0 edi=00000000 eip=ba6c774a esp=bacc6f50 ebp=bacc70a0 iopl=0 nv up ei ng nz na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286 ACPI!AcpiArbCrackPRT+0x142: ba6c774a ff5710 call dword ptr [edi+10h] ds:0023:00000010=???????? Resetting default scope PROCESS_NAME: System ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung "0x%08lx" verweist auf Speicher bei "0x%08lx". Die Daten wurden wegen eines E/A-Fehlers in "0x%081x" nicht in den Arbeitsspeicher bertragen. EXCEPTION_PARAMETER1: 00000000 EXCEPTION_PARAMETER2: 00000010 READ_ADDRESS: 00000010 FOLLOWUP_IP: ACPI!AcpiArbCrackPRT+142 [c:\acpi\acpi_sp1\base\busdrv\acpi\driver\nt\irqarb.c @ 3537] ba6c774a ff5710 call dword ptr [edi+10h] BUGCHECK_STR: 0x7E DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre DPC_STACK_BASE: FFFFFFFFBACCC000 LOCK_ADDRESS: 80afd6c0 -- (!locks 80afd6c0) Resource @ nt!IopDeviceTreeLock (0x80afd6c0) Shared 1 owning threads Threads: 8a528da8-01<*> 1 total locks, 1 locks currently held PNP_TRIAGE: Lock address : 0x80afd6c0 Thread Count : 1 Thread address: 0x8a528da8 Thread wait : 0xd2 LAST_CONTROL_TRANSFER: from 80a30d7b to 80ac37ec STACK_TEXT: bacc70a0 ba709c2f 8a4be0f0 bacc70cc bacc70e0 ACPI!AcpiArbCrackPRT+0x142 [c:\acpi\acpi_sp1\base\busdrv\acpi\driver\nt\irqarb.c @ 3537] bacc70d4 ba719e52 ba6ff200 bacc70f0 e134c934 ACPI!AcpiArbAddAllocation+0x9f [c:\acpi\acpi_sp1\base\busdrv\acpi\driver\nt\irqarb.c @ 1474] bacc7158 ba708821 e1359d50 e134c934 ba6ff200 ACPI!ArbBootAllocation+0xf4 [d:\xpsp\base\ntos\arb\arbiter.c @ 1406] bacc716c ba719ed0 ba6ff200 e134c934 e134c934 ACPI!AcpiArbBootAllocation+0x4b [c:\acpi\acpi_sp1\base\busdrv\acpi\driver\nt\irqarb.c @ 1850] bacc7188 80b6c111 ba6ff200 00000009 bacc71a8 ACPI!ArbArbiterHandler+0x54 [d:\xpsp\base\ntos\arb\arbiter.c @ 1562] bacc71c4 80b6d093 bacc71b8 00000000 80afd1c0 nt!IopBootAllocation+0xbb bacc7208 80b6d80b 00000004 e1359d00 e1350ef8 nt!IopAllocateBootResourcesInternal+0xc5 bacc7228 80d38c8b 00000004 8a4be0f0 e1350ef8 nt!IopAllocateBootResources+0x75 bacc724c 80b5653a 00000004 8a4be0f0 e1350ef8 nt!IopReportBootResources+0x65 bacc727c 80b5cb93 8a4e5598 800005f8 00000001 nt!PiQueryAndAllocateBootResources+0x150 bacc736c 80b5d26d 8a4e5598 00000000 00000000 nt!PipProcessNewDeviceNode+0xc9d bacc75c4 80a2cff0 8a4f1828 00000000 00000000 nt!PipProcessDevNodeTree+0x1bd bacc7608 80a2d2fb 00000000 00000000 80091178 nt!PipDeviceActionWorker+0xc4 bacc7620 80d37f53 00000000 00000006 00000000 nt!PipRequestDeviceAction+0x13b bacc7684 80d341f1 80085000 bacc76a0 00034000 nt!IopInitializeBootDrivers+0x39b bacc7830 80d31940 80085000 00000000 8a528da8 nt!IoInitSystem+0x82d bacc7dac 80bd81ac 80085000 00000000 00000000 nt!Phase1Initialization+0xb12 bacc7ddc 80ae4212 80d30e2e 80085000 00000000 nt!PspSystemThreadStartup+0x34 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 FAULTING_SOURCE_LINE: c:\acpi\acpi_sp1\base\busdrv\acpi\driver\nt\irqarb.c FAULTING_SOURCE_FILE: c:\acpi\acpi_sp1\base\busdrv\acpi\driver\nt\irqarb.c FAULTING_SOURCE_LINE_NUMBER: 3537 FAULTING_SOURCE_CODE: No source found for 'c:\acpi\acpi_sp1\base\busdrv\acpi\driver\nt\irqarb.c' SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: ACPI!AcpiArbCrackPRT+142 FOLLOWUP_NAME: MachineOwner MODULE_NAME: ACPI IMAGE_NAME: ACPI.sys DEBUG_FLR_IMAGE_TIMESTAMP: 625620c2 IMAGE_VERSION: 5.1.2600.7777 STACK_COMMAND: .cxr 0xffffffffbacc6b84 ; kb FAILURE_BUCKET_ID: 0x7E_ACPI!AcpiArbCrackPRT+142 BUCKET_ID: 0x7E_ACPI!AcpiArbCrackPRT+142 ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x7e_acpi!acpiarbcrackprt+142 FAILURE_ID_HASH: {c4048bc0-99af-0abf-1d12-09bf78ac8e19} Followup: MachineOwner ---------

@Mov AX, 0xDEAD Thanks. I just set up whole new XP SP1 Sources, because I noticed, that also with the original files I get the same 5 errors, brrr.. Interesting, why this happens. Tomorrow I run a Beyond Compare 2 binary session, comparing each file from Sources with each other. This acpi.sys I try in few min Dietmar

@Mov AX, 0xDEAD Crazy. Can you send me this modded acpi.sys for testing Dietmar

@Mov AX, 0xDEAD I got 5 compiler errors with only for this modded irqarb.c from Sources for XP SP1. Can you please tell me, what I have done wrong Dietmar irqarb.7z

@Damnation Thanks for help also!

Same *** Assertion failed: PciInterfacesInstantiated *** Source File: e:\xpsp1\nt\base\busdrv\acpi\driver\nt\irqarb.c, line 3526 Break repeatedly, break Once, Ignore, terminate Process, or terminate Thread (boipt)? i i *** Assertion failed: pciInterface *** Source File: e:\xpsp1\nt\base\busdrv\acpi\driver\nt\irqarb.c, line 3541 Break repeatedly, break Once, Ignore, terminate Process, or terminate Thread (boipt)? i i PS: Unhandled Kernel Mode Exception Pointers = 0xBACC69DC Code c0000005 Addr BA6C9DEC Info0 00000000 Info1 00000010 Info2 00000010 Info3 8A52B9F0 *** Fatal System Error: 0x0000007e (0xC0000005,0xBA6C9DEC,0xBACC6E90,0xBACC6B8C) 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 12 20:05:28.125 2022 (UTC + 2:00)), ptr64 FALSE Loading Kernel Symbols .................................... Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7E, {c0000005, ba6c9dec, bacc6e90, bacc6b8c} *** ERROR: Module load completed but symbols could not be loaded for ACPI.sys *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 Probably caused by : ACPI.sys ( ACPI+10dec ) Followup: MachineOwner --------- nt!RtlpBreakWithStatusInstruction: 80ac37ec cc int 3 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: c0000005, The exception code that was not handled Arg2: ba6c9dec, The address that the exception occurred at Arg3: bacc6e90, Exception Record Address Arg4: bacc6b8c, Context Record Address Debugging Details: ------------------ *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung "0x%08lx" verweist auf Speicher bei "0x%08lx". Die Daten wurden wegen eines E/A-Fehlers in "0x%081x" nicht in den Arbeitsspeicher bertragen. FAULTING_IP: ACPI+10dec ba6c9dec ff5610 call dword ptr [esi+10h] EXCEPTION_RECORD: bacc6e90 -- (.exr 0xffffffffbacc6e90) ExceptionAddress: ba6c9dec (ACPI+0x00010dec) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 00000000 Parameter[1]: 00000010 Attempt to read from address 00000010 CONTEXT: bacc6b8c -- (.cxr 0xffffffffbacc6b8c;r) eax=bacc7070 ebx=bacc70cc ecx=0000bb40 edx=00000056 esi=00000000 edi=00000000 eip=ba6c9dec esp=bacc6f58 ebp=bacc70a0 iopl=0 nv up ei ng nz na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286 ACPI+0x10dec: ba6c9dec ff5610 call dword ptr [esi+10h] ds:0023:00000010=???????? Last set context: eax=bacc7070 ebx=bacc70cc ecx=0000bb40 edx=00000056 esi=00000000 edi=00000000 eip=ba6c9dec esp=bacc6f58 ebp=bacc70a0 iopl=0 nv up ei ng nz na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286 ACPI+0x10dec: ba6c9dec ff5610 call dword ptr [esi+10h] ds:0023:00000010=???????? Resetting default scope PROCESS_NAME: System ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung "0x%08lx" verweist auf Speicher bei "0x%08lx". Die Daten wurden wegen eines E/A-Fehlers in "0x%081x" nicht in den Arbeitsspeicher bertragen. EXCEPTION_PARAMETER1: 00000000 EXCEPTION_PARAMETER2: 00000010 READ_ADDRESS: 00000010 FOLLOWUP_IP: ACPI+10dec ba6c9dec ff5610 call dword ptr [esi+10h] BUGCHECK_STR: 0x7E DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre DPC_STACK_BASE: FFFFFFFFBACCC000 LOCK_ADDRESS: 80afd6c0 -- (!locks 80afd6c0) Resource @ nt!IopDeviceTreeLock (0x80afd6c0) Shared 1 owning threads Threads: 8a528da8-01<*> 1 total locks, 1 locks currently held PNP_TRIAGE: Lock address : 0x80afd6c0 Thread Count : 1 Thread address: 0x8a528da8 Thread wait : 0xd2 LAST_CONTROL_TRANSFER: from 80a30d7b to 80ac37ec STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. bacc70a0 ba70a6fa 8a4a8100 bacc70cc bacc70e0 ACPI+0x10dec bacc70d4 ba71a0df ba700380 bacc70f0 e13448cc ACPI+0x516fa bacc7158 ba7093ed e1023d50 e13448cc ba700380 ACPI+0x610df bacc716c ba71a156 ba700380 e13448cc e13448cc ACPI+0x503ed bacc7188 80b6c111 ba700380 00000009 bacc71a8 ACPI+0x61156 bacc71c4 80b6d093 bacc71b8 00000000 80afd1c0 nt!IopBootAllocation+0xbb bacc7208 80b6d80b 00000004 e1023d00 e1307048 nt!IopAllocateBootResourcesInternal+0xc5 bacc7228 80d38c8b 00000004 8a4a8100 e1307048 nt!IopAllocateBootResources+0x75 bacc724c 80b5653a 00000004 8a4a8100 e1307048 nt!IopReportBootResources+0x65 bacc727c 80b5cb93 8a545da8 8000074c 00000001 nt!PiQueryAndAllocateBootResources+0x150 bacc736c 80b5d26d 8a545da8 00000000 00000000 nt!PipProcessNewDeviceNode+0xc9d bacc75c4 80a2cff0 8a4f1828 00000000 00000000 nt!PipProcessDevNodeTree+0x1bd bacc7608 80a2d2fb 00000000 00000000 800911c0 nt!PipDeviceActionWorker+0xc4 bacc7620 80d37f53 00000000 00000006 00000000 nt!PipRequestDeviceAction+0x13b bacc7684 80d341f1 80085000 bacc76a0 00034000 nt!IopInitializeBootDrivers+0x39b bacc7830 80d31940 80085000 00000000 8a528da8 nt!IoInitSystem+0x82d bacc7dac 80bd81ac 80085000 00000000 00000000 nt!Phase1Initialization+0xb12 bacc7ddc 80ae4212 80d30e2e 80085000 00000000 nt!PspSystemThreadStartup+0x34 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: ACPI+10dec FOLLOWUP_NAME: MachineOwner MODULE_NAME: ACPI IMAGE_NAME: ACPI.sys DEBUG_FLR_IMAGE_TIMESTAMP: 6255b7d5 IMAGE_VERSION: 5.1.2600.1106 STACK_COMMAND: .cxr 0xffffffffbacc6b8c ; kb FAILURE_BUCKET_ID: 0x7E_ACPI+10dec BUCKET_ID: 0x7E_ACPI+10dec ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x7e_acpi+10dec FAILURE_ID_HASH: {d2dd5a9b-5d3f-7fe4-fd81-6b57d2f4580f} Followup: MachineOwner ---------

@Damnation This is now on the Strix 450 gaming II board, same AM4 sockel, same cpu Ryzen 3700x. Fast cpu >8700k same Bsod *** Assertion failed: PciInterfacesInstantiated *** Source File: e:\xpsp1\nt\base\busdrv\acpi\driver\nt\irqarb.c, line 3526 Break repeatedly, break Once, Ignore, terminate Process, or terminate Thread (boipt)? i i *** Assertion failed: pciInterface *** Source File: e:\xpsp1\nt\base\busdrv\acpi\driver\nt\irqarb.c, line 3541 Break repeatedly, break Once, Ignore, terminate Process, or terminate Thread (boipt)? i i PS: Unhandled Kernel Mode Exception Pointers = 0xBACC69DC Code c0000005 Addr BA6C9DEC Info0 00000000 Info1 00000010 Info2 00000010 Info3 8A52B9F0 *** Fatal System Error: 0x0000007e (0xC0000005,0xBA6C9DEC,0xBACC6E90,0xBACC6B8C) 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 12 19:42:04.937 2022 (UTC + 2:00)), ptr64 FALSE Loading Kernel Symbols .................................... Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7E, {c0000005, ba6c9dec, bacc6e90, bacc6b8c} *** ERROR: Module load completed but symbols could not be loaded for ACPI.sys *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 Probably caused by : ACPI.sys ( ACPI+10dec ) Followup: MachineOwner --------- nt!RtlpBreakWithStatusInstruction: 80ac37ec cc int 3 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: c0000005, The exception code that was not handled Arg2: ba6c9dec, The address that the exception occurred at Arg3: bacc6e90, Exception Record Address Arg4: bacc6b8c, Context Record Address Debugging Details: ------------------ *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung "0x%08lx" verweist auf Speicher bei "0x%08lx". Die Daten wurden wegen eines E/A-Fehlers in "0x%081x" nicht in den Arbeitsspeicher bertragen. FAULTING_IP: ACPI+10dec ba6c9dec ff5610 call dword ptr [esi+10h] EXCEPTION_RECORD: bacc6e90 -- (.exr 0xffffffffbacc6e90) ExceptionAddress: ba6c9dec (ACPI+0x00010dec) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 00000000 Parameter[1]: 00000010 Attempt to read from address 00000010 CONTEXT: bacc6b8c -- (.cxr 0xffffffffbacc6b8c;r) eax=bacc7070 ebx=bacc70cc ecx=0000bb40 edx=00000056 esi=00000000 edi=00000000 eip=ba6c9dec esp=bacc6f58 ebp=bacc70a0 iopl=0 nv up ei ng nz na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286 ACPI+0x10dec: ba6c9dec ff5610 call dword ptr [esi+10h] ds:0023:00000010=???????? Last set context: eax=bacc7070 ebx=bacc70cc ecx=0000bb40 edx=00000056 esi=00000000 edi=00000000 eip=ba6c9dec esp=bacc6f58 ebp=bacc70a0 iopl=0 nv up ei ng nz na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286 ACPI+0x10dec: ba6c9dec ff5610 call dword ptr [esi+10h] ds:0023:00000010=???????? Resetting default scope PROCESS_NAME: System ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung "0x%08lx" verweist auf Speicher bei "0x%08lx". Die Daten wurden wegen eines E/A-Fehlers in "0x%081x" nicht in den Arbeitsspeicher bertragen. EXCEPTION_PARAMETER1: 00000000 EXCEPTION_PARAMETER2: 00000010 READ_ADDRESS: 00000010 FOLLOWUP_IP: ACPI+10dec ba6c9dec ff5610 call dword ptr [esi+10h] BUGCHECK_STR: 0x7E DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre DPC_STACK_BASE: FFFFFFFFBACCC000 LOCK_ADDRESS: 80afd6c0 -- (!locks 80afd6c0) Resource @ nt!IopDeviceTreeLock (0x80afd6c0) Shared 1 owning threads Threads: 8a528da8-01<*> 1 total locks, 1 locks currently held PNP_TRIAGE: Lock address : 0x80afd6c0 Thread Count : 1 Thread address: 0x8a528da8 Thread wait : 0xd2 LAST_CONTROL_TRANSFER: from 80a30d7b to 80ac37ec STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. bacc70a0 ba70a6fa 8a4e6108 bacc70cc bacc70e0 ACPI+0x10dec bacc70d4 ba71a0df ba700380 bacc70f0 e13448cc ACPI+0x516fa bacc7158 ba7093ed e1023d50 e13448cc ba700380 ACPI+0x610df bacc716c ba71a156 ba700380 e13448cc e13448cc ACPI+0x503ed bacc7188 80b6c111 ba700380 00000009 bacc71a8 ACPI+0x61156 bacc71c4 80b6d093 bacc71b8 00000000 80afd1c0 nt!IopBootAllocation+0xbb bacc7208 80b6d80b 00000004 e1023d00 e1307048 nt!IopAllocateBootResourcesInternal+0xc5 bacc7228 80d38c8b 00000004 8a4e6108 e1307048 nt!IopAllocateBootResources+0x75 bacc724c 80b5653a 00000004 8a4e6108 e1307048 nt!IopReportBootResources+0x65 bacc727c 80b5cb93 8a4bb208 8000074c 00000001 nt!PiQueryAndAllocateBootResources+0x150 bacc736c 80b5d26d 8a4bb208 00000000 00000000 nt!PipProcessNewDeviceNode+0xc9d bacc75c4 80a2cff0 8a4f1828 00000000 00000000 nt!PipProcessDevNodeTree+0x1bd bacc7608 80a2d2fb 00000000 00000000 800911c0 nt!PipDeviceActionWorker+0xc4 bacc7620 80d37f53 00000000 00000006 00000000 nt!PipRequestDeviceAction+0x13b bacc7684 80d341f1 80085000 bacc76a0 00034000 nt!IopInitializeBootDrivers+0x39b bacc7830 80d31940 80085000 00000000 8a528da8 nt!IoInitSystem+0x82d bacc7dac 80bd81ac 80085000 00000000 00000000 nt!Phase1Initialization+0xb12 bacc7ddc 80ae4212 80d30e2e 80085000 00000000 nt!PspSystemThreadStartup+0x34 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: ACPI+10dec FOLLOWUP_NAME: MachineOwner MODULE_NAME: ACPI IMAGE_NAME: ACPI.sys DEBUG_FLR_IMAGE_TIMESTAMP: 6255b7d5 IMAGE_VERSION: 5.1.2600.1106 STACK_COMMAND: .cxr 0xffffffffbacc6b8c ; kb FAILURE_BUCKET_ID: 0x7E_ACPI+10dec BUCKET_ID: 0x7E_ACPI+10dec ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x7e_acpi+10dec FAILURE_ID_HASH: {d2dd5a9b-5d3f-7fe4-fd81-6b57d2f4580f} Followup: MachineOwner ---------

@Damnation The same. Now I go back to the Strixx 450 board for further tests Dietmar *** Assertion failed: PciInterfacesInstantiated *** Source File: e:\xpsp1\nt\base\busdrv\acpi\driver\nt\irqarb.c, line 3519 Break repeatedly, break Once, Ignore, terminate Process, or terminate Thread (boipt)? i i *** Assertion failed: pciInterface *** Source File: e:\xpsp1\nt\base\busdrv\acpi\driver\nt\irqarb.c, line 3534 Break repeatedly, break Once, Ignore, terminate Process, or terminate Thread (boipt)? i i PS: Unhandled Kernel Mode Exception Pointers = 0xBACC69DC Code c0000005 Addr BA6C9DCD Info0 00000000 Info1 00000010 Info2 00000010 Info3 8A868918 *** Fatal System Error: 0x0000007e (0xC0000005,0xBA6C9DCD,0xBACC6E90,0xBACC6B8C) 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 12 19:08:34.843 2022 (UTC + 2:00)), ptr64 FALSE Loading Kernel Symbols .................................... Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7E, {c0000005, ba6c9dcd, bacc6e90, bacc6b8c} *** ERROR: Module load completed but symbols could not be loaded for ACPI.sys *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 Probably caused by : ACPI.sys ( ACPI+10dcd ) Followup: MachineOwner --------- nt!RtlpBreakWithStatusInstruction: 80ac37ec cc int 3 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: c0000005, The exception code that was not handled Arg2: ba6c9dcd, The address that the exception occurred at Arg3: bacc6e90, Exception Record Address Arg4: bacc6b8c, Context Record Address Debugging Details: ------------------ *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung "0x%08lx" verweist auf Speicher bei "0x%08lx". Die Daten wurden wegen eines E/A-Fehlers in "0x%081x" nicht in den Arbeitsspeicher bertragen. FAULTING_IP: ACPI+10dcd ba6c9dcd ff5610 call dword ptr [esi+10h] EXCEPTION_RECORD: bacc6e90 -- (.exr 0xffffffffbacc6e90) ExceptionAddress: ba6c9dcd (ACPI+0x00010dcd) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 00000000 Parameter[1]: 00000010 Attempt to read from address 00000010 CONTEXT: bacc6b8c -- (.cxr 0xffffffffbacc6b8c;r) eax=bacc7070 ebx=bacc70cc ecx=0000bb40 edx=00000056 esi=00000000 edi=8a70bec8 eip=ba6c9dcd esp=bacc6f58 ebp=bacc70a0 iopl=0 nv up ei ng nz na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286 ACPI+0x10dcd: ba6c9dcd ff5610 call dword ptr [esi+10h] ds:0023:00000010=???????? Last set context: eax=bacc7070 ebx=bacc70cc ecx=0000bb40 edx=00000056 esi=00000000 edi=8a70bec8 eip=ba6c9dcd esp=bacc6f58 ebp=bacc70a0 iopl=0 nv up ei ng nz na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286 ACPI+0x10dcd: ba6c9dcd ff5610 call dword ptr [esi+10h] ds:0023:00000010=???????? Resetting default scope PROCESS_NAME: System ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung "0x%08lx" verweist auf Speicher bei "0x%08lx". Die Daten wurden wegen eines E/A-Fehlers in "0x%081x" nicht in den Arbeitsspeicher bertragen. EXCEPTION_PARAMETER1: 00000000 EXCEPTION_PARAMETER2: 00000010 READ_ADDRESS: 00000010 FOLLOWUP_IP: ACPI+10dcd ba6c9dcd ff5610 call dword ptr [esi+10h] BUGCHECK_STR: 0x7E DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre DPC_STACK_BASE: FFFFFFFFBACCC000 LOCK_ADDRESS: 80afd6c0 -- (!locks 80afd6c0) Resource @ nt!IopDeviceTreeLock (0x80afd6c0) Shared 1 owning threads Threads: 8a8a4da8-01<*> 1 total locks, 1 locks currently held PNP_TRIAGE: Lock address : 0x80afd6c0 Thread Count : 1 Thread address: 0x8a8a4da8 Thread wait : 0xcd LAST_CONTROL_TRANSFER: from 80a30d7b to 80ac37ec STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. bacc70a0 ba70a6fa 8a70bec8 bacc70cc bacc70e0 ACPI+0x10dcd bacc70d4 ba71a0df ba700380 bacc70f0 e1356e24 ACPI+0x516fa bacc7158 ba7093ed e13319c0 e1356e24 ba700380 ACPI+0x610df bacc716c ba71a156 ba700380 e1356e24 e1356e24 ACPI+0x503ed bacc7188 80b6c111 ba700380 00000009 bacc71a8 ACPI+0x61156 bacc71c4 80b6d093 bacc71b8 00000000 80afd1c0 nt!IopBootAllocation+0xbb bacc7208 80b6d80b 00000004 e1331970 e1350038 nt!IopAllocateBootResourcesInternal+0xc5 bacc7228 80d38c8b 00000004 8a70bec8 e1350038 nt!IopAllocateBootResources+0x75 bacc724c 80b5653a 00000004 8a70bec8 e1350038 nt!IopReportBootResources+0x65 bacc727c 80b5cb93 8a6d8858 80000438 00000001 nt!PiQueryAndAllocateBootResources+0x150 bacc736c 80b5d26d 8a6d8858 00000000 00000000 nt!PipProcessNewDeviceNode+0xc9d bacc75c4 80a2cff0 8a86d968 00000000 00000000 nt!PipProcessDevNodeTree+0x1bd bacc7608 80a2d2fb 00000000 00000000 80091008 nt!PipDeviceActionWorker+0xc4 bacc7620 80d37f53 00000000 00000006 00000000 nt!PipRequestDeviceAction+0x13b bacc7684 80d341f1 80085000 bacc76a0 00034000 nt!IopInitializeBootDrivers+0x39b bacc7830 80d31940 80085000 00000000 8a8a4da8 nt!IoInitSystem+0x82d bacc7dac 80bd81ac 80085000 00000000 00000000 nt!Phase1Initialization+0xb12 bacc7ddc 80ae4212 80d30e2e 80085000 00000000 nt!PspSystemThreadStartup+0x34 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: ACPI+10dcd FOLLOWUP_NAME: MachineOwner MODULE_NAME: ACPI IMAGE_NAME: ACPI.sys DEBUG_FLR_IMAGE_TIMESTAMP: 62530b9f IMAGE_VERSION: 5.1.2600.1106 STACK_COMMAND: .cxr 0xffffffffbacc6b8c ; kb FAILURE_BUCKET_ID: 0x7E_ACPI+10dcd BUCKET_ID: 0x7E_ACPI+10dcd ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x7e_acpi+10dcd FAILURE_ID_HASH: {ed12b94d-5be7-2ab3-b166-5377fcbd21f6} Followup: MachineOwner ---------

@Damnation Now, the name of AcpiArbCrackPRT() is gone, but Bsod is the same *** Assertion failed: PciInterfacesInstantiated *** Source File: e:\xpsp1\nt\base\busdrv\acpi\driver\nt\irqarb.c, line 3519 Break repeatedly, break Once, Ignore, terminate Process, or terminate Thread (boipt)? i i *** Assertion failed: pciInterface *** Source File: e:\xpsp1\nt\base\busdrv\acpi\driver\nt\irqarb.c, line 3534 Break repeatedly, break Once, Ignore, terminate Process, or terminate Thread (boipt)? i i PS: Unhandled Kernel Mode Exception Pointers = 0xBACC69DC Code c0000005 Addr BA6C9DCD Info0 00000000 Info1 00000010 Info2 00000010 Info3 8A83AC00 *** Fatal System Error: 0x0000007e (0xC0000005,0xBA6C9DCD,0xBACC6E90,0xBACC6B8C) 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 12 18:27:21.250 2022 (UTC + 2:00)), ptr64 FALSE Loading Kernel Symbols .................................... Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7E, {c0000005, ba6c9dcd, bacc6e90, bacc6b8c} *** ERROR: Module load completed but symbols could not be loaded for ACPI.sys *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 Probably caused by : ACPI.sys ( ACPI+10dcd ) Followup: MachineOwner --------- nt!RtlpBreakWithStatusInstruction: 80ac37ec cc int 3 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: c0000005, The exception code that was not handled Arg2: ba6c9dcd, The address that the exception occurred at Arg3: bacc6e90, Exception Record Address Arg4: bacc6b8c, Context Record Address Debugging Details: ------------------ *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 *** No owner thread found for resource 80afd640 EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung "0x%08lx" verweist auf Speicher bei "0x%08lx". Die Daten wurden wegen eines E/A-Fehlers in "0x%081x" nicht in den Arbeitsspeicher bertragen. FAULTING_IP: ACPI+10dcd ba6c9dcd ff5610 call dword ptr [esi+10h] EXCEPTION_RECORD: bacc6e90 -- (.exr 0xffffffffbacc6e90) ExceptionAddress: ba6c9dcd (ACPI+0x00010dcd) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 00000000 Parameter[1]: 00000010 Attempt to read from address 00000010 CONTEXT: bacc6b8c -- (.cxr 0xffffffffbacc6b8c;r) eax=bacc7070 ebx=bacc70cc ecx=0000bb40 edx=00000056 esi=00000000 edi=8a7f71c8 eip=ba6c9dcd esp=bacc6f58 ebp=bacc70a0 iopl=0 nv up ei ng nz na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286 ACPI+0x10dcd: ba6c9dcd ff5610 call dword ptr [esi+10h] ds:0023:00000010=???????? Last set context: eax=bacc7070 ebx=bacc70cc ecx=0000bb40 edx=00000056 esi=00000000 edi=8a7f71c8 eip=ba6c9dcd esp=bacc6f58 ebp=bacc70a0 iopl=0 nv up ei ng nz na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286 ACPI+0x10dcd: ba6c9dcd ff5610 call dword ptr [esi+10h] ds:0023:00000010=???????? Resetting default scope PROCESS_NAME: System ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung "0x%08lx" verweist auf Speicher bei "0x%08lx". Die Daten wurden wegen eines E/A-Fehlers in "0x%081x" nicht in den Arbeitsspeicher bertragen. EXCEPTION_PARAMETER1: 00000000 EXCEPTION_PARAMETER2: 00000010 READ_ADDRESS: 00000010 FOLLOWUP_IP: ACPI+10dcd ba6c9dcd ff5610 call dword ptr [esi+10h] BUGCHECK_STR: 0x7E DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre DPC_STACK_BASE: FFFFFFFFBACCC000 LOCK_ADDRESS: 80afd6c0 -- (!locks 80afd6c0) Resource @ nt!IopDeviceTreeLock (0x80afd6c0) Shared 1 owning threads Threads: 8a8a4da8-01<*> 1 total locks, 1 locks currently held PNP_TRIAGE: Lock address : 0x80afd6c0 Thread Count : 1 Thread address: 0x8a8a4da8 Thread wait : 0xcd LAST_CONTROL_TRANSFER: from 80a30d7b to 80ac37ec STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. bacc70a0 ba70a6fa 8a7f71c8 bacc70cc bacc70e0 ACPI+0x10dcd bacc70d4 ba71a0df ba700380 bacc70f0 e1356e24 ACPI+0x516fa bacc7158 ba7093ed e1345860 e1356e24 ba700380 ACPI+0x610df bacc716c ba71a156 ba700380 e1356e24 e1356e24 ACPI+0x503ed bacc7188 80b6c111 ba700380 00000009 bacc71a8 ACPI+0x61156 bacc71c4 80b6d093 bacc71b8 00000000 80afd1c0 nt!IopBootAllocation+0xbb bacc7208 80b6d80b 00000004 e1345810 e132e578 nt!IopAllocateBootResourcesInternal+0xc5 bacc7228 80d38c8b 00000004 8a7f71c8 e132e578 nt!IopAllocateBootResources+0x75 bacc724c 80b5653a 00000004 8a7f71c8 e132e578 nt!IopReportBootResources+0x65 bacc727c 80b5cb93 8a7f2e80 80000438 00000001 nt!PiQueryAndAllocateBootResources+0x150 bacc736c 80b5d26d 8a7f2e80 00000000 00000000 nt!PipProcessNewDeviceNode+0xc9d bacc75c4 80a2cff0 8a86d968 00000000 00000000 nt!PipProcessDevNodeTree+0x1bd bacc7608 80a2d2fb 00000000 00000000 80091008 nt!PipDeviceActionWorker+0xc4 bacc7620 80d37f53 00000000 00000006 00000000 nt!PipRequestDeviceAction+0x13b bacc7684 80d341f1 80085000 bacc76a0 00034000 nt!IopInitializeBootDrivers+0x39b bacc7830 80d31940 80085000 00000000 8a8a4da8 nt!IoInitSystem+0x82d bacc7dac 80bd81ac 80085000 00000000 00000000 nt!Phase1Initialization+0xb12 bacc7ddc 80ae4212 80d30e2e 80085000 00000000 nt!PspSystemThreadStartup+0x34 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: ACPI+10dcd FOLLOWUP_NAME: MachineOwner MODULE_NAME: ACPI IMAGE_NAME: ACPI.sys DEBUG_FLR_IMAGE_TIMESTAMP: 62530b9f IMAGE_VERSION: 5.1.2600.1106 STACK_COMMAND: .cxr 0xffffffffbacc6b8c ; kb FAILURE_BUCKET_ID: 0x7E_ACPI+10dcd BUCKET_ID: 0x7E_ACPI+10dcd ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x7e_acpi+10dcd FAILURE_ID_HASH: {ed12b94d-5be7-2ab3-b166-5377fcbd21f6} Followup: MachineOwner ---------

@daniel_k @Mov AX, 0xDEAD @Damnation I just want to tell you, that deleting of every entry for the device GPIO in DSDT does not solve the problem. Still exact the same message about AcpiArbCrackPRT() and Bsod 0x7E, (0xC0000005, xxx, yyy, zzz) appears on Ryzen AM4 boards Dietmar PS: Here is the readout of the new DSDT of the Bioschip on the AB350 k4 AMD board nonononoGPIO.7z

@Damnation With elseif (! ((PDEVICE_EXTENSION)Pdo->DeviceExtension)->Flags & DEV_CAP_PCI_DEVICE ) { // return STATUS_NOT_FOUND; } is there an advantage against my hack, just to jmp over? What happens to GPIO then? I ask this, because I hope, that it is possible to keep the GPIO device alive in XP (if there is hardware with GPIO pins) Dietmar

@Mov AX, 0xDEAD Do you have a new acpi.sys Debug for me (with *.pdb), that I can test? I can compile it also by myself, for me this is hard work ). I think, that the idea from @daniel_k is to be 100% sure, that the GPIO device makes this Bsod. The GPIO is really "ISA device", even I do not know, that there are especially things for ISA, that have to be fullfilled Dietmar

@daniel_k I will test your DSDT tomorrow. But this is only for to look, if we caught the right ^^. Next task is with help of Source Code to write some part of acpi.sys new, how to manage this problem Dietmar

@daniel_k Now I am with the Ryzen 3700x on the AB350 gaming k4 board. Bios is 5.80 . Win7 SP1 works, Win8.0 works Dietmar PS: I notice, that RWeverything produces garbage when you use it for to read out Bios DSDT. So I use the Bios tool V2. The DSDT is exact the same as you send to me with Mods, so that I am not going nuts with this Bsod )..

@daniel_k I think the same. But to change Interrupt (ResourceConsumer, Level, ActiveLow, Shared, ,, ) ----> Interrupt (ResourceConsumer, Edge, ActiveHigh, Shared, ,, ) does not help. The BSOD is still the same 0x7E 0xc0000005 after *** Assertion failed: PciInterfacesInstantiated *** Source File: d:\xpsp\base\busdrv\acpi\driver\nt\irqarb.c, line 3512 This I tried already, Dietmar PS: In Linux they introduce an extra function for this problem

@daniel_k I put all together, but does not help. Again I see the famous Bsod 7E (0xC0000005, xxx, yyy, zzz) Dietmar PS: And when I change the acpi.sys Debug V2 against acpi.sys free V2 with my Ryzen hack, compi boots to desktop. Happy, that the AB350 gaming k6 is still alive )..

@daniel_k I integrate your *.raw file into Bios. Then I read with Uefitool again DSDT out in *.raw and compare it with your *.raw before. They are identic ). Now I need to put Bios chip, cpu, ram etc. into this board again, because 2 years not used Dietmar EDIT1: I just flash the Bios chip and read it out again and compare with Bios.rom, identic. Now fun starts )..

@daniel_k Microsoft tells, that GPIO must be from type Edge Dietmar

@daniel_k Can you please modd the DSDT from the AMD AM4 board AB350 gaming k4 for me via your wished way, because I do not know how to put Device (GPIO) inside Device (PCI0). This DSDT I read just out via EEpromer of the Bios chip. May be hard work, to make again a *.raw from it and integrate it back into Bios, because of missing entries in head. Dietmar DSDTAB350k4ORI.7z

@daniel_k Fresh from Bios of PRIME X570 PRO ASUS board crash Dietmar Earlier AMD boards do not have this problem. And I think, it is Ryzen related, because this AM4 have GPIO, but only Ryzen crashes, other CPU on the same board not. Maybe, that only Ryzen offers these GPIO connectors IRQ 7 override to edge, high Scope (_SB) { ... Device (GPIO)

@daniel_k And now I remember, that I come to the idea of GPIO and this Bsod also, because of the changed use in Ryzen cpu of signals for GPIO "Active-High and Active-Low". And from exact this hardware changes for GPIO came the very big problems for Linux and Ryzen Dietmar EDIT: In DSDT table the IRQ is defined as Interrupt (ResourceConsumer, Level, ActiveLow, Shared, ,, ) { 0x00000007, } but in dmesg it prints [ 0.098531] ACPI: IRQ 7 override to edge, high

GPIO Interfaces =============== The documents in this directory give detailed instructions on how to access GPIOs in drivers, and how to write a driver for a device that provides GPIOs itself. Due to the history of GPIO interfaces in the kernel, there are two different ways to obtain and use GPIOs: - The descriptor-based interface is the preferred way to manipulate GPIOs, and is described by all the files in this directory excepted gpio-legacy.txt. - The legacy integer-based interface which is considered deprecated (but still usable for compatibility reasons) is documented in gpio-legacy.txt. The remainder of this document applies to the new descriptor-based interface. gpio-legacy.txt contains the same information applied to the legacy integer-based interface. What is a GPIO? =============== A "General Purpose Input/Output" (GPIO) is a flexible software-controlled digital signal. They are provided from many kinds of chip, and are familiar to Linux developers working with embedded and custom hardware. Each GPIO represents a bit connected to a particular pin, or "ball" on Ball Grid Array (BGA) packages. Board schematics show which external hardware connects to which GPIOs. Drivers can be written generically, so that board setup code passes such pin configuration data to drivers. System-on-Chip (SOC) processors heavily rely on GPIOs. In some cases, every non-dedicated pin can be configured as a GPIO; and most chips have at least several dozen of them. Programmable logic devices (like FPGAs) can easily provide GPIOs; multifunction chips like power managers, and audio codecs often have a few such pins to help with pin scarcity on SOCs; and there are also "GPIO Expander" chips that connect using the I2C or SPI serial buses. Most PC southbridges have a few dozen GPIO-capable pins (with only the BIOS firmware knowing how they're used). The exact capabilities of GPIOs vary between systems. Common options: - Output values are writable (high=1, low=0). Some chips also have options about how that value is driven, so that for example only one value might be driven, supporting "wire-OR" and similar schemes for the other value (notably, "open drain" signaling). - Input values are likewise readable (1, 0). Some chips support readback of pins configured as "output", which is very useful in such "wire-OR" cases (to support bidirectional signaling). GPIO controllers may have input de-glitch/debounce logic, sometimes with software controls. - Inputs can often be used as IRQ signals, often edge triggered but sometimes level triggered. Such IRQs may be configurable as system wakeup events, to wake the system from a low power state. - Usually a GPIO will be configurable as either input or output, as needed by different product boards; single direction ones exist too. - Most GPIOs can be accessed while holding spinlocks, but those accessed through a serial bus normally can't. Some systems support both types. On a given board each GPIO is used for one specific purpose like monitoring MMC/SD card insertion/removal, detecting card write-protect status, driving a LED, configuring a transceiver, bit-banging a serial bus, poking a hardware watchdog, sensing a switch, and so on. Common GPIO Properties ====================== These properties are met through all the other documents of the GPIO interface and it is useful to understand them, especially if you need to define GPIO mappings. Active-High and Active-Low -------------------------- It is natural to assume that a GPIO is "active" when its output signal is 1 ("high"), and inactive when it is 0 ("low"). However in practice the signal of a GPIO may be inverted before is reaches its destination, or a device could decide to have different conventions about what "active" means. Such decisions should be transparent to device drivers, therefore it is possible to define a GPIO as being either active-high ("1" means "active", the default) or active-low ("0" means "active") so that drivers only need to worry about the logical signal and not about what happens at the line level. Open Drain and Open Source -------------------------- Sometimes shared signals need to use "open drain" (where only the low signal level is actually driven), or "open source" (where only the high signal level is driven) signaling. That term applies to CMOS transistors; "open collector" is used for TTL. A pullup or pulldown resistor causes the high or low signal level. This is sometimes called a "wire-AND"; or more practically, from the negative logic (low=true) perspective this is a "wire-OR". One common example of an open drain signal is a shared active-low IRQ line. Also, bidirectional data bus signals sometimes use open drain signals. Some GPIO controllers directly support open drain and open source outputs; many don't. When you need open drain signaling but your hardware doesn't directly support it, there's a common idiom you can use to emulate it with any GPIO pin that can be used as either an input or an output: LOW: gpiod_direction_output(gpio, 0) ... this drives the signal and overrides the pullup. HIGH: gpiod_direction_input(gpio) ... this turns off the output, so the pullup (or some other device) controls the signal. The same logic can be applied to emulate open source signaling, by driving the high signal and configuring the GPIO as input for low. This open drain/open source emulation can be handled transparently by the GPIO framework. If you are "driving" the signal high but gpiod_get_value(gpio) reports a low value (after the appropriate rise time passes), you know some other component is driving the shared signal low. That's not necessarily an error. As one common example, that's how I2C clocks are stretched: a slave that needs a slower clock delays the rising edge of SCK, and the I2C master adjusts its signaling rate accordingly.

@daniel_k Scope (_SB) { ... Device (GPIO)

@daniel_k No crash from Intel board z370 gaming k6. No Device (GPIO) in DSDT at all Dietmar