@next84
Bah j'ai tout le temps la même erreur.
System Information (local)
--------------------------------------------------------------------------------
Computer name: DESKTOP-TGCV2M8
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\Windows
Hardware: H110M-S2H, Gigabyte Technology Co., Ltd., H110M-S2H-CF
CPU: GenuineIntel Intel(R) Core(TM) i5-7400 CPU @ 3.00GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8540065792 bytes total
On Thu 21/09/2017 22:21:44 your computer crashed
crash dump file: C:\Windows\Minidump\092117-42640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F8B0)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF8002C61E540)
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 appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 Mon 18/09/2017 20:24:57 your computer crashed
crash dump file: C:\Windows\Minidump\091817-41609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F8B0)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF80245A33540, 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 appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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.
@azertyiop ok je verrai, même si je pense que c'est plutôt un problème de drivers.
Message édité par fynmorph le 21-09-2017 à 22:27:29