Hello everybody,
I've been facing these BSOD problems for months now and I've tried my best to fix them on my own but no good. Does not crash at all when playing video games and during discord calls... I don't know why, zoom and skype just crash within 15mins.
PC spec:
Ryzen 7 2700x
Gigabyte b450 aorus pro wifi rev1
GTX 1060 6gb
ddr4 16GB RAM
650 watt PSU
On Sat 19-06-2021 02:08:27 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061921-14843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F6C20)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF807270858F1, 0xFFFFBD841BF9A918, 0xFFFFBF805298F920)
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 Sat 19-06-2021 02:08:27 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!memset+0x78DE)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF807270858F1, 0xFFFFBD841BF9A918, 0xFFFFBF805298F920)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 19-06-2021 01:43:28 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061921-13421-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F6C20)
Bugcheck code: 0xA (0x1, 0xFF, 0x1, 0xFFFFF806628087B3)
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 Sat 19-06-2021 12:35:33 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061921-19062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F6C20)
Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
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 Sat 19-06-2021 12:30:06 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061921-8750-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F6C20)
Bugcheck code: 0xA (0xA, 0x2, 0x0, 0xFFFFF80583824CFD)
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.
Things I did to find and fix the problem:
sfc /scannow - sometimes it's clean (Windows resource protection did not find any integrity violations.) but sometimes it says
"Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the
CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log." , then I'll do the DISM /Online
/Cleanup-Image /RestoreHealth and run the scan again and clean results.
memtest - I've done both the normal and extensive tests and found nothing bad.
Driver verifier - I followed this article. Did not check ntoskrnl.exe as the author told not to check any microsoft related drivers.
Reset PC - did using cloud download and external USB flash.
Checked my SSD and HDD using CrystalDiskInfo and got clean results.
https://1drv.ms/u/s!AuTTVAjTMfxLliV4PZExN_5-YAFo?e=ASSMZ0 these are the dumpfiles.
Any help is appreciated.
I've been facing these BSOD problems for months now and I've tried my best to fix them on my own but no good. Does not crash at all when playing video games and during discord calls... I don't know why, zoom and skype just crash within 15mins.
PC spec:
Ryzen 7 2700x
Gigabyte b450 aorus pro wifi rev1
GTX 1060 6gb
ddr4 16GB RAM
650 watt PSU
On Sat 19-06-2021 02:08:27 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061921-14843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F6C20)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF807270858F1, 0xFFFFBD841BF9A918, 0xFFFFBF805298F920)
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 Sat 19-06-2021 02:08:27 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!memset+0x78DE)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF807270858F1, 0xFFFFBD841BF9A918, 0xFFFFBF805298F920)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 19-06-2021 01:43:28 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061921-13421-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F6C20)
Bugcheck code: 0xA (0x1, 0xFF, 0x1, 0xFFFFF806628087B3)
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 Sat 19-06-2021 12:35:33 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061921-19062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F6C20)
Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
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 Sat 19-06-2021 12:30:06 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061921-8750-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F6C20)
Bugcheck code: 0xA (0xA, 0x2, 0x0, 0xFFFFF80583824CFD)
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.
Things I did to find and fix the problem:
sfc /scannow - sometimes it's clean (Windows resource protection did not find any integrity violations.) but sometimes it says
"Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the
CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log." , then I'll do the DISM /Online
/Cleanup-Image /RestoreHealth and run the scan again and clean results.
memtest - I've done both the normal and extensive tests and found nothing bad.
Driver verifier - I followed this article. Did not check ntoskrnl.exe as the author told not to check any microsoft related drivers.
Reset PC - did using cloud download and external USB flash.
Checked my SSD and HDD using CrystalDiskInfo and got clean results.
https://1drv.ms/u/s!AuTTVAjTMfxLliV4PZExN_5-YAFo?e=ASSMZ0 these are the dumpfiles.
Any help is appreciated.