Bonjour ! 
Merci beaucoup pour ta réponse master71 ! 
J'ai essayé de comprendre quel driver je devais chercher pour ma carte USB 3.0 Qumos:
je ne comprends quel est le fabricant de la carte -et donc ce que je dois chercher sur "touslesdrivers"... 
Avec la carte, le CD fourni contenait un driver que j'ai bien sûr installé :
VIA_XHCI_Driver_V4.00B_NoAp.exe
(description : VIA Windows XCHI Driver)
Dans le Gestionnaire de périphériques de Windows :
- VIA USB eXtensible Host Controller :
Pilote :
Fournisseur : VIA
Date du Pilote : 19/03/2013
Version du pilote : 6.1.7600.4004
A partir de ce Gestionnaire,
quand je lance la Mise à jour de ce Pilote,
Windows va la chercher en ligne et me répond :
"que le meilleur pilote pour mon périphérique est déjà installé"
(VIA USB eXtensible Host Controller).
J'ai aussi installé et lancé comme tu me l'avais proposé un Whocrashed.
Voici le résultat :
"
----------Début---------
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: XXXXX
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASUSTeK Computer INC., P7P55D DELUXE
CPU: GenuineIntel Intel(R) Core(TM) i7 CPU 860 @ 2.80GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8586846208 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 09/09/2014 09:13:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090914-32058-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8008D4E870, 0xFFFFF80005970518, 0xFFFFFA800D3FB010)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 09/09/2014 09:13:36 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8008D4E870, 0xFFFFF80005970518, 0xFFFFFA800D3FB010)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 07/09/2014 10:22:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090714-30264-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800B762A70, 0xFFFFF80005970518, 0xFFFFFA800CAD6BD0)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 06/09/2014 09:32:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090614-69638-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800CFD2CC0, 0xFFFFF80000BA2748, 0xFFFFFA800B3F2BD0)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 02/09/2014 11:50:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090214-91322-01.dmp
This was probably caused by the following module: wdf01000.sys (0xFFFFF88000E3B91B)
Bugcheck code: 0x50 (0xFFFFFF8FFFB6FF88, 0x0, 0xFFFFF88000E3B91B, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l’infrastructure de pilotes en mode noyau
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 13/03/2014 14:04:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031314-27814-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800E4663E0, 0xFFFFF80000B9C518, 0xFFFFFA800F4ED6C0)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 12/03/2014 22:11:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031214-32058-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0xAA96)
Bugcheck code: 0x10D (0x7, 0x57FF797DFF8, 0xFFFFFA8008682000, 0xFFFFFA8007386480)
Error: WDF_VIOLATION
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l’infrastructure de pilotes en mode noyau
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 12/03/2014 21:47:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031214-26722-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0xAA96)
Bugcheck code: 0x10D (0x7, 0x57FF7DD7FF8, 0xFFFFFA8008228000, 0xFFFFFA8007D987D0)
Error: WDF_VIOLATION
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l’infrastructure de pilotes en mode noyau
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 12/03/2014 20:43:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031214-32198-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA80092FF870, 0xFFFFF80000B9C518, 0xFFFFFA8009DC9500)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 12/03/2014 11:29:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031214-25833-01.dmp
This was probably caused by the following module: flxhcic.sys (0xFFFFF88004911F94)
Bugcheck code: 0x50 (0xFFFFF900C4979E08, 0x0, 0xFFFFF88004911F94, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\flxhcic.sys
product: FLxHCI
company: Fresco Logic
description: Fresco Logic xHCI (USB3) Bus Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: flxhcic.sys (Fresco Logic xHCI (USB3) Bus Driver, Fresco Logic).
Google query: Fresco Logic PAGE_FAULT_IN_NONPAGED_AREA
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
32 crash dumps have been found and analyzed. Only 10 are included in this report. 4 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
rt64win7.sys (Realtek 8136/8168/8169 NDIS 6.20 64-bit Driver , Realtek )
flxhcic.sys (Fresco Logic xHCI (USB3) Bus Driver, Fresco Logic)
atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.)
kl1.sys (Kaspersky Unified Driver, Kaspersky Lab ZAO)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
...
----------Fin---------
"
Bien sûr les derniers plantages (septembre) correspondent à mes nouveaux essais avec carte USB 3.0.
En mars 2014, c'était aussi la période où j'avais essayé la précédente carte USB 3.0 de chez Inateck avec driver Fresco Logic.
Voilà, je ne sais pas si cela peut aider... 
Merci d'avance pour votre aide... 
FORUM HardWare.fr
Mais j'ai quand même un gros problème :
.