On Mon 2021. 11. 29. 19:25:17 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\112921-4875-01.dmp
This was probably caused by the following module: intelppm.sys (intelppm+0x138f)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF800390FB320)
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 2021. 11. 29. 19:25:17 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: spawdm64.sys (spawdm64+0x2019)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF800390FB320)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\drivers\spawdm64.sys
product: AUDIOPROBE HS SPA Audio driver
company: AUDIOPROBE
description: AUDIOPROBE HS SPA Audio 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).
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: spawdm64.sys (AUDIOPROBE HS SPA Audio driver, AUDIOPROBE).
Google query: spawdm64.sys AUDIOPROBE DPC_WATCHDOG_VIOLATION



On Sun 2021. 11. 28. 23:30:24 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\112821-7812-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0xfd015)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF8017C0FB320)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 Fri 2021. 11. 26. 17:17:22 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\112621-5062-01.dmp
This was probably caused by the following module: intelppm.sys (intelppm+0x138f)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF8032C6FB320)
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 Sat 2021. 11. 20. 14:00:07 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\112021-7906-01.dmp
This was probably caused by the following module: intelppm.sys (intelppm+0x138f)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF802568FB320)
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 Thu 2021. 11. 04. 22:35:00 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\110421-5640-01.dmp
This was probably caused by the following module: intelppm.sys (intelppm+0x138f)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF805750FB320)
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.





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

6 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

spawdm64.sys (AUDIOPROBE HS SPA Audio driver, AUDIOPROBE)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.


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.