BSOD on latest 6.2.379.1984 beta version

[skipik]

It was during internet serfing. No KIS or ESET, just Windows Defender.
Opera 48 Dev, Windows 10 Pro x64 v1703 (15063.413).
Dumps (RAR5): https://yadi.sk/d/Fv5ChJTn3KrxQE

[atkrv]

Minidump 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: fffff807aee6cec6, The address that the exception occurred at
Arg3: ffff99803257d608, Exception Record Address
Arg4: ffff99803257ce50, Context Record Address

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

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

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

FAULTING_IP: 
ndis!NdisAllocateCloneNetBufferList+196
fffff807`aee6cec6 488b5f08        mov     rbx,qword ptr [rdi+8]

EXCEPTION_RECORD:  ffff99803257d608 -- (.exr 0xffff99803257d608)
ExceptionAddress: fffff807aee6cec6 (ndis!NdisAllocateCloneNetBufferList+0x0000000000000196)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000008
Attempt to read from address 0000000000000008

CONTEXT:  ffff99803257ce50 -- (.cxr 0xffff99803257ce50)
rax=ffffe208f5a0dcd0 rbx=ffffe208f5a0db60 rcx=ffffe208f5a0dd80
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff807aee6cec6 rsp=ffff99803257d840 rbp=ffff99803257d8c0
 r8=0000000000000000  r9=0000000000000002 r10=0000000000000000
r11=fffff807aee879c7 r12=ffffe208f5a0dcd0 r13=0000000000000000
r14=ffffe208f1467a40 r15=ffffe208f5a0db60
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
ndis!NdisAllocateCloneNetBufferList+0x196:
fffff807`aee6cec6 488b5f08        mov     rbx,qword ptr [rdi+8] ds:002b:00000000`00000008=????????????????
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:  0000000000000008

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 0000000000000008 

FOLLOWUP_IP: 
ndis!NdisAllocateCloneNetBufferList+196
fffff807`aee6cec6 488b5f08        mov     rbx,qword ptr [rdi+8]

BUGCHECK_STR:  AV

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

EXCEPTION_STR:  0x0

LAST_CONTROL_TRANSFER:  from fffff807aefb4a7e to fffff807aee6cec6

STACK_TEXT:  
ffff9980`3257d840 fffff807`aefb4a7e : ffff9980`3257da20 ffff9980`3257da38 00000000`00000000 ffffe208`ff7952a0 : ndis!NdisAllocateCloneNetBufferList+0x196
ffff9980`3257d9e0 fffff807`aeff3edf : ffffe208`ff7952a0 ffffe208`ff795200 00000000`00000000 00000000`00000000 : NETIO!NetioAllocateAndReferenceCloneNetBufferListEx+0x3e
ffff9980`3257da20 fffff807`aefefa14 : ffffe208`ff7952a0 ffffe208`ff7952a0 ffffe208`fafdccc0 00000000`00000433 : NETIO!StreamDataAdvanceToDataStart+0x37
ffff9980`3257da70 fffff807`aefefb85 : 00000000`00000000 ffffe208`f7c1f1b0 00000000`00000000 ffffe208`00000000 : NETIO!StreamPermitDataHelper+0x24
ffff9980`3257daa0 fffff803`8acb8e8b : ffffe208`f6308300 00000000`00000000 ffffe208`f3aa7e40 00000000`00000000 : NETIO!StreamPermitRemoveDataWorkerRoutine+0xe5
ffff9980`3257db10 fffff803`8acd7ca8 : 00000000`00000000 ffffe208`f1d70040 fffff803`8acb8d90 fffff803`0000000c : nt!IopProcessWorkItem+0xfb
ffff9980`3257db80 fffff803`8ad76a37 : ffff9980`32440180 00000000`00000080 ffffe208`f148b040 ffffe208`f1d70040 : nt!ExpWorkerThread+0xd8
ffff9980`3257dc10 fffff803`8ae0b876 : ffff9980`32440180 ffffe208`f1d70040 fffff803`8ad769f0 00000000`00000000 : nt!PspSystemThreadStartup+0x47
ffff9980`3257dc60 00000000`00000000 : ffff9980`3257e000 ffff9980`32578000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

STACK_COMMAND:  .cxr 0xffff99803257ce50 ; kb

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE

BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE

Followup: memory_corruption

[vozersky]

the network driver has been reworked, here's the latest release candidate
if you will encounter bsods again, please let us know in the new consolidated issue