Long ago I learned that the first troubleshooting step in an overclocked system is to remove the overclock. This is for 2 reasons:
1) in case the overclock is at fault (and it hasn't damaged any hardware yet) - this will fix the problem.
2) the tests we use for troubleshooting are based on a standard system operating normally - so an overclocked system won't necessarily give correct results because of the stress on the components. This is why I recommend stopping the overclock completely while troubleshooting.
Also, I found that overclocks will degrade over time - the system just won't be able to hold a high overclock forever. The system will get older and it's tolerance for this sort of stress will lessen - resulting in more errors.
Finally, hardware errors aren't necessarily just hardware, they can be:
- borked (broken) hardware (several different procedures used to isolate the problem device)
- BIOS problems (check for updates at the motherboard manufacturer's website)
- overclocking - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- compatibility issues (3rd party hardware/drivers)
- low-level driver problems
- or even malware (scanned for when we ask for hardware diagnostics from Initial Hardware Diagnostics or Hardware Diagnostics ).
You're not using UEFI/Seecure Boot:
I noticed that you don't have Secure Boot and/or UEFI enabled. If you were having problems with it and changed it, please let us know.
It's not necessary to enable it now. But, should you reinstall Windows at some point in the future, please enable it first.
I mention this because it may happen that (one day) the system won't boot. This can be caused by a program changing your UEFI settings, or an update of the UEFI resetting it to default values.
To test and see if this is the cause, boot into the UEFI and see if the settings have been changed. If uncertain, try with Secure Boot both on and off (and the UEFI on UEFI or Legacy (CSM))
If it still doesn't boot after trying this, then move on to other troubleshooting tools as it's not likely to be due to this.
Riva Tuner (along with MSI Afterburner and EVGA Precision) are known to cause BSOD's in some Windows systems (it's driver is usually RTCore64.sys). Please un-install them immediately!
In the WER section of MSINFO32, one of the memory dumps points to ha20x22k.sys - a driver for your Creative Sound Card. I'd start by ensuring that you have the latest Win8.1 compatible drivers for it. If there are no 8.1 compatible drivers, then I'd suggest uninstalling the software for the card and then physically removing the card from the system in order to see if that helps with the BSOD's.
Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :
LGBusEnum.sys Mon Nov 23 20:36:48 2009 (4B0B38B0)
Logitech Keyboard
http://www.carrona.org/drivers/driver.php?id=LGBusEnum.sys
LGVirHid.sys Mon Nov 23 20:36:48 2009 (4B0B38B0)
Logitech Gamepanel Virtual HID Device Driver
http://www.carrona.org/drivers/driver.php?id=LGVirHid.sys
If all of this doesn't stop the BSOD's, please run Driver Verifier according to these instructions:
Driver Verifier Settings
Also, these are STOP 0x124 errors. As such, they have a high chance of being hardware related. Please run these free hardware diagnostics:
Hardware Diagnostics. Let us know the results and we can move on from there.
Analysis:
The following is for informational purposes only.
Code:
[font=lucida console]**************************Thu May 1 01:27:15.982 2014 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\050114-6796-01.dmp]
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Built by: [B]9600[/B].17041.amd64fre.winblue_gdr.140305-1710
System Uptime:[B]0 days 2:45:12.626[/B]
Probably caused by :[B]GenuineIntel[/B]
BugCheck [B]124, {0, ffffe001c11cd028, bf800000, 124}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000124]WHEA_UNCORRECTABLE_ERROR (124)[/url]
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe001c11cd028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR: 0x124_GenuineIntel
PROCESS_NAME: DayZ.exe
FAILURE_BUCKET_ID: [B]0x124_GenuineIntel__UNKNOWN[/B]
CPUID: "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed: 3500
CurrentSpeed: [B]3500[/B]
BIOS Version 1402
BIOS Release Date 01/28/2014
Manufacturer ASUS
Product Name All Series
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Apr 30 21:07:38.790 2014 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\043014-6703-01.dmp]
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Built by: [B]9600[/B].17041.amd64fre.winblue_gdr.140305-1710
System Uptime:[B]0 days 0:01:18.435[/B]
Probably caused by :[B]GenuineIntel[/B]
BugCheck [B]124, {0, ffffe00007fef028, bf800000, 124}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000124]WHEA_UNCORRECTABLE_ERROR (124)[/url]
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe00007fef028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR: 0x124_GenuineIntel
PROCESS_NAME: svchost.exe
FAILURE_BUCKET_ID: [B]0x124_GenuineIntel__UNKNOWN[/B]
CPUID: "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed: 3500
CurrentSpeed: [B]3500[/B]
BIOS Version 1402
BIOS Release Date 01/28/2014
Manufacturer ASUS
Product Name All Series
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]
3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
Code:
[font=lucida console]**************************Thu May 1 01:27:15.982 2014 (UTC - 4:00)**************************
[COLOR=RED][B]LGBusEnum.sys Mon Nov 23 20:36:48 2009 (4B0B38B0)[/B][/COLOR]
[COLOR=RED][B]LGVirHid.sys Mon Nov 23 20:36:48 2009 (4B0B38B0)[/B][/COLOR]
AsIO.sys Wed Aug 22 05:54:47 2012 (5034AC67)
CORK70.sys Wed Oct 31 04:55:40 2012 (5090E78C)
asahci64.sys Wed Jan 9 21:52:36 2013 (50EE2CF4)
ALSysIO64.sys Tue Mar 5 16:50:34 2013 (513668AA)
[COLOR=RED][B]RTCore64.sys Mon Mar 11 01:32:06 2013 (513D6C56)[/B][/COLOR]
e1i63x64.sys Wed Mar 20 03:37:29 2013 (51496739)
cthda.sys Wed Jul 3 03:45:44 2013 (51D3D6A8)
cthdb.sys Wed Jul 3 03:45:50 2013 (51D3D6AE)
iaStorA.sys Thu Aug 1 21:39:52 2013 (51FB0DE8)
dump_iaStorA.sys Thu Aug 1 21:39:52 2013 (51FB0DE8)
TeeDriverx64.sys Mon Aug 19 13:23:31 2013 (52125493)
intelppm.sys Thu Aug 22 04:46:35 2013 (5215CFEB)
Wof.sys Thu Mar 13 04:27:29 2014 (53216BF1)
nvvad64v.sys Fri Mar 21 13:42:58 2014 (532C7A22)
nvlddmkm.sys Wed Mar 26 17:42:33 2014 (533349C9)
[/font]
http://www.carrona.org/drivers/driver.php?id=LGBusEnum.sys
http://www.carrona.org/drivers/driver.php?id=LGVirHid.sys
http://www.carrona.org/drivers/driver.php?id=AsIO.sys
CORK70.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=asahci64.sys
http://www.carrona.org/drivers/driver.php?id=ALSysIO64.sys
http://www.carrona.org/drivers/driver.php?id=RTCore64.sys
http://www.carrona.org/drivers/driver.php?id=e1i63x64.sys
http://www.carrona.org/drivers/driver.php?id=cthda.sys
http://www.carrona.org/drivers/driver.php?id=cthdb.sys
http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
http://www.carrona.org/drivers/driver.php?id=dump_iaStorA.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverx64.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
Wof.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys