BSOD – 0x139 KERNEL_SECURITY_CHECK_FAILURE

A Kernel can be termed as one of the most critical part of an operating system.

It enjoys control over every operation and task that you request Windows to perform. At times, things may go wrong and you may land up with the BSOD – 0x139 KERNEL_SECURITY_CHECK_FAILURE error.

 

Recommended Act

Besides ticking all the checkboxes for applying the changes and modifications suggested below, use a system optimizer to sweep away all the junk as well as sort and defrag the Windows Registry. The combined result of both of these steps will result in a more stable and faster computer that will be a lot less prone to be affected by sudden crashes like the Blue Screen Of Death (BSOD). One such program that can help accomplish all of this is RegInOut System Utilities.

 

Change Virtual Memory Size

Page Swapping feature, a part of memory management of your computer, extends the amount of memory available on specific occasions when required. The feature uses a swap file to create a temporary storage on your HDD instead of storing data onto the RAM. Make sure your computer is not set to use the default page size allocation. Manually change the paging size as follows:

  1. Press Windows Key + X; choose System.
  2. Click Advanced system settings.
  3. Click Advanced > Settings (Performance).
  4. Click Advanced.
  5. Click Change (Virtual Memory).
  6. Disable default paging file allocation. Uncheck the box labelled Automatically manage paging file size for all drives.
  7. Select the drive containing Windows installation, typically C:\, and then select Custom size option.
  8. Specify Initial Size (MB) and Maximum Size (MB).
  9. Click Set.
  10. Click OK thrice, and then reboot.

 

Add an Exception to your Firewall Protection

You might want to add the application that shows the BSOD – 0x139 KERNEL_SECURITY_CHECK_FAILURE error to the Windows Firewall or third-party firewall security software’s exception list.

  1. Right-click the Kaspersky Internet Security program icon in the System Tray area of the Taskbar.
  2. Select Settings.
  3. Click the Protection tab.
  4. Click Firewall icon.
  5. Click Configure application rules link.
  6. You will see the Application Network Rules dialog on your screen with four main nodes namely Trusted, Low Restricted, High Restricted and Unrestricted.
  7. Expand the Trusted node.
  8. Right-click the Trusted node and select Add application to group.
  9. You’ll be prompted to browse and locate the Executable File (.exe) you intend to exclude from the Firewall protection.
  10. Locate the appropriate file, click Open.
  11. Finally, close the dialog.

 

Use Microsoft Hotfix

Microsoft rolled out an update that automatically fixes this problem. Here’s how:

  1. Visit the Microsoft Download Center to obtain Windows Update KB3055343.
  2. Execute the downloaded update installation file to complete the installation.

 

Uninstall Faulty Asus Utility

Asus Utility provides an all-in-one interface to access several Asus features. Several users have complained about the compatibility issues due to shared app components and internal conflicts.

  1. Press Windows Key + X; choose Programs and Features.
  2. This will bring up the list of all installed apps. Search and uninstall the following product(s):
    • Asus ATK0110 ACPI Utility
    • Asus PCProbe
    • AISuite Utilities
  3. Reboot your laptop/ computer.

 

Restore Verifier Defaults

Reset the Driver Verifier defaults through a command-line given below:

  1. Press Windows Key + X; choose Command Prompt (Admin).
  2. Execute the following commands:
    • verifier /reset
    • Exit

 

Get Updated Version of ASACPI.SYS

Older versions of ASACPI.SYS cause this error. Fire up the File Properties dialog box, check current version and update it, if required.

  1. Double-click This PC icon on the Desktop.
  2. Navigate to the following location: C:\Windows\System32\Drivers
  3. Right-click ASACPI.SYS and choose Properties.
  4. Make sure that the date of creation isn’t earlier than 2009. If the file creation date is, for example 2008, you might want to rename the old file as ASACPI.SYS.OLD and obtain an updated copy online.