Do two things.
► Download and install Malwarebytes Free version ... scroll down to this page. Boot the computer in safe mode and perform a full scan.
► Enable Driver Verifier to monitor the drivers.Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.
How Can we know that DV is enabled:
It will make the system bit of slow, laggy.
Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner
looking at Tools > System Restore.
If there is no points, make a System Restore Point manually
before enabling DV.
Let us know the results, with the subsequent crash dumps, if any.
** If you have anything installed from an unknown/warez source, uninstall it.
A driver has overrun a stack-based buffer. This overrun could potentially
allow a malicious user to gain control of this machine.
A driver overran a stack-based buffer (or local variable) in a way that would
have overwritten the function's return address and jumped back to an arbitrary
address when the function returned. This is the classic "buffer overrun"
hacking attack and the system has been brought down to prevent a malicious user
from gaining complete control of it.
Do a kb to get a stack backtrace -- the last routine on the stack before the
buffer overrun handlers and bugcheck call is the one that overran its local
Arg1: 0000000000000000, Actual security check cookie from the stack
Arg2: 000057ffc2fb06cf, Expected security check cookie
Arg3: ffffa8003d04f930, Complement of the expected security check cookie
Arg4: 0000000000000000, zero