This generally happens when I idle my computer for about 5-10 minutes, I've turned essentially set all the power settings to always on, removed any screensaver.

I have the dump file below, I can't seem to figure out what's causing it.  

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure.  The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffffd0011d1bb310, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffd0011d1bb268, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

Debugging Details:
------------------

Page 1199d3 not present in the dump file. Type ".hh dbgerr004" for details

OVERLAPPED_MODULE: Address regions for 'NvStreamKms' and 'mfeavfk01.sys' overlap

TRAP_FRAME:  ffffd0011d1bb310 -- (.trap 0xffffd0011d1bb310)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffe0001acbf8a0 rbx=0000000000000000 rcx=0000000000000003
rdx=ffffe0001956ac70 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8004b6c7acd rsp=ffffd0011d1bb4a0 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000002 r10=ffffe0001a32e420
r11=ffffe00018d82aa0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
ndis!ndisNsiGetInterfaceInformation+0x21b8d:
fffff800`4b6c7acd cd29            int     29h
Resetting default scope

EXCEPTION_RECORD:  ffffd0011d1bb268 -- (.exr 0xffffd0011d1bb268)
ExceptionAddress: fffff8004b6c7acd (ndis!ndisNsiGetInterfaceInformation+0x0000000000021b8d)
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
  ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 0000000000000003

DEFAULT_BUCKET_ID:  LIST_ENTRY_CORRUPT

BUGCHECK_STR:  0x139

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

EXCEPTION_PARAMETER1:  0000000000000003

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

LAST_CONTROL_TRANSFER:  from fffff803bc1747e9 to fffff803bc168ca0

STACK_TEXT:  
ffffd001`1d1bafe8 fffff803`bc1747e9 : 00000000`00000139 00000000`00000003 ffffd001`1d1bb310 ffffd001`1d1bb268 : nt!KeBugCheckEx
ffffd001`1d1baff0 fffff803`bc174b10 : 00000000`00000000 00000000`00000001 ffffd001`1d1bb1d8 ffffd001`00000000 : nt!KiBugCheckDispatch+0x69
ffffd001`1d1bb130 fffff803`bc173d34 : ffffc001`40695060 00000004`0000000c 00000000`00000000 ffffc001`406954d0 : nt!KiFastFailDispatch+0xd0
ffffd001`1d1bb310 fffff800`4b6c7acd : 00000000`ffffe000 00000000`00000000 ffffd001`1d1bb610 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0xf4
ffffd001`1d1bb4a0 fffff800`4b20e572 : ffffd001`1d1bb610 ffffe000`18d82a02 ffffe000`18d82a00 00000000`00000000 : ndis!ndisNsiGetInterfaceInformation+0x21b8d
ffffd001`1d1bb550 fffff800`4c59da25 : 00000000`00000050 00000000`00000050 ffffe000`1956d370 00000000`00000000 : NETIO!NsiGetParameterEx+0x222
ffffd001`1d1bb6b0 fffff800`4c59dbe3 : 00000000`00000000 ffffe000`1d425b30 ffffe000`1d425a60 00000000`00000000 : nsiproxy!NsippGetParameter+0x195
ffffd001`1d1bb840 fffff803`bc43d77f : 00000000`00000000 ffffe000`1d425a60 ffffe000`1d425a60 00000000`00000001 : nsiproxy!NsippDispatch+0x53
ffffd001`1d1bb880 fffff803`bc43cd22 : ffffd001`1d1bba38 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0xa4f
ffffd001`1d1bba20 fffff803`bc1744b3 : ffffe000`1c1f1080 00000000`001f0003 000000c2`ac6df248 00000000`00000001 : nt!NtDeviceIoControlFile+0x56
ffffd001`1d1bba90 00007ffb`c4b3123a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
000000c2`ac6df2c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`c4b3123a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETIO!NsiGetParameterEx+222
fffff800`4b20e572 8bd8            mov     ebx,eax

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  NETIO!NsiGetParameterEx+222

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME:  NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  546029c5

BUCKET_ID_FUNC_OFFSET:  222

FAILURE_BUCKET_ID:  0x139_3_NETIO!NsiGetParameterEx

BUCKET_ID:  0x139_3_NETIO!NsiGetParameterEx

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x139_3_netio!nsigetparameterex

FAILURE_ID_HASH:  {863902cf-27d7-671f-3d7f-44a47e15711d}

Followup: MachineOwner

  We do need the actual log files (called a DMP files) as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  

Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here If you have any questions about the procedure please ask

Hi,

NETIO.sys is a Windows networking driver. This issue can be caused by following factors:

1. Network drivers themselves; whether they need to be updated, reinstalled due to corruption, rolled back due to bug in latest version, etc.

               

2. 3rd party antivirus or firewall software causing NETBIOS and/or network related conflicts.

Please first reinstall or update your network adapter drivers including wired and wireless to check the issue.

If the issue still persists, this points us towards networking related 3rd party drivers or programs.

A faster way to attempt to identify the faulting driver is by the use of Driver Verifier (the STOP 0xD1 errors are well suited in provoking the actual faulting driver to identify itself). Please follow the instructions here to use Driver Verifier:

http://answers.microsoft.com/en-us/windows/wiki/windows_other-system/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983

To remove or reinstall the problematic drivers, if the driver is related to 3^rd part program, just remove the program to check the issue.

For further help, please upload the latest dump file as zig mentioned for our research.