System Information (local)
--------------------------------------------------------------------------------
Computer name: DESKTOP-NNKGJAQ
Windows version: Windows 10, 10.0, version 2009, build: 19042
Windows dir: C:\Windows
Hardware: H110 Gaming Infinite(MS-B915), Micro-Star International Co., Ltd., H110M GRENADE (MS-7A82)
CPU: GenuineIntel Intel(R) Core(TM) i5-7400 CPU @ 3.00GHz 8664, level: 6
4 logical processors, active mask: 15
RAM: 17128030208 bytes (16,0GB)
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Mon 10/05/2021 21:54:16 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\051121-4640-01.dmp
This was probably caused by the following module: intelppm.sys (intelppm+0x138f)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF8042E6FB320, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\drivers\intelppm.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 Mon 10/05/2021 21:54:16 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntfs.sys (ntfs+0xff46d)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF8042E6FB320, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
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.
On Mon 10/05/2021 10:56:04 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\051021-4265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5E40)
Bugcheck code: 0x1A (0x61941, 0x17D089A98E8, 0xD, 0xFFFFCE020C4DFA00)
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.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. 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 Sun 09/05/2021 19:42:00 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\050921-4265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x26c686)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF806356FB320, 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 Sun 09/05/2021 14:22:17 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\050921-4250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5E40)
Bugcheck code: 0xA (0x888, 0x2, 0x0, 0xFFFFF803316986EB)
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 08/05/2021 09:11:00 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\050821-4265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5E40)
Bugcheck code: 0x1A (0x61948, 0x1503C5, 0x1, 0x1503C5)
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.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. 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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
6 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.
