Uncontrollable hardware error. Straight after building

[lxlramlxl]

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]

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.
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
allowing it to run overnight is actually ideal if you are about to call it.

 

[lxlramlxl]

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

I shall try mem test while at work today.

 

[lxlramlxl]

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]

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]

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]

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]

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.
http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

basic debug info follows:

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]

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]

http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html
Sadly that's really all there is left to do in this situation now.

 

[lxlramlxl]

I have no option to turn XMP off in UFEI(bios).
I checked the ram settings didnt really understand much.
On the packaging it says 9-9-9-24 but it doesn't indicate that in bios, I'm
Not sure what the numbers represent or even if it is significant. Im at work at the minute so can't really do anything untill I get home.

 

[lxlramlxl]

Ok, I tried rebuilding the computer and no success.
I have no POST beeps but it doesn't have a speaker.

I tried updating the bios and it just turned itself off. It's like the power is tripping just randomly, getting more frequent the longer I have the computer on. (If I leave it for 10 minutes it will stay on a little longer) My cpu is at 99c so I dont think that's whats causing it.

I tried removing the graphics card and booting without it to see if that was the problem but still the same thing. the power just seems to trip. When I press the power button there seems to actually be a delay until the computer turns on. For example when the power trips and i goto turn it back on, when I press the button 2-5 seconds later it will start to power up.

 

[Maguscreed]

your cpu is at 99c? idle?
50 to 70 would be normal operating temps
99c while idle is slowly killing the chip.
Even GPU's shouldn't be hitting temps near that high in normal use.

I would expect around 35-40c while it's not being stressed though.

 

[lxlramlxl]

I don't know why it's so high. It's has a cooler on and all it is doing is booting up.

Do you think that's what is tripping the power? But that wouldn't cause a BSOD would it?

 

[Maguscreed]

if the temp is that high the system may be shutting itself off.
something is not right, did you use thermal compound?
IS the cpu fan plugged in.
Is it spinning?
Is the specific cpu you are using approved for your motherboard?

 

[lxlramlxl]

I used thermal paste but may have used too much.
It's the stock cooler that comes with the i5, and yes it is plugged in and spinning. (My motherboard is Asrock Extreme4 z77)

 

[lxlramlxl]

Sorted now I think.
Removed the stock cooler and put the one I bought on and now running at around 35-40c idle.

 

[Maguscreed]

things working better now?
I'm doubtful the chip was exposed to high enough temps long enough to harm it.
Glad you mentioned that little detail. Prolonged that could have actually caused some harm.