Bsod system thread exception

Bonjour a tous

J'ai monté un pc moi meme il y a 2 jours, depuis j'ai le bsod system thread no exception found et no more stack locations remaining. Cela arrive quelques minutes apres le démarrage.
Ma config :

SSD crucial cx500
HDD seagate 2TO
MSI carbon B540 gaming AC
Nvidia geforce gygabyte 1060 6GB
16GB ram
AMD Ryzen 5 2600
corsair VSU 650W


Voici le rapport who crashed

System Information (local)

Computer name: DESKTOP-AB9JDMB
Windows version: Windows 10 , 10.0, version 1903, build: 18362
Windows dir: C:\Windows
Hardware: MS-7B85, Micro-Star International Co., Ltd., B450 GAMING PRO CARBON AC (MS-7B85)
CPU: AuthenticAMD AMD Ryzen 5 2600 Six-Core Processor AMD8664, level: 23
12 logical processors, active mask: 4095
RAM: 17128538112 bytes (16,0GB)



Crash Dump Analysis

Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Wed 26/06/2019 12:03:05 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062619-11953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BC8A0)
Bugcheck code: 0x35 (0xFFFFA785D3638730, 0x0, 0x0, 0x0)
Error: NO_MORE_IRP_STACK_LOCATIONS
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 occurs when the IoCallDriver packet has no more stack locations remaining.
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 Wed 26/06/2019 12:03:05 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: envirtahci.sys (envirtahci+0x16D1C)
Bugcheck code: 0x35 (0xFFFFA785D3638730, 0x0, 0x0, 0x0)
Error: NO_MORE_IRP_STACK_LOCATIONS
file path: C:\Windows\system32\drivers\envirtahci.sys
product: AHCI Virtual Storage Miniport Driver
company: AMD
description: AHCI Virtual Storage Driver
Bug check description: This bug check occurs when the IoCallDriver packet has no more stack locations remaining.
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 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 Wed 26/06/2019 11:55:54 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062619-8515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x31CBC)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8047E431CBC, 0xFFFFF68337C93648, 0xFFFFF68337C92E90)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread 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 Wed 26/06/2019 11:21:55 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062619-10796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x31CBC)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8013E031CBC, 0xFFFFF38AD17C6648, 0xFFFFF38AD17C5E90)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread 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.


Merci d'avance pour votre aide c'est tres gentil de votre part.