System crash on Windows 10 host when using vbox network adapter together with Windows 10 networking bridging feature

[Andazeus]

Steps to reproduce the issue:

1) Install vbox on a Windows 10 device 2) Make sure to also enable the vbox network adapter 3) Set physical network adapter within the Windows 10 network settings to bridge mode (Control Panel\Network and Internet\Network Connections -> right click network connection -> bridge connection) 4) Leave device running as normal. In my case, the crashes seemed to happen fairly consistently after roughly 14 hours of system uptime, give or take a few hours.

Unfortunately my system settings were set to full crash dumps and not minidumps, so the full dump is likely too large to upload here. However, I will paste the information the Windows debugger was able to extract from my crash dump here:

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e) 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. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff8027f4580c3, The address that the exception occurred at Arg3: fffffe8c1f2a2ab8, Exception Record Address Arg4: ffffa400c67f5920, Context Record Address

Debugging Details:

---

KEY_VALUES_STRING: 1

Key : AV.Fault Value: Read

Key : Analysis.CPU.Sec Value: 2

Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-INRFD0B

Key : Analysis.DebugData Value: CreateObject

Key : Analysis.DebugModel Value: CreateObject

Key : Analysis.Elapsed.Sec Value: 4

Key : Analysis.Memory.CommitPeak.Mb Value: 73

Key : Analysis.System Value: CreateObject

BUGCHECK_CODE: 7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8027f4580c3

BUGCHECK_P3: fffffe8c1f2a2ab8

BUGCHECK_P4: ffffa400c67f5920

EXCEPTION_RECORD: fffffe8c1f2a2ab8 -- (.exr 0xfffffe8c1f2a2ab8) ExceptionAddress: fffff8027f4580c3 (bridge+0x00000000000080c3)

ExceptionCode: c0000005 (Access violation)

ExceptionFlags: 00000000

NumberParameters: 2

Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff

Attempt to read from address ffffffffffffffff

CONTEXT: ffffa400c67f5920 -- (.cxr 0xffffa400c67f5920) rax=0000000000000000 rbx=0000000000000000 rcx=b2a29e05584ac880 rdx=0000000000000000 rsi=ffffb8880f8ee2c0 rdi=ffffb888098a48e0 rip=fffff8027f4580c3 rsp=fffffe8c1f2a2cf0 rbp=fffffe8c1f2a2e00

r8=0000000000000001 r9=0000000000000001 r10=0000000000000002

r11=fffffe8c1f2a2b90 r12=0000000000000000 r13=0000000000000000 r14=ffffb8880f8ee4f0 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010282 bridge+0x80c3: fffff8027f4580c3 488b4918 mov rcx,qword ptr [rcx+18h] ds:002b:b2a29e05584ac898=???????????????? Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: System

READ_ADDRESS: ffffffffffffffff

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

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

EXCEPTION_STR: 0xc0000005

BAD_STACK_POINTER: ffffa400c67f50e8

STACK_TEXT: fffffe8c1f2a2cf0 fffff8027f458786 : 0000009400000000 0000000000000003 fffffe8c1f2a2e80 0000000000000003 : bridge+0x80c3 fffffe8c1f2a2d80 fffff802674f53b5 : ffffb88808528040 ffffb88808528040 fffff8027f458550 0000000000000003 : bridge+0x8786 fffffe8c1f2a3c10 fffff802675fe278 : ffffa400c67b3180 ffffb88808528040 fffff802674f5360 0000000000000000 : ntPspSystemThreadStartup+0x55 fffffe8c1f2a3c60 0000000000000000 : fffffe8c1f2a4000 fffffe8c1f29e000 0000000000000000 0000000000000000 : ntKiStartSystemThread+0x28

SYMBOL_NAME: bridge+80c3

MODULE_NAME: bridge

IMAGE_NAME: bridge.sys

STACK_COMMAND: .cxr 0xffffa400c67f5920 ; kb

BUCKET_ID_FUNC_OFFSET: 80c3

FAILURE_BUCKET_ID: AV_STACKPTR_ERROR_bridge!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {7c978e5a-5f78-1ec3-8e3c-e245486b5eda}

Followup: MachineOwner

---