Intermittent BSOD while gaming, 0x0000124

juxstapo · 17 Oct 2013

Getting this one with increased frequency lately, either it's only happening when I'm running rather graphically intensive games with several other applications going in the background (Teamspeak or FRAPs), or... thats just the only time I notice it; which is possible since this is my nothing but gaming rig. I do pop on to surf or listen to music for short spurts, or let my kids watch netflix on it and don't seem to experience this issue under those light loads

I've removed the (very mild) overclocks from the proc and GPU. Thought it might be heat but temps are showing fine across the board (cleaned the collection of fans anyway).

I've patch'n'hacked (the junkyard wars kind of "hack",

not the computer literate kind of "hack") several so called gaming-rigs over the years. Vis-a-vis questionable upgrades to OEM boxes, but this is my first completely built-from-scratch lightsab

err.. computer. So I'd place user/assembler error high on the list of potentials.

here's my measurements:

Urph, I think I followed teh BSOD posting instructions properly, but I'll not wager money on it.

Arc · 19 Oct 2013

A stop 0x124 is mainly a hardware related BSOD.

What is expected for an overclocked system that it may face stop 0x124 BSODs .... so you need to revert your hardware back to stock settings and observe the situation.

Code:

CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3399

Also, a latest BIOS update is a good plan to fight against stop 0x124. Plan to get the Version 4105 dated 2013.07.23 from ASUSTeK Computer Inc. -Support- Drivers and Download P8Z68-V LX . Yours is ....

Code:

BiosVersion = 3703
BiosReleaseDate = 03/02/2012

Need to check some info .... like ....

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.
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 your PSU.

Need to perform some hardware tests.

► 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

Dont run Logitech Launch LCore at startup. Remove it from there. Also update the drivers to Logitech devices. How old the device is?

Code:

    Image name: LGVirHid.sys
    Timestamp:        Tue Nov 24 07:06:48 2009 (4B0B38B0)

The XHCI (USB3) driver is also seeming very old.

Code:

    Image name: asmtxhci.sys
    Timestamp:        Thu Jun 02 07:57:46 2011 (4DE6F522)

Update it from Station-Drivers - Asmedia

Let us know the results.
_________________________________________________________________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8009a8f028, be000000, 800400}

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: fffffa8009a8f028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, 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:  MWOClient.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff800`04befa98 fffff800`03a0ba3b : 00000000`00000124 00000000`00000000 fffffa80`09a8f028 00000000`be000000 : nt!KeBugCheckEx
fffff800`04befaa0 fffff800`0359f453 : 00000000`00000001 fffffa80`076aab50 00000000`00000000 fffffa80`076aaba0 : hal!HalBugCheckSystem+0x1e3
fffff800`04befae0 fffff800`03a0b700 : 00000000`00000728 fffffa80`076aab50 fffff800`04befe70 fffff800`04befe00 : nt!WheaReportHwError+0x263
fffff800`04befb40 fffff800`03a0b052 : fffffa80`076aab50 fffff800`04befe70 fffffa80`076aab50 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`04befc90 fffff800`03a0af0d : 00000000`00000004 00000000`00000001 fffff800`04befef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`04befcd0 fffff800`039fee88 : fffffa80`0a19aa18 fffffa80`0ac5b410 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`04befd00 fffff800`0348746c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`04befd30 fffff800`034872d3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`04befe70 fffff880`0424a3e8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff800`04be9e40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : USBPORT!USBPORT_Core_iGetNextPriorityTransfer+0x94


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

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