Windows 7 blue screen ndis.sys

[TheOoKiller]

Hi there, im experiencing VERY frequent BSODs and crashes while I'm gaming.
Below is the dmp file, help is appreciated...

Spoiler

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23572.amd64fre.win7sp1_ldr.161011-0600
Machine Name:
Kernel base = 0xfffff800`03002000 PsLoadedModuleList = 0xfffff800`03244730
Debug session time: Sat Mar 18 09:05:52.221 2017 (UTC - 4:00)
System Uptime: 0 days 0:02:12.517
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL (d5)
Memory was referenced after it was freed.
This cannot be protected by try-except.
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff98007132ff8, memory referenced
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation
Arg3: fffff880014b65b0, if non-zero, the address which referenced memory.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032ae100
GetUlongFromAddress: unable to read from fffff800032ae1c8
fffff98007132ff8

FAULTING_IP:
ndis!ndisDispatchIoWorkItem+0
fffff880`014b65b0 488b4a28 mov rcx,qword ptr [rdx+28h]

MM_INTERNAL_CODE: 0

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0xD5

PROCESS_NAME: System

CURRENT_IRQL: 0

TRAP_FRAME: fffff8800318c9a0 -- (.trap 0xfffff8800318c9a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800e2d1030 rbx=0000000000000000 rcx=fffffa800e2d6050
rdx=fffff98007132fd0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880014b65b0 rsp=fffff8800318cb38 rbp=fffff8000321b280
r8=0000000000000000 r9=0000000000007e00 r10=000000000000000d
r11=fffffa800b1f1c44 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
ndis!ndisDispatchIoWorkItem:
fffff880`014b65b0 488b4a28 mov rcx,qword ptr [rdx+28h] ds:fffff980`07132ff8=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800030ef2be to fffff80003072400

STACK_TEXT:
fffff880`0318c838 fffff800`030ef2be : 00000000`00000050 fffff980`07132ff8 00000000`00000000 fffff880`0318c9a0 : nt!KeBugCheckEx
fffff880`0318c840 fffff800`0307052e : 00000000`00000000 fffff980`07132ff8 fffffa80`09cff700 fffffa80`0e2d6050 : nt! ?? ::FNODOBFM::`string'+0x3bc5f
fffff880`0318c9a0 fffff880`014b65b0 : fffff800`0336e413 00000000`00000001 00000000`00000001 fffffa80`09cff780 : nt!KiPageFault+0x16e
fffff880`0318cb38 fffff800`0336e413 : 00000000`00000001 00000000`00000001 fffffa80`09cff780 fffffa80`09d48660 : ndis!ndisDispatchIoWorkItem
fffff880`0318cb40 fffff800`0307b355 : fffff800`0321b200 fffff800`0336e301 fffffa80`09d48600 fffffa80`00000000 : nt!IopProcessWorkItem+0x23
fffff880`0318cb70 fffff800`0330d236 : 00000000`00000000 fffffa80`09d48660 00000000`00000080 fffffa80`09d265d0 : nt!ExpWorkerThread+0x111
fffff880`0318cc00 fffff800`03063706 : fffff880`02fd7180 fffffa80`09d48660 fffff880`02fe1fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0318cc40 00000000`00000000 : fffff880`0318d000 fffff880`03187000 fffff880`0318c8a0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
ndis!ndisDispatchIoWorkItem+0
fffff880`014b65b0 488b4a28 mov rcx,qword ptr [rdx+28h]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: ndis!ndisDispatchIoWorkItem+0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ndis

IMAGE_NAME: ndis.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 561c7ad7

FAILURE_BUCKET_ID: X64_0xD5_ndis!ndisDispatchIoWorkItem+0

BUCKET_ID: X64_0xD5_ndis!ndisDispatchIoWorkItem+0

Followup: MachineOwner

 

[SA_tasko]

looks like wifi or ethernet driver fault try update thooso drive what ever u use ethernet or wifi hope this help.

 

[TheOoKiller]

looks like wifi or ethernet driver fault try update thooso drive what ever u use ethernet or wifi hope this help.

Will try and post results here, thanks. Im using a USB broadband fyi.