Windows 10: BSOD This was probably caused by the following module: ntoskrnl.exe nt+0x3F5780 Bugcheck...

Hi,

I'm currently having BSOD every time my pc is under intense gaming 3 hours

My cpu and gpu are both overclocked.
I have enough storage, all drivers are up to date.


CPU: i7-8700k w/ Corsair H115i AIO liquid cooler
GPU: Aorus RX 580
MOBO: Aorus Gaming 7
RAM: Corsair Dominator 32GB 4x8 3200mhz
PSU: Corsair tx750m
FANS: 4x120mm2 in, 1 out
SSD: 2 SSD 120gb, 250gb, m.2 1tb
HDD: 2TB Seagate





REPORT:

Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Sat 02/01/2021 23:39:07 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010221-11000-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x3F5780
Bugcheck code: 0x3B 0xC000001D, 0xFFFFF80075408060, 0xFFFFB402F1DCFE80, 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 Sat 02/01/2021 22:04:25 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010221-11671-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x3F5780
Bugcheck code: 0xA 0x28E57E60, 0xFF, 0xA0, 0xFFFFF8044FC08A12
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 02/01/2021 19:34:32 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010221-10718-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x3F5780
Bugcheck code: 0x3B 0xC0000005, 0xFFFFF802335FE180, 0xFFFFA70CE08FC8E0, 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 Sat 02/01/2021 19:33:06 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010221-10765-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x3F5780
Bugcheck code: 0xA 0x0, 0x2, 0x0, 0xFFFFF80505235711
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 02/01/2021 01:56:14 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010221-10828-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x3F5780
Bugcheck code: 0x3B 0xC0000005, 0xFFFFF8035DC650BC, 0xFFFFD5019B486920, 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.

:)

 

Crash probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)

Hi,

Am getting different type os errors since a few months and I was not able to find the root cause so far. Help is more then welcome.

Thank,

Mustafa

Crash Dump Analysis

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Fri 17-2-2017 18:47:49 your computer crashed

crash dump file: C:\WINDOWS\Minidump\021717-11281-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)

Bugcheck code: 0xC9 (0x6, 0x103, 0xFFFFDE831AF202E0, 0x0)

Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION


file path: C:\WINDOWS\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This is the bug check code for all Driver Verifier

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 13-2-2017 22:18:57 your computer crashed

crash dump file: C:\WINDOWS\Minidump\021317-11375-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)

Bugcheck code: 0xC9 (0x6, 0x103, 0xFFFFCD8AC4DCC2D0, 0x0)

Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION


file path: C:\WINDOWS\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This is the bug check code for all Driver Verifier

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 Thu 9-2-2017 01:00:34 your computer crashed

crash dump file: C:\WINDOWS\Minidump\020917-12515-01.dmp

This was probably caused by the following module: wdf01000.sys (Wdf01000+0xCCBF)

Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF803EEEF5D2C, 0xFFFFD301A09DC518, 0xFFFFD301A09DBD40)

Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

file path: C:\WINDOWS\system32\drivers\wdf01000.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: Kernel Mode Driver Framework Runtime

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 a standard 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 Sat 4-2-2017 00:34:11 your computer crashed

crash dump file: C:\WINDOWS\Minidump\020417-20687-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)

Bugcheck code: 0x1A (0x41792, 0xFFFF85BEFC8B9000, 0xE00800000000, 0x0)

Error: MEMORY_MANAGEMENT

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 severe memory management error occurred.

This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).

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 25-1-2017 12:31:51 your computer crashed

crash dump file: C:\WINDOWS\Minidump\012517-15546-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)

Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0x5C3, 0xDDA67A0, 0xFFFFC2808F6B6000)

Error: FAULTY_HARDWARE_CORRUPTED_PAGE

file path: C:\WINDOWS\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This bug check indicates that a single-bit error was found in this page. This is a hardware memory error.

This is likely to be caused by a hardware problem problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test).

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

Crash probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)

Hello David,

I have tried a lot like update bios / drivers but still errors as per below.

In the past I also run memtest for a whole night but without any errors found.

Your help is welcome.

Thanks,

Mustafa

System Information (local)

Computer name: TECRA

Windows version: Windows 10 , 10.0, build: 14393

Windows dir: C:\WINDOWS

