the cpu called the error because of a internal timer error.
Error Type : Micro-Architectural Error
Severity : Fatal
Error : Internal timer (Proc 4 Bank 4)
Status : 0xbe00000000800400
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.
I see you have various drivers installed that cause various problems but none of them would cause this problem.
I would look for overheating problems (monitor temps) and power problems, check the voltages in the bios and compare them to what they should be.
https://www.lifewire.com/power-supply-voltage-tolerances-2624583
most of the bad drivers would break the graphic or usb subsystem which would be unrelated to this bugcheck.
generally when I see Error Type : Micro-Architectural Error
the problem is overheating or a power supply that is no longer providing correct voltages.
here are some of your other issues with your drivers:
AsrAppCharger.sys Tue May 10 01:28:46 2011
(this is a driver that overrides the usb power limits to charge Apple devices faster, it is also too old and does not have the 2012 updates to the USB 2 specs so it tend to break usb 2 devices and cause large amounts of error on the usb bus. I have seen some version generate 30 or 40 error logs a second, to the internal error log.
remove it if you don't use it, or update it to the current version if you do.
old driver:
Atheros Wireless LAN Driver
athw8x.sys Thu Jan 28 01:52:54 2016
(gets sold under different names for a network device, you have to look up the name, google to find its chipset and look for a new driver under the chipset name) (if the vendor does not provide the proper update)
Killer PCI-E Gigabit Ethernet Controller (these network drivers are modified to give you a gaming advantage, they have lots of bugs and you should look for a update from the motherboard vendor or killer networks)
e2xw10x64.sys Wed Sep 14 13:52:26 2016
https://www.killernetworking.com/
old version of Intel Smart Connect Technology Driver
ISCTD64.sys Tue Nov 27 11:52:34 2012
even intel stopped using this, you need to update the current version or disable it
best to update the version and disable it. (you don't want the bad driver version)
https://www.intel.com/content/www/us/en/support/products/65386/technologies/intel-smart-connect-technology.html
old versions of Logitech drivers for camera and webcam, update or remove if not being used.
lvrs64.sys Mon Oct 22 19:11:24 2012
lvuvc64.sys Mon Oct 22 19:12:08 2012
https://support.logitech.com/en_us/home
various old intel drivers:
TeeDriverx64.sys Tue Sep 23 13:01:14 2014
https://downloadcenter.intel.com/
just run the tool and it will detect the old version and provide new ones.
this driver has a bug:
Scarlet.Crush Productions Scp Dual Shock 3 Virtual Bus Driver
ScpVBus.sys Sun May 5 14:31:26 2013
but I don't think anyone has ever made a fix. the bug tends to cause random crashes and corrupt memory after about 9 hours. the driver does not pass verifier tests.
https://forums.pcsx2.net/Thread-XInput-Wrapper-for-DS3-and-Play-com-USB-Dual-DS2-Controller?pid=186161#pid186161
very old motherboard sound drivers, fixes came out in aug 2017 and about 2 months ago for problems that would crash current GPU drivers. look to see if the motherboard vendor has a update. if not you have to look at the motherboard specs to see what sound chip version is being used then go to the chips vendors website and download the driver that is for that chip number:
Realtek High Definition Audio Function Driver
RTKVHD64.sys Tue Jul 30 05:06:46 2013
(they moved files around on their website but this link will get you to the site, you might have to dig to find the correct driver)
https://www.realtek.com/en/component/zoo/advanced-search/461?Itemid=276
you should also check your razer devices, you have updated drivers but some might also require a firmware update the actual device. it could be something that could mess up the timer.
you should also change your memory dump type to kernel and provide the next kernel memory dump. it will include info on your hardware, the timer tables and the internal error logs.
the file will be stored as c:\windows\memory.dmp (different directory and file name)
most of these issues will mess up virus scanners and usb devices, streaming software and the gpu
but should not cause this bugcheck.
again none of these would normally cause this bugcheck. but it can not hurt to do the updates.
chris.freshmaker :
johnbl :
the bugcheck info indicates that the cpu called a bugcheck because of a internal problem. Most likely the wrong voltage was being applied for the clock rate.
the first fix attempt would be to update your bios version from the p1.00 version dated 04/24/2014
to the current one v 2.60 dated march of 2018
the most likely cause of this bugcheck is the old bios is applying too high of a voltage to the cpu.
your cpu came out june of 2014 and uses a lower voltage than the cpus that were released before it.
you bios came out 4/2014 and will have the wrong voltage/clock rate table.
the bios update should fix the problem.
I think this is the motherboard:
https://www.asrock.com/MB/Intel/Fatal1ty%20Z97X%20Killer/index.asp#BIOS
Okay I updated the bios, and everything with that went fine, but I'm still crashing and getting the same WHEA_UNCONTROLLABLE_ERROR BSOD after about an hour of playing.
On top of that the debugger I was using (Windbg) stopped working and now wont install off the windows store anymore so I'm don't know how to make any new dump files readable. Here's the dump file itself.
http://s000.tinyupload.com/?file_id=07875280373959098716
Let me know if there's a better way to get you that file in the future.
Facebook
Twitter
Instagram