try some of the things below, if none help then you can run verifier.exe and set debug flags to catch what is modifying the internal tables. The system was up 2hr 40 mins before windows detected the change in its internal table.
you have several machine problems but my guess is this driver ESEADriver2.sys is the cause of this bugcheck.
---------
first bugcheck, something modified a session import table.
the system ended up breaking while trying to read a performance Counter.
this could be a bug, a memory problem or a hack.
I would remove the overclocking software both of them:
RTCore64.sys
C:\Users\VALK~1\AppData\Local\Temp\ALSysIO64.sys Sat Jul 09 17:27:45 2011
(just too old for your newer CPU)
in terms of drivers this file date really does not look good:
likely a part of Pinnacle Studio's Marvin Bus (not really sure what this is)
\SystemRoot\System32\drivers\MarvinBus64.sys Fri Sep 23 14:17:03 2005
I would remove this as well:
\SystemRoot\SysWow64\drivers\AsIO.sys Wed Aug 22 02:54:47 2012
this driver is also suspect>
?\C:\Users\VALK~1\AppData\Local\Temp\ESEADriver2.sys Mon Jan 04 15:03:27 2016
it is installed from a temp directory, and the driver is too new. (I would suspect malware)
your machine:
BIOS Version 2406
BIOS Starting Address Segment f000
BIOS Release Date 05/15/2015
Manufacturer ASUSTeK COMPUTER INC.
Product Z97-C
Version Rev X.0x
Processor Version Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz
Processor Voltage 8ch - 1.2V
External Clock 100MHz
Max Speed 3900MHz
Current Speed 3500MHz
Facebook
Twitter
Instagram