Computer name: | DESKTOP-52EVVHP |
Windows version: | Windows 11, 10.0, version 2009, build: 22621 (x64) |
Windows dir: | C:\Windows |
Hardware: | ASUS TUF Gaming A17 FA706IU_FX706IU, ASUSTeK COMPUTER INC., FA706IU |
CPU: | AuthenticAMD AMD Ryzen 7 4800H with Radeon Graphics 8664, level: 23 |
Processor count: | 16 logical processors, active mask: 65535 |
RAM: | 15789,7MB |
Crash dump file: | C:\Windows\Minidump\013023-8890-01.dmp (Minidump) |
Bugcheck code: | 0xA(0x2, 0x2, 0x1, 0xFFFFF8065ECCC1A4) |
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. |
Crash dump file: | C:\Windows\MEMORY.DMP (Kernel memory dump) |
Bugcheck code: | 0xA(0x2, 0x2, 0x1, 0xFFFFF8065ECCC1A4) |
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. |
Crash dump file: | C:\Windows\Minidump\012923-8921-01.dmp (Minidump) |
Bugcheck code: | 0xA(0x24, 0xFF, 0x0, 0xFFFFF80138027E45) |
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. |
Crash dump file: | C:\Windows\Minidump\012923-8781-02.dmp (Minidump) |
Bugcheck code: | 0xA(0x2, 0x2, 0x1, 0xFFFFF8025C4CC3F4) |
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. |
Crash dump file: | C:\Windows\Minidump\012923-8734-01.dmp (Minidump) |
Bugcheck code: | 0x1E(0xFFFFFFFFC000001D, 0xFFFFF8016CC2EBF1, 0xFFFFFFFFFFFFFFFF, 0xFFFFFD8E3514F500) |
Bugcheck name: | KMODE_EXCEPTION_NOT_HANDLED |
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 |