Hardware: TECRA Z50-A, TOSHIBA

CPU: GenuineIntel Intel(R) Core(TM) i5-4200U CPU @ 1.60GHz Intel586, level: 6

4 logical processors, active mask: 15

RAM: 8511639552 bytes total



Crash Dump Analysis

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Tue 28-2-2017 19:58:15 your computer crashed

crash dump file: C:\WINDOWS\Minidump\022817-22109-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)

Bugcheck code: 0xC9 (0x6, 0x103, 0xFFFFAA8B1DB97720, 0x0)

Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION


file path: C:\WINDOWS\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This is the bug check code for all Driver Verifier

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 Sun 26-2-2017 22:29:31 your computer crashed

crash dump file: C:\WINDOWS\Minidump\022617-12000-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)

Bugcheck code: 0xC9 (0x6, 0x103, 0xFFFFCF03A3B9FA10, 0x0)

Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION


file path: C:\WINDOWS\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This is the bug check code for all Driver Verifier

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 Fri 17-2-2017 18:47:49 your computer crashed

crash dump file: C:\WINDOWS\Minidump\021717-11281-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)

Bugcheck code: 0xC9 (0x6, 0x103, 0xFFFFDE831AF202E0, 0x0)

Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION


file path: C:\WINDOWS\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This is the bug check code for all Driver Verifier

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.

 

BSOD caused by the following modules : win32kfull.sys ,ntoskrnl.exe

Hi,

It has been months since I'm getting different types of BSOD and I'm unable to solve this problem.

I would be grateful if you could help me with this issue.

Wael,

Crash dumps are enabled on your computer.

Crash dump directories:

C:\Windows

C:\Windows\Minidump

On Sat 12/10/2019 18:01:18 your computer crashed or a problem was reported

crash dump file: C:\Windows\Minidump\101219-8500-01.dmp

This was probably caused by the following module: win32kfull.sys (0xFFFFDFBF4D6D3FB4)

Bugcheck code: 0x3B (0xC0000005, 0xFFFFDFBF4D6D3FB4, 0xFFFFCE070AAEEBD0, 0x0)

Error: SYSTEM_SERVICE_EXCEPTION

file path: C:\Windows\system32\win32kfull.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: Full/Desktop Win32k Kernel Driver

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 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 Sat 12/10/2019 18:01:18 your computer crashed or a problem was reported

crash dump file: C:\Windows\MEMORY.DMP

This was probably caused by the following module: win32kfull.sys (0xFFFFDFBF4D6D3FB4)

Bugcheck code: 0x3B (0xC0000005, 0xFFFFDFBF4D6D3FB4, 0xFFFFCE070AAEEBD0, 0x0)

Error: SYSTEM_SERVICE_EXCEPTION

file path: C:\Windows\system32\win32kfull.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: Full/Desktop Win32k Kernel Driver

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 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 Sat 12/10/2019 17:29:16 your computer crashed or a problem was reported

crash dump file: C:\Windows\Minidump\101219-8125-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1220)

Bugcheck code: 0xA (0xFFFFFFFEFFFFFFF8, 0x2, 0x0, 0xFFFFF80309842B74)

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 12/10/2019 15:02:52 your computer crashed or a problem was reported

crash dump file: C:\Windows\Minidump\101219-11125-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1220)

Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8045381DEF8, 0x1, 0x0)

Error: KMODE_EXCEPTION_NOT_HANDLED

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 program generated an exception which the error handler did not catch.

This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.

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 10/10/2019 23:17:49 your computer crashed or a problem was reported

crash dump file: C:\Windows\Minidump\101019-11171-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1220)

Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80476E33054, 0xFFFFA78932CD6C40, 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 09/10/2019 21:56:40 your computer crashed or a problem was reported

crash dump file: C:\Windows\Minidump\100919-11187-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1220)

Bugcheck code: 0x1A (0x403, 0xFFFF8D8AF45C5920, 0x81000001D0669867, 0xFFFF8D8AF41B5920)

Error: MEMORY_MANAGEMENT

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 severe memory management error occurred. The page table and PFNs are out of sync . This is probably a hardware error, especially if parameters 3 & 4 differ by only a single bit.

This is likely to be caused by a hardware problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test) and make sure your system is not getting overheated. This problem
might also be caused because of overheating (thermal issue).

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.