Blue Screen différent à chaque démarrage

Bonjour,
Je reçois récemment des bsod souvent quand je joue ou après un démarrage et à chaque fois le message d'erreur est différent. J'ai fait une analyse avec le logiciel "WhoCrashed" dont je vais coller ici une copie du résultat. Je tiens à préciser que malgré les multiples écrans bleus, mon ordinateur tourne comme si tout allait bien après avoir redémarré, du moins c'est mon ressentit:

On Sun 04/09/2022 08:59:13 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\090422-13312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x417D40)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80153EB03C4, 0x1, 0xFFFF880988EEBCB0)
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 Sun 04/09/2022 08:59:13 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: usbxhci.sys (USBXHCI+0x3B67)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80153EB03C4, 0x1, 0xFFFF880988EEBCB0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote XHCI USB
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 storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Sat 03/09/2022 19:44:00 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\090322-17609-01.dmp
This was probably caused by the following module: cng.sys (0xFFFFF8035D3B0DDA)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8035D3B0DDA, 0xFFFFE3092342E9D0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\cng.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Cryptography, Next Generation
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 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 Sat 03/09/2022 14:51:36 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\090322-17531-01.dmp
This was probably caused by the following module: intelppm.sys (intelppm+0x153f)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF80041905330, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\drivers\intelppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
The crash took place in a Microsoft module. The description of the module may give a hint about a non responding device in the system.



On Wed 31/08/2022 21:07:30 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\083122-17453-01.dmp
This was probably caused by the following module: bddci.sys (0xFFFFF8060639EB62)
Bugcheck code: 0xD1 (0xFFFFF805063BBE10, 0x2, 0x0, 0xFFFFF8060639EB62)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\bddci.sys
product: Bitdefender BDDCI
company: Bitdefender
description: BDDCI filter driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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.
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: bddci.sys (BDDCI filter driver, Bitdefender).
Google query: bddci.sys Bitdefender DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Wed 31/08/2022 18:46:06 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\083122-8984-01.dmp
This was probably caused by the following module: vgk.sys (vgk+0x15cfc)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF8072BD05330)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Program Files\Riot Vanguard\vgk.sys
product: Vanguard Driver
company: Riot Games, Inc.
description: Vanguard kernel-mode driver.
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
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: vgk.sys (Vanguard kernel-mode driver., Riot Games, Inc.).
Google query: vgk.sys Riot Games, Inc. DPC_WATCHDOG_VIOLATION