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-L365BP3
Windows version: Windows 10, 10.0, version 2009, build: 19045 (x64)
Windows dir: C:\Windows
Hardware: MS-7D91, Micro-Star International Co., Ltd., MAG Z790 TOMAHAWK WIFI DDR4 (MS-7D91)
CPU: GenuineIntel 13th Gen Intel(R) Core(TM) i5-13600K 8664, level: 6
Processor count: 20 logical processors, active mask: 1048575
RAM: 32539,4MB
Crash Dump Analysis
Crash dumps are enabled on your computer. This system is not configured for complete or automatic crash dumps. For best results, configure your system to write out complete or automatic crash dumps. Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Sat 09/03/2024 14:54:35 your computer crashed or a problem was reported
Crash dump file: C:\Windows\Minidump\030924-8687-01.dmp (Minidump)
Bugcheck code: 0x101(0xA, 0x0, 0xFFFFE3019038E180, 0x2)
Bugcheck name: CLOCK_WATCHDOG_TIMEOUT
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (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.
On Sat 09/03/2024 13:14:36 your computer crashed or a problem was reported
Crash dump file: C:\Windows\Minidump\030924-8593-01.dmp (Minidump)
Bugcheck code: 0x101(0xA, 0x0, 0xFFFFC900F7247180, 0x3)
Bugcheck name: CLOCK_WATCHDOG_TIMEOUT
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (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 following dump file was found but appeared to be corrupt: C:\Windows\MEMORY.DMP
Conclusion
3 crash dumps have been found and analyzed. Only 2 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.
No offending third party drivers have been found. Consider 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 suggestions displayed in the bugcheck analysis above.
The analysis process took 0:00:04 (h:mm:ss).