Dietmar Posted April 24, 2022 Share Posted April 24, 2022 But a quick test with Windbg and the debug version of acpi.sys V4 shows something other Dietmar 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 MTRR feature disabled. KiInitializeMTRR: OS support for MTRRs disabled KiInitializeMTRR: OS support for MTRRs disabled KiInitializeMTRR: OS support for MTRRs disabled KiInitializeMTRR: OS support for MTRRs disabled KiInitializeMTRR: OS support for MTRRs disabled KiInitializeMTRR: OS support for MTRRs disabled KiInitializeMTRR: OS support for MTRRs disabled KiInitializeMTRR: OS support for MTRRs disabled KiInitializeMTRR: OS support for MTRRs disabled KiInitializeMTRR: OS support for MTRRs disabled KiInitializeMTRR: OS support for MTRRs disabled KiInitializeMTRR: OS support for MTRRs disabled *** Assertion failed: (Pfn1->u3.e2.ReferenceCount != 0) || ((Pfn1->u3.e1.Rom == 1) && (CacheType == MmCached)) *** Source File: d:\xpsp\base\ntos\mm\iosup.c, line 6745 Break repeatedly, break Once, Ignore, terminate Process, or terminate Thread (boipt)? i i *** Assertion failed: (Pfn1->u4.PteFrame == MI_MAGIC_AWE_PTEFRAME) || (Pfn1->PteAddress == (PVOID) (ULONG_PTR)(X64K | 0x1)) || (Pfn1->u4.PteFrame == MI_MAGIC_4GB_RECLAIM) *** Source File: d:\xpsp\base\ntos\mm\iosup.c, line 6810 Break repeatedly, break Once, Ignore, terminate Process, or terminate Thread (boipt)? i i *** Fatal System Error: 0x000000a5 (0x00000003,0x314C5054,0xC0140004,0x494E495F) 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 (Sun Apr 24 23:33:12.187 2022 (UTC + 2:00)), ptr64 FALSE Loading Kernel Symbols ................................................ Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A5, {3, 314c5054, c0140004, 494e495f} Probably caused by : ACPI.sys ( ACPI!ACPIBuildCompleteMustSucceed+43 ) Followup: MachineOwner --------- nt!RtlpBreakWithStatusInstruction: 80ac37ec cc int 3 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* ACPI_BIOS_ERROR (a5) The ACPI Bios in the system is not fully compliant with the ACPI specification. The first value indicates where the incompatibility lies: This bug check covers a great variety of ACPI problems. If a kernel debugger is attached, use "!analyze -v". This command will analyze the precise problem, and display whatever information is most useful for debugging the specific error. Arguments: Arg1: 00000003, ACPI_FAILED_MUST_SUCCEED_METHOD ACPI tried to run a control method while creating device extensions to represent the ACPI namespace, but this control method failed. Arg2: 314c5054, The ACPI Object that was being run Arg3: c0140004, return value from the interpreter Arg4: 494e495f, Name of the control method (in ULONG format) Debugging Details: ------------------ ACPI_OBJECT: 314c5054 DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0xA5 PROCESS_NAME: System ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre LAST_CONTROL_TRANSFER: from 80a30d7b to 80ac37ec STACK_TEXT: b8583858 80a30d7b 00000003 b8583bb4 00000000 nt!RtlpBreakWithStatusInstruction b85838a4 80a319e6 00000003 8b15c888 8b113000 nt!KiBugCheckDebugBreak+0x19 b8583c84 80a31f77 000000a5 00000003 314c5054 nt!KeBugCheck2+0x574 b8583ca4 b7e3f953 000000a5 00000003 314c5054 nt!KeBugCheckEx+0x1b b8583cc0 b7e65fdd 8b1bba20 c0140004 00000000 ACPI!ACPIBuildCompleteMustSucceed+0x43 [c:\nt\base\busdrv\acpi\driver\nt\buildsrc.c @ 433] b8583cf8 b7e63e3d b7e3f910 c0140004 00000000 ACPI!AsyncCallBack+0xe5 [c:\nt\base\busdrv\acpi\driver\amlinew\sync.c @ 82] b8583d1c b7e66dbb c0140004 4556414c 8b113000 ACPI!RunContext+0x1f5 [c:\nt\base\busdrv\acpi\driver\amlinew\ctxt.c @ 649] b8583d44 b7e66ee7 8b113000 00000000 b7e85408 ACPI!InsertReadyQueue+0x15a [c:\nt\base\busdrv\acpi\driver\amlinew\sched.c @ 275] b8583d64 b7e57fdf 8b15b468 00000000 8b272020 ACPI!RestartCtxtPassive+0x54 [c:\nt\base\busdrv\acpi\driver\amlinew\sched.c @ 384] b8583dac 80bd81ac 00000000 00000000 00000000 ACPI!ACPIWorker+0xbf [c:\nt\base\busdrv\acpi\driver\nt\worker.c @ 302] b8583ddc 80ae4212 b7e57f20 00000000 00000000 nt!PspSystemThreadStartup+0x34 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 STACK_COMMAND: kb FOLLOWUP_IP: ACPI!ACPIBuildCompleteMustSucceed+43 [c:\nt\base\busdrv\acpi\driver\nt\buildsrc.c @ 433] b7e3f953 c7401802000000 mov dword ptr [eax+18h],2 FAULTING_SOURCE_LINE: c:\nt\base\busdrv\acpi\driver\nt\buildsrc.c FAULTING_SOURCE_FILE: c:\nt\base\busdrv\acpi\driver\nt\buildsrc.c FAULTING_SOURCE_LINE_NUMBER: 433 FAULTING_SOURCE_CODE: 429: // Note: we don't have a race condition here because only one 430: // routine can be processing a request at any given time. Thus it 431: // is safe for us to specify a new next phase 432: // > 433: buildRequest->NextWorkDone = WORK_DONE_FAILURE; 434: 435: // 436: // Transition to the next stage 437: // 438: ACPIBuildCompleteCommon( SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: ACPI!ACPIBuildCompleteMustSucceed+43 FOLLOWUP_NAME: MachineOwner MODULE_NAME: ACPI IMAGE_NAME: ACPI.sys DEBUG_FLR_IMAGE_TIMESTAMP: 626570df IMAGE_VERSION: 5.1.2600.7777 FAILURE_BUCKET_ID: 0xA5_ACPI!ACPIBuildCompleteMustSucceed+43 BUCKET_ID: 0xA5_ACPI!ACPIBuildCompleteMustSucceed+43 ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0xa5_acpi!acpibuildcompletemustsucceed+43 FAILURE_ID_HASH: {5ff4cd30-9433-c4e0-8096-0615b3b5c98a} Followup: MachineOwner --------- Link to comment Share on other sites More sharing options...
Dietmar Posted April 24, 2022 Share Posted April 24, 2022 @Mov AX, 0xDEAD Just now I am prepairing the loong !amli output and hope, that it says something to you Dietmar Link to comment Share on other sites More sharing options...
George King Posted April 24, 2022 Share Posted April 24, 2022 @Dietmar Have you tried it without _OSI modification too? Link to comment Share on other sites More sharing options...
Dietmar Posted April 24, 2022 Share Posted April 24, 2022 (edited) @George King @Mov AX, 0xDEAD I build acpi.sys V4 also without the _OSI modd, but now I test "full" acpi.sys V4 Dietmar PS: I think, this acpi error is different from all the others. It appears first time on all >= Skylake boards when using asl.exe for loading a DSDT table to Bios. Very easy way but this special Bsod destroys until now its possibility for to use with sense. Here is the loong output, about 1 Mbyte. I load new version up because it is better readable ottoASL5.7z Edited April 24, 2022 by Dietmar Link to comment Share on other sites More sharing options...
Andalu Posted April 24, 2022 Share Posted April 24, 2022 (edited) @Mov AX, 0xDEAD taking a look at other resources, I noticed that there is a conflict related to the PCHRESV. But I have not found any reference for the memory range involved in any other devices/resources, included the 'PCI device' indicated. Below two images: https://anonfiles.com/ZdMbV7Zexa/Resources1_png https://anonfiles.com/j3N2V6Z4x0/Resources2_png Edit: it seems a common presumed problem also for my other boards (Q370 and Q87) and probably for the others not yet checked. Edited April 24, 2022 by Andalu Link to comment Share on other sites More sharing options...
Mov AX, 0xDEAD Posted April 25, 2022 Author Share Posted April 25, 2022 6 hours ago, Andalu said: @Mov AX, 0xDEAD taking a look at other resources, I noticed that there is a conflict related to the PCHRESV. But I have not found any reference for the memory range involved in any other devices/resources, included the 'PCI device' indicated. Below two images @Andalu First Yellow mark_resource.png told about NAME duplicates, not resource conflict Today i will play in VM what happens if i'l create two devices with same _HID/_UID as your DSDT and will report about findings Link to comment Share on other sites More sharing options...
Mov AX, 0xDEAD Posted April 25, 2022 Author Share Posted April 25, 2022 7 hours ago, Dietmar said: @Mov AX, 0xDEAD Just now I am prepairing the loong !amli output and hope, that it says something to you Dietmar I can't help with it, as i wrote few times before, BIOS reconfig DSDT/SSDT tables before running OS Then you overwrite dynamic DSDT with static DSDT from registry and get two assertions from kernel and bsod from acpi with "Arg0=0xa,)AMLI_ERROR(c0140004): Index is too big" My old https://github.com/MovAX0xDEAD/ACPI-Patcher patches BIOS's DSDT copy, so it is actual on every reboot Link to comment Share on other sites More sharing options...
Damnation Posted April 25, 2022 Share Posted April 25, 2022 (edited) @Mov AX, 0xDEAD OK, I got it started - Microsoft (R) Windows Debugger Version 10.0.19041.685 X86 Copyright (c) Microsoft Corporation. All rights reserved. Using NET for debugging Opened WinSock 2.0 Waiting to reconnect... Connected to target 192.168.88.22 on port 50000 on local IP 192.168.88.33. You can get the target MAC address by running .kdtargetmac command. Connected to Windows XP 2600 x86 compatible target at (Mon Apr 25 15:29:39.685 2022 (UTC + 8:00)), ptr64 FALSE Kernel Debugger connection established. ************* Path validation summary ************** Response Time (ms) Location OK C:\Symbols Symbol search path is: C:\Symbols Executable search path is: Windows XP Kernel Version 2600 MP (1 procs) Free x86 compatible Built by: 2600.xpsp_sp3_qfe.180912-0606 Machine Name: Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720 System Uptime: not available Break instruction exception - code 80000003 (first chance) nt!DbgBreakPoint: 8052b718 cc int 3 ************* Path validation summary ************** Response Time (ms) Location OK C:\Symbols Symbol search path is: C:\Symbols Executable search path is: Windows XP Kernel Version 2600 MP (1 procs) Free x86 compatible Built by: 2600.xpsp_sp3_qfe.180912-0606 Machine Name: Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720 System Uptime: not available Break instruction exception - code 80000003 (first chance) nt!DbgBreakPoint: 8052b718 cc int 3 kd> g ACPIInitializeDDB: AMLILoadDDB failed 0xc0000035 *** Assertion failed: ACPIInitializeDDB: AMLILoadDDB failed to load DDB 0 *** Source File: e:\xpsp1\nt\base\busdrv\acpi\driver\shared\acpiinit.c, line 509 Break repeatedly, break Once, Ignore, terminate Process, or terminate Thread (boipt)? I recall you saying I need to enter !amli set spewon verboseon logon traceon after ed KD_ACPI_Mask 0xFFFFFFF at some point but I haven't reached that point yet. so what do I type in next? Edited April 25, 2022 by Damnation Link to comment Share on other sites More sharing options...
Damnation Posted April 25, 2022 Share Posted April 25, 2022 @Mov AX, 0xDEAD I followed example set by @Andalu and got this output. too large to attach uncompressed, sorry. TRX40_DESIGNARE_ACPI_DEBUG_1.zip Link to comment Share on other sites More sharing options...
Damnation Posted April 25, 2022 Share Posted April 25, 2022 @Mov AX, 0xDEAD I get these AE_ALREADY_EXISTS errors when I boot into Linux and check the boot logs too. Linux at least, although it notes the error, seems to not care. Link to comment Share on other sites More sharing options...
Damnation Posted April 25, 2022 Share Posted April 25, 2022 @George King I'll make a new ACPI x64 once @Mov AX, 0xDEAD has a fix for object already existing. 1 Link to comment Share on other sites More sharing options...
Mov AX, 0xDEAD Posted April 25, 2022 Author Share Posted April 25, 2022 (edited) 5 hours ago, Damnation said: @Mov AX, 0xDEAD I followed example set by @Andalu and got this output. @Damnation SSDT7 is copy of DSDT, many deviced defined in DSDT, then again in SSDT, nice BIOS from gigabyte There is no simple workaround, i have three options 1) You can try to bypass creating doubled devices: Quote if (!(dwfNS & NSF_EXIST_OK)) { rc = AMLI_LOGERR(AMLIERR_OBJ_ALREADY_EXIST, ("CreateNameSpaceObject: object already exist - %s", pszName)); } Quote if (!(dwfNS & NSF_EXIST_OK)) { //rc = AMLI_LOGERR(AMLIERR_OBJ_ALREADY_EXIST, // ("CreateNameSpaceObject: object already exist - %s", // pszName)); } rc will be STATUS_SUCCESS, pns = NULL Quote Name (MWTT, 0xFF) Scope (\_SB.I2CA) { Device (WT1A) { Name (_ADR, Zero) // _ADR: Address Name (_HID, "STK0001A") // _HID: Hardware ID So device WT1A will not be created again, but then acpi will want to create names _ADR,_HID and many methods and link to "we don't created new" device, i dont know what will happens, check log again after patching normal creation by DSDT: Quote b8165487: Scope(I2CA) b816548e: { b816548e: Device(WT1A)OSNotifyCreate: 8C446FD8 (WT1A) = 00000103 b8165496: { b8165496: Name(_ADR,Zero) b816549c: Name(_HID,"STK0001A") b81654ab: Name(_CID,"SPBTestKMDFA") b81654be: Method(_CRS,0x0) b81654f1: Method(_STA,0x0) b8165507: } 2) If CreateNameSpaceObject() found already existed device, it will patch it's name to make it unique: DSDT creates WT1A SSDT creates zT1A W->z just as example, maybe some other rare allowed symbol This option can make mess if WT1A reports about some claimed resources, zT1A will report same resources. There is other autoexecuted methods like _STA or _INI 3) Totaly ignore device and all child names and child methods but i dont know to make it, too much work :) Edited April 25, 2022 by Mov AX, 0xDEAD Link to comment Share on other sites More sharing options...
Damnation Posted April 25, 2022 Share Posted April 25, 2022 (edited) @Mov AX, 0xDEAD I recall from my linux boot logs (sorry I don't have it to share right now) WT1A was not the only duplicate device, there were about 10 other duplicates or so. I can boot into linux and get the log if you're curious. I'll give option 1 a try since it seems to be easiest. I wounder how Windows 8.1 handles duplicates? does it just ignore them? or handle them some other way? edit: from the linux boot logs 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CD.MT5D], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CD.MT4D], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CD.WT4D], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CD.MT3D], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CD.WT3D], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CD.MT2D], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CD.WT2D], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CD.MT1D], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CD.WT1D], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CC.MT5C], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CC.MT4C], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CC.WT4C], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CC.MT3C], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CC.WT3C], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CC.MT2C], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CC.WT2C], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CC.MT1C], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CC.WT1C], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CB.MT5B], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CB.MT4B], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CB.WT4B], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CB.MT3B], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CB.WT3B], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CB.MT2B], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CB.WT2B], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CB.MT1B], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CB.WT1B], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CA.MT5A], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CA.MT4A], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CA.WT4A], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CA.MT3A], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CA.WT3A], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CA.MT2A], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CA.WT2A], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CA.MT1A], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CA.WT1A], AE_ALREADY_EXISTS (20190816/dswload2-326) Edited April 25, 2022 by Damnation Link to comment Share on other sites More sharing options...
genieautravail Posted April 25, 2022 Share Posted April 25, 2022 19 hours ago, daniel_k said: Please do one last test. Install Win7 and the Modded USB3 from MDL. Do not install the Intel USB3 HCSwitch driver. Can you dump the DSDT from ACPI tables using RWEverything? http://rweverything.com/download/ As I'm curious, already done in my previous tests! Before installing the Intel USB3 HCSwitch driver and only with the Modded USB3 from MDL, I can plug and use all my USB devices (even the problematic USB flash drives) but not at full USB3 speed (around 30MB/s speed for file transfer). I guess that without the HCSwitch driver, the USB 3.0 ports stay in 2.0 mode. Here the link for all the ACPI tables + ACPI tables in binary format: ACPITables Link to comment Share on other sites More sharing options...
Damnation Posted April 25, 2022 Share Posted April 25, 2022 (edited) @George King updated amd64 build https://anonfiles.com/zcCehfa1yf/acpi_xp_amd64_forGK_3_7z and src https://anonfiles.com/v5Y4hfaby3/acpi_v4_amd64_src_7z Edited April 25, 2022 by Damnation 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