Windows 7 x64 BSOD 124 (Minidmps Attached)

[ankit]

Hi,

I am getting a BSOD 124 error after my computer restarts (lines come up or the screen just goes black before the restart). It happens at random.

I have read the increasing vcore and/or vtt may help but I have and that doesn't seem to do anything. I have done no overclocking.

I have attached all 9 minidumps below.

Thanks

 

[zigzag3143]

Hi,

I am getting a BSOD 124 error after my computer restarts (lines come up or the screen just goes black before the restart). It happens at random.

I have read the increasing vcore and/or vtt may help but I have and that doesn't seem to do anything. I have done no overclocking.

I have attached all 9 minidumps below.

Thanks

Hey ankit and welcome

all of these are the same probably caused by hardware. Interestingly doesnt give any hint as to what hardware

I would start with memory
download memtestx86 and run for 5 passes
If you are overclocking stop

Hope this helps


Ken J+

122009-24562-01.dmp    12/20/2009 3:53:40 PM        0x00000124    00000000`00000000    fffffa80`064eb8f8    00000000`00000000    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+4a63cc                    
122409-17281-01.dmp    12/24/2009 10:01:00 AM        0x00000124    00000000`00000000    fffffa80`06cc7038    00000000`00000000    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+4a63cc                    
122409-18531-01.dmp    12/24/2009 8:38:34 AM        0x00000124    00000000`00000000    fffffa80`06cad398    00000000`00000000    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+4a63cc                    
122409-19562-01.dmp    12/24/2009 10:19:24 PM        0x00000124    00000000`00000000    fffffa80`06c538f8    00000000`00000000    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+4a63cc                    
122609-18359-01.dmp    12/26/2009 8:11:04 AM        0x00000124    00000000`00000000    fffffa80`06bfa338    00000000`00000000    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+4a63cc                    
122809-18531-01.dmp    12/28/2009 7:05:02 PM        0x00000124    00000000`00000000    fffffa80`06c328f8    00000000`00000000    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+4a63cc                    
122809-18796-01.dmp    12/28/2009 7:01:16 PM        0x00000124    00000000`00000000    fffffa80`06c16038    00000000`00000000    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+4a63cc                    
122809-19218-01.dmp    12/28/2009 1:08:30 PM        0x00000124    00000000`00000000    fffffa80`06c13038    00000000`00000000    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+4a63cc                    
122809-28500-01.dmp    12/28/2009 7:18:58 PM        0x00000124    00000000`00000000    fffffa80`06bf98f8    00000000`00000000    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+4a63cc

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\MiniDumps BSOD 124\122409-19562-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
[B]Built by: 7600.16385.amd64fre.win7_rtm.090713-1255[/B]
Machine Name:
Kernel base = 0xfffff800`02a16000 PsLoadedModuleList = 0xfffff800`02c53e50
Debug session time: Fri Dec 25 00:19:16.796 2009 (GMT-5)
System Uptime: 0 days 0:00:08.812
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, fffffa8006c538f8, 0, 0}

[B]Probably caused by : hardware[/B]

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

5: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
[B]
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: fffffa8006c538f8, 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.[/B]

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`0337e6f0 fffff800`02cd0a89 : fffffa80`06c538d0 fffffa80`0553f040 00000000`0000000a 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`0337ec10 fffff800`02bb2547 : fffffa80`06c538d0 fffff800`02c2b5f8 fffffa80`0553f040 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`0337ec40 fffff800`02b1ab95 : fffff800`02c8d360 fffffa80`06bde538 fffffa80`06bde530 fffffa80`0553f040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`0337ec80 fffff800`02a95161 : fffff880`01100e00 fffff800`02b1ab70 fffffa80`0553f040 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`0337ecb0 fffff800`02d2b166 : e524e524`f457f457 fffffa80`0553f040 00000000`00000080 fffffa80`05528840 : nt!ExpWorkerThread+0x111
fffff880`0337ed40 fffff800`02a66486 : fffff880`03186180 fffffa80`0553f040 fffff880`031910c0 8ee28ee2`ce98ce98 : nt!PspSystemThreadStartup+0x5a
fffff880`0337ed80 00000000`00000000 : fffff880`0337f000 fffff880`03379000 fffff880`04134670 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_MAE_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

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

 

[ankit]

Thanks for your response,

I ran window's memory diagnostic 5 times on extended mode since I couldn't run this 32-bit software. The memory was good. Is there anything else to check? I just got another BSOD that was on a different partition if it helps.

EDIT I found out how to run the memtest and it has passed.

 

[ankit]

Memtest Complete

The memtest is complete and there are no errors, is there anything else that could be causing the problem. The problem has only been happening for the last 10 days and not since the day I built the PC, so I dont know if its hardware. Maybe the second minidump shows anything?

 

[computersplus]

Video

Have a hard look at the video card is it onboard or PCI-E etc. if so look at power supply requirements vs power supply output I find this overlooked a lot

 

[computersplus]

Motherboard

What motherboard is it? possible as well it could be the problem more info would help

 

[chev65]

Thats all I could get is hardware also, maybe a USB device, loose wire, hard to say.

You might have a look at your events error log and see what was going on before the crash took place.

MSDN says this about it.
A machine check exception occurred.

These parameter descriptions apply if the processor is based on the x64 architecture, or the x86 architecture that has the MCA feature available (for example, Intel Pentium Pro, Pentium IV, or Xeon).



You might try reseating the CPU and the GPU and see it if helps.
An uncorrectable PCI Express error occurred.

 

[computersplus]

What Happened

what happened prior to this starting any upgrades changes?

 

[zigzag3143]

Thanks for your response,

I ran window's memory diagnostic 5 times on extended mode since I couldn't run this 32-bit software. The memory was good. Is there anything else to check? I just got another BSOD that was on a different partition if it helps.

EDIT I found out how to run the memtest and it has passed.

By the way memtestx86 runs on 32 and 64bit since it runs outside the windows environment

 

[computersplus]

Bios Settings

check bios settings you are using 64 bit so how much ram are you using? check memory hole remapping

 

[chev65]

Thanks for your response,

I ran window's memory diagnostic 5 times on extended mode since I couldn't run this 32-bit software. The memory was good. Is there anything else to check? I just got another BSOD that was on a different partition if it helps.

EDIT I found out how to run the memtest and it has passed.

By the way memtestx86 runs on 32 and 64bit since it runs outside the windows environment

Good point Ken, Which is one of the reasons I like the Windows version of Memtest better.
MemTest for Windows Download Page

 

[ankit]

System Info

Here is all the system info.

Processor: Core i7 920 2.66gHz
Video Card: XFX HD5770 PCI-E
RAM: OCZ GOLD 6gb (2gb x 3)
Motherboard: MSI x58 Platinum SLI
PSU: Ultra LSP-750 750watt
Hard Drive: Western Digital 640gb Caviar Black 32mb cache

I occupied the proper RAM slots and the PSU seems to be more than enough. This video only needs one PCI-E connector also.

How can I see all the changes that took place, and what are likely changes that would cause such a thing to happen?

 

[computersplus]

Event Viewer

go to control panel administrative tools event viewer then look for windows logs on the left pane then check system and application are the two main ones to check look for red marks

 

[ankit]

Not Much

It shows the errors, but nothing that helps. I am running in safe mode right now and have not had any BSODs. I will run safe mode for a week just to be sure and will reinstall windows.

 

[computersplus]

Safe Mode

if it's ok in safe mode I would have a good look at start up programs and services... it may be something that loads with windows that's causing the crashes

 

[computersplus]

Error Codes

what red error codes are you getting in the event viewer

 

[ankit]

The ones I saw were distributed COM, Kernel-Power, BUGCHECK, and WHEA Logger.

 

[computersplus]

WHEA Logger

WHEA Logger is the one that concerns me i am researching that for you I will get back to but I think you have some bad hardware and I am leaning toward CPU

 

[chev65]

According to the ATI CrossfireX site, your HD 5570 requires a special power supply rating. Are you sure that your power supply is rated to run the 5570? It says that a certified power supply is recommend and also that if you want to run the card in dual mode you need to hook up both of the 6 pin power plugs to the card. My GTX280 needs an 8 and a 6 pin and your card may need both plugged in also.

 

[computersplus]

WHEA Logger

what event ID number does it give for this it would help for me to pinpoint