BIOS dates from 2012. Check to see if there are any updates for it.
No Windows Updates installed. My system has 2 updates. Please check and install any available updates
The WER section of MSINFO32 shows a lot of 0xEF STOP errors and a single 0xF7 error. I'd start by suspecting hardware issues and would suggest running these free diagnostics: Hardware Diagnostics
AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Windows systems.
NOTE:these symptoms were from the previous release of OverDrive. The new release uses the same driver name, but is dated from 4 November 2013.
Please un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program
Then, download (but DO NOT install) a fresh copy of the ATI drivers from Global Provider of Innovative Graphics, Processors and Media Solutions | AMD (in the upper right corner of the page)
Use this procedure to install the
DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure - Sysnative blog
If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Un-install". Reboot for changes to take affect.
Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.
If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.
XENfiltv.sys is outdated (Thu Jul 30 23:40:32 2009) and likely not compatible w/Win10. It belongs to your Sound Blaster card.
If unable to find an updated, Win8.1 compatible driver (or a WIn10 driver), I would suggest removing the software for this card and then physically removing the card from the system to test to see if it's to blame for the BSOD's.
Analysis:
The following is for informational purposes only.
Code:
**************************Thu Apr 9 19:11:19.072 2015 (UTC - 4:00)************************** Loading Dump File [C:UsersJohnSysnativeBSODApps