Синий экран смерти при установки драйвера Guardant II

Добрый день!
После установки апрельских обновлений ОС Windows 10 10.0.18363
Вышел синий экран смерти, до этого момента всё корректно работало

Зайдя в безопасный режим удалил драйвер устройства вместе с файлами
После чего ПК загрузился в штатном режиме

Далее скачал с Вашего сайта последнюю версию драйвера guardant stealth 2 (7.0.215 от 29.07.2020)
при попытке запуска снова синий экран смерти
так же снова удалил в безопасном режиме устройство guardant и ПК вновь заработал

Пробовал установить более раннюю версию драйвера guardant 7.0.206 от 16.07.2018, но результат тот же - синий экран.

Мини дамп:
************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 18362 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff805`3b60c000 PsLoadedModuleList = 0xfffff805`3ba51e70
Debug session time: Thu May 13 08:31:00.171 2021 (UTC + 8:00)
System Uptime: 0 days 0:00:18.143
Loading Kernel Symbols
...............................................................
................................................................
..............................................................
Loading User Symbols
Loading unloaded module list
........
For analysis of this file, run !analyze -v
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck 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: fffff8053a4e3077, The address that the exception occurred at
Arg3: ffff8100250670f8, Exception Record Address
Arg4: ffff810025066940, Context Record Address

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

*** WARNING: Unable to verify timestamp for grdkey.sys

KEY_VALUES_STRING: 1

    Key  : AV.Fault
    Value: Execute

    Key  : Analysis.CPU.Sec
    Value: 1

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on GUS1WS-00343

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 4

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

    Key  : Analysis.System
    Value: CreateObject

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b

BUGCHECK_CODE:  7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8053a4e3077

BUGCHECK_P3: ffff8100250670f8

BUGCHECK_P4: ffff810025066940

EXCEPTION_RECORD:  ffff8100250670f8 -- (.exr 0xffff8100250670f8)
ExceptionAddress: fffff8053a4e3077 (grdkey+0x0000000000003077)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000008
   Parameter[1]: fffff8053a4e3077
Attempt to execute non-executable address fffff8053a4e3077

CONTEXT:  ffff810025066940 -- (.cxr 0xffff810025066940)
rax=0000000000000000 rbx=ffffd086bfa4f990 rcx=ffffe6002a040180
rdx=0000000000000000 rsi=ffff8100250673c0 rdi=ffff8100250673b0
rip=fffff8053a4e3077 rsp=ffff810025067330 rbp=ffff8100250674b0
r8=cfffffffffffffff  r9=fffffcfe7e014e90 r10=0000000000000000
r11=ffff8100250671a8 r12=ffffffff800006dc r13=0000000000000002
r14=ffffa10639efd410 r15=ffffd086b38fe000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00250286
grdkey+0x3077:
fffff805`3a4e3077 68ccf33600      push    36F3CCh
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

EXECUTE_ADDRESS: fffff8053a4e3077

FAILED_INSTRUCTION_ADDRESS:
grdkey+3077
fffff805`3a4e3077 68ccf33600      push    36F3CCh

ERROR_CODE: (NTSTATUS) 0xc0000005 -                      0x%p                               0x%p.                      %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000008

EXCEPTION_PARAMETER2:  fffff8053a4e3077

MISALIGNED_IP:
grdkey+3077
fffff805`3a4e3077 68ccf33600      push    36F3CCh

EXCEPTION_STR:  0xc0000005

STACK_TEXT: 
ffff8100`25067330 ffffd086`b35dae50 : ffffd086`b38fe000 00000000`00000002 ffffd086`bf6f7510 ffffffff`800006dc : grdkey+0x3077
ffff8100`25067338 ffffd086`b38fe000 : 00000000`00000002 ffffd086`bf6f7510 ffffffff`800006dc ffff8100`250674b0 : 0xffffd086`b35dae50
ffff8100`25067340 00000000`00000002 : ffffd086`bf6f7510 ffffffff`800006dc ffff8100`250674b0 00000000`0000000e : 0xffffd086`b38fe000
ffff8100`25067348 ffffd086`bf6f7510 : ffffffff`800006dc ffff8100`250674b0 00000000`0000000e fffff805`3a4e312e : 0x2
ffff8100`25067350 ffffffff`800006dc : ffff8100`250674b0 00000000`0000000e fffff805`3a4e312e ffffd086`bf6f7510 : 0xffffd086`bf6f7510
ffff8100`25067358 ffff8100`250674b0 : 00000000`0000000e fffff805`3a4e312e ffffd086`bf6f7510 ffffd086`bf6f7510 : 0xffffffff`800006dc
ffff8100`25067360 00000000`0000000e : fffff805`3a4e312e ffffd086`bf6f7510 ffffd086`bf6f7510 ffffd086`bf6f7500 : 0xffff8100`250674b0
ffff8100`25067368 fffff805`3a4e312e : ffffd086`bf6f7510 ffffd086`bf6f7510 ffffd086`bf6f7500 ffffd086`bf6f7510 : 0xe
ffff8100`25067370 ffffd086`bf6f7510 : ffffd086`bf6f7510 ffffd086`bf6f7500 ffffd086`bf6f7510 00000000`00000000 : grdkey+0x312e
ffff8100`25067378 ffffd086`bf6f7510 : ffffd086`bf6f7500 ffffd086`bf6f7510 00000000`00000000 fffff805`3a4e30fa : 0xffffd086`bf6f7510
ffff8100`25067380 ffffd086`bf6f7500 : ffffd086`bf6f7510 00000000`00000000 fffff805`3a4e30fa 00000000`00000000 : 0xffffd086`bf6f7510
ffff8100`25067388 ffffd086`bf6f7510 : 00000000`00000000 fffff805`3a4e30fa 00000000`00000000 fffff805`3bd15e22 : 0xffffd086`bf6f7500
ffff8100`25067390 00000000`00000000 : fffff805`3a4e30fa 00000000`00000000 fffff805`3bd15e22 00000000`00000000 : 0xffffd086`bf6f7510

SYMBOL_NAME:  grdkey+3077

IMAGE_NAME:  hardware

STACK_COMMAND:  .cxr 0xffff810025066940 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  IP_MISALIGNED_grdkey.sys

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f843f302-0dfe-271e-ff31-bc0b25a5cdc7}

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