Problème BSOD !!!

Bonjour

Je me tourne vers vous car je suis désespéré et je ne trouve aucune réponse nul part , j'ai emmené ma tour 5 FOIS chez l'informaticien et j'ai pourtant encore ces BSOD , je vous explique la situation, depuis le mois d'août j'ai de gros problèmes de blue screen très aléatoire , ceux-ci se produisent soit au démarrage et font des Bsod en boucle pendant le démarrage jusqu'à ce que ça marche , sinon c'est pendant que j'utilise l'ordinateur. Il m'arrive même d'avoir des freez et l'ordi redémarre tout seul.Sinon ils apparaissent un peu quand ils veulent même quand je fait juste de la Bureautique, je passe quasiment jamais une journée sans BSOD.

Au début était avancé l'idée d'un virus mais j'avais encore les BSOD même après avoir remis l'ordinateur à zéro plusieurs fois et fait des vérifications Bitdefender , ensuite l'alimentation que j'ai changé mais toujours le même problème.

Les codes d'erreur change souvent j'en ai bien des récurrent mais sinon ça change souvent.

Je vous poste un rapport Whocrashed pour avoir plus de détails :

On Sun 14/02/2021 18:31:37 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021421-5890-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80)
Bugcheck code: 0xEF (0xFFFF8A06C802C080, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
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 critical system process died.
There is a possibility this problem was caused by a virus or other malware.
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 14/02/2021 18:31:37 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntdll.sys (ntdll!NtTerminateProcess+0x14)
Bugcheck code: 0xEF (0xFFFF8A06C802C080, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
Bug check description: This indicates that a critical system process died.
There is a possibility this problem was caused by a virus or other malware.
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: ntdll.sys .
Google query: ntdll.sys CRITICAL_PROCESS_DIED



On Sun 14/02/2021 18:22:00 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021421-5437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80643106C04, 0xFFFF980AE011EC60, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 Sat 13/02/2021 20:15:41 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021321-5546-01.dmp
This was probably caused by the following module: win32kfull.sys (0xFFFF97DB78C63847)
Bugcheck code: 0x50 (0xFFFFFFFFF18B41DB, 0x0, 0xFFFF97DB78C63847, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel 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.
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.



Honnêtement je ne sais vraiment plus quoi faire , j'espère vraiment que l'un d'entre vous puisse m'aider je suis à bout.