OK so had a look at your Dumpfiles and system info, you seem to be getting two differnt errors, the newest indicating a hardware failure of a USB device pluggedi nto your system:
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck FE, {5, fffffa8004ec01a0, 10024398, fffffa80046b5258}
Probably caused by : usbohci.sys ( usbohci!OHCI_PollIsoEndpoint+5d )
Followup: MachineOwner
---------
3: kd> !analyze -v
ERROR: FindPlugIns 80070005
ERROR: Some plugins may not be available [80070005]
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
using a physical memory address that was not allocated by
the USBport driver.
Arg2: fffffa8004ec01a0, Device extension pointer of the host controller
Arg3: 0000000010024398, PCI Vendor,Product id for the controller
Arg4: fffffa80046b5258, Pointer to Endpoint data structure
Debugging Details:
------------------
This could be anything that is plugged in to a USB port, I would slowly remove everything that is usb, or remove everything you don't need that is plugged into a USB port and see if this helps stabilize the system
The second seems to be caused by either a driver malfunctioning or by a memory problem:
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41790, fffffa80034d9bb0, ffff, 0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::Free+a2 )
Followup: MachineOwner
Now for this on i would like you to enable Driver Verifier and let it run for at least 24 hours and then post back with your new crash dumps once you get a BSOD. Heres a tutorial on how to do that:
Driver Verifier - Enable and Disable
WARNING: If you can not boot into windows normally after enabling Driver verifier boot into Safe Mode and then Disable Driver verifier, then boot normally and post your new crash dumps.