BSOD when playing games and watch youtube HD, error 0x0000124

Welcome to the forum.

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try: Stop 124 - What it means and what to try

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\admin\Downloads\SF_07-07-2014 (1)\SF_07-07-2014\070714-24102-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02e54000 PsLoadedModuleList = 0xfffff800`03099e90
Debug session time: Mon Jul  7 21:01:29.136 2014 (UTC + 6:00)
System Uptime: 0 days 1:43:04.102
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8004fa8028, b2000040, 800}

Probably caused by : GenuineIntel

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8004fa8028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000040, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000800, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  linpack64.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff800`0447ba98 fffff800`02e1da3b : 00000000`00000124 00000000`00000000 fffffa80`04fa8028 00000000`b2000040 : nt!KeBugCheckEx
fffff800`0447baa0 fffff800`02fe17d3 : 00000000`00000001 fffffa80`04a22a00 00000000`00000000 fffffa80`04a22a50 : hal!HalBugCheckSystem+0x1e3
fffff800`0447bae0 fffff800`02e1d700 : 00000000`00000728 fffffa80`04a22a00 fffff800`0447be70 fffff800`0447be00 : nt!WheaReportHwError+0x263
fffff800`0447bb40 fffff800`02e1d052 : fffffa80`04a22a00 fffff800`0447be70 fffffa80`04a22a00 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`0447bc90 fffff800`02e1cf0d : 00000000`00000004 00000000`00000001 fffff800`0447bef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`0447bcd0 fffff800`02e10e88 : 00000000`00000001 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`0447bd00 fffff800`02ed2f2c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`0447bd30 fffff800`02ed2d93 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`0447be70 00000001`403454a0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`3b3af868 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00000001`403454a0


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS

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

0: kd> !sysinfo cpuspeed
CPUID:        "Intel(R) Core(TM)2 Quad  CPU   Q8200  @ 2.33GHz"
MaxSpeed:     2330
CurrentSpeed: 2331

Read this thread: Stop 0x124 - what it means and what to try