Here is full log from driver.
I have intel i7-9700f
Memory integrity - off
i've tried to fix it but i can't.
this log from fully original urs code.
I hope u fix it and help me with this issue,
btw thx u are the best one<3
[hv] DriverEntry — Hypervisor initializing...
[hv] Stealth CPUID cache: MaxStd=0x16, MaxExt=0x80000008, XCR0=0x7, InvalidLeaf={0x0, 0x0, 0x0, 0x0}
[hv] INVVPID caps: supported=1 individual=1 single=1 all=1 retaining_globals=1
[hv] EPT: Page at PFN 0x0 crosses MTRR boundary (split recommended)
[hv] EPT: Page at PFN 0x0 crosses MTRR boundary (split recommended)
[hv] EPT initialized for 2 processors
KDTARGET: Refreshing KD connection
*** Fatal System Error: 0x00000050
(0xFFFFFFFFFFFFFE00,0x0000000000000000,0xFFFFF80210F846A1,0x0000000000000002)
Driver at fault:
*** Ophion.sys - Address FFFFF80210F846A1 base at FFFFF80210F80000, DateStamp 69bd4a76
.
Break instruction exception - code 80000003 (first chance)
A fatal system error has occurred.
Debugger entered on first try; Bugcheck callbacks have not been invoked.
A fatal system error has occurred.
For analysis of this file, run !analyze -v
nt!DbgBreakPointWithStatus:
fffff802`796fc810 cc int 3
0: kd> !analyze -v
Connected to Windows 10 26100 x64 target at (Fri Mar 20 14:25:56.697 2026 (UTC + 1:00)), ptr64 TRUE
Loading Kernel Symbols
.................................
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................
................................................................
................................................................
.
Loading User Symbols
Loading unloaded module list
........
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: fffffffffffffe00, memory referenced.
Arg2: 0000000000000000, X64: bit 0 set if the fault was due to a not-present PTE.
bit 1 is set if the fault was due to a write, clear if a read.
bit 3 is set if the processor decided the fault was due to a corrupted PTE.
bit 4 is set if the fault was due to attempted execute of a no-execute PTE.
- ARM64: bit 1 is set if the fault was due to a write, clear if a read.
bit 3 is set if the fault was due to attempted execute of a no-execute PTE.
Arg3: fffff80210f846a1, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)
Debugging Details:
Here is full log from driver.
I have intel i7-9700f
Memory integrity - off
i've tried to fix it but i can't.
this log from fully original urs code.
I hope u fix it and help me with this issue,
btw thx u are the best one<3
[hv] DriverEntry — Hypervisor initializing...
[hv] Stealth CPUID cache: MaxStd=0x16, MaxExt=0x80000008, XCR0=0x7, InvalidLeaf={0x0, 0x0, 0x0, 0x0}
[hv] INVVPID caps: supported=1 individual=1 single=1 all=1 retaining_globals=1
[hv] EPT: Page at PFN 0x0 crosses MTRR boundary (split recommended)
[hv] EPT: Page at PFN 0x0 crosses MTRR boundary (split recommended)
[hv] EPT initialized for 2 processors
KDTARGET: Refreshing KD connection
*** Fatal System Error: 0x00000050
(0xFFFFFFFFFFFFFE00,0x0000000000000000,0xFFFFF80210F846A1,0x0000000000000002)
Driver at fault:
*** Ophion.sys - Address FFFFF80210F846A1 base at FFFFF80210F80000, DateStamp 69bd4a76
.
Break instruction exception - code 80000003 (first chance)
A fatal system error has occurred.
Debugger entered on first try; Bugcheck callbacks have not been invoked.
A fatal system error has occurred.
For analysis of this file, run !analyze -v
nt!DbgBreakPointWithStatus:
fffff802`796fc810 cc int 3
0: kd> !analyze -v
Connected to Windows 10 26100 x64 target at (Fri Mar 20 14:25:56.697 2026 (UTC + 1:00)), ptr64 TRUE
Loading Kernel Symbols
.................................
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................
................................................................
................................................................
.
Loading User Symbols
Loading unloaded module list
........
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: fffffffffffffe00, memory referenced.
Arg2: 0000000000000000, X64: bit 0 set if the fault was due to a not-present PTE.
bit 1 is set if the fault was due to a write, clear if a read.
bit 3 is set if the processor decided the fault was due to a corrupted PTE.
bit 4 is set if the fault was due to attempted execute of a no-execute PTE.
- ARM64: bit 1 is set if the fault was due to a write, clear if a read.
bit 3 is set if the fault was due to attempted execute of a no-execute PTE.
Arg3: fffff80210f846a1, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)
Debugging Details: