BSOD Witcher 3: Wild Hunt KERNEL_SECURITY_CHECK_FAILURE

First few hours played beautifully, but not I can't load the game up without it causing a BSOD. I ran WhoCrashed and there are the results. One of the failures are a DRIVER_POWER_STATE_FAILURE, but most were the KERNEL_SECURITY_CHECK_FAILURE type crash.


Windows 8.1 64

4th Generation Intel Core i7-4720HQ Processor (2.60GHz 1600MHz 6MB)

16.0GB PC3-12800 DDR3L SDRAM 1600 MHz

NVIDIA GeForce GTX 860M 4GB

Here is a youtube video of the game running on a similar system, running on high settings.

The computer is only two months old, it shouldn't be a lemon, I'd hope. Though I'd like to contact Lenovo last, since I hear their customer service is just lovely...

And a copy and paste of the WhoCrashed Reports:

On Wed 5/27/2015 8:33:43 PM GMT your computer crashed
crash dump file: C:\windows\Minidump\052715-20781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x139 (0x3, 0xFFFFD000216CD710, 0xFFFFD000216CD668, 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 5/27/2015 8:33:43 PM GMT your computer crashed
crash dump file: C:\windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x139 (0x3, 0xFFFFD000216CD710, 0xFFFFD000216CD668, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
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 Tue 5/26/2015 11:52:25 PM GMT your computer crashed
crash dump file: C:\windows\Minidump\052615-23937-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x139 (0x3, 0xFFFFD000396D1710, 0xFFFFD000396D1668, 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 Tue 5/26/2015 10:10:38 PM GMT your computer crashed
crash dump file: C:\windows\Minidump\052615-24515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x139 (0x3, 0xFFFFD000530B1710, 0xFFFFD000530B1668, 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 Tue 5/26/2015 9:53:22 PM GMT your computer crashed
crash dump file: C:\windows\Minidump\052615-23046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x139 (0x3, 0xFFFFD00023FB7710, 0xFFFFD00023FB7668, 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 Tue 5/26/2015 9:08:28 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\052615-38140-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x9F (0x3, 0xFFFFE000DF78E6D0, 0xFFFFF80398CBCCB0, 0xFFFFE000E09E8C60)
Error: DRIVER_POWER_STATE_FAILURE
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 driver is in an inconsistent or invalid power state.
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.

Share of the Minidumps DMP files and MSinfo32 here: https://drive.google.com/folderview?id=0B9r8p26myLmrfjh3bWdfR2lmd3QwUHNEQzVUWldhMkk5QUxaZE04Tzh4bVhPMUJ1Qi1XNms&usp=sharing


 

Question Info


Last updated February 20, 2018 Views 1,279 Applies to:
Answer
Answer

Hi Taiin,

Thanks for the update on the issue, let me help you further.

This seems that the ntoskrnl.exe is missing or corrupt.

I would like to know;

  1. What is the model of your Lenovo computer?
  2. What is the current status of your computer? Are you able to boot to the desktop?

Please follow the methods below and check.

Method 1: Check the screen resolution.

Get the best display on your monitor screen resolution windows 8

If the issue persists, follow method 2.

Method 2: Update graphic driver.

Incompatible or not properly installed graphics card drivers are the most common cause of this issue, let’s update the graphics card driver and check if that solves the problem.

Follow the steps below to update the graphics card drivers.

  1. Press Windows + X key on the keyboard
  2. Go to device manager
  3. Right-click your display/graphic device
  4. Click Update Driver Software and then follow the steps in the wizard that appears.

If the issue still persists, follow method 3.

Method 3: Perform Clean Boot.

 

Placing your system in Clean Boot state helps in identifying if any third party applications or startup items are causing the issue. You need to follow the steps from the article mentioned below to perform a Clean Boot.

How to perform a clean boot in Windows

Note: Refer "How to reset the computer to start normally after clean boot troubleshooting" to reset the computer to start as normal after troubleshooting.

Let us know if you need further assistance. We will be glad to help you further.

 

____________________

Thanks & Regards,

Isha Soni

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

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

How satisfied are you with this response?

Thanks for your feedback.