BSOD Stop code 124

Cyralax · 07 Dec 2011

Hi guys, I encountered a BSOD while just browsing the internet, I managed to get the STOP code of 124 though before it cleared. I HAVE been having some issues with my HDD not maintaining constant speeds during file transfers, so maybe its a HDD problem?

System specs are underneath.

panais · 07 Dec 2011

Yes you have the,

Stop 0x124 - what it means and what to try

Though the one and only minidump you upload points also the avg.

So, before you try anything else,remove avg from your system.

Download,install and use Microsoft Security Essentials with windows firewall and see if that helps.

Also if you are overclocking anything stop and set everything back to default settings..

Tews · 07 Dec 2011

Very possible to likely ..

Stop 0x124 - what it means and what to try
Synopsis:

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.

Stop 0x124 - what it means and what to try

Cyralax · 07 Dec 2011

@Panais What do you mean "points to AVG"? Do you mean that AVG could be creating a false error?
And as for running chkdsk, the cmd window opens up for a fraction of a second and then closes again. I can post a recent HDTune test if that helps?

panais · 07 Dec 2011

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8008ea5028, bf800000, 200001}

Unable to load image \SystemRoot\system32\DRIVERS\avgrkx64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for avgrkx64.sys
*** ERROR: Module load completed but symbols could not be loaded for avgrkx64.sys
Probably caused by : hardware

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

2: 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: fffffa8008ea5028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000200001, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  avgscana.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`0316da58 fffff800`0320da3b : 00000000`00000124 00000000`00000000 fffffa80`08ea5028 00000000`bf800000 : nt!KeBugCheckEx
fffff880`0316da60 fffff800`02d9f513 : 00000000`00000001 fffffa80`061642c0 00000000`00000000 fffffa80`06164310 : hal!HalBugCheckSystem+0x1e3
fffff880`0316daa0 fffff800`0320d700 : 00000000`00000728 fffffa80`061642c0 fffff880`0316de30 fffff880`0316de00 : nt!WheaReportHwError+0x263
fffff880`0316db00 fffff800`0320d052 : fffffa80`061642c0 fffff880`0316de30 fffffa80`061642c0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`0316dc50 fffff800`0320cf0d : 00000000`00000004 00000000`00000001 fffff880`0316deb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`0316dc90 fffff800`03200e88 : fffffa80`0c1afc10 fffff880`03bb0220 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`0316dcc0 fffff800`02c8d52c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`0316dcf0 fffff800`02c8d393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`0316de30 fffff880`01835d94 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`094e9838 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : avgrkx64+0x5d94


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

Followup: MachineOwner

So,uninstall avg and use mse for testing purposes.

Yes you have X64_0x124,though lets try that simple step first.

Sometimes the solution is simple,sometimes not.

If not then continue with this Stop 0x124 - what it means and what to try