KMODE EXEPTION NOT HANDLE

Bonjour,

Depuis plusieurs jours l'écran bleu KMODE EXEPTION NOT HANDLE apparait. J'ai passé des heures à essayer de me sortir de ce pétrin sans succes.
Voici le rapport whocrashed:

D'avance merci à celui qui passera par la!

Eléonore

--------------------------------------------------------------------------------------------------

Crash dumps are enabled on your computer.

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

On Mon 19/04/2021 16:02:20 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\041921-36390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5C50)
Bugcheck code: 0x1E (0xFFFFFFFFC0000094, 0xFFFFF8051C8E8616, 0xFFFF9288CFB8C870, 0x5A)
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 19/04/2021 16:02:20 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!HvlPerformEndOfInterrupt+0x4DEE)
Bugcheck code: 0x1E (0xFFFFFFFFC0000094, 0xFFFFF8051C8E8616, 0xFFFF9288CFB8C870, 0x5A)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 19/04/2021 14:41:02 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\041921-29843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5C50)
Bugcheck code: 0x1E (0xFFFFFFFFC0000094, 0xFFFFF800268E8616, 0xFFFFC78166FB2880, 0x5A)
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 14/04/2021 14:51:45 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\041421-33703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5C50)
Bugcheck code: 0x1E (0xFFFFFFFFC0000094, 0xFFFFF806358E8616, 0xFFFF9A06F0C86330, 0x5A)
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 31/03/2021 10:22:30 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\LiveKernelReports\NDIS-20210331-1022.dmp
This was probably caused by the following module: ndis.sys (ndis!NdisMatchPdoWithPacket+0xD95)
Bugcheck code: 0x15E (0x25, 0x23, 0xFFFFE48DDF7FDB38, 0xFD010101)
Error: BUGCODE_NDIS_DRIVER_LIVE_DUMP
file path: C:\WINDOWS\system32\drivers\ndis.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: NDIS (Network Driver Interface Specification)
Bug check description: NDIS has captured a live kernel dump. NDIS does not generate a bug check in this situation.
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.



The following dump files were found but could not be read. These files may be corrupted:
C:\WINDOWS\Minidump\041921-37640-01.dmp
C:\WINDOWS\Minidump\041921-30921-01.dmp




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

7 crash dumps have been found and analyzed. Only 5 are included in this report. If dump files are found and they could not be analuzed, it means they are corrupted. Because crash dumps are an emergency measure it is not uncommon for this to happen, however often it points to a problem in the storage stack. It is suggested that you run CHKDSK on your system drive to check your drive for errors.
No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


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.