BSOD Playing League of Legends, other processor intensive tasks

[Hoosteen]

Having random BSODs when I play games or do processor-intensive tasks like watch videos. I haven't made any changes in my hardware recently so I don't see why this should be happening.

Information from crash window:

BCCode: fc
BCP1: 000186A0
BCP2: 7AD6D847
BCP3: 8E2CBC04
BCP4: 00000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Thanks in advance.

 

[Arc]

There was Stop 0x124 BSOD last week. So it is to take care at first.

The BIOS is old, of 2009; but the latest.

Make it sure that the SSD is running with the latest firmware.
How to Upgrade Samsung SSD Firmware | StorageReview.com - Storage Reviews

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know the wattage of the PSU.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Let us know the results.
__________________________________________________________________________________________

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR=Red]BugCheck 124[/COLOR], {[COLOR=Red]0[/COLOR], 8647076c, 0, 0}

Probably caused by : hardware

Followup: MachineOwner
---------