BSOD: STOP: 0x00000124

Hello darksider and welcome to Seven Forums. Olease read this tutorial about BSOD posting instructions. I will request this post be moved to the Crashes and Debugging section where the experts in this area will try to help.

Take a look at this thread and let us know if you have any questions.

Stop 0x124 - what it means and what to try

Can you fill in your system specs?
Lower left corner on any of your posts, 'My System Specs'.
This is a hardware issue, give as much detail as possible.

STOP 0x00000124: WHEA_UNCORRECTABLE_ERROR
Usual causes: Hardware, Incompatibility, May be driver corruption
This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA)

The dump file blames the GenuineIntel_PROCESSOR_CACHE

Your CPU may or may not be to blame.
Run Prime95 to test your CPU.
CPU - Stress Test with Prime95

Select the Small FFTs test.
Enter 8 cores for your CPU.
In Advanced tab select 'Round off checking'.
Use Real Temp , to check the CPU temps when at idle, under load and/or testing.
Tell us what the idle temp is, Don't go over 72°C, this is the Intel recommended max CPU core temp.

Intel® Core™ i7-920 Processor

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8006c7b028, b6000000, 115}

Probably caused by : hardware

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

6: 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: fffffa8006c7b028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b6000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000115, 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:  plugin-contain

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`0311db58 fffff800`037fda3b : 00000000`00000124 00000000`00000000 fffffa80`06c7b028 00000000`b6000000 : nt!KeBugCheckEx
fffff880`0311db60 fffff800`0338f563 : 00000000`00000001 fffffa80`064f2a60 00000000`00000000 fffffa80`064f2ab0 : hal!HalBugCheckSystem+0x1e3
fffff880`0311dba0 fffff800`037fd700 : 00000000`00000728 fffffa80`064f2a60 fffff880`0311df30 fffff880`0311df00 : nt!WheaReportHwError+0x263
fffff880`0311dc00 fffff800`037fd052 : fffffa80`064f2a60 fffff880`0311df30 fffffa80`064f2a60 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`0311dd50 fffff800`037fcf0d : 00000000`00000008 00000000`00000001 fffff880`0311dfb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`0311dd90 fffff800`037f0e88 : 00000000`00000002 00000000`0569d800 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`0311ddc0 fffff800`032805ec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`0311ddf0 fffff800`03280453 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`0311df30 00000000`6bec12d1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`0828f724 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6bec12d1


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

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

Some of your drivers should be updated.
Check your Dell website and update all drivers available.

Broadcom iLine10(tm) PCI Network Adapter, check http://www.broadcom.com/support/

Broadcom 802.11g Network Adapter - Dell Wireless 1390 WLAN Mini-Card, same as above.

e1y60x64.sys, which is component of Intel(R) 82567LM Gigabit Network Connection, please download and install fresh copy of it as well (I would go Computer-->manage-->device manager to uninstall old version beforeinstall new one)
http://downloadcenter.intel.com/Default.aspx

Sonic CD/DVD driver (used by many different CD/DVD programs) - PxHlpa64.sys

Get a new version of Team Viewer, TeamViewerVPN Network Adapter


This event log confirms the CPU error.

Code:

Event[3754]:
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2011-07-26T08:16:56.961
  Event ID: 18
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: Roger-PC2
  Description: 
A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Internal Timer Error
Processor ID: 6

The details view of this entry contains further information.

STOP 0x00000101: CLOCK_WATCHDOG_TIMEOUT
Usual causes: Device driver, BIOS bug, hardware defect
Cause: The specified processor is not processing interrupts. Typically, this occurs when the processor is nonresponsive or is deadlocked.

Code:

Event[3814]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2011-07-26T08:16:27.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Roger-PC2
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000101 (0x0000000000000019, 0x0000000000000000, 0xfffff88003115180, 0x0000000000000006). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 072611-19812-01.

There are a lot of these event errors.

Code:

Event[1]:
  Log Name: Application
  Source: WinVNC4
  Date: 2011-07-27T14:17:03.000
  Event ID: 1
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Roger-PC2
  Description: 
SocketManager: unknown listener event: 0

You should see something from Prime95 in the first two hours, if not then you can stop the test.

That definitely could be the cause.

Let us know if you get anymore BSoDs.