forth bugcheck was also a bad memory address passed to the windows kernel, remove overclocking software
third bughceck was a bad memory address coming out of the directx video subsystem.
remove the overclocking software: (best guess)
C:\Program Files\AMD\ATI.ACE\Fuel\amd64\AODDriver2.sys Tue Feb 11 03:06:52 2014
--------------
second bugcheck was running eseaclient.exe
it also was a bad memory address coming out of the filesystem.
I would run cmd.exe as an admin then run
sfc.exe /scannow
dism.exe /online /cleanup-image /restorehealth
I would also run
fltmc.exe
it will display the list of filter drivers on your machine.
here is my list: (just look for something not in my list and we can find out what it is)
C:\WINDOWS\system32>fltmc
Filter Name Num Instances Altitude Frame
------------------------------ ------------- ------------ -----
wcnfs 0 409900 0
WdFilter 4 328010 0
storqosflt 0 244000 0
wcifs 0 189900 0
FileCrypt 0 141100 0
luafv 1 135000 0
npsvctrig 1 46000 0
FileInfo 4 45000 0
Wof 3 40700 0
-------------------
first bugcheck was cause by the windows search indexer, it make a call that went thru some filter driver on your machine, then hit the file system and filesystem ended up calling a bugcheck because of a bad memory address.
I can not read what filter services you have installed on the machine with a mini dump, the info is only stored with a kernel memory dump.
the search index service might be hitting a problem with your filesystem or the memory address might have been modified as it was sent to the file system.
(malware)
your machine was up 3 minutes. I would boot, start cmd.exe as an admin then type
net.exe stop "windows search"
(you need to have the quotes in this case)
this should give you more time before it crashes again.
I would then delete the windows search index database
look here
http://www.thewindowsclub.com/windows-edb-file
(or google for better instructions)
and do a
chkdsk /f C:
----------
overclock driver:
C:\Program Files\AMD\ATI.ACE\Fuel\amd64\AODDriver2.sys Tue Feb 11 03:06:52 2014
driver loaded out of a temp directory: (just not a good practice, often indicates malware)
E-Sports Entertainment LLC.
C:\Users\Joe\AppData\Local\Temp\ESEADriver2.sys Thu May 19 22:07:38 2016
I would also go into bios and look at what mode the SATA controller is set to, it kind of looks like it is set to IDE mode which is going to be the slowest.
most systems would be set in AHCI mode. you can change the mode but if the system was installed in IDE mode you have to make a registry setting in windows before you change the BIOS mode or your system will not boot (until you change it back)
look here or google for instructions:
http://www.tomshardware.com/answers/id-2795928/switch-ide-ahci-windows.html
machine info:
BIOS Version F5
BIOS Starting Address Segment f000
BIOS Release Date 08/06/2013
Manufacturer Gigabyte Technology Co., Ltd.
Product 970A-D3P
Processor Manufacturer AMD
Processor ID 200f6000fffb8b17
Processor Version AMD FX(tm)-6300 Six-Core Processor
Processor Voltage 8dh - 1.3V
External Clock 200MHz
Max Speed 4200MHz
Current Speed 4200MHz
memory:
Speed 667MHz
Manufacturer Corsair
Part Number CMZ8GX3M2A186
bios update:http://www.gigabyte.com/products/product-page.aspx?pid=4642#bios