BSOD random times ngfilter.sys

I leave this Win 7 ent x64 company laptop on all the time (docked). Half of the mornings it has rebooted with this BSOD. I have updated all the drivers I could find. Any help appreciated.



Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\072214-152225-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Machine Name:
Kernel base = 0xfffff800`03600000 PsLoadedModuleList = 0xfffff800`038436d0
Debug session time: Tue Jul 22 16:58:28.319 2014 (UTC - 4:00)
System Uptime: 0 days 21:24:52.531
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff880046f3800, fffff88003df4098, fffff88003df38f0}

Unable to load image \SystemRoot\system32\DRIVERS\ngfilter.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ngfilter.sys
*** ERROR: Module load completed but symbols could not be loaded for ngfilter.sys
Probably caused by : ngfilter.sys ( ngfilter+2704 )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880046f3800, The address that the exception occurred at
Arg3: fffff88003df4098, Exception Record Address
Arg4: fffff88003df38f0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
afd!AfdCheckAndReferenceEndpoint+2
fffff880`046f3800 8b4138 mov eax,dword ptr [rcx+38h]

EXCEPTION_RECORD: fffff88003df4098 -- (.exr 0xfffff88003df4098)
ExceptionAddress: fffff880046f3800 (afd!AfdCheckAndReferenceEndpoint+0x0000000000000002)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000038
Attempt to read from address 0000000000000038

CONTEXT: fffff88003df38f0 -- (.cxr 0xfffff88003df38f0)
rax=ffff000007afb293 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000022 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880046f3800 rsp=fffff88003df42d8 rbp=fffff88003df4438
r8=fffff88003df4460 r9=0000000000000000 r10=fffff88003df4460
r11=0000000000000022 r12=fffffa80440838d0 r13=fffff88003df4430
r14=fffffa804c1f0d88 r15=fffff88003df4a80
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
afd!AfdCheckAndReferenceEndpoint+0x2:
fffff880`046f3800 8b4138 mov eax,dword ptr [rcx+38h] ds:002b:00000000`00000038=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000038

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800038ad100
0000000000000038

FOLLOWUP_IP:
ngfilter+2704
fffff880`206ce704 ?? ???

BUGCHECK_STR: 0x7E

DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER: from fffff88004757883 to fffff880046f3800

STACK_TEXT:
fffff880`03df42d8 fffff880`04757883 : 00000000`00000000 fffff880`03df4430 fffffa80`4f50cd88 fffff880`03df4a80 : afd!AfdCheckAndReferenceEndpoint+0x2
fffff880`03df42e0 fffff880`206ce704 : 00000000`00000026 fffff880`03df43e0 fffff880`03df4400 00000000`00000801 : afd!AfdReceiveDatagramEventHandler+0x53
fffff880`03df43d0 00000000`00000026 : fffff880`03df43e0 fffff880`03df4400 00000000`00000801 00000000`00000000 : ngfilter+0x2704
fffff880`03df43d8 fffff880`03df43e0 : fffff880`03df4400 00000000`00000801 00000000`00000000 504e474e`00000200 : 0x26
fffff880`03df43e0 fffff880`03df4400 : 00000000`00000801 00000000`00000000 504e474e`00000200 00000000`00000026 : 0xfffff880`03df43e0
fffff880`03df43e8 00000000`00000801 : 00000000`00000000 504e474e`00000200 00000000`00000026 fffff880`00000026 : 0xfffff880`03df4400
fffff880`03df43f0 00000000`00000000 : 504e474e`00000200 00000000`00000026 fffff880`00000026 fffff880`03df4438 : 0x801


SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: ngfilter+2704

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ngfilter

IMAGE_NAME: ngfilter.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5230cef5

STACK_COMMAND: .cxr 0xfffff88003df38f0 ; kb

FAILURE_BUCKET_ID: X64_0x7E_ngfilter+2704

BUCKET_ID: X64_0x7E_ngfilter+2704

Followup: MachineOwner
---------

Hi tika9119.

Please post a report following Windows Genuine and Activation Issue Posting Instructions before we start troubleshooting.

Diagnostic Report (1.9.0027.0):
-----------------------------------------

This is a KMS license owned by DELL itself as far as I can tell - you are very likely to be severely restricted in what you are able to do in terms of troubleshooting, as the Group Policy settings are probably such as to lock you out of much of the system.

I think you'd be well advised to ask your System Admin for assistance - their reaction is very likely to be a reformat and reinstall.