我有一台配有 Gigabyte GA-P67A-D3-B3 主板的 PC，主板上有 2 个 USB 3.0 端口和一些 USB 2.0 端口。我想使用 2 个以上的 USB 3.0 设备，所以我想到使用 USB 3.0 集线器。我买了两个这样的集线器：Unitek Y-3089 和 Sharkoon 集线器（EAN：4044951016976）。这两个都产生相同的错误。
如果我将它们插入计算机上的任何 USB 3.0 端口，并将我的 Sharkoon Drivelink Combo USB 3.0（硬盘架）或 Samsung Galaxy S10+ 插入其中，则 Windows 7（我知道它不再受支持）会显示一条通知：无法安装驱动程序，我无法使用它们。
但是，如果我将这些设备直接插入同一个 USB 3.0 端口，它们就可以完美运行。
此外，如果我将这些集线器中的任何一个插入 USB 2.0 端口，并将 HDD 机架或电话插入其中，它就可以工作（尽管速度较慢）。
主板是否可能与 USB 3.0 集线器不兼容？
如果我想使用至少 4 个 USB 3.0 设备但只有 2 个端口，该怎么办？
更新
我购买了一张 Delock 89281 PCIe USB 3.0 卡，它有三个外部端口和一个内部端口：https://www.delock.com/produkte/G_89281/treiber.html?setLanguage=en
我通过运行盒子里的 CD 中的 Setup.exe 来安装硬件和软件。
我的设备可以在新端口上工作（我可以读取它们的内容等），即使它们通过集线器连接到该端口。
但是，在关机时我总是会出现 BSOD，请稍后查看其详细信息。
我从 PC 上移除了卡（硬件），不再出现 BSOD。尽管我的 DVD 驱动器和虚拟克隆驱动器在设备管理器中有一个带黑色感叹号的黄色三角形，并且它们的属性显示：
Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)
BSOD 的详细信息始终如下（除了内存地址的确切值）：
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Commander\Desktop\minidumps2\041520-24788-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*C:\Symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23915.amd64fre.win7sp1_ldr.170913-0600
Machine Name:
Kernel base = 0xfffff800`03605000 PsLoadedModuleList = 0xfffff800`03847750
Debug session time: Wed Apr 15 18:17:03.598 2020 (UTC + 2:00)
System Uptime: 0 days 0:05:54.362
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff88804594428, 0, fffff8800459180a, 5}
Unable to load image \SystemRoot\system32\DRIVERS\AppleCharger.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for AppleCharger.sys
*** ERROR: Module load completed but symbols could not be loaded for AppleCharger.sys
Could not read faulting driver name
Probably caused by : AppleCharger.sys ( AppleCharger+280a )
Followup: MachineOwner
---------
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff88804594428, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8800459180a, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800038b1100
fffff88804594428
FAULTING_IP:
AppleCharger+280a
fffff880`0459180a 498b14dc mov rdx,qword ptr [r12+rbx*8]
MM_INTERNAL_CODE: 5
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: wininit.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff880027b83c0 -- (.trap 0xfffff880027b83c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000ffffffff rbx=0000000000000000 rcx=fffff88004592340
rdx=fffff88004594580 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800459180a rsp=fffff880027b8550 rbp=0000000000000000
r8=0000000000000001 r9=0000000000000004 r10=0000000000000001
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
AppleCharger+0x280a:
fffff880`0459180a 498b14dc mov rdx,qword ptr [r12+rbx*8] ds:91b0:00000000`00000000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800036f10d1 to fffff80003675e00
STACK_TEXT:
fffff880`027b8258 fffff800`036f10d1 : 00000000`00000050 fffff888`04594428 00000000`00000000 fffff880`027b83c0 : nt!KeBugCheckEx
fffff880`027b8260 fffff800`03673f2e : 00000000`00000000 fffff888`04594428 24700003`b2500100 00000000`ffffffff : nt! ?? ::FNODOBFM::`string'+0x3a421
fffff880`027b83c0 fffff880`0459180a : fffffa80`0c72e840 00000000`00000000 fffffa80`0d61a1a0 fffff880`03ea76eb : nt!KiPageFault+0x16e
fffff880`027b8550 fffffa80`0c72e840 : 00000000`00000000 fffffa80`0d61a1a0 fffff880`03ea76eb 00000000`00000000 : AppleCharger+0x280a
fffff880`027b8558 00000000`00000000 : fffffa80`0d61a1a0 fffff880`03ea76eb 00000000`00000000 00000000`00000002 : 0xfffffa80`0c72e840
STACK_COMMAND: kb
FOLLOWUP_IP:
AppleCharger+280a
fffff880`0459180a 498b14dc mov rdx,qword ptr [r12+rbx*8]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: AppleCharger+280a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: AppleCharger
IMAGE_NAME: AppleCharger.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d2ad809
FAILURE_BUCKET_ID: X64_0x50_AppleCharger+280a
BUCKET_ID: X64_0x50_AppleCharger+280a
Followup: MachineOwner
---------
任何想法？