BSOD et problème USB 3.0... la totale ;-)

Bonsoir !

Je m'en remets à vous après avoir épuisé mon temps sur mon ordinateur portable.
Voici les 2 problèmes :

- J'ai des BSOD depuis que j'ai acheté mon ordinateur, après l'avoir passé sous Seven (Win 8 à l'origine). Je l'ai depuis réinstallé sous Win 8.1 Pro, et rien n'a changé. Je fournirai la liste des crashs de Whocrashed en fin de post.
C'est déjà pas mal.

Ensuite, deuxième problème :
- Mes disques durs externes (qui fonctionnent très bien pour les avoir testés sur d'autres machines), ne sont reconnus par Windows que sur un seul port : le port power charger. Les autres reconnaissent toutefois ma clé USB 3.0 (pourquoi ?!) très bien, puisque j'arrive à des débits honorables (120 Mo /s)
Je suppose que les problèmes sont liés. Travaillant dans le monde du développement, cela m'ennuie quand l'ordinateur crashe et redémarre, de manière arbitraire ;-)

Les spécs :
Asus G750JH-T4040
Windows 8.1 Pro x64
Intel I7-4700HQ (2.4~3.4 GHz) à 8 coeurs logiques, Chip HM87
32 Go de RAM DDR3 à 1600 MHz
Nvidia GTX 780m

Si besoin est, je compléterai la liste en fonction de ce que vous demanderez


Et enfin, le rapport WhoCrashed (un peu long !!!!)




Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Fri 09/01/2015 16:31:58 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\010915-21125-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x5873)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80175351873, 0xFFFFD00022C8D4C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\fltmgr.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Fri 09/01/2015 16:31:58 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr!FltReleaseContext+0xE03)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80175351873, 0xFFFFD00022C8D4C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\fltmgr.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 07/01/2015 08:10:27 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\010715-18937-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150AA0)
Bugcheck code: 0xA (0xFFFFF78000020008, 0xD, 0x0, 0xFFFFF80234EBAA3F)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Mon 05/01/2015 21:06:33 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\010515-19437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150AA0)
Bugcheck code: 0xC7 (0x8, 0x1, 0xFFFFE000E2D574F0, 0x2000)
Error: TIMER_OR_DPC_INVALID
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a kernel timer or delayed procedure call (DPC) is found somewhere in memory where it is not permitted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 04/01/2015 19:02:54 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\010415-18109-01.dmp
This was probably caused by the following module: portcls.sys (portcls+0x4CEB)
Bugcheck code: 0xD1 (0xFFFFF802F9D2FC09, 0x2, 0x8, 0xFFFFF802F9D2FC09)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\portcls.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Port Class (Class Driver for Port/Miniport Devices)
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 Sun 04/01/2015 17:29:40 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\010415-19468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150AA0)
Bugcheck code: 0xA (0xFFFFD002551559F5, 0xF, 0x0, 0xFFFFF800086B1567)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 30/12/2014 14:20:31 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\123014-6531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150AA0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800AFB124AB, 0x0, 0xDACB8)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 Mon 29/12/2014 15:49:01 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\122914-6843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150AA0)
Bugcheck code: 0x3D (0xFFFFD00068E222F0, 0x0, 0x0, 0xFFFFF80139A9DA7F)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
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 appears very infrequently.
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 27/12/2014 14:51:35 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\122714-7109-01.dmp
This was probably caused by the following module: athwbx.sys (athwbx+0xC863E)
Bugcheck code: 0x1E (0xFFFFFFFF80000003, 0xFFFFF8006AD6463E, 0x0, 0xFFFFD001B3B54B5C)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\athwbx.sys
product: Driver for Qualcomm Atheros CB42/CB43/MB42/MB43 Network Adapter
company: Qualcomm Atheros Communications, Inc.
description: Qualcomm Atheros Extensible Wireless LAN device driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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: athwbx.sys (Qualcomm Atheros Extensible Wireless LAN device driver, Qualcomm Atheros Communications, Inc.).
Google query: Qualcomm Atheros Communications, Inc. KMODE_EXCEPTION_NOT_HANDLED



On Fri 26/12/2014 12:59:10 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\122614-7906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150AA0)
Bugcheck code: 0xC7 (0x8, 0x1, 0xFFFFD0013B46A800, 0x2000)
Error: TIMER_OR_DPC_INVALID
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a kernel timer or delayed procedure call (DPC) is found somewhere in memory where it is not permitted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




La conclusion du rapport WhoCrashed est :


14 crash dumps have been found and analyzed. Only 10 are included in this report. 2 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:

usbstor.sys (Pilote de classe de stockage de masse USB, Microsoft Corporation)
athwbx.sys (Qualcomm Atheros Extensible Wireless LAN device driver, Qualcomm Atheros Communications, Inc.)






En espérant avoir été assez clair,


Merci d'avance pour vos réponses