BSOD, KERNEL_SECURITY_CHECK_FAILURE

Hi all,

i have had my pc for around 2/3 months now, and just recently i have been getting a BSOD very often; whenever i am playing a steam game on my PC. The error message that comes up is KERNEL_SECURITY_CHECK_FAILURE. I have looked in event viewer and in sync with the BSOD's are 8 warningsalong the lines of "processor x in group x has reduced processing power and has been like this for 71 seconds".

I have a link to my three most recent dump files from C:/Windows/minidump --> https://1drv.ms/u/s!AjlixJub_TV7gXVF7Mpbxf4-SPLR

I have tried most of the things that have come up in other forums.

If it means anything i have an MSI laptop, running Windows 10. 

Harry

What is your computer make and model? If not a branded computer what is your motherboard make and model?

 

Please download and run Driver View and upload a copy of the report it produces to your OneDrive. To get a report on all drivers select Edit, Select All followed by File, Save Selected Items. Text file format please.

http://www.nirsoft.net/utils/driverview.html

 

Please provide a copy of your System Information file. To access your System Information file select the keyboard shortcut Win+R, type msinfo32 and press the ENTER key. Select File, Export and give the file a name noting where it is located. Do not place the cursor within the body of the report before exporting the file. The system creates a new System Information file each time system information is accessed. You need to allow a minute or two for the file to be fully populated before exporting a copy. Please upload the file to your OneDrive, share with everyone and post a link here.

 

For help with OneDrive see paragraph 9.3:

http://www.gerryscomputertips.co.uk/MicrosoftCommunity1.htm

Gerry
Stourport-on-Severn, Worcestershire, England
Enquire Plan Execute

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hi,

Be sure you are running the latest available BIOS, chipset drivers, and major
drivers. That error can also be caused by incompatible 3rd party antivirus
and other startup programs and drivers. Of course there are other possibilities.

Troubleshoot blue screen errors
http://windows.microsoft.com/en-us/windows-10/troubleshoot-blue-screen-errors

BugCheck 139, {3, ffffd0007cfa49f0, ffffd0007cfa4948, 0}

Probably caused by : dc1-controller.sys ( dc1_controller!DccRemoveRequestQueue+7e )

dc1-controller.sys is a Windows component which means something else drove it into
Fault.

1. Check with MSI Support, their on-line documentation and drivers, and ask in their
forums about any known issues. Update the BIOS, chipset drivers, and the major
on-board and separate device drivers (see driver update methods below). Especially
update the network and video drivers.


BiosVersion = E1775IMS.10B
BiosReleaseDate = 09/17/2015
SystemManufacturer = Micro-Star International Co., Ltd.
SystemProductName = GS70 6QE
SystemVersion = REV:1.0
SystemSKU = Default string
BaseBoardManufacturer = Micro-Star International Co., Ltd.
BaseBoardProduct = MS-1775
BaseBoardVersion = REV:1.0

MSI Support
http://www.msi.com/index.php?func=service

MSI - Downloads (BIOS and Drivers)
http://www.msi.com/index.php?func=downloadindex


MSI - Forums
http://forum-en.msi.com/


MSI - Service
http://us.msi.com/index.php?func=service

MSI - Live Update On-Line
http://www.msi.com/index.php?func=downloadindex

MSI - Contacts - Set to North America - USA
http://www.msi.com/index.php?func=html&name=aboutus


2. Check with Steam Support and Forums about known issues.

3. Uninstall Norton/Symantec which has been known to be involved is such issues. Use
Windows Defender which in Windows 8/8.1 & 10 is a full antivirus. Despite all the hype
WD and the Windows Firewall offer superior protection and compatibility.

4. Use ALL the methods in the troubleshooters below.

5. If needed run Driver Verifier to see if it can indicate a CAUSE (see Driver Verifier methods below).

=========================================================

Check these resources :

BCCode: 139  0x00000139 <-- read this link
http://www.faultwire.com/solutions-fatal_error/KERNEL-SECURITY-CHECK-FAILURE-0x00000139-*1346.html?order=votes

Bug Check 0x139 KERNEL_SECURITY_CHECK_FAILURE Parameters <- read this link
http://msdn.microsoft.com/en-us/library/jj569891(v=vs.85).aspx

====================================================
 
This is my generic how to for proper driver updates :

This utility makes it easy to see which versions are loaded : Run DriverView - set
VIEW to Hide Microsoft drivers - update those without Dump in their names (and
BIOS and chipset drivers).

DriverView - Free - utility displays the list of all device drivers currently loaded
on your system. For each driver in the list, additional useful information is
displayed: load address of the driver, description, version, product name,
company that created the driver, and more.
http://www.nirsoft.net/utils/driverview.html

For Drivers check System Maker as fallbacks and Device Maker's which are the  

most current. Control Panel - Device Manager - Display Adapter - write down 
the make and complete model of your video adapter - double click - Driver's tab -
write down the version info. Now click UPdate Driver (this may not do anything
as MS is far behind certifying drivers) - then Right Click - Uninstall - REBOOT this
will refresh the driver stack.

Repeat that for Network - Network Card (NIC), Wifi, Sound, Mouse and Keyboard
if 3rd party with their own software and drivers and any other major device drivers
you have.

Now go to System Maker's site (Dell, HP, Toshiba as examples) (as rollback) and
then Device  Maker's site (Realtek, Intel, Nvidia, ATI as examples) and get their
latest versions. (Look for BIOS, Chipset and software updates at System Maker's
site while there.)

Download - SAVE - go to where you put them - Right Click - RUN AD ADMIN -
REBOOT after each installation.

Always check in Device Manager - Drivers tab to be sure the version you are
installing actually shows up. This is because some drivers rollback before the
latest is installed (sound drivers  particularly do this) so install a driver - reboot -
check to be sure it is installed and repeat as needed.

Repeat at Device Makers - BTW at Device Makers DO NOT RUN THEIR SCANNER
- check manually by model.

Manually look at manufacturer's sites for drivers - and Device Maker's sites.
http://pcsupport.about.com/od/driverssupport/ht/driverdlmfgr.htm
 ___________________________________________________________________________________


After doing ALL the updates you can, and if the issue continues, then run
DriverVerifier. 

Driver Verifier can help find some BSOD issues :

Using Driver Verifier to identify issues with Windows drivers for advanced users
http://support.microsoft.com/kb/244617

How To Troubleshoot Driver Problems in Windows Vista or 7. ((8/8.1 and 10
are essemtially the same).
http://www.winvistaclub.com/t79.html

Using Driver Verifier
http://msdn.microsoft.com/en-us/library/ff554113(v=VS.85).aspx

How to use Windows Driver Verifier Manager to Troubleshoot & Identify Driver Issues
http://www.youtube.com/watch?v=_VwIDD9xngM


Driver Verifier
http://www.techsupportforum.com/2110308-post3.html

Using Driver Verifier
http://www.faultwire.com/solutions/using_driver_verifier.php

You can disable Driver Verifier
http://support.microsoft.com/kb/244617

WINKEY + X - RUN - type in -> verifier /reset      hit enter to disable

Use BlueScreenView to see if there is a driver specified in the error message.
Also check with MyEventViewer at the time of the BlueScreen.

If Driver Verifier creates a minidump upload it and post the link here so we
can analyze it.


Hope this helps.
--------------------------------------------------------------------------------------------
Rob Brown - Microsoft MVP <- profile - Windows and Devices for IT : Bicycle - Mark Twain said it right.

Rob Brown - past Microsoft MVP - Windows Insider MVP 2016 - 2021
Microsoft MVP Windows and Devices for IT 2009 - 2020

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Gerry,

thanks for the fast response.

My driver viewer data is here - https://1drv.ms/t/s!AjlixJub_TV7gXayoF1iBRdHNF1b

My system info is here - https://1drv.ms/t/s!AjlixJub_TV7gXfXP0h_iMz7AC2C

I couldn't determine the motherboard model.

thanks,

Harry

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Probably caused by : dc1-controller.sys ( dc1_controller!DccRemoveRequestQueue+7e )

dc1-controller.sys is your x-box controller

See the thread linked below, especially JesseW_4's post.

http://answers.microsoft.com/en-us/windows/forum/windows_10-performance/just-installed-a-new-motherboard-memory-and-cpu-i/5cbcd0fc-6401-4b58-824c-085205ffddc5

Take time to let us know if the suggestion worked...or not.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I have realised that as soon as i connected my headset to the controller, and then to the PC via USB, i started to get these crashes. The reason why the headset is connected to the controller then the pc is because the only way the microphone will work on the headset is if it is connected via usb, and connecting the controller was the easiest way to fix this

thanks

Harry

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Have the crashes stopped now?
Take time to let us know if the suggestion worked...or not.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

 
 

Question Info


Last updated April 30, 2020 Views 2,190 Applies to: