Dietmar

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

Device (GPIO) { Name (_HID, "AMDI0030") // _HID: Hardware ID Name (_CID, "AMDI0030") // _CID: Compatible ID Name (_UID, Zero) // _UID: Unique ID Method (_CRS, 0, NotSerialized) // _CRS: Current Resource Settings { Name (RBUF, ResourceTemplate () { Here is Level ActiveLow ===>> Interrupt (ResourceConsumer, Level, ActiveLow, Shared, ,, ) { 0x00000007, } Memory32Fixed (ReadWrite, 0xFED81500, // Address Base 0x00000400, // Address Length ) }) Return (RBUF) /* \_SB_.GPIO._CRS.RBUF */ } Method (_STA, 0, NotSerialized) // _STA: Status { If ((TSOS >= 0x70)) { Return (0x0F) } Else { Return (Zero) } } } @daniel_k This is from DSDT of the AMD AB350 k4, crashes Dietmar

@Damnation I think this is the right idea to keep the "ISA" device mode. It is also possible, that it is just an mistake in DSDT for GPIO. But because it is very close to hardware the idea with "ISA" should be kept Dietmar

On the AMD board AB350 gaming k4 I have soldered by myself a socket for its Bios chip. So there I can easy change DSDT with EEpromer entry for GPIO to If ((OSYS >= 0x07D6)) { } Dietmar PS: Also possible to do add something like "GPIO is not under usual _SB.PCI0. path - i think this is problem". But then GPIO becomes forced a PCI device and "ISA" mode is gone?

@Mov AX, 0xDEAD Nice, that you find the reason for this loong standing Bsod! Do you have an idea, how to forbid a call to AcpiArbCrackPRT() from GPIO (connected to SystemBus directly) before pci.sys has started? This can be used in general for other "ISA" like devices under XP also. Of course we can disable AMDI0030 (GPIO) in DSDT for XP, but maybe some programs (near to hardware) make use of GPIO connected to SystemBus directly. I think the hack before in acpi.sys comes very close to this idea because Bsod via AcpiArbCrackPRT() without pci.sys is meaningless Dietmar

@Mov AX, 0xDEAD I am happy, that you take a deeper look in the problem of Ryzen cpu with XP! And for sure this helps you also for better understanding XP ). With this acpi.sys the compi boots to desktop in about 10min on the same AMD board as before. Loong txt output. During the whole session with Windbg over Lan, no error message at all. Here is the log file, hope that it helps you Dietmar ottocrack.7z ottoPCI.7z

I tried the Quantum browser from Feodor for XP SP3. Even just now you can work with it, look HTML5 movies Dietmar