The .dmp files are evenly split between ntkrnlmp.exe (which is a core Windows file and not likely to cause a BSOD) and e1q62x64.sys which is part of your Intel based Ethernet Adapter..
Update it here...
Intel® Driver Update Utility
http://downloadcenter.intel.com/
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {9, 2, 0, fffff8800167d616}
Unable to load image \SystemRoot\system32\DRIVERS\e1q62x64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for e1q62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e1q62x64.sys
Probably caused by : e1q62x64.sys ( e1q62x64+21219 )
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {0, 2, 8, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
Followup: MachineOwner
---------
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffff8000b05b644, f, 0, fffff80002e740a9}
Probably caused by : ntkrnlmp.exe ( nt!EtwpAllocateFreeBuffers+1c1 )
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {9, 2, 0, fffff8800167a616}
Unable to load image \SystemRoot\system32\DRIVERS\e1q62x64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for e1q62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e1q62x64.sys
Probably caused by : e1q62x64.sys ( e1q62x64+239e9 )
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {a0, 2, 0, fffff88011e1b867}
Unable to load image \SystemRoot\system32\DRIVERS\e1q62x64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for
*** ERROR: Module load completed but symbols could not be loaded for e1q62x64.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c000001d, fffff80002edccf9, fffff8800912e120, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiTryUnwaitThread+49 )
Followup: MachineOwner
---------
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff8000315ddf8, 0, 2}
Probably caused by : ntkrnlmp.exe ( nt!CmpBuildHashStackAndLookupCache+418 )
Followup: MachineOwner
---------