Ecran bleu DPC WATCHDOG VIOLATION

Je vais essayer de faire comme toi.

j ai déja fait le test disque dur et il tourne nickel.
voici le lien pour core temp
https://pjjoint.malekal.com/files.php?id=20180126_x8o9k11g15r13

par acquis de conscience voici la capture d'écran de Crystaldiskinfo
https://pjjoint.malekal.com/files.php?id=20180126_y11j7x6f7d9

Non rien en usb

Crash dumps are enabled on your computer.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Thu 25/01/2018 08:34:54 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012518-18531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x154EA0)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 25/01/2018 08:34:54 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: fltmgr.sys (fltmgr!fltreleasecontext+0x3f4)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\drivers\fltmgr.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
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 file system 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.





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

2 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.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

FRST.txt
https://pjjoint.malekal.com/files.php?id=FRST_20180125_f7s8u9n7c14

Shortcut.txt
https://pjjoint.malekal.com/files.php?id=20180125_y6n6j15d5d7
Additionnal.txt
https://pjjoint.malekal.com/files.php?id=20180125_r13r8e9w7u5

Salut,

Débranche tout sauf le clavier et la souris.
Quelle est la version de Windows ?