Windows 8 BSOD

Solution
overall, run a malwarebytes scan, update two drivers, reboot and see if you still get the bugcheck.
if you do, post the memory dump again and I will tell you what you need to do to figure out the problem.

===========

I looked at the bugcheck dump and you have a few suspect drivers
I would update (or remove)
SystemRoot\System32\drivers\ISCTD64.sys Tue Nov 27 11:52:34 2012

from here:https://downloadcenter.intel.com/SearchResult.aspx?lang=eng&keyword=Intel%20Smart%20Connect

the second driver is
\SystemRoot\system32\DRIVERS\Rt630x64.sys Wed Oct 19 05:12:55 2011
get the driver from realtek website or from your motherboard vendor if they have a update.
http://www.realtek.com.tw/downloads/
you have to dig around for it

MSI website should...
overall, run a malwarebytes scan, update two drivers, reboot and see if you still get the bugcheck.
if you do, post the memory dump again and I will tell you what you need to do to figure out the problem.

===========

I looked at the bugcheck dump and you have a few suspect drivers
I would update (or remove)
SystemRoot\System32\drivers\ISCTD64.sys Tue Nov 27 11:52:34 2012

from here:https://downloadcenter.intel.com/SearchResult.aspx?lang=eng&keyword=Intel%20Smart%20Connect

the second driver is
\SystemRoot\system32\DRIVERS\Rt630x64.sys Wed Oct 19 05:12:55 2011
get the driver from realtek website or from your motherboard vendor if they have a update.
http://www.realtek.com.tw/downloads/
you have to dig around for it

MSI website should have the current onboard ethernet driver for this under your motherboard version. http://us.msi.com/
Manufacturer MSI
Product B75MA-P45 (MS-7798)
Version 1.0



=========
basically, windows detected a stack overrun and took that modified a critical windows memory structure.
It shut the system down because of it. Malware can use stack overruns to gain access to critical windows core components.

I would start by doing a malwarebytes scan and seeing if it turns up anything.
The problem can also be caused by simple driver bugs.
I will look in the memory dmp to see if I can see something obvious, but most of the time you can not tell with out turning on some special tracking with the verifier.exe command.
 
Solution