Dell Insprion 5515.
Frequent, and I mean today alone: 5 - 7 BSOD errors. I have wiped and reinstalled Windows 10 Home, upgraded to Windows 10 Pro, then upgraded to Windows 11 Pro, twice. Updated drivers, ran Windows Update, it's all current. Ran Dell Support Assist. It finds no issues with hardware or out-of-date drivers. Yet, I continue to get BSOD errors.
Below is the analysis of the crash dumps of the past several BSOD errors. While this report is only of the several that have occured today, it frequently mentions thermal issues. I don't know what to do to fix any of this. My wife has an identical model laptop (they were bought at the same time, same model, same configuration). She has had *no* BSODs. I have run the quick scan by Dell Support Assist, and the extended scan. It finds no issues. Yet, the BSODs continue.
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 Sun 6/5/2022 2:56:09 PM your computer crashed or a problem was reported
| Crash dump file: | C:\WINDOWS\Minidump\060522-9031-01.dmp (Minidump) |
| Bugcheck code: | 0xD1(0x7FFE7AFF043C, 0xFF, 0xD4, 0x7FFE7AFF043C) |
| Bugcheck name: | DRIVER_IRQL_NOT_LESS_OR_EQUAL |
| Bug check description: | This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. |
| Analysis: | This is a typical software problem. Most likely this is caused by a bug in a driver.
|
| | |
On Sun 6/5/2022 2:56:09 PM your computer crashed or a problem was reported
| Crash dump file: | C:\WINDOWS\MEMORY.DMP (Kernel memory dump) |
| Bugcheck code: | 0xD1(0x7FFE7AFF043C, 0xFF, 0xD4, 0x7FFE7AFF043C) |
| Bugcheck name: | DRIVER_IRQL_NOT_LESS_OR_EQUAL |
| Bug check description: | This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. |
| Analysis: | This is a typical software problem. Most likely this is caused by a bug in a driver.
|
| | |
On Sun 6/5/2022 10:56:20 AM your computer crashed or a problem was reported
| Crash dump file: | C:\WINDOWS\Minidump\060522-10078-01.dmp (Minidump) |
| Bugcheck code: | 0xFC(0xFFFFFBDCC08F6000, 0x8100000234822863, 0xFFFFDD04D8A91E80, 0x2) |
| Bugcheck name: | ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY |
| Bug check description: | This indicates that an attempt was made to execute non-executable memory. |
| Analysis: | This particular bugcheck may be caused by malware or a security product that does not follow programming guidelines. This can also be caused by memory corruption. This is possibly a software problem. There is a possibility that this is caused by memory corruption. Memory corruption can be caused by a faulty driver, faulty RAM, overheating and more. Read this article on memory corruption. Read this article on thermal issues
|
| | |
On Sun 6/5/2022 10:53:49 AM your computer crashed or a problem was reported
| Crash dump file: | C:\WINDOWS\Minidump\060522-9781-01.dmp (Minidump) |
| Bugcheck code: | 0xA(0x5D6, 0xFF, 0x3E, 0xFFFFF8030C49737A) |
| 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 Sun 6/5/2022 10:32:37 AM your computer crashed or a problem was reported
| Crash dump file: | C:\WINDOWS\Minidump\060522-9265-01.dmp (Minidump) |
| Bugcheck code: | 0x50(0xFFFFFFFFFFFFFFFF, 0x0, 0xFFFFF8054D6812F5, 0x2) |
| Bugcheck name: | PAGE_FAULT_IN_NONPAGED_AREA |
| Bug check description: | This indicates that invalid system memory has been referenced. This can be caused by a faulty driver. Antivirus software can also trigger this error, as can a corrupted NTFS volume. It can also be caused by faulty hardware, (in particular faulty or overheated RAM or video RAM) or an overheated system component. |
| Analysis: | This is likely a software problem which means that it was probably caused by a bug in a driver.
There is a possibility that this is caused by memory corruption. Memory corruption can be caused by a faulty driver, faulty RAM, overheating and more. Read this article on memory corruption. Read this article on thermal issues
|
| | |
On Sun 6/5/2022 8:31:48 AM your computer crashed or a problem was reported
| Crash dump file: | C:\WINDOWS\Minidump\060522-9062-01.dmp (Minidump) |
| Bugcheck code: | 0x3B(0xC000001D, 0xFFFFF8067D829B0B, 0xFFFFDB00BBFE2900, 0x0) |
| Bugcheck name: | SYSTEM_SERVICE_EXCEPTION |
| 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.
|
| | |
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:14 (h:mm:ss).
