Speccy does not show anything wrong related to temperature or hardware that is obvious...
The crash dumps were all from October so I am not certain if they are relevant...
0x50 was your most common crash, here is info about that directly from microsoft:
Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache (CPU), or video RAM).
Another common cause is the installation of a faulty system service.
Antivirus software can also trigger this error, as can a corrupted NTFS volume.
One of the crash dumps was caused by Avast so my first move would be to uninstall avast.
If that changes nothing I would recommend running memtest: download and burn this file directly to disc, do not extract: Download - Pre-Compiled Bootable ISO (.zip) Then boot to the disc and run at least 2 passes. See if you have any errors.
If the ram shows no errors, my next step would be to run prime95: http://files.extremeoverclocking.com/file.php?f=205 to test the cpu, and then furmark: http://www.ozone3d.net/benchmarks/fur/ to test the video card.
You can look in event viewer at the exact times that these things happen and see if there is anything noted: to open event viewer, in the start menu, search programs and files type in event viewer and hit enter. Then click the windows logs and then system. The exact time would be most helpful.
The only other crash 0xA info and possible solutions:
BCCode: 0A 0x0000000A
This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.
The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.
If you encounter bug check 0xA while upgrading to a later version of Windows, this error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.
Resolving the Problem
If a kernel debugger is available, obtain a stack trace.
To resolve an error caused by a faulty device driver, system service, or BIOS
- Restart your computer.
- Press F8 at the character-based menu that displays the operating system choices.
- Select the Last Known Good Configuration option from the Windows Advanced Options menu. This option is most effective when only one driver or service is added at a time.
To resolve an error caused by an incompatible device driver, system service, virus scanner, or backup tool
- Check the System Log in Event Viewer for error messages that might identify the device or driver that caused the error.
- Try disabling memory caching of the BIOS.
- Run the hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owner's manual for your computer.
- Make sure the latest Service Pack is installed.
- If your system has small computer system interface (SCSI) adapters, contact the adapter manufacturer to obtain updated Windows drivers. Try disabling sync negotiation in the SCSI BIOS, checking the cabling and the SCSI IDs of each device, and confirming proper termination.
- For integrated device electronics (IDE) devices, define the onboard IDE port as Primary only. Also, check each IDE device for the proper master/subordinate/stand-alone setting. Try removing all IDE devices except for hard disks.
Edited by zingo156, 28 February 2014 - 01:32 PM.