I have followed all the offered suggestions, (update Windows, update drivers, scan hardware for errors using Dell Support Assist as well as the diagnostic routines in the BIOS, run Memtest86 to scan for memory errors. No errors reported, drivers up to date, BIOS up to date. Yet, I still have BSODs.
Here is the latest crash dump report from WhoCrashed:
Welcome to WhoCrashed (HOME EDITION) v 7.01
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: | CARROLL-5515 |
| Windows version: | Windows 11, 10.0, version 2009, build: 22000 (x64) |
| Windows dir: | C:\WINDOWS |
| Hardware: | Inspiron 5515, Dell Inc., 0KDKG8 |
| CPU: | AuthenticAMD AMD Ryzen 7 5700U with Radeon Graphics 8664, level: 23 |
| Processor count: | 16 logical processors, active mask: 65535 |
| RAM: | 15720.2MB |
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Sat 6/11/2022 12:44:31 AM your computer crashed or a problem was reported
| Crash dump file: | C:\WINDOWS\Minidump\061122-9296-01.dmp (Minidump) |
| Bugcheck code: | 0x101(0xC, 0x0, 0xFFFF8600131C0180, 0x2) |
| Bugcheck name: | CLOCK_WATCHDOG_TIMEOUT |
| Driver or module in which error occurred: | amdppm.sys (amdppm+0x3a22) |
| File path: | C:\WINDOWS\System32\drivers\amdppm.sys |
| Description: | Processor Device Driver |
| Product: | Microsoft® Windows® Operating System |
| Company: | Microsoft Corporation |
| 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 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 6/11/2022 12:44:31 AM your computer crashed or a problem was reported
| Crash dump file: | C:\WINDOWS\MEMORY.DMP (Kernel memory dump) |
| Bugcheck code: | 0x101(0xC, 0x0, 0xFFFF8600131C0180, 0x2) |
| Bugcheck name: | CLOCK_WATCHDOG_TIMEOUT |
| Driver or module in which error occurred: | amdppm.sys (amdppm+0x3a22) |
| File path: | C:\WINDOWS\System32\drivers\amdppm.sys |
| Description: | Processor Device Driver |
| Product: | Microsoft® Windows® Operating System |
| Company: | Microsoft Corporation |
| 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 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 6/10/2022 12:21:16 AM your computer crashed or a problem was reported
| Crash dump file: | C:\WINDOWS\Minidump\061022-9078-01.dmp (Minidump) |
| Bugcheck code: | 0x1E(0xFFFFFFFFC000001D, 0xFFFFF80452576E74, 0x1, 0xFFFFF80456550650) |
| Bugcheck name: | KMODE_EXCEPTION_NOT_HANDLED |
| Driver or module in which error occurred: | FLTMGR.SYS (FLTMGR+0x6E74) |
| File path: | C:\WINDOWS\System32\drivers\FLTMGR.SYS |
| Description: | Microsoft Filesystem Filter Manager |
| Product: | Microsoft® Windows® Operating System |
| Company: | Microsoft Corporation |
| Bug check description: | This indicates that a kernel-mode program generated an exception which the error handler did not catch. |
| Analysis: | This could be caused by either a software or hardware problem.
Hardware failure is often caused by overheating. Read this article on thermal issues
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 to check your drive(s) for errors.
|
| | |
On Fri 6/10/2022 12:17:54 AM your computer crashed or a problem was reported
| Crash dump file: | C:\WINDOWS\Minidump\061022-11281-01.dmp (Minidump) |
| Bugcheck code: | 0xA(0x288, 0xFF, 0xC4, 0xFFFFF8060FB36FC0) |
| Bugcheck name: | IRQL_NOT_LESS_OR_EQUAL |
| 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. |
| Analysis: | This is a typical software problem. Most likely this is caused by a bug in a driver.
|
| | |
On Fri 6/10/2022 8:22:15 PM your computer crashed or a problem was reported
| Crash dump file: | C:\WINDOWS\Minidump\061022-9343-01.dmp (Minidump) |
| Bugcheck code: | 0x1E(0xFFFFFFFFC0000005, 0xFFFFF804434264B8, 0x1, 0x4) |
| Bugcheck name: | KMODE_EXCEPTION_NOT_HANDLED |
| Driver or module in which error occurred: | win32kbase.sys (win32kbase+0x7CB01) |
| File path: | C:\WINDOWS\System32\win32kbase.sys |
| Description: | Base Win32k Kernel Driver |
| Product: | Microsoft® Windows® Operating System |
| Company: | Microsoft Corporation |
| Bug check description: | This indicates that a kernel-mode program generated an exception which the error handler did not catch. |
| Analysis: | This could be caused by either a software or hardware problem.
Hardware failure is often caused by overheating. Read this article on thermal issues
Since there is no other responsible driver detected, it is suggested that you look for an updated driver for your graphics hardware. It's also possible that your graphics hardware was non-functional or overheated.
|
| | |
On Fri 6/10/2022 8:19:47 PM your computer crashed or a problem was reported
| Crash dump file: | C:\WINDOWS\Minidump\061022-8781-01.dmp (Minidump) |
| Bugcheck code: | 0xA(0x288, 0xFF, 0x24, 0xFFFFF80238536FC0) |
| Bugcheck name: | IRQL_NOT_LESS_OR_EQUAL |
| 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. |
| Analysis: | This is a typical software problem. Most likely this is caused by a bug in a driver.
|
| | |
Conclusion
6 crash dumps have been found and analyzed. 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:11 (h:mm:ss).
I need to get this issue resolved. I can not depend on this laptop for any serious work, as I can not depend on it to stay running without interrupting me with a BSOD. The latest was this morning at church as we were setting up to live stream the morning service. It crashed, and I had to run home (thankfully, only a 3 minute drive from the church) and grab my wife's identical laptop, to do the livestream with. No issues with that one. It's not been upgraded to Windows 11 yet, but it's identical in all hardware specifications to my laptop.
