Frequent crashes citing 0x124_GenuineIntel

#1
Hey guys and gals,
I'm diagnosing a Latitude D620 running Windows 7 x64. Recently it's been crashing every couple of days - occasionally with a BSOD, but more typically just locking up or shutting down immediately. Most of the logged events are along the lines of:
Code:
Error      4/8/2010 1:20:42 PM       Microsoft-Windows-WHEA-Logger
18           None    
"A  fatal hardware error has occurred.
   
  Reported by component: Processor Core
  Error Source: Machine Check Exception
  Error Type: Bus/Interconnect Error
  Processor ID: 0
   
  The details view of this entry contains further information."
and the minidump gives:
Code:
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: fffffa80027608f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, 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:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`02fc76f0 fffff800`02cd6a89 : fffffa80`027608d0 fffffa80`018e0040 00000000`00000007 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02fc7c10 fffff800`02bb8547 : fffffa80`027608d0 fffff800`02c315f8 fffffa80`018e0040 00000003`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02fc7c40 fffff800`02b20b95 : fffff800`02c93360 fffffa80`024c0518 fffffa80`024c0510 fffffa80`018e0040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02fc7c80 fffff800`02a9b161 : fffff880`01030e00 fffff800`02b20b70 fffffa80`018e0040 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02fc7cb0 fffff800`02d31166 : 00000000`00000000 fffffa80`018e0040 00000000`00000080 fffffa80`018cd040 : nt!ExpWorkerThread+0x111
fffff880`02fc7d40 fffff800`02a6c486 : fffff880`009ef180 fffffa80`018e0040 fffff880`009f9f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02fc7d80 00000000`00000000 : fffff880`02fc8000 fffff880`02fc2000 fffff880`0375e540 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

Followup: MachineOwner
I suspect the issue is heat, but do not have the means to take the system apart at the moment (this is a remote diagnosis). If it isn't a heat issue, any other ideas as to what might be causing this? The dump log doesn't seem super helpful.

Thanks!
 


busydog

New Member
#2
Hey guys and gals,
I'm diagnosing a Latitude D620 running Windows 7 x64. Recently it's been crashing every couple of days - occasionally with a BSOD, but more typically just locking up or shutting down immediately. Most of the logged events are along the lines of:
Code:
Error      4/8/2010 1:20:42 PM       Microsoft-Windows-WHEA-Logger
18           None    
"A  fatal hardware error has occurred.
   
  Reported by component: Processor Core
  Error Source: Machine Check Exception
  Error Type: Bus/Interconnect Error
  Processor ID: 0
   
  The details view of this entry contains further information."
and the minidump gives:
Code:
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: fffffa80027608f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, 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:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`02fc76f0 fffff800`02cd6a89 : fffffa80`027608d0 fffffa80`018e0040 00000000`00000007 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02fc7c10 fffff800`02bb8547 : fffffa80`027608d0 fffff800`02c315f8 fffffa80`018e0040 00000003`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02fc7c40 fffff800`02b20b95 : fffff800`02c93360 fffffa80`024c0518 fffffa80`024c0510 fffffa80`018e0040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02fc7c80 fffff800`02a9b161 : fffff880`01030e00 fffff800`02b20b70 fffffa80`018e0040 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02fc7cb0 fffff800`02d31166 : 00000000`00000000 fffffa80`018e0040 00000000`00000080 fffffa80`018cd040 : nt!ExpWorkerThread+0x111
fffff880`02fc7d40 fffff800`02a6c486 : fffff880`009ef180 fffffa80`018e0040 fffff880`009f9f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02fc7d80 00000000`00000000 : fffff880`02fc8000 fffff880`02fc2000 fffff880`0375e540 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

Followup: MachineOwner
I suspect the issue is heat, but do not have the means to take the system apart at the moment (this is a remote diagnosis). If it isn't a heat issue, any other ideas as to what might be causing this? The dump log doesn't seem super helpful.

Thanks!
I'd run a surface scan on your HD (check for bad sectors) and run a check of your system memory before going further. Sounds like one or the other to me. Also, try unplugging anything hardware-wise that you can eliminate.
 


#3
Yeah, I'm going to try and set up a MemTest86 run soon. I don't believe it's a hard drive error, as there are absolutely no Disk errors in the event log. Are there any decent programs to test RAM from within Windows?
 


busydog

New Member
#4
Try Windows 7: Memory Test | Windows 7 Themes


Yeah, I'm going to try and set up a MemTest86 run soon. I don't believe it's a hard drive error, as there are absolutely no Disk errors in the event log. Are there any decent programs to test RAM from within Windows?
 


#5
Sweet, I had no idea that was there.
 


#6
i am having the same problem..just wondering if you guys have found a fix for this.

my logged event and debugging gives the following


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\072210-21718-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a18000 PsLoadedModuleList = 0xfffff800`02c55e50
Debug session time: Thu Jul 22 19:10:20.000 2010 (UTC - 5:00)
System Uptime: 0 days 0:00:10.750
Loading Kernel Symbols
.......................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80050228f8, 0, 0}

Probably caused by : hardware

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

1: 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: fffffa80050228f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, 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: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`033b66f0 fffff800`02cd2a79 : fffffa80`050228d0 fffffa80`03d01680 00000000`00000006 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`033b6c10 fffff800`02bb45a7 : fffffa80`050228d0 fffff800`02c2d5f8 fffffa80`03d01680 00000003`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`033b6c40 fffff800`02b1cb85 : fffff800`02c8f360 fffffa80`04d0f848 fffffa80`04d0f840 fffffa80`03d01680 : nt!WheapProcessWorkQueueItem+0x57
fffff880`033b6c80 fffff800`02a95861 : fffff880`01329e00 fffff800`02b1cb60 fffffa80`03d01680 ff0100ef`e08788cd : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`033b6cb0 fffff800`02d2da86 : c70c78da`ff7fce6c fffffa80`03d01680 00000000`00000080 fffffa80`03ceb890 : nt!ExpWorkerThread+0x111
fffff880`033b6d40 fffff800`02a66b06 : fffff880`03163180 fffffa80`03d01680 fffff880`0316dfc0 ff0100ef`e08788cd : nt!PspSystemThreadStartup+0x5a
fffff880`033b6d80 00000000`00000000 : fffff880`033b7000 fffff880`033b1000 fffff880`03095540 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

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


#7
Hi and welcome, Brackmayhall.

If you create a thread while posting the actual crash dump(s), we can give it sole attention there. Each case if different.

You can go to C:\Windows\Minidump - Copy the files in there to any other folder. Then zip them. Attach the zip to a post using the paperclip above where you type, in advanced mode reply.

In the meantime, 0x124 stops are hardware based and difficult to diagnose. Please see this excellent resource about them:

Stop 0x124 - what it means and what to try - Windows 7 Forums
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.