The download links are in Deutsche (this is an English forum and all of our analysts use English as a common language). Luckily I spent enough time in Germany that I can understand the prompts - others may not be able to understand it though.
FWIW - you can upload .zip files here. I don't know about .rar, as I don't use them myself.
Please stop overclocking while we're troubleshooting this problem:
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 ).
Some systems will "auto" overclock - and I'm seeing more and more of this in Win8 systems.
Please wait until the system freezes, then recover from the freeze and immediately generate this report:
Please do the following:
- open Event Viewer (run eventvwr.msc from the "Run" dialog)
- expand the Custom Views category (left click on the > next to the words "Custom Views")
- right click on the "Administrative Events" heading
- select "Save all Events in Custom View as..."
- save the file as Admin.evtx
- zip up the file (right click on it, select "Send to", select "Compressed (zipped) folder")
- upload it with your next post (if it's too big, then upload it to a free file-hosting service and post a link here).
FYI - If we're looking for Event ID 41 errors (unexplained shutdowns), there's more info on that here: http://support.microsoft.com/kb/2028504
While waiting for a reply, please monitor your temps with this free utility: http://www.cpuid.com/softwares/hwmonitor.html
Your UEFI/BIOS (version P1.90) dates from 2010. Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system. If you are able to install the update through Windows (without booting from an external drive), then go ahead and update it. WARNING - if the computer might shut down during this procedure, please don't do it, as this may physically damage the computer and prevent it from booting.
Also, W8/10 communicates with the BIOS/UEFI much more than W7 and earlier. As such, a problem in the BIOS (if it's not compatible w/W10) can cause problems that aren't fixable (in other words, you may have to revert to W7 to get acceptable performance).
Only 6 Windows Update hotfixes installed. Most build 10586 (TH2/1511) systems have more than this. Please visit Windows Update and get ALL available Windows Updates.
The actual number is not important. Rather it's important that you checked manually, installed any available updates, and didn't experience any errors when checking or updating.
On 08 May 2016 (at 08:58) you experienced a STOP 0x124 BSOD error
I hope to confirm this with the Admin log that I requested earlier in this post - as there wasn't a memory dump in the uploaded files (nor is one listed in the KernelDumpFiles.txt report).
But, in general, the STOP 0x124 error is most often a hardware error - but it can be caused by compatibility issues, or even by low-level drivers.\
As such, please start with these free hardware diagnostics: http://www.carrona.org/hwdiag.html
Edited by usasma, 05 June 2016 - 06:43 AM.