BSODs (KERNEL_SECURITY_CHECK_FAILURE) caused by ntoskrnl.exe, wdiwifi.sys

  • Thread starter Thread starter JCY95
  • Start date Start date
J

JCY95

Guest
Hey everyone, hope you can help me I've been having frequent BSODs after the May 2020 windows update failed installing

(Edit: 2020-06 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4560960) is also Install error - 0x800f0831)

Things I did to fix this

1. SFC /scannow - no errors

2. Uninstalled Throttlestop and MSI Afterburner, reset BIOS settings to default

3. Scanned and cleaned system using Malwarebytes


BSODs became less frequent afterwards, then had another one recently


Below are the error dumps


On Wed 6/10/2020 2:43:02 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\061020-14109-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0x139 (0x1D, 0xFFFF9885BEAD6060, 0xFFFF9885BEAD5FB8, 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 Wed 6/10/2020 2:43:02 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: wdiwifi.sys (wdiwifi!DllUnload+0x27B52)
Bugcheck code: 0x139 (0x1D, 0xFFFF9885BEAD6060, 0xFFFF9885BEAD5FB8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\drivers\wdiwifi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: WDI Driver Framework Driver
Bug check description: The kernel has detected the corruption of a critical data structure.
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.


Continue reading...
 

Similar threads

C
Replies
0
Views
8
Charles BAGUIDI-INTIA
C
A
Replies
0
Views
5
Aaron Ramirez2
A
Back
Top