So ever since the 20th of October i've been getting bsod's constantly only in normal mode never in safe mode.
Things i've tried
sfc scannow
memtest 86
reinstalling windows
reverting gpu drivers and updating them
re seating ram
however obviously like most things pc related it doesnt work or has not helped.
I have a screen dump off the bsod's im getting so if someone can point out what is causing that would be amazing thank you
https://www.mediafire.com/file/67ibf0x30hbf0p4/WhoCrashedOutput.htm/file
just incase link doesn't work
Things i've tried
sfc scannow
memtest 86
reinstalling windows
reverting gpu drivers and updating them
re seating ram
however obviously like most things pc related it doesnt work or has not helped.
I have a screen dump off the bsod's im getting so if someone can point out what is causing that would be amazing thank you
https://www.mediafire.com/file/67ibf0x30hbf0p4/WhoCrashedOutput.htm/file
just incase link doesn't work
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Wed 08/12/2021 12:39:08 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\120821-20875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F71B0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8041E363C1B, 0xFFFF8B081EBB8728, 0xFFFF8B081EBB7F60)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread generated an exception which the error handler did not catch.
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 Wed 08/12/2021 12:39:08 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: wof.sys (Wof+0x21474)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8041E363C1B, 0xFFFF8B081EBB8728, 0xFFFF8B081EBB7F60)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\wof.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Windows Overlay Filter
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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 Wed 08/12/2021 12:08:50 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\120821-27750-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F71B0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80547E745C6, 0xFFFFC701C15F8920, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Wed 08/12/2021 11:00:30 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\120821-22093-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F71B0)
Bugcheck code: 0xA (0x170, 0xD, 0x0, 0xFFFFF8031AE166CB)
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.
On Tue 07/12/2021 22:11:02 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\120721-31921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F71B0)
Bugcheck code: 0x139 (0x3, 0xFFFFF80050C91700, 0xFFFFF80050C91658, 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 07/12/2021 21:08:04 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\120721-24437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F71B0)
Bugcheck code: 0x18 (0x0, 0xFFFFA086B25CA460, 0x2, 0xFFFFFFFFFFFFFFFF)
Error: REFERENCE_BY_POINTER
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 the reference count of an object is illegal for the current state of the object.
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.
Conclusion
6 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Wed 08/12/2021 12:39:08 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\120821-20875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F71B0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8041E363C1B, 0xFFFF8B081EBB8728, 0xFFFF8B081EBB7F60)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread generated an exception which the error handler did not catch.
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 Wed 08/12/2021 12:39:08 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: wof.sys (Wof+0x21474)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8041E363C1B, 0xFFFF8B081EBB8728, 0xFFFF8B081EBB7F60)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\wof.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Windows Overlay Filter
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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 Wed 08/12/2021 12:08:50 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\120821-27750-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F71B0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80547E745C6, 0xFFFFC701C15F8920, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Wed 08/12/2021 11:00:30 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\120821-22093-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F71B0)
Bugcheck code: 0xA (0x170, 0xD, 0x0, 0xFFFFF8031AE166CB)
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.
On Tue 07/12/2021 22:11:02 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\120721-31921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F71B0)
Bugcheck code: 0x139 (0x3, 0xFFFFF80050C91700, 0xFFFFF80050C91658, 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 07/12/2021 21:08:04 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\120721-24437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F71B0)
Bugcheck code: 0x18 (0x0, 0xFFFFA086B25CA460, 0x2, 0xFFFFFFFFFFFFFFFF)
Error: REFERENCE_BY_POINTER
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 the reference count of an object is illegal for the current state of the object.
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.
Conclusion
6 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
Last edited by a moderator: