Sorry for interrupting your thread but I'll try and give a bit of advice, it looks possibly virus related.
You are getting driver related crashes, the driver responsible cannot be identified in terms of I can find no information on it.
I think the cause can be one of two things.
Firstly it could be virus related so I recommend running a full scan with your Avast AV, then download and run malwarebytes anti malware to scan for viruses.
http://www.malwarebytes.org/
Make sure you untick the box that starts a free trial of malwarebytes pro
The other issue it could be is you've accidentally installed a driver that contains bugs.
I would try the virus root first as uninstalling an unknown driver
could have fatal consequences.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff880033a2ff8, 0, fffff80002ccc816, 0}
Unable to load image \SystemRoot\system32\DRIVERS\9573898drv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for 9573898drv.sys
*** ERROR: Module load completed but symbols could not be loaded for 9573898drv.sys
Could not read faulting driver name
Probably caused by : [COLOR="Red"]9573898drv.sys[/COLOR] ( 9573898drv+4bc41 )
Followup: MachineOwner
Actually, looking at your other dump files it looks very probable that the cause is virus related as you're getting all sorts of bugchecks.
NETIO.SYS which is the Network Input Output Subsystem, this generally means a network driver is causing an illegal operation or it's getting the blame.
You're also getting bugchecks that point to
usbehci.sys which is the usb miniport driver.
nvlddmkm.sys which is the Nvidia video card graphics driver.
Intelppm.sys which is the Intel Processor driver.
All these are very suspicious and most of all random with little correlation between them.
Please do as I've stated above and post back the results.
As Harribo stated it could be heat related, better to be safe than sorry.
Post back the results.