Plusieurs message d'écran bleu

j'ai plusieurs messagge d'érreurs quand je joue ou je regarde vidéos ex de code d'erreur : IRQL_NOT_LESS_OR_EQUAL ou
SYSTEM_SERVICE_EXEPTION voila mon report avec whocrashed
Home Edition Notice
--------------------------------------------------------------------------------

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.

PLEASE NOTE THAT THIS VERSION OF WHOCRASHED IS NOT LICENSED FOR USE BY PROFESSIONAL SUPPORT ENGINEERS.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.


--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

Computer name: DESKTOP-PVEQU6U
Windows version: Windows 10, 10.0, version 1709, build: 16299
Windows dir: C:\WINDOWS
Hardware: Latitude 3470, Dell Inc.,
CPU: GenuineIntel Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz 8664, level: 6
4 logical processors, active mask: 15
RAM: 16839872512 bytes (15,7GB)




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dumps are enabled on your computer.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Fri 25/12/2020 10:13:03 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\122520-8078-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF807646B4D0E)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF807646B4D0E, 0xFFFFF8016D45C448, 0xFFFFF8016D45BC90)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\tcpip.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in a 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 25/12/2020 10:13:03 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: athw8x.sys (athw8x+0x28BB39)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF807646B4D0E, 0xFFFFF8016D45C448, 0xFFFFF8016D45BC90)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\athw8x.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 might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
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: athw8x.sys (Qualcomm Atheros Extensible Wireless LAN device driver, Qualcomm Atheros Communications, Inc.).
Google query: athw8x.sys Qualcomm Atheros Communications, Inc. KMODE_EXCEPTION_NOT_HANDLED



On Fri 25/12/2020 10:03:34 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\122520-7718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1637D0)
Bugcheck code: 0x50 (0xFFFFD80150703C7A, 0x10, 0xFFFFD80150703C7A, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 25/12/2020 9:37:20 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\122520-7968-01.dmp
This was probably caused by the following module: hal.dll (0xFFFFF8022360480D)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF8022360480D, 0xFFFFF1062AFEE570, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 25/12/2020 9:34:03 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\122520-8234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1637D0)
Bugcheck code: 0xA (0xF8, 0x2, 0x0, 0xFFFFF8036B4AC28C)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 25/12/2020 9:32:20 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\122520-7781-01.dmp
This was probably caused by the following module: hal.dll (hal+0x2931)
Bugcheck code: 0xA (0xFFFF8A909299DA10, 0x2, 0x1, 0xFFFFF8024C0A090A)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 21/12/2020 10:58:50 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\LiveKernelReports\PoW32kWatchdog-20201221-2258.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!IoUnregisterShutdownNotification+0xBBE)
Bugcheck code: 0x1A1 (0xFFFF9609A03E0040, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

7 crash dumps have been found and analyzed. A third party driver has 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:

athw8x.sys (Qualcomm Atheros Extensible Wireless LAN device driver, Qualcomm Atheros Communications, Inc.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
MERCI D'AVANCE ;)