BSOD while playing games, or just randomly 0x124 and others

[angryandconfuse]

Hi, after several months of having this BSOD and a few weeks of using this computer with less issues after I actually spent time debugging, my problems start coming back to me aGAIn and again and again!!!!!!
Usually this occurs while i game (LoL, Skyrim, Tera) but can happen while i'm not gaming.

I bought a new cpu cooler, used fail safe default settings on my BIOS, cleaned the dust from my computer, updated my drivers, memtest each memory YET I STILL GET BSOD 0x124 daily, sometimes once every hour. On a weekly basis I get a "Stop 0x00000101 A clock interrupt was not received on a secondary processor within the allocated time interval." bsod also. Sometimes my computer locks up and freezes and couldn't do anything til i restart it.

Lastest DUMP from today (bsod 0x124)

________________________________________________________________________________________

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: srv*
Executable search path is: srv*
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18205.amd64fre.win7sp1_gdr.130708-1532
Machine Name:
Kernel base = 0xfffff800`03063000 PsLoadedModuleList = 0xfffff800`032a66d0
Debug session time: Sat Aug 24 20:40:10.539 2013 (UTC - 6:00)
System Uptime: 0 days 0:08:57.381
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffd3018). Type ".hh dbgerr001" for details
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800723d028, f2000000, 20008f}

Probably caused by : GenuineIntel

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

4: 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: fffffa800723d028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000020008f, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR: 0x124_GenuineIntel

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: csrss.exe

CURRENT_IRQL: f

STACK_TEXT:
fffff880`009bab58 fffff800`0302ca3b : 00000000`00000124 00000000`00000000 fffffa80`0723d028 00000000`f2000000 : nt!KeBugCheckEx
fffff880`009bab60 fffff800`031ef453 : 00000000`00000001 fffffa80`0669fc80 00000000`00000000 fffffa80`0669fcd0 : hal!HalBugCheckSystem+0x1e3
fffff880`009baba0 fffff800`0302c700 : 00000000`00000728 fffffa80`0669fc80 fffff880`009baf30 fffff880`009baf00 : nt!WheaReportHwError+0x263
fffff880`009bac00 fffff800`0302c052 : fffffa80`0669fc80 fffff880`009baf30 fffffa80`0669fc80 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009bad50 fffff800`0302bf0d : 00000000`00000008 00000000`00000001 fffff880`009bafb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009bad90 fffff800`0301fe88 : 00000000`00000000 fffff880`0deb8d90 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009badc0 fffff800`030d746c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009badf0 fffff800`030d72d3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009baf30 fffff960`00124198 : fffff880`0deb8d90 00000000`00000000 fffff880`0deb8f00 00000000`01086ce0 : nt!KiMcheckAbort+0x153
fffff880`0deb8bb0 fffff960`00123cd2 : 00000000`00000031 00000000`00000000 fffff880`0deb8d90 00000000`01086d5c : win32k!ExecutePhaseControl+0x4c
fffff880`0deb8be0 fffff960`000ebe75 : 00000000`01086d56 fffff960`00000000 fffff880`00000140 00000000`00000014 : win32k!itrp_IUP+0xa2
fffff880`0deb8cd0 fffff960`0010fb38 : 00000753`00000428 000078ac`ffffffff 0000087a`00000410 ffffff2c`ffffff96 : win32k!itrp_InnerExecute+0x35
fffff880`0deb8d00 fffff960`000ebf12 : fffff900`c21b0d00 00000000`01086d5c 00000000`00000000 fffff960`000eb8f5 : win32k!itrp_Execute+0x390
fffff880`0deb8e20 fffff960`00110eb3 : 00000000`0000007c 00000000`00000001 fffff900`c21b0d00 fffff900`c21ac658 : win32k!itrp_ExecuteGlyphPgm+0x7a
fffff880`0deb8e70 fffff960`001100d2 : 00000000`00000000 fffff900`c21b1e60 fffff900`c21ae1f0 00000000`00000000 : win32k!fsg_SimpleInnerGridFit+0x323
fffff880`0deb8f20 fffff960`0010fd64 : 00000000`00000007 fffff900`c21ac34c fffff900`c21ae1f0 fffff880`00000007 : win32k!fsg_ExecuteGlyph+0x2ce
fffff880`0deb9040 fffff960`0010cbfb : fffff900`c21ac1b8 fffff900`00000001 fffff900`c21ac600 fffff900`c21b0d00 : win32k!fsg_CreateGlyphData+0x194
fffff880`0deb9110 fffff960`0010c8d9 : fffff900`c21ac020 fffff900`c21ac0d0 00000000`00000000 00000000`00000004 : win32k!fsg_GridFit+0xb7
fffff880`0deb91a0 fffff960`0010c335 : 00000000`01000000 fffff900`c21ac0d0 fffff880`00000001 00000000`00000000 : win32k!fs__Contour+0x551
fffff880`0deb9270 fffff960`0010d1dc : fffff900`c071e030 fffff880`0deb9610 00000000`00000000 00000000`00000001 : win32k!bGetGlyphOutline+0x129
fffff880`0deb92b0 fffff960`0010d148 : fffff900`c071e030 00000000`0000005e 00000000`0000005e 00000000`ffffffff : win32k!lGetGlyphBitmap+0x4c
fffff880`0deb9470 fffff960`0010ce76 : 00000000`00000000 00000000`ffffffff fffff900`c2311010 fffff900`c2311010 : win32k!ttfdQueryFontData+0x278
fffff880`0deb94d0 fffff960`000e0bba : fffff960`0010ce04 fffff900`c2311010 00000000`00000001 fffff800`00000004 : win32k!ttfdSemQueryFontData+0x72
fffff880`0deb9530 fffff960`000e0cdb : fffff900`c2311010 fffff900`c22a4310 00000000`0000005e fffff880`0deb9730 : win32k!PDEVOBJ::QueryFontData+0x82
fffff880`0deb95c0 fffff960`000dda68 : fffff900`c0081000 fffff880`0deb9a50 00000000`00000040 fffff800`030e1a8b : win32k!xInsertMetricsRFONTOBJ+0xe3
fffff880`0deb9680 fffff960`0010ad2a : 00000000`00000000 00000000`00000060 00000000`00000040 00000000`00000020 : win32k!RFONTOBJ::bGetGlyphMetrics+0x178
fffff880`0deb9700 fffff960`0010aa80 : fffff8a0`169d6d60 fffff8a0`026776f0 fffff8a0`026776f0 fffff800`033d1054 : win32k!GreGetCharABCWidthsW+0x22a
fffff880`0deb9b20 fffff800`030d7e13 : 00000000`7b010cde 0000007f`00000040 fffffa80`00000040 00000000`00000000 : win32k!NtGdiGetCharABCWidthsW+0x1b0
fffff880`0deb9bb0 00000000`742b1e8a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0da8e3e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x742b1e8a


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_MEMORY__UNKNOWN

BUCKET_ID: X64_0x124_GenuineIntel_MEMORY__UNKNOWN

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

4: kd> lmvm GenuineIntel
start end module name
_____________________________________________________________________________________

Please help!!!!!!!!

 

[angryandconfuse]

Btw, SF Diag does not work for me. When I start it it always freezes soryr i couldnt help you there.

 

[koolkat77]

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