I'm able to execute the driver correctly but after a while (time varies from a few minutes to a few hours) I get one of these:
CRITICAL_STRUCTURE_CORRUPTION (109)
Arguments:
Arg1: a3a015666418d834, Reserved
Arg2: b3b721ecb69c3de8, Reserved
Arg3: fffff80269e64fb0, Failure type dependent information
Arg4: 0000000000000003, Type of corrupted region, can be
0 : A generic data region
1 : Modification of a function or .pdata
2 : A processor IDT
3 : A processor GDT
...
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2687
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 3579
Key : Analysis.Init.CPU.mSec
Value: 3687
Key : Analysis.Init.Elapsed.mSec
Value: 98923
Key : Analysis.Memory.CommitPeak.Mb
Value: 78
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
BUGCHECK_CODE: 109
BUGCHECK_P1: a3a015666418d834
BUGCHECK_P2: b3b721ecb69c3de8
BUGCHECK_P3: fffff80269e64fb0
BUGCHECK_P4: 3
PROCESS_NAME: System
STACK_TEXT:
fffffb06`55f0d678 fffff802`64912b12 : fffffb06`55f0d7e0 fffff802`6477d200 00000000`00000100 00000000`00000000 : nt!DbgBreakPointWithStatus
fffffb06`55f0d680 fffff802`649120f6 : 00000000`00000003 fffffb06`55f0d7e0 fffff802`6480c0c0 00000000`00000109 : nt!KiBugCheckDebugBreak+0x12
fffffb06`55f0d6e0 fffff802`647f72b7 : 00000000`fffffb06 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheck2+0x946
fffffb06`55f0ddf0 00000000`00000000 : 00000000`00000109 a3a01566`6418d834 b3b721ec`b69c3de8 fffff802`69e64fb0 : nt!KeBugCheckEx+0x107
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x109_3_ANALYSIS_INCONCLUSIVE!unknown_function
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
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: ffffc6086b831ff8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: ffffb205fc11d87a, address which referenced memory
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 8452
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 193043
Key : Analysis.Init.CPU.mSec
Value: 2077
Key : Analysis.Init.Elapsed.mSec
Value: 6984915
Key : Analysis.Memory.CommitPeak.Mb
Value: 61
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
BUGCHECK_CODE: d1
BUGCHECK_P1: ffffc6086b831ff8
BUGCHECK_P2: 2
BUGCHECK_P3: 1
BUGCHECK_P4: ffffb205fc11d87a
WRITE_ADDRESS: ffffc6086b831ff8
PROCESS_NAME: System
TRAP_FRAME: ffff9b0170745e40 -- (.trap 0xffff9b0170745e40)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000109
rdx=a39ff15e8ddf06d3 rsi=0000000000000000 rdi=0000000000000000
rip=ffffb205fc11d87a rsp=ffff9b0170745fd8 rbp=ffff9b0170746059
r8=b3b6fde4e0615bcf r9=fffff8005f064fb0 r10=ffffc6086b831ff8
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
ffffb205`fc11d87a 498902 mov qword ptr [r10],rax ds:ffffc608`6b831ff8=????????????????
Resetting default scope
STACK_TEXT:
ffff9b01`70745548 fffff800`59712b12 : ffff9b01`707456b0 fffff800`5957d200 00000000`00000000 00000000`00000000 : nt!DbgBreakPointWithStatus
ffff9b01`70745550 fffff800`597120f6 : 00000000`00000003 ffff9b01`707456b0 fffff800`5960c0c0 00000000`000000d1 : nt!KiBugCheckDebugBreak+0x12
ffff9b01`707455b0 fffff800`595f72b7 : 00000000`00000000 00000000`00000000 fffff800`5f064fb0 00000000`00000000 : nt!KeBugCheck2+0x946
ffff9b01`70745cc0 fffff800`59609169 : 00000000`0000000a ffffc608`6b831ff8 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx+0x107
ffff9b01`70745d00 fffff800`59605469 : 00000001`ffffffff fffffff6`00000000 ffff9b01`70746020 20726574`66612064 : nt!KiBugCheckDispatch+0x69
ffff9b01`70745e40 ffffb205`fc11d87a : ffffb205`fc11d00a fffff800`592e3028 ffff9b01`70746fb0 fffff800`594a0927 : nt!KiPageFault+0x469
ffff9b01`70745fd8 ffffb205`fc11d00a : fffff800`592e3028 ffff9b01`70746fb0 fffff800`594a0927 ffff9b01`70745a60 : 0xffffb205`fc11d87a
ffff9b01`70745fe0 fffff800`592e3028 : ffff9b01`70746fb0 fffff800`594a0927 ffff9b01`70745a60 00000000`00000003 : 0xffffb205`fc11d00a
ffff9b01`70745fe8 ffff9b01`70746fb0 : fffff800`594a0927 ffff9b01`70745a60 00000000`00000003 fffff800`595f71b0 : nt!setjmpexused <PERF> (nt+0xe3028)
ffff9b01`70745ff0 fffff800`594a0927 : ffff9b01`70745a60 00000000`00000003 fffff800`595f71b0 ffffc608`6b837c90 : 0xffff9b01`70746fb0
ffff9b01`70745ff8 4dd5d1ac`b84d7059 : 4dd5d1ac`baedd1ac 00000000`00000000 00000000`00000000 fffff800`59200000 : nt!MiFastLockLeafPageTable+0x357
ffff9b01`70746078 4dd5d1ac`baedd1ac : 00000000`00000000 00000000`00000000 fffff800`59200000 ffff9b01`70746760 : 0x4dd5d1ac`b84d7059
ffff9b01`70746080 00000000`00000000 : 00000000`00000000 fffff800`59200000 ffff9b01`70746760 ffffc608`6b837428 : 0x4dd5d1ac`baedd1ac
SYMBOL_NAME: nt!KiPageFault+469
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 469
FAILURE_BUCKET_ID: AV_nt!KiPageFault
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10