U
understandably
Here are the bugchecks
On Sat 2/6/2021 3:57:05 PM
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: 0xD1 (0x1, 0x2,
0x8, 0x1)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path:
C:\WINDOWS\system32\win32kbase.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Base Win32k
Kernel Driver
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 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.
On
Fri 2/5/2021 6:38:16 PM your computer crashed or a problem was
reported
crash dump file: C:\WINDOWS\Minidump\020521-6578-01.dmp
This
was probably caused by the following module: fltmgr.sys (0xFFFFF80470041E55)
Bugcheck code: 0x50
(0xFFFFA703A77FFFE5, 0x0, 0xFFFFF80470041E55, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path:
C:\WINDOWS\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft
Filesystem Filter Manager
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 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.
On Wed 2/3/2021 2:09:47 PM your computer
crashed or a problem was reported
crash dump file:
C:\WINDOWS\Minidump\020321-6328-01.dmp
This was probably caused by the
following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0x139
(0x3, 0xFFFF828379E92750, 0xFFFF828379E926A8, 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 Fri 1/29/2021 11:56:13 PM your computer crashed or
a problem was reported
crash dump file:
C:\WINDOWS\Minidump\012921-6484-01.dmp
This was probably caused by the
following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0x139
(0x3, 0xFFFFF0835B6E6190, 0xFFFFF0835B6E60E8, 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 Thu 1/28/2021 5:39:12 PM your computer crashed or
a problem was reported
crash dump file:
C:\WINDOWS\Minidump\012821-6515-01.dmp
This was probably caused by the
following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0xFC
(0xFFFFE301AA270128, 0x8A0000012C6009E3, 0xFFFFB40FBB124470, 0x3)
Error:
ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
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 an attempt was made to
execute non-executable memory.
This may be a case of memory corruption. More
often memory corruption happens because of software errors in buggy drivers, not
because of faulty RAM modules. Memory corruption can also occur because of
overheating (thermal issue). There is a possibility this problem was caused by a
virus or other malware.
The crash took place in the Windows kernel. Possibly
this problem is caused by another driver that cannot be identified at this time.
Continue reading...
On Sat 2/6/2021 3:57:05 PM
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: 0xD1 (0x1, 0x2,
0x8, 0x1)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path:
C:\WINDOWS\system32\win32kbase.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Base Win32k
Kernel Driver
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 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.
On
Fri 2/5/2021 6:38:16 PM your computer crashed or a problem was
reported
crash dump file: C:\WINDOWS\Minidump\020521-6578-01.dmp
This
was probably caused by the following module: fltmgr.sys (0xFFFFF80470041E55)
Bugcheck code: 0x50
(0xFFFFA703A77FFFE5, 0x0, 0xFFFFF80470041E55, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path:
C:\WINDOWS\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft
Filesystem Filter Manager
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 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.
On Wed 2/3/2021 2:09:47 PM your computer
crashed or a problem was reported
crash dump file:
C:\WINDOWS\Minidump\020321-6328-01.dmp
This was probably caused by the
following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0x139
(0x3, 0xFFFF828379E92750, 0xFFFF828379E926A8, 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 Fri 1/29/2021 11:56:13 PM your computer crashed or
a problem was reported
crash dump file:
C:\WINDOWS\Minidump\012921-6484-01.dmp
This was probably caused by the
following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0x139
(0x3, 0xFFFFF0835B6E6190, 0xFFFFF0835B6E60E8, 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 Thu 1/28/2021 5:39:12 PM your computer crashed or
a problem was reported
crash dump file:
C:\WINDOWS\Minidump\012821-6515-01.dmp
This was probably caused by the
following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0xFC
(0xFFFFE301AA270128, 0x8A0000012C6009E3, 0xFFFFB40FBB124470, 0x3)
Error:
ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
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 an attempt was made to
execute non-executable memory.
This may be a case of memory corruption. More
often memory corruption happens because of software errors in buggy drivers, not
because of faulty RAM modules. Memory corruption can also occur because of
overheating (thermal issue). There is a possibility this problem was caused by a
virus or other malware.
The crash took place in the Windows kernel. Possibly
this problem is caused by another driver that cannot be identified at this time.
Continue reading...