First, this isn't technically a Windows server issue as I'm running Hyper-V on my Windows 10 laptop. I'm using Mikael Nystrom's hydration kit to run a virtual lab on my laptop. This requires that I bridge my wireless adapter with the "Internet"
vSwitch in order for the VM's to have Internet access. It also uses a virtual RRAS server to route traffic between the rest of the VM's, which are on the "InternalHQ" vSwitch, and the Internet.
The issue is that when the bridge is configured and the RRAS server is online, the host (my laptop) BSOD's repeatedly. After 2-3 times, the VM's stop booting, allowing me to shut off the RRAS server or disable the bridged connection, which stops the
BSOD from happening again. The specific BSOD is IRQ_NOT_LESS_OR_EQUAL on bridge.sys (the Microsoft driver that handles bridging of network devices).
From other posts, it seems that bridge.sys BSOD errors are usually network driver related, but I'm running the latest drivers from Dell. I have a Dell Precision 5510 with an Intel AC 8260 wireless adapter. The OS is Windows 10 Build 586.
Any suggestions are appreciated.
Here is the debug info from the minidump:
4: 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: 0000000000000018, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80167258feb, address which referenced memory
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10586.420.amd64fre.th2_release_sec.160527-1834
SYSTEM_MANUFACTURER: Dell Inc.
SYSTEM_PRODUCT_NAME: Precision 5510
SYSTEM_SKU: 06E5
BIOS_VENDOR: Dell Inc.
BIOS_VERSION: 01.02.00
BIOS_DATE: 04/07/2016
BASEBOARD_MANUFACTURER: Dell Inc.
BASEBOARD_PRODUCT: 0N8J4R
BASEBOARD_VERSION: A00
DUMP_TYPE: 2
BUGCHECK_P1: 18
BUGCHECK_P2: 2
BUGCHECK_P3: 0
BUGCHECK_P4: fffff80167258feb
READ_ADDRESS: fffff800839fc520: Unable to get MiVisibleState
0000000000000018
CURRENT_IRQL: 2
FAULTING_IP:
bridge+8feb
fffff801`67258feb 498b4f18 mov rcx,qword ptr [r15+18h]
CPU_COUNT: 8
CPU_MHZ: a98
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 5e
CPU_STEPPING: 3
CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: 84'00000000 (cache) 84'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: AV
PROCESS_NAME: System
ANALYSIS_SESSION_HOST: 1S2WN72
ANALYSIS_SESSION_TIME: 07-10-2016 00:12:39.0394
ANALYSIS_VERSION: 10.0.10586.567 amd64fre
TRAP_FRAME: ffffd00020d519b0 -- (.trap 0xffffd00020d519b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=ffffe0011ef588e0
rdx=0000000000006002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80167258feb rsp=ffffd00020d51b40 rbp=ffffd00020d51c01
r8=00001000fe206cc0 r9=ffffe0011ef588a0 r10=0000000000000004
r11=ffffd00020d51a60 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
bridge+0x8feb:
fffff801`67258feb 498b4f18 mov rcx,qword ptr [r15+18h] ds:00000000`00000018=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800837cb3e9 to fffff800837c07a0
STACK_TEXT:
ffffd000`20d51868 fffff800`837cb3e9 : 00000000`0000000a 00000000`00000018 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffd000`20d51870 fffff800`837c9bc7 : 00000000`00000000 ffffd000`20d51ac0 ffffd001`e4a120a8 00000000`00000001 : nt!KiBugCheckDispatch+0x69
ffffd000`20d519b0 fffff801`67258feb : 00000000`0000606f ffffe001`200ae990 ffffd000`20d51c01 ffffe001`200ae990 : nt!KiPageFault+0x247
ffffd000`20d51b40 00000000`0000606f : ffffe001`200ae990 ffffd000`20d51c01 ffffe001`200ae990 00000000`00000000 : bridge+0x8feb
ffffd000`20d51b48 ffffe001`200ae990 : ffffd000`20d51c01 ffffe001`200ae990 00000000`00000000 00000000`00000000 : 0x606f
ffffd000`20d51b50 ffffd000`20d51c01 : ffffe001`200ae990 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffe001`200ae990
ffffd000`20d51b58 ffffe001`200ae990 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffd000`20d51c01
ffffd000`20d51b60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffe001`200ae990
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: 2cbc7bc8e4cf99ce46138ceaa8710912227cb254
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 32bb0ec3d333d2d513a72511ca3f932345ec3cd5
THREAD_SHA1_HASH_MOD: 3cc4251f80231b1fe217f569e2d2b1461e5bb701
FOLLOWUP_IP:
bridge+8feb
fffff801`67258feb 498b4f18 mov rcx,qword ptr [r15+18h]
FAULT_INSTR_CODE: 184f8b49
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: bridge+8feb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: bridge
IMAGE_NAME: bridge.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 56cc1e9b
BUCKET_ID_FUNC_OFFSET: 8feb
FAILURE_BUCKET_ID: AV_bridge!Unknown_Function
BUCKET_ID: AV_bridge!Unknown_Function
PRIMARY_PROBLEM_CLASS: AV_bridge!Unknown_Function
TARGET_TIME: 2016-07-09T20:01:25.000Z
OSBUILD: 10586
OSSERVICEPACK: 0
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2016-05-27 23:59:07
BUILDDATESTAMP_STR: 160527-1834
BUILDLAB_STR: th2_release_sec
BUILDOSVER_STR: 10.0.10586.420.amd64fre.th2_release_sec.160527-1834
ANALYSIS_SESSION_ELAPSED_TIME: 5f6b
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:av_bridge!unknown_function
FAILURE_ID_HASH: {fc408975-df9e-bb6d-cca0-5d9f6ee3388a}
Followup: MachineOwner
---------
Does seem to be an issue with a driver. Wondering if maybe I should try to move the bridge from wireless to Ethernet for testing.