AMIRREZA
2021-05-13T08:37:51+00:00
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Tue 2021/5/18 5:49:38 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\051821-5234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F6CF0)
Bugcheck code: 0xE3 (0xFFFFE7862FB82E10, 0xFFFFE7862FAAA080, 0xFFFFE78632B7C670, 0x2)
Error: RESOURCE_NOT_OWNED
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 thread tried to release a resource it did not own.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 2021/5/18 5:26:52 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\051821-4703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F6CF0)
Bugcheck code: 0x139 (0x3, 0xFFFFDD89388ED5F0, 0xFFFFDD89388ED548, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft? Windows? Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 2021/5/18 5:09:37 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\051821-4484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F6CF0)
Bugcheck code: 0x50 (0xFFFFFFFFEE1E5D00, 0x0, 0xFFFFF80060D5FEDE, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 2021/5/18 5:49:38 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: win32kbase.sys (win32kbase!UserSessionSwitchLeaveCrit+0x74)
Bugcheck code: 0xE3 (0xFFFFE7862FB82E10, 0xFFFFE7862FAAA080, 0xFFFFE78632B7C670, 0x2)
Error: RESOURCE_NOT_OWNED
file path: C:\Windows\system32\win32kbase.sys
product: Microsoft? Windows? Operating System
company: Microsoft Corporation
description: 基 Win32k 内核驱动程序
Bug check description: This indicates that a thread tried to release a resource it did not own.
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.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Tue 2021/5/18 5:49:38 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\051821-5234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F6CF0)
Bugcheck code: 0xE3 (0xFFFFE7862FB82E10, 0xFFFFE7862FAAA080, 0xFFFFE78632B7C670, 0x2)
Error: RESOURCE_NOT_OWNED
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 thread tried to release a resource it did not own.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 2021/5/18 5:26:52 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\051821-4703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F6CF0)
Bugcheck code: 0x139 (0x3, 0xFFFFDD89388ED5F0, 0xFFFFDD89388ED548, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft? Windows? Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 2021/5/18 5:09:37 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\051821-4484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F6CF0)
Bugcheck code: 0x50 (0xFFFFFFFFEE1E5D00, 0x0, 0xFFFFF80060D5FEDE, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 2021/5/18 5:49:38 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: win32kbase.sys (win32kbase!UserSessionSwitchLeaveCrit+0x74)
Bugcheck code: 0xE3 (0xFFFFE7862FB82E10, 0xFFFFE7862FAAA080, 0xFFFFE78632B7C670, 0x2)
Error: RESOURCE_NOT_OWNED
file path: C:\Windows\system32\win32kbase.sys
product: Microsoft? Windows? Operating System
company: Microsoft Corporation
description: 基 Win32k 内核驱动程序
Bug check description: This indicates that a thread tried to release a resource it did not own.
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.