Écrans bleus récurrents

Bonjour,
Je viens vers vous pour un probleme tout simple : je rencontre beaucoup d'écran bleus depuis peu (2 jours), mais régulièrement. C'est un PC que j'ai monté moi même, tous les composants sont neufs.

Voici le copié collé du compte rendu WhoCrashed :

On Thu 11/03/2021 23:57:57 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031121-6406-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF805681857C5)
Bugcheck code: 0x7F (0x8, 0xFFFFDF80B2EEDE70, 0x100, 0xFFFFF805681857C5)
Error: UNEXPECTED_KERNEL_MODE_TRAP
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 bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also 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 Thu 11/03/2021 23:57:57 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: tcpip.sys (0xFFFFF805681857C5)
Bugcheck code: 0x7F (0x8, 0xFFFFDF80B2EEDE70, 0x100, 0xFFFFF805681857C5)
Error: UNEXPECTED_KERNEL_MODE_TRAP
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 bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also 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 Thu 11/03/2021 21:35:29 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031121-6687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5C50)
Bugcheck code: 0x1A (0x403, 0xFFFF8400AD39C5F0, 0x90000001BB89F025, 0xFFFF8400ECB1C2F8)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred. The page table and PFNs are out of sync . This is probably a hardware error, especially if parameters 3 & 4 differ by only a single bit.
This is likely to be caused by a hardware problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test) and make sure your system is not getting overheated. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 11/03/2021 21:12:04 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031121-7109-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5C50)
Bugcheck code: 0xA (0x2000, 0x2, 0x1, 0xFFFFF80119C2E07E)
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 Wed 10/03/2021 21:24:21 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031021-6406-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5C50)
Bugcheck code: 0xA (0x2020, 0xFF, 0x0, 0xFFFFF8012E1160B0)
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 Wed 10/03/2021 18:41:59 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031021-6343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80706C09590, 0xFFFFAE85415126B0, 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.

Plusieurs soucis donc...
J'ai fais un Memtest, pas de problèmes détectés, j'ai tous mes drivers à jours. Je suis un peu bloqué.

Quelqu'un aurait une piste ?
Merci