Windows 7: Uncontrollable hardware error. Straight after building

lxlramlxl · 24 Sep 2012

Hi since my computer just blue screened again I'm posting this on my phone. As the title says I'm getting hardware errors after litterally finishing the build and installing windows. I will post the dumps tomorrow since its 00:30 already here.

Thanks

Maguscreed · 24 Sep 2012

The first thing I would look at is ram.
NEW parts do sometimes arrive in non-working order.
I've seen it happen to the best and cheapest parts nearly equally.
Ram is the easiest thing to test though.
RAM - Test with Memtest86+
allowing it to run overnight is actually ideal if you are about to call it.

lxlramlxl · 25 Sep 2012

Bump, there is my info dump. (First post)

I shall try mem test while at work today.

lxlramlxl · 25 Sep 2012

Started Memtest86. 25% and no errors.
Don't know whether that's good or bad - if it's not my ram it's something more serious :/

Maguscreed · 25 Sep 2012

memtest should be allowed to run for several full passes to be sure.
I generally suggest doing it overnight for that reason.

Also since it's a new build go back over everything make sure everything that needs a plug in it has one.
Graphics cards generally make a horrid noise if they aren't hooked in properly. Other components may give no warning though.

lxlramlxl · 25 Sep 2012

Yeah, memtest is still running.
I only have my graphics card and a Sata hard drive installed.
Do the logs not give and clue to what is wrong?

Edit:
If it is of any significance on memtest it only indicates 667 MHz of Ram. I should have 8GB.

Maguscreed · 25 Sep 2012

totally forgot you had put up a zip for me. Long day.
Give me about 20 minutes with that hopefully there is a minidump file those help a lot more than logs in general.

Maguscreed · 25 Sep 2012

Alright didn't need that much time, dump confirms my suspicion something has arrived bad.
OR there is a overclock / improper settings in bios.
IF the system has xmp, try turning it off. (sometimes without the perfect match of motherboard and make model of ram it doesn't work right) That will be located in the bios settings.
That would be the easiest fix I can think of off the top of my head with a new build.

Anyhow what you have is a 124 stop error. This one is really specific. As I said above it's most commonly damaged hardware. Though it can be caused by bad clock/memory timings. Fortunately if all of this is like some strange new language to you we also have a page already set up for what to do next.
Stop 0x124 - what it means and what to try

basic debug info follows:

Code:

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8007fb5028, b2000000, 81000402}

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: fffffa8007fb5028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000081000402, 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:  TrustedInstall

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`009f7a58 fffff800`0281e903 : 00000000`00000124 00000000`00000000 fffffa80`07fb5028 00000000`b2000000 : nt!KeBugCheckEx
fffff880`009f7a60 fffff800`029db513 : 00000000`00000001 fffffa80`07fb6ea0 00000000`00000000 fffffa80`07fb6ef0 : hal!HalBugCheckSystem+0x1e3
fffff880`009f7aa0 fffff800`0281e5c8 : 00000000`00000728 fffffa80`07fb6ea0 fffff880`009f7e30 fffff880`009f7e00 : nt!WheaReportHwError+0x263
fffff880`009f7b00 fffff800`0281df1a : fffffa80`07fb6ea0 fffff880`009f7e30 fffffa80`07fb6ea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009f7c50 fffff800`0281ddd5 : 00000000`00000004 00000000`00000001 fffff880`009f7eb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009f7c90 fffff800`02811e88 : 00000000`00000000 00000000`00357980 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009f7cc0 fffff800`028c57ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009f7cf0 fffff800`028c5613 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009f7e30 00000000`77a638f8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`0141ddb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a638f8


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
---------

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: fffffa8007fb5028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000081000402, 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:  TrustedInstall

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`009f7a58 fffff800`0281e903 : 00000000`00000124 00000000`00000000 fffffa80`07fb5028 00000000`b2000000 : nt!KeBugCheckEx
fffff880`009f7a60 fffff800`029db513 : 00000000`00000001 fffffa80`07fb6ea0 00000000`00000000 fffffa80`07fb6ef0 : hal!HalBugCheckSystem+0x1e3
fffff880`009f7aa0 fffff800`0281e5c8 : 00000000`00000728 fffffa80`07fb6ea0 fffff880`009f7e30 fffff880`009f7e00 : nt!WheaReportHwError+0x263
fffff880`009f7b00 fffff800`0281df1a : fffffa80`07fb6ea0 fffff880`009f7e30 fffffa80`07fb6ea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009f7c50 fffff800`0281ddd5 : 00000000`00000004 00000000`00000001 fffff880`009f7eb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009f7c90 fffff800`02811e88 : 00000000`00000000 00000000`00357980 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009f7cc0 fffff800`028c57ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009f7cf0 fffff800`028c5613 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009f7e30 00000000`77a638f8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`0141ddb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a638f8


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

lxlramlxl · 26 Sep 2012

Well ran the memtest for 11 hours and got to 4 Passes.
Had a quick look inside and had the power and reset cables placed wrongly, but I doubt that would cause a bsod.

Maguscreed · 26 Sep 2012

Stop 0x124 - what it means and what to try
Sadly that's really all there is left to do in this situation now.

Windows 7: Uncontrollable hardware error. Straight after building

Uncontrollable hardware error. Straight after building problems?