Suddenly getting BSOD KMODE_EXCEPTION_NOT_HANDLED (NETIO.SYS)

So yeah, just what the title says. I'm getting these BSOD's while playing DCS World, and it's really annoying me. I uploaded the dumps to OneDrive but I can't post the link here yet because my account is not verified or something.

EDIT: link to dumps https://onedrive.live.com/redir?resid=A9508A4001B33274%213366

  • Edited by Haribo112 Tuesday, April 07, 2015 11:38 PM
April 7th, 2015 9:25pm

Alright, running verifier now.
Free Windows Admin Tool Kit Click here and download it now
April 8th, 2015 8:53am

Got another blue screen today. dumps uploaded here. Dumps
April 8th, 2015 2:40pm

HA

Driver verified and Related to tapoas.sys TAP-Win32 Virtual Network Driver from The OpenVPN Project.  Yours is 5 years old.  Long before win 8 was released.  I would remove it or update to current

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


Loading Dump File [C:\Users\zigza\Desktop\040815-5828-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17668.amd64fre.winblue_r8.150127-1500
Machine Name:
Kernel base = 0xfffff802`4941f000 PsLoadedModuleList = 0xfffff802`496f8250
Debug session time: Wed Apr  8 09:45:54.543 2015 (UTC - 4:00)
System Uptime: 0 days 0:02:12.264
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {ffffcf81b0772f40, 2, 0, fffff800dc06d1b8}

*** WARNING: Unable to verify timestamp for tapoas.sys
*** ERROR: Module load completed but symbols could not be loaded for tapoas.sys
Probably caused by : tapoas.sys ( tapoas+31b8 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: ffffcf81b0772f40, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff800dc06d1b8, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80249782138
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 ffffcf81b0772f40 

CURRENT_IRQL:  2

FAULTING_IP: 
tapoas+31b8
fffff800`dc06d1b8 83bb9002000000  cmp     dword ptr [rbx+290h],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  AV

PROCESS_NAME:  System

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

TRAP_FRAME:  ffffd000360c0a90 -- (.trap 0xffffd000360c0a90)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000004c rbx=0000000000000000 rcx=00000000000000ae
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800dc06d1b8 rsp=ffffd000360c0c20 rbp=ffffd000360c0d40
 r8=0000000000000000  r9=ffffe00082703e30 r10=0000000000000002
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
tapoas+0x31b8:
fffff800`dc06d1b8 83bb9002000000  cmp     dword ptr [rbx+290h],0 ds:00000000`00000290=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8024957b4e9 to fffff8024956f9a0

STACK_TEXT:  
ffffd000`360c0948 fffff802`4957b4e9 : 00000000`0000000a ffffcf81`b0772f40 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffd000`360c0950 fffff802`49579d3a : 00000000`00000000 ffffcf81`b0772cb0 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffd000`360c0a90 fffff800`dc06d1b8 : 00000000`00000000 ffffcf81`b0f5cc70 ffffe000`82703e30 fffff800`d90a7ef7 : nt!KiPageFault+0x23a
ffffd000`360c0c20 00000000`00000000 : ffffcf81`b0f5cc70 ffffe000`82703e30 fffff800`d90a7ef7 00000000`00000000 : tapoas+0x31b8


STACK_COMMAND:  kb

FOLLOWUP_IP: 
tapoas+31b8
fffff800`dc06d1b8 83bb9002000000  cmp     dword ptr [rbx+290h],0

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  tapoas+31b8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: tapoas

IMAGE_NAME:  tapoas.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c3a627f

FAILURE_BUCKET_ID:  AV_VRF_tapoas+31b8

BUCKET_ID:  AV_VRF_tapoas+31b8

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:av_vrf_tapoas+31b8

FAILURE_ID_HASH:  {faed8498-0d65-79c8-ffe6-470816c2c3a2}

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


Free Windows Admin Tool Kit Click here and download it now
April 9th, 2015 9:42am

Okay, that virtual network adapter was not connected anyway. Windows also reported that there was no newer driver available for it, so I just disabled it from Networkadapters. Hopefully that will end my bluescreens.
April 13th, 2015 5:12am

No it is not fixed. It keeps happening. This time with these  dump files. Both the same BSOD's and same drivers listed. what i should probably have noted before is that this all started after i swapped my RAM for a new kit. I did not reinstall windows as that is usually not neccessary after just a RAM swap. Could all of this random behaviour come from faulty RAM?
Free Windows Admin Tool Kit Click here and download it now
April 13th, 2015 12:49pm

And now even a new BSOD. Haven't seen this one before: Dump file here

EDIT:

and now another completely new one: kernel security check failure

I have ordered some new RAM to try and see if that resolves it, given the fact that all of this nonsense started after installing different RAM.


April 14th, 2015 6:48am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics