BSOD randomly occurring, BCcode 124

[Thoord]

Hi

I have BSOD randomly occurring, seems to be unrelated to the software running on the computer. I've read BCcode 124 is a bit of a tricky error to analyze. I do however hope you're able to help. I'm also having difficulties upgrading with the SP1 update (KB976932 error 0x80070490). I know this isn't the right forum for that issue, I'm only mentioning in case it may be related . I have tried every tutorial I've found online (for both issues), and I can't figure it out. Please see the attached file for mini-dumps etc.

Help is much appreciated

Thoord

 

[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

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


Loading Dump File [C:\Users\USER\Downloads\Thoord\SF_05-11-2013\110513-15802-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532
Machine Name:
Kernel base = 0xfffff800`02e61000 PsLoadedModuleList = 0xfffff800`0309de70
Debug session time: Tue Nov  5 15:33:27.457 2013 (UTC + 6:00)
System Uptime: 0 days 0:00:10.566
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, fffffa8027b7b8f8, 0, 0}

Probably caused by : GenuineIntel

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

23: 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: fffffa8027b7b8f8, 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:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`03b6f6f0 fffff800`0311a979 : fffffa80`27b7b8d0 fffffa80`25d01040 fffff8a0`00252a70 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`03b6fc10 fffff800`02ffc677 : fffffa80`27b7b8d0 fffff800`030755f8 fffffa80`25d01040 fffff800`030755f8 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`03b6fc40 fffff800`02f64c85 : fffff800`030d7380 fffffa80`274f6c28 fffff8a0`002529e8 fffffa80`25d01040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`03b6fc80 fffff800`02eddb21 : fffff800`032f4800 fffff800`02f64c60 fffffa80`25d01040 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`03b6fcb0 fffff800`0316f47a : 00000000`00000000 fffffa80`25d01040 00000000`00000080 fffffa80`25c619e0 : nt!ExpWorkerThread+0x111
fffff880`03b6fd40 fffff800`02eaeda6 : fffff880`03a8f180 fffffa80`25d01040 fffff880`03a9a4c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03b6fd80 00000000`00000000 : fffff880`03b70000 fffff880`03b6a000 fffff880`03b6f620 00000000`00000000 : nt!KxStartSystemThread+0x16


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_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_MEMORY__UNKNOWN_PRV

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

• Test and Diagnose RAM issues with MEMTEST86+
  • Pay close attention to Part 3 of the tutorial "If you have errors". Take the test for at least 7-10 passes. It may take up to 22 passes to find problems.
    • Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold. http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html