Crash pc fréquent écran bleu

Bonjour, j'ai décidé de construire mon pc moi-même et je l'ai depuis environ 5 jours, il fonctionne niquel sauf que depuis deux jours il plante souvent en m'affichant le fameux message sur un fond bleu (windows a rencontré un problème et doit redémarrer) alors celà a commencé lorsque je voulais mettre une commande dans le cmd, car comme un con après avoir entré ma commande je m'amusais avec mon clavier mécanique et j'ai spam enter dans le cmd.. puis ce message est apparu et mon pc a planté et redémarré rapidement, mais il marche tjr niquel, pensez vous que ce soit une coincidence ou j'ai vraiment merdé avec mon cmd?
on m'a aussi conseillé de télécharger WhoCrashed, et voici le rapport de mes 4 derniers crashs.
Crash dumps are enabled on your computer.

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

On Sat 19-12-20 16:28:30 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\121920-47828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF8013BC4528D)
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 Sat 19-12-20 16:28:30 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!setjmpex+0x8299)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF8013BC4528D)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Sat 19-12-20 13:53:25 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\121920-44140-01.dmp
This was probably caused by the following module: amdppm.sys (amdppm+0x2ec7)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF80164AFA320, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\drivers\amdppm.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 Sat 19-12-20 12:58:38 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\121920-53796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0xA (0x140009350, 0x2, 0x0, 0xFFFFF8000F26E19F)
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.





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

4 crash dumps have been found and analyzed. 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.


merci à celui ou ceux qui pourraient m'aider