Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Mon 23/11/2020 19:41:57 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\LiveKernelReports\PoW32kWatchdog-20201123-1941.dmp
This was probably caused by the following module:
ntkrnlmp.exe (nt!IoUnregisterShutdownNotification+0xBEE)
Bugcheck code: 0x1A1 (0xFFFF988FF48EC040, 0x0, 0x0, 0x0)
Error:
CUSTOM_ERROR
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 16/11/2020 22:44:42 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111620-16375-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x1C3B20)
Bugcheck code: 0xD1 (0xFFFFF805275CAF2E, 0x2, 0x8, 0xFFFFF805275CAF2E)
Error:
DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product:
Microsoft® Windows® Operating System
company:
Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 15/11/2020 18:18:18 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111520-14250-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x1C3B20)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8055D49BE82, 0x0, 0xFFFFFFFFFFFFFFFF)
Error:
KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product:
Microsoft® Windows® Operating System
company:
Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 28/09/2020 13:22:22 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\092820-9890-01.dmp
This was probably caused by the following module:
dxgkrnl.sys (dxgkrnl+0x40F25)
Bugcheck code: 0x100000EA (0xFFFFA78CC2EB9080, 0x0, 0x0, 0x0)
Error:
THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys
product:
Microsoft® Windows® Operating System
company:
Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
The following dump files were found but could not be read. These files may be corrupted:
C:\WINDOWS\LiveKernelReports\PoW32kWatchdog-20201022-2022.dmp