--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 7.06
--------------------------------------------------------------------------------
WhoCrashed is a comprehensible crash dump analyzer. It analyzes the system crashes of your computer or a remote computer on the network.
If your computer has displayed a blue (or black) screen of death or rebooted suddenly then your system may have crashed because of a malfunctioning device driver or because of a hardware failure. WhoCrashed will go to great lengths to help you find the root cause of the problem and a solution if available. It will analyze the crash dump files on your system or a system on the network with the single click of a button. In case the problem is caused by a malfunctioning driver, it will tell you what drivers are likely to be responsible for crashing your computer. In case of a hardware failure, it will tell you the most likely root cause and how to fix the problem.
When the analysis process is complete, WhoCrashed will write a report that offers suggestions on how to proceed in any situation, including internet links which will help you further troubleshoot any detected problems.
WhoCrashed will do great efforts to find out why your system crashed and what can be done to remedy the problem.
To obtain technical support visit www.resplendence.com/support
Click here to check if you have the latest version or if an update is available.
Just click the Analyze button for a comprehensible report ...
--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.
Please note that this version of WhoCrashed is not licensed for use by professional support engineers.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
Computer name: DESKTOP-AVSBC0U
Windows version: Windows 10, 10.0, version 2009, build: 19045 (x64)
Windows dir: C:\Windows
Hardware: HP EliteBook 8540w, Hewlett-Packard, 1521
CPU: GenuineIntel Intel(R) Core(TM) i5 CPU M 560 @ 2.67GHz 8664, level: 6
Processor count: 4 logical processors, active mask: 15
RAM: 3937,8MB
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Tue 29/08/2023 15:30:21 your computer crashed or a problem was reported
Crash dump file: C:\Windows\Minidump\082923-14109-01.dmp (Minidump)
Bugcheck code: 0x133(0x0, 0x501, 0x500, 0xFFFFF80773CFB320)
Bugcheck name: DPC_WATCHDOG_VIOLATION
Driver or module in which error occurred: intelppm.sys (intelppm+0x138f)
File path: C:\Windows\System32\drivers\intelppm.sys
Description: Processor Device Driver
Product: Microsoft® Windows® Operating System
Company: Microsoft Corporation
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).
Analysis: This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver.
This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device.
Read this article on thermal issues
A full memory dump will likely provide more useful information on the cause of this particular bugcheck. 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 Tue 29/08/2023 15:30:21 your computer crashed or a problem was reported
Crash dump file: C:\Windows\MEMORY.DMP (Kernel memory dump)
Bugcheck code: 0x133(0x0, 0x501, 0x500, 0xFFFFF80773CFB320)
Bugcheck name: DPC_WATCHDOG_VIOLATION
Driver or module in which error occurred: nvlddmkm.sys (nvlddmkm+0x1a2d45)
File path: C:\Windows\system32\DRIVERS\nvlddmkm.sys
Description: NVIDIA Windows Kernel Mode Driver, Version 341.74
Product: NVIDIA Windows Kernel Mode Driver, Version 341.74
Company: NVIDIA Corporation
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).
Analysis: This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver.
This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device.
Read this article on thermal issues
A full memory dump will likely provide more useful information on the cause of this particular bugcheck. 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:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 341.74 , NVIDIA Corporation).
Google query: nvlddmkm NVIDIA Corporation DPC_WATCHDOG_VIOLATION
On Fri 25/08/2023 10:17:34 your computer crashed or a problem was reported
Crash dump file: C:\Windows\Minidump\082523-14968-01.dmp (Minidump)
Bugcheck code: 0x116(0xFFFFC6898BE9E010, 0xFFFFF805105F4608, 0xFFFFFFFFC00000B5, 0xA)
Bugcheck name: VIDEO_TDR_ERROR
Driver or module in which error occurred: nvlddmkm.sys (nvlddmkm+0x154608)
File path: C:\Windows\system32\DRIVERS\nvlddmkm.sys
Description: NVIDIA Windows Kernel Mode Driver, Version 341.74
Product: NVIDIA Windows Kernel Mode Driver, Version 341.74
Company: NVIDIA Corporation
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
Analysis: This is a video related crash. 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:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 341.74 , NVIDIA Corporation).
Google query: nvlddmkm NVIDIA Corporation VIDEO_TDR_ERROR
On Thu 17/08/2023 13:02:30 your computer crashed or a problem was reported
Crash dump file: C:\Windows\Minidump\081723-14375-01.dmp (Minidump)
Bugcheck code: 0x116(0xFFFFBE8F64796010, 0xFFFFF8012C210B40, 0xFFFFFFFFC000009A, 0x4)
Bugcheck name: VIDEO_TDR_ERROR
Driver or module in which error occurred: nvlddmkm.sys (nvlddmkm+0x9B0B40)
File path: C:\Windows\system32\DRIVERS\nvlddmkm.sys
Description: NVIDIA Windows Kernel Mode Driver, Version 341.74
Product: NVIDIA Windows Kernel Mode Driver, Version 341.74
Company: NVIDIA Corporation
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
Analysis: This is a video related crash. 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:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 341.74 , NVIDIA Corporation).
Google query: nvlddmkm NVIDIA Corporation VIDEO_TDR_ERROR
On Thu 10/08/2023 11:30:06 your computer crashed or a problem was reported
Crash dump file: C:\Windows\Minidump\081023-14578-01.dmp (Minidump)
Bugcheck code: 0x133(0x0, 0x501, 0x500, 0xFFFFF80425EFB320)
Bugcheck name: DPC_WATCHDOG_VIOLATION
Driver or module in which error occurred: intelppm.sys (intelppm+0x138f)
File path: C:\Windows\System32\drivers\intelppm.sys
Description: Processor Device Driver
Product: Microsoft® Windows® Operating System
Company: Microsoft Corporation
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).
Analysis: This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver.
This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device.
Read this article on thermal issues
A full memory dump will likely provide more useful information on the cause of this particular bugcheck. 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 Sun 30/07/2023 10:08:03 your computer crashed or a problem was reported
Crash dump file: C:\Windows\Minidump\073023-11156-01.dmp (Minidump)
Bugcheck code: 0x3B(0xC0000005, 0xFFFFF8036117DE30, 0xFFFFDC0BAFB954C0, 0x0)
Bugcheck name: SYSTEM_SERVICE_EXCEPTION
Driver or module in which error occurred: nvlddmkm.sys (nvlddmkm+0xCDE30)
File path: C:\Windows\system32\DRIVERS\nvlddmkm.sys
Description: NVIDIA Windows Kernel Mode Driver, Version 341.74
Product: NVIDIA Windows Kernel Mode Driver, Version 341.74
Company: NVIDIA Corporation
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
Analysis: This is a typical software problem. Most likely this is caused by a bug in a driver. 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:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 341.74 , NVIDIA Corporation).
Google query: nvlddmkm NVIDIA Corporation SYSTEM_SERVICE_EXCEPTION
The following dump file was found but appeared to be corrupt: C:\Windows\LiveKernelReports\WATCHDOG-20230805-1251.dmp
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
7 crash dumps have been found and analyzed. Only 6 are included in this report. If one or more dump files were found that could not be analyzed, it means they are corrupted. It's an emergency measure for the system to write out a crash dump file and because of this, it's not uncommon for this process to fail. Often, but not always, it points to a problem in the storage stack. For instance, if the disk that should write out the crash dump file has failed, there will be no crash dump file written out. It is suggested that you run CHKDSK on your system drive to check your drive for errors.
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:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 341.74 , NVIDIA Corporation)
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 suggestions displayed in the bugcheck analysis above.
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.
The analysis process took 0:00:15 (h:mm:ss).
