Windows 10: BSOD on startup after upgrading (Bug check code: 0x00000139)

Hello!

Ever since I upgraded to Windows 10 in July, I've gotten one or more BSODs (KERNEL_SECURITY_CHECK_FAILURE) on practically every startup. I'll boot, log in, and start using the computer for about two minutes before I get a BSOD. It happens even if I'm not logged in as well. Most of the time, this will happen on multiple consecutive boots until it either stops for some reason, or Windows boots into its recovery options (only after three BSODs in a row). Interestingly enough, when I remain on the recovery screen for an extended period of time and reboot, I don't get the BSOD again and can boot successfully. The crashes are caused mostly by ntoskrnl.exe with occasional assistance from dxgkrnl.exe. As I understand, this error is caused by incompatible drivers, but I'm not quite sure how to approach the issue since both of those files appear to be system files (NT Kernel & DirectX). I've attached the necessary info below! Thanks!

Attachment 60452

:)

 

BSOD: IRQL_NOT_LESS_OR_EQUAL, SYSTEM_THREAD_NOT_HANDLED

Greetings,

last week i made some hardware changes to my laptop (lenovo z70-80). I installed a new ssd and upgraded my 4gb RAM to 16 gb RAM . The next day i experienced some BSOD errors (only at a cold startup, after the reboot of the system everything works just fine).
Most commonly the cause of BSOD was SYSTEM_THREAD_NOT_HANDLED and just lately the IRQL_NOT_LESS_OR_EQUAL. I post the info from the last BSOD as got from blue screen viewer :

Bug Check String;

IRQL_NOT_LESS_OR_EQUAL

Bug Check Code: 0x0000000a

Parameter1: 00000000`00060001

Parameter2: 00000000`000000ff

Parameter3: 00000000`00000000

Parameter4: fffff802`8266bf72

Caused by Driver: ntoskrnl.exe

Caused by Address: ntoskrnl.exe+16c580

File Description: NT Kernel & System

thanks in advance.

 

Kernel_Security_Check_Failure on Windows 10

I upgraded through the Windows 10 Update Launch

And the bug check was 0x00000139 (0x0000000000000003,0xffffd00033f8d710, 0xffffd00033f8d668, 0x0000000000000000). a dump was saved in C:\WINDOWS\MEMORY.DMP. Report Id: 111115-29640-01.

I get this error at random times, about 30 minutes after I turn it on. Sometimes longer and sometimes not for hours. It is really random.

 

The latest 7 dumpfiles were all bugcheck 0x139 with 2 of them mentioning
Code: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 139, {21, ffffd001bbaf8370, ffffd001bbaf82c8, 0} *** WARNING: Unable to verify timestamp for netr28ux.sys *** ERROR: Module load completed but symbols could not be loaded for netr28ux.sys Probably caused by : netr28ux.sys ( netr28ux+2af08 )[/quote] This the driver for
Driver Description: Ralink RT2870 series USB802.11n Wireless Adapter Driver (you may have a different manufacturer)
Driver Update Site: Broadband Wi-Fi
Please update to a windows 10 compatible version or uninstall/remove this device.
download here MediaTek - Semiconductor Technology and Cutting-Edge SoC

Your motherboard has no windows 10 driver on the intel site.


You have many more outdated driver/programs Please update to the latest windows 10 compatible versions
Coretemp
Avermedia livegamer C985
K9 parental webfilter
Logitech webcamera
Razar Devices
Speedfan
Splitmedialabs Xplit device
Intel management engine driver.
Airdisplay (not compatible with windows 10)

Please also start with SFC and/or DISM there are many mentions of windowsstorecorruption in your WER

SFC
Use SFC to checkand repair windows systemfiles.

See this tutorial http://www.eightforums.com/tutorials/3047-sfc-scannow-command-run-windows-8-a.html
Note
If SFC could not fix something, then run the command again to see if it may be able to the next time. Sometimes it may take running the sfc /scannow command 3 times restarting the PC after each time to completely fix everything that it's able to.

If not, then run the Dism /Online /Cleanup-Image/RestoreHealth command to repair any component store corruption, restart the PC afterwards,and try the sfc /scannow command again.