BSOD due to ntoskrnl.exe and ntkrnlmp.exe (

Hi,
7f bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
139 bug check indicates that the kernel has detected the corruption of a critical data structure.
Probably some driver cause memory corruption. Determining the cause of this issues typically requires the use of the debugger to gather additional information or multiple dump files should be examined.

Please share all available dumps to OneDrive for analysis. Try to use driver verifier - https://support.microsoft.com/en-us/help/244617... - and share dumps it may create.

Hello Igor,

Thanks a lot for your answer, you can find the dump files on below URL(this is all I have, yesterday I installed clean windows again) 

Dump files: https://drive.google.com/drive/folders/1qA5KvuFogxHWZjNrVKb0jqIylzvNK6iF?usp=sharing

Verify system files with sfc /scannow command and check the results.

I did several times, nothing happened.

Now i configured Driver verifier and waiting for BSOD. I'll share dump files whenever I recieve.

Looks like the issue occurred due to Logitech driver. 

I've removed the driver and now looks everything okay, but still running verifier to be sure that there is no more driver issues.

Here is the dump files: That would be really great if you can check and comment to be sure there is no other issue. 

https://drive.google.com/drive/folders/1qA5KvuFogxHWZjNrVKb0jqIylzvNK6iF

Crash Dump Analysis

Crash dumps are enabled on your computer.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Fri 12.06.2020 01:09:37 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\061220-7515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDA20)
Bugcheck code: 0x7F (0x8, 0xFFFFA90028075E70, 0xFFFFF30BD45F6EF0, 0xFFFFF802795EB7D0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
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 the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also 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 12.06.2020 21:56:36 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\061220-4046-01.dmp
This was probably caused by the following module: verifierext.sys (VerifierExt+0x24501)
Bugcheck code: 0xC4 (0x2004, 0xFFFF8301421F9BA8, 0xFFFFF808485F01F0, 0xFFFF80852DF33210)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\WINDOWS\system32\drivers\verifierext.sys
product: Microsoft® Windows® İşletim Sistemi
company: Microsoft Corporation
description: Sürücü Doğrulayıcı Uzantısı
Bug check description: This is the general bug check code for fatal errors found by 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 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 12.06.2020 21:56:36 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: wmbenum.sys (0xFFFFF808485F01F0)
Bugcheck code: 0xC4 (0x2004, 0xFFFF8301421F9BA8, 0xFFFFF808485F01F0, 0xFFFF80852DF33210)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: wmbenum.sys .
Google query: wmbenum.sys DRIVER_VERIFIER_DETECTED_VIOLATION



On Fri 12.06.2020 20:51:51 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\061220-7125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDA20)
Bugcheck code: 0x139 (0x0, 0x0, 0x0, 0xFFF)
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 11.06.2020 23:43:39 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\061120-5906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDA20)
Bugcheck code: 0x139 (0x3, 0xFFFFBF8788BA2D30, 0xFFFFBF8788BA2C88, 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.

@Igor different issue started to occur. 

I've recieved below BSOD and also PUBG crashing(no BSOD just applicaiton crash) while i'm trying to play...

https://drive.google.com/file/d/1mR18LG7RFJoCHDaKyGz80ebOz0npmXR8/view?usp=sharing

On Fri 12.06.2020 22:32:17 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\061220-7234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDA20)
Bugcheck code: 0x192 (0xFFFF998691870080, 0xFFFFF803428482F8, 0x0, 0x0)
Error: KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL
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 lock tracked by AutoBoost was acquired while executing at DISPATCH_LEVEL or above.
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 Fri 12.06.2020 22:32:17 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: wdfilter.sys (WdFilter+0x34BBB)
Bugcheck code: 0x192 (0xFFFF998691870080, 0xFFFFF803428482F8, 0x0, 0x0)
Error: KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL
file path: C:\WINDOWS\system32\drivers\wdfilter.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft antimalware file system filter driver
Bug check description: This indicates that a lock tracked by AutoBoost was acquired while executing at DISPATCH_LEVEL or above.
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. 

Another BSOD...

https://drive.google.com/file/d/16cFDWF-fVA0css2obYg70s3l7Gf18MqM/view?usp=sharing

On Sat 13.06.2020 02:31:45 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!setjmpex+0x81B9)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80066E1F20A, 0xFFFFDB0CC766E630, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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. 

Update or at least reinstall Logitech WingMan software.

Run Windows Defender offline scan. If this will not help the problem may be in hardware. Please check a PV in service center.

Update or at least reinstall Logitech WingMan software.

Run Windows Defender offline scan. If this will not help the problem may be in hardware. Please check a PV in service center.