UNEXPECTED KERNEL MODE TRAP crash when attempting to load UDEFX2 driver

[forderud]

I'm experiencing a "UNEXPECTED KERNEL MODE TRAP" blue screen when attempting to load the UDEFX2 driver:

Steps to reproduce

• Apply pull requests AGENT: Remove unreferenced variables #2, Fix ExAllocatePool deprecation warning #3 and MODE enum conflict with enum in wdm.h #4 to revive the build.
• Comment-out S2EInvokePlugin call in FuzzerGetCoverage function to avoid compiler error.
• In the UDEFX2 project settings, use "SHA256" digest for driver signing to fix signing error.
• Build driver in Visual Studio.
• Run devcon.exe install UDEFX2.inf Root\UDEFX2 to install the driver.
• Observe blue screen.

WinDBG details

BUGCHECK_CODE:  7f

BUGCHECK_P1: 8

BUGCHECK_P2: ffff8500a17bce70

BUGCHECK_P3: ffffd48d479b9e20

BUGCHECK_P4: fffff80479ba91d6

PROCESS_NAME:  System

LOCK_ADDRESS:  fffff8047a0462e0 -- (!locks fffff8047a0462e0)

Resource @ nt!PiEngineLock (0xfffff8047a0462e0)    Exclusively owned
    Contention Count = 24
    NumberOfExclusiveWaiters = 1
     Threads: ffffb284cffbe0c0-01<*> 

     Threads Waiting On Exclusive Access:
              ffffb284cfa66080       
1 total locks

PNP_TRIAGE_DATA: 
	Lock address  : 0xfffff8047a0462e0
	Thread Count  : 1
	Thread address: 0xffffb284cffbe0c0
	Thread wait   : 0x1793

STACK_TEXT:  
nt!DbgBreakPointWithStatus
nt!KiBugCheckDebugBreak+0x12
nt!KeBugCheck2+0xa71
nt!KeBugCheckEx+0x107
nt!KiBugCheckDispatch+0x69
nt!KiDoubleFaultAbort+0x307
nt!CmpDoParseKey+0x56
nt!CmpParseKey+0x2df
nt!ObpLookupObjectName+0x1111
nt!ObOpenObjectByNameEx+0x1f1
nt!CmOpenKey+0x2c0
nt!NtOpenKey+0x49
nt!KiSystemServiceCopyEnd+0x25
nt!KiServiceLinkage
WdFilter+0x406b8
WdFilter+0x3fee1
WdFilter+0x3f679
nt!CmpCallCallBacksEx+0x1b3
nt!CmpParseKey+0x269
nt!ObpLookupObjectName+0x1111
nt!ObOpenObjectByNameEx+0x1f1
nt!CmCreateKey+0x480
nt!NtCreateKey+0x52
nt!KiSystemServiceCopyEnd+0x25
nt!KiServiceLinkage
nt!_RegRtlCreateKeyTransacted+0xe2
nt!_RegRtlCreateTreeTransacted+0x76
nt!SysCtxRegCreateTree+0x60
nt!PnpCtxRegCreateTree+0x4c
nt!_CmOpenCommonClassRegKeyWorker+0x263
nt!_CmOpenCommonClassRegKey+0xfd
nt!CmOpenInterfaceClassRegKey+0x3a
nt!_CmCreateInterfaceClassWorker+0x55
nt!_CmCreateInterfaceClass+0xd5
nt!_CmCreateDeviceInterfaceWorker+0x80
nt!_CmCreateDeviceInterface+0xcc
nt!IopRegisterDeviceInterface+0x294
nt!IoRegisterDeviceInterface+0xbe
Wdf01000!FxDeviceInterface::Register+0x2b [minkernel\wdf\framework\shared\support\km\fxdeviceinterfacekm.cpp @ 183] 
Wdf01000!imp_WdfDeviceCreateDeviceInterface+0x151 [minkernel\wdf\framework\shared\support\fxdeviceinterfaceapi.cpp @ 138] 
ucx01000!UcxControllerCreate+0x1097
udecx!Controller_UcxControllerCreate+0x1f3
udecx!UdecxWdfDeviceAddUsbDeviceEmulation+0x154
UDEFX2!UdecxWdfDeviceAddUsbDeviceEmulation+0x43 [C:\Program Files (x86)\Windows Kits\10\Include\10.0.22621.0\km\ude\1.0\UdecxWdfDevice.h @ 206] 
UDEFX2!UDEFX2CreateDevice+0x4a6 [C:\OpenSource\UDEFuzz\UDEFX2\Device.c @ 182] 
UDEFX2!UDEFX2EvtDeviceAdd+0xaf [C:\OpenSource\UDEFuzz\UDEFX2\Driver.c @ 140] 
Wdf01000!FxDriver::AddDevice+0xa2 [minkernel\wdf\framework\shared\core\km\fxdriverkm.cpp @ 72] 
Wdf01000!FxDriver::AddDevice+0x2c [minkernel\wdf\framework\shared\core\km\fxdriverkm.cpp @ 51] 
nt!PpvUtilCallAddDevice+0x3b
nt!PnpCallAddDevice+0x94
nt!PipCallDriverAddDevice+0x82a
nt!PipProcessDevNodeTree+0x1b9
nt!PiRestartDevice+0xba
nt!PnpDeviceActionWorker+0x626
nt!ExpWorkerThread+0x14f
nt!PspSystemThreadStartup+0x55
nt!KiStartSystemThread+0x34


SYMBOL_NAME:  WdFilter+406b8

MODULE_NAME: WdFilter

IMAGE_NAME:  WdFilter.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  406b8

FAILURE_BUCKET_ID:  0x7f_8_WdFilter!unknown_function

OS_VERSION:  10.0.22000.1

BUILDLAB_STR:  co_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

According to Bug check 0x7F: UNEXPECTED_KERNEL_MODE_TRAP then the Parameter 1 0x00000008 "Double Fault" type is commonly caused by a kernel stack overflow.