Hello.
[070525-13078-01.dmp]
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
BugCheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a portion of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: ffffa400bdbf8e50
Arg3: fffff509eeb48ff0
Arg4: fffff8028371ff99
*** WARNING: Unable to verify timestamp for sysdiag.sys
....
PROCESS_NAME: re4.exe
MODULE_NAME: rdbss
IMAGE_NAME: rdbss.sys
IMAGE_VERSION: 10.0.19041.5848
FAILURE_BUCKET_ID: 0x7f_8_rdbss!RxFsdCommonDispatch
.............................
Stack overflow error caused by an application (process) re4.exe when referring to Redirected Drive Buffering SubSystem. The probable causes may be different, ranging from incorrect re4 application code to hardware problems with the hard disk or memory (according to stack information).
Unfortunately, due to the peculiarities of writing this dump, the debugger command to output hardware information does not work, so it is not possible to check, for example, memory modules.
First, carefully examine the source code of your application for correct access to the OS drivers. For a more detailed review of the source code, I recommend asking a question about problematic areas of the code in the developer help section (the "Windows Development" tag, the "Windows API" child tag —
Win32"), so that programming specialists can help you.