Mov AX, 0xDEAD Posted April 12, 2022 Author Share Posted April 12, 2022 1 hour ago, daniel_k said: @Mov AX, 0xDEAD I see that there is a NoOp (No Operation) operator. Still don't know how the built in AML interpreter in ACPI.SYS works, but what if we create a generic function based on the NoOp and use it for all unsupported opcodes, so the DSDT is properly loaded? @daniel_k i dont understand idea, if you want keep original acpi 1.0b driver and patch instead tables - I'm not interested Link to comment Share on other sites More sharing options...
Damnation Posted April 12, 2022 Share Posted April 12, 2022 @Mov AX, 0xDEAD @daniel_k Could we use code from reactos for unsupported opcodes? 1 Link to comment Share on other sites More sharing options...
Dietmar Posted April 12, 2022 Share Posted April 12, 2022 @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 Link to comment Share on other sites More sharing options...
Dietmar Posted April 12, 2022 Share Posted April 12, 2022 @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 Link to comment Share on other sites More sharing options...
Damnation Posted April 12, 2022 Share Posted April 12, 2022 15 minutes ago, Dietmar said: is there an advantage against my hack, just to jmp over? What happens to GPIO then? Other than not needing to apply your hack to acpi.sys every time we build it I'm not sure, I don't recall ever making use of the GPIO. 1 Link to comment Share on other sites More sharing options...
Dietmar Posted April 12, 2022 Share Posted April 12, 2022 (edited) @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 Edited April 12, 2022 by Dietmar Link to comment Share on other sites More sharing options...
Damnation Posted April 12, 2022 Share Posted April 12, 2022 @Dietmar Can you test this checked acpi.sys to see if 7E BSOD still happens? https://anonfiles.com/V2A4b2Wex5/acpi_checked_crackprt_test1_7z 1 Link to comment Share on other sites More sharing options...
Dietmar Posted April 12, 2022 Share Posted April 12, 2022 (edited) @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 --------- Edited April 12, 2022 by Dietmar Link to comment Share on other sites More sharing options...
Damnation Posted April 12, 2022 Share Posted April 12, 2022 @Dietmar and this one? https://anonfiles.com/73gdc4W8x6/acpi_checked_crackprt_test2_7z 1 Link to comment Share on other sites More sharing options...
Dietmar Posted April 12, 2022 Share Posted April 12, 2022 @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 --------- Link to comment Share on other sites More sharing options...
Damnation Posted April 12, 2022 Share Posted April 12, 2022 @Dietmar hopefully this one is different~ https://anonfiles.com/raZ1cfW1x5/acpi_checked_crackprt_test3_7z 1 Link to comment Share on other sites More sharing options...
Dietmar Posted April 12, 2022 Share Posted April 12, 2022 (edited) @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 --------- Edited April 12, 2022 by Dietmar Link to comment Share on other sites More sharing options...
Damnation Posted April 12, 2022 Share Posted April 12, 2022 @Dietmar I commented out ASSERT(PciInterfacesInstantiated) still BSOD? https://anonfiles.com/34u6daW9x3/acpi_checked_crackprt_test5_7z 1 Link to comment Share on other sites More sharing options...
Dietmar Posted April 12, 2022 Share Posted April 12, 2022 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 --------- Link to comment Share on other sites More sharing options...
Damnation Posted April 12, 2022 Share Posted April 12, 2022 @Dietmar odd, I commented out line 3526 yet it still says assert failed for // ASSERT(PciInterfacesInstantiated) ? I'm tired, I'll try something else tomorrow. Thanks for testing. 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now