Kenel-power in windows events,Kernel Security Check Failure BSODs

Game_man

Commendable
Dec 15, 2016
48
0
1,530
I have been getting 'Kernel Security Check Failure' bsods sometimes when I start the vpn client or rarely when I start Kaspersky 17...but never ever when I play demanding games or never while browsing.And today in windows events I found the error is kernel power.Yes,I changed the PSU (to CORSAIR CS850M),but do the symptoms say so?
Nvdia driver updated,temps are fine too
 
Solution
Kernel power event 41 is the result of windows running a report at start up and discovering it was not shut down properly the previous time. Its a reaction, its not a cause.

Kernel security check may be a driver error.

Neither is related to power supply directly.


Can you download and run who crashed - it will give us a glimpse of the errors you getting and might help us solve them

Copy/paste summary in here and I see what I can do :)
Kernel power event 41 is the result of windows running a report at start up and discovering it was not shut down properly the previous time. Its a reaction, its not a cause.

Kernel security check may be a driver error.

Neither is related to power supply directly.


Can you download and run who crashed - it will give us a glimpse of the errors you getting and might help us solve them

Copy/paste summary in here and I see what I can do :)
 
Solution
quoted from PM -
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 05-05-2017 06:11:40 PM your computer crashed
crash dump file: C:\Windows\Minidump\050517-18734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0x139 (0x3, 0xFFFF8001B2C60C40, 0xFFFF8001B2C60B98, 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 Fri 05-05-2017 06:11:40 PM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: klim6.sys (klim6+0x2C72)
Bugcheck code: 0x139 (0x3, 0xFFFF8001B2C60C40, 0xFFFF8001B2C60B98, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\drivers\klim6.sys
product: System Interceptors PDK
company: AO Kaspersky Lab
description: Packet Network Filter [fre_win8_x64]
Bug check description: The kernel has detected the corruption of a critical data structure.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: klim6.sys (Packet Network Filter [fre_win8_x64], AO Kaspersky Lab).
Google query: AO Kaspersky Lab KERNEL_SECURITY_CHECK_FAILURE



On Tue 25-04-2017 07:16:37 PM your computer crashed
crash dump file: C:\Windows\Minidump\042517-20718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0x139 (0x3, 0xFFFFF803B5680C60, 0xFFFFF803B5680BB8, 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 Sun 09-04-2017 09:38:25 PM your computer crashed
crash dump file: C:\Windows\Minidump\040917-19890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0x139 (0x3, 0xFFFFB201D3745BB0, 0xFFFFB201D3745B08, 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 Sun 09-04-2017 12:43:02 PM your computer crashed
crash dump file: C:\Windows\Minidump\040917-20453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0x139 (0x3, 0xFFFFD501E42B5370, 0xFFFFD501E42B52C8, 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.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

12 crash dumps have been found and analyzed. Only 5 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

klim6.sys (Packet Network Filter [fre_win8_x64], AO Kaspersky Lab)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.

Last one caused by Kapersky, I would remove or update it. Its also likely the actual cause is lan drivers so I would check motherboard web site and make sure you have latest.

Can you also follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c/windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it :)

dumps will reveal more to this than what who crashed can.