S
SidFou
Hi all,
I have been facing some BSOD errors for quite some time now, have tried multiple things but nothing worked for me so far. The errors are random and occur with no pattern they are not frequent but I face them maybe twice a week randomly. I tried installing WhoCrashed to check what is causing the problem but it seems it cant point me in the right direction. following are the analysis of some recent errors. I will also be attaching a system log file at the bottom of this
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Fri 1/8/2021 10:20:00 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010821-9750-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0xEF (0xFFFFCC8C64F8D080, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
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 critical system process died.
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.
On Fri 1/8/2021 10:20:00 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntdll.sys (ntdll!NtTerminateProcess+0x14)
Bugcheck code: 0xEF (0xFFFFCC8C64F8D080, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
Bug check description: This indicates that a critical system process died.
There is a possibility this problem was caused by a virus or other malware.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ntdll.sys .
Google query: ntdll.sys CRITICAL_PROCESS_DIED
On Mon 1/4/2021 7:16:42 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010421-6328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0x139 (0x4, 0xFFFFF8061E281010, 0xFFFFF8061E280F68, 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/1/2021 4:46:16 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010121-10890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0x1 (0x7FFEDEF6C1D4, 0x0, 0xFFFF, 0xFFFFDE0CEDBF9B80)
Error: APC_INDEX_MISMATCH
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 there has been a mismatch in the APC state index.
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 Mon 12/28/2020 11:36:34 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\122820-5875-01.dmp
This was probably caused by the following module: fltmgr.sys (0xFFFFF80373D5443E)
Bugcheck code: 0x50 (0xFFFFCD014D187968, 0x0, 0xFFFFF80373D5443E, 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 Thu 12/24/2020 9:13:59 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\122420-7328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0xA (0xFFFFF10285A4CA40, 0x2, 0x0, 0xFFFFF8033960D05C)
Error: 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
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.
OneDrive link to the system logs: eventvwrSystemFiles.evtx
Continue reading...
I have been facing some BSOD errors for quite some time now, have tried multiple things but nothing worked for me so far. The errors are random and occur with no pattern they are not frequent but I face them maybe twice a week randomly. I tried installing WhoCrashed to check what is causing the problem but it seems it cant point me in the right direction. following are the analysis of some recent errors. I will also be attaching a system log file at the bottom of this
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Fri 1/8/2021 10:20:00 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010821-9750-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0xEF (0xFFFFCC8C64F8D080, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
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 critical system process died.
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.
On Fri 1/8/2021 10:20:00 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntdll.sys (ntdll!NtTerminateProcess+0x14)
Bugcheck code: 0xEF (0xFFFFCC8C64F8D080, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
Bug check description: This indicates that a critical system process died.
There is a possibility this problem was caused by a virus or other malware.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ntdll.sys .
Google query: ntdll.sys CRITICAL_PROCESS_DIED
On Mon 1/4/2021 7:16:42 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010421-6328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0x139 (0x4, 0xFFFFF8061E281010, 0xFFFFF8061E280F68, 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/1/2021 4:46:16 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010121-10890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0x1 (0x7FFEDEF6C1D4, 0x0, 0xFFFF, 0xFFFFDE0CEDBF9B80)
Error: APC_INDEX_MISMATCH
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 there has been a mismatch in the APC state index.
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 Mon 12/28/2020 11:36:34 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\122820-5875-01.dmp
This was probably caused by the following module: fltmgr.sys (0xFFFFF80373D5443E)
Bugcheck code: 0x50 (0xFFFFCD014D187968, 0x0, 0xFFFFF80373D5443E, 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 Thu 12/24/2020 9:13:59 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\122420-7328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0xA (0xFFFFF10285A4CA40, 0x2, 0x0, 0xFFFFF8033960D05C)
Error: 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
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.
OneDrive link to the system logs: eventvwrSystemFiles.evtx
Continue reading...