Code:
Bugcheck code 1000007E
Arguments ffffffff`80000003 fffff802`43f4d0a5 ffffb404`dd476588 ffffb404`dd475dd0
We have an 0x1000007E bugcheck, very similar (entirely similar, actually) to 0x7E which actually has documentation on it per the MSDN. This bugcheck in layman terms happens when a thread within kernel (system) space encounters violates a specific ruleset and the CPU raises an exception, and obviously it cannot recover so Windows throws a bugcheck to protect your data. When normal processes encounter an exception and the CPU raises an exception, typically the program will just crash.
Code:
ExceptionAddress: fffff80243f4d0a5 (nt!KeCheckStackAndTargetAddress+0x0000000000000045) [COLOR=#006400]//Where the exception occurred[/COLOR]
ExceptionCode: 80000003 (Break instruction exception) [COLOR=#006400]//Our specific exception type[/COLOR]
ExceptionFlags: 00000010
NumberParameters: 1
Parameter[0]: 0000000000000000 [COLOR=#006400]//It was a read-based exception[/COLOR]
Our actual exception was 0x80000003, which indicates a breakpoint or ASSERT was encountered when no kernel debugger was attached to the system. This is a really interesting exception to see because you obviously aren't setting any breakpoints in kernel/system space.
Code:
rax=ffffb404dd4767e8 rbx=ffffb404dd4779a8 rcx=0000000000000000
rdx=ffffb404dd4779a8 rsi=ffffb404dd476e50 rdi=0000000000000000
rip=fffff80243f4d0a5 rsp=ffffb404dd4767c0 rbp=ffffb404dd476990
r8=ffffb404dd476fb0 r9=ffffb404dd476930 r10=00007ffffffeffff
r11=fffff80244014cc0 r12=ffffb404dd477b10 r13=ffffb404dd477768
r14=ffffb404dd476930 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00000246
nt!KeCheckStackAndTargetAddress+0x45:
fffff802`43f4d0a5 cc int 3
Jumping to the assembler shows us a
very consistent instruction that the exception is being raised on - nt!KeCheckStackAndTargetAddress+0x45. This is the faulting instruction in every dump you've attached.
Code:
00 ffffb404`dd4767c0 fffff802`44014cfb nt!KeCheckStackAndTargetAddress+0x45
01 ffffb404`dd4767f0 fffff802`4404094d nt!_C_specific_handler+0x3b
02 ffffb404`dd476860 fffff802`43f4cb16 nt!RtlpExecuteHandlerForException+0xd
03 ffffb404`dd476890 fffff802`43f4e613 nt!RtlDispatchException+0x416
04 ffffb404`dd476f80 fffff802`44048d42 nt!KiDispatchException+0x1f3
05 ffffb404`dd477630 fffff802`440458bf nt!KiExceptionDispatch+0xc2
06 ffffb404`dd477810 00000000`00000000 nt!KiPageFault+0x3ff
We can see from frame 06 that we hit a pagefault and from there on out, the exception handling is carried out and nt!_C_specific_handler+0x3b attempts to figure out what to do with the exception that was raised.
So there's a few things I am going to recommend first:
1. Perhaps OS corruption, so try a repair -
How To Repair Windows 10
2. If #1 doesn't work, run a malware scan with Malwarebytes. I'm curious.
3. Update all of your drivers and if they already are, try rolling back to a previous GPU driver version since you mentioned nVidia drivers have given you trouble in the past.
Due to the consistency I doubt this is a RAM issue, but it's possible as well. You may also run Memtest86 if you wish.
