The last dumpfiles are all very different.
Code:
BugCheck A, {b0, 2, 0, fffff800862a54a7}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Followup: memory_corruption
---------
BugCheck 50, {ffffffffffffffe8, 0, ffffd1d622a49d88, 0}
Could not read faulting driver name
Probably caused by : win32kfull.sys ( win32kfull!TimersProc+88
BugCheck 139, {3, ffffd800fdedfae0, ffffd800fdedfa38, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiFastFailDispatch+d0 )
BugCheck A, {10200000005, 2, 0, fffff800f46eb844}
Probably caused by : memory_corruption
Followup: memory_corruption
BugCheck 124, {0, ffff8e8ac5cea028, be000000, 800400}
Probably caused by : GenuineIntel
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffff8e8ac5cea028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.
BugCheck 3B, {c0000005, 0, ffffa881c7e38a90, 0}
Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGADAPTER::DdiEscape+de )
Followup: MachineOwner
The differing error codes are usually symptomatic of a lower level problem within the system. They are usually caused by one of these things:
- faulting (broken) hardware (several different procedures used to isolate the problem device)
- BIOS issues (check for updates at the motherboard manufacturer's website)
- overclocking/overheating - You'll know if you're overclocking or not. Please stop at least during troubleshooting.
- compatibility issues (3rd party hardware/drivers)
- low-level driver/system problems within windows (SFC/DISM)
- or even malware.
In many dumpfiles the proces was PROCESS_NAME: TUFLOW_iSP_w64. (hopes this give a clue).
A few dumpfiles point to memory corruption, testing your memory could be necessary. Although this is troublesome as you mentioned in your post.
So start first with.
There are newer bios version for your mobo here Access Denied
Looking through your drivermodules i found this older drivers.
And in the unloaded modules there are references to your Kaspersky software and Aladdin/Safenet software ?.
aksdf Thu Oct 17 10:47:38 2013
Driver Description: Data Filter Driver by Aladdin Knowledge Systems
Driver Update Site: Aladdin Knowledge Systems: Support
e1d65x64 Thu Aug 13 11:14:29 2015
Driver Description: Intel Pro/1000 Network Adapter driver
Driver Update Site: Drivers & Software
iocbios2 Thu May 28 22:42:10 2015
Driver Description: Intel Extreme Tuning Utility - Desktop Control
Driver Update Site: Drivers & Software
kl1 Thu Jun 18 20:58:13 2015 (558314
klbackupdisk Tue Jun 02 22:18:33 2015 (556E0F99)
klbackupflt Thu Nov 26 10:59:25 2015 (5656D7FD)
kldisk Tue Nov 10 14:38:35 2015 (5641F35B)
klflt Fri Dec 04 14:27:50 2015
part of Kasparsky
Sentinel64 Mon Jun 02 08:14:55 2008
Driver Description: Rainbow Tech/SafeNet USB Security Device
Driver Update Site: Technical Support | Gemalto Troubleshooting guide: http://www.integratedsoft.com/suppor...ting_Guide.pdf
And install latest version of speedfan.
Also if you use it update to the latest version of the Asus Utilities or uninstal.
First look for updating these driver from your supportpage and also check if all the other drivers have the latest version installed.