BSOD - occurs when I try to start from hibernation

[swodniw8guy]

BSOD - occurs when I try to start from hibernation, This just started 2 days ago. Here are the notes from whocrashed

Crash dump directory: C:\Windows\Minidump


Crash dumps are enabled on your computer.


On Sat 22/10/2016 06:34:14 GMT your computer


crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following


module: Unknown (0xFFFFD00022A00BE0)
Bugcheck code: 0x139 (0x3, 0xFFFFD00022A00BE0,


0xFFFFD00022A00B38, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
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.
Google query: KERNEL_SECURITY_CHECK_FAILURE






On Fri 21/10/2016 15:35:51 GMT your computer


crashed
crash dump file: C:\Windows\Minidump\102116-


25921-01.dmp
This was probably caused by the following


module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x139 (0x3, 0xFFFFD00021EBDBE0,


0xFFFFD00021EBDB38, 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.

Here's the logfile gathered from dm_log collector. Would really appreciate some help here.

 

[axe0]

Hi swodniw8guy,

Welcome to the 8forums

Please remove / disable items from the startup in taskmanager
These programs could interfere with the boot process giving you trouble and increase the boot time.

Please ensure that your recovery settings are properly set for a minidump
BSOD Minidump - Configure to Create in Windows 10 - Windows 10 Forums

Event[50254]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2016-10-22T07:35:10.000
  Event ID: 1005
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: SID-PC
  Description: 
Unable to produce a minidump file from the full dump file.

Diagnostics Test

System File Check

Please try following:

• Open an admin command prompt
• Copy/paste "sfc /scannow" (without quotes) and press enter
• When it is finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

If sfc/scannow says "Windows Resource Protection found corrupt files but was unable to fix some of them" after the second SFC, please upload the cbs.log file located at %systemroot%\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

Make a photo of SFC and post it.



Please uninstall Avast, use Windows Defender as alternative while troubleshooting and uninstall Sandboxie.

ffffd000`21ebd2a8  fffff801`491dbb63Unable to load image \??\C:\Program Files\Sandboxie\SbieDrv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SbieDrv.sys
*** ERROR: Module load completed but symbols could not be loaded for SbieDrv.sys
 SbieDrv+0x10b63
ffffd000`21ebd2b0  ffffd000`21ebd700
ffffd000`21ebd2b8  00000000`0000001d
ffffd000`21ebd2c0  00000000`00000000
ffffd000`21ebd2c8  fffff801`49aa5009Unable to load image \SystemRoot\system32\drivers\aswSnx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSnx.sys
*** ERROR: Module load completed but symbols could not be loaded for aswSnx.sys
 aswSnx+0x58009