bug in battleye service and driver, you will have to get a updated version from them.
-------
this bugcheck shows that verifier did catch the game anticheat software messing up.
basicaly, BEService.exe passed a usermode handle to its companion driver
\C:\Program Files (x86)\Common Files\BattlEye\BEDaisy.sys
that driver then used it as a kernel mode handle and corrupted the stack.
generally, this should not be done but would mostly work if the driver locks down the memory at each call.
Problem, the systems memory manager is free to move the memory around if it needs to for some reason and the driver will bugcheck if it used the old memory address (the address my have another drivers data)
this is a bug in the design of battleye software.
it looks like your system was up for 11 mins and 30 seconds before verifier caught the bug.
here is the debug info:
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000e2, IRP field is a user-mode address but Irp->RequestorMode is KernelMode.
Arg2: ffffcf80c0b2e790, IRP address.
Arg3: 00000000010b3040, User-mode address present as the value of an IRP field.
Arg4: 0000000000000000