New PC BSOD on First day

[paulmh5]

I've just finished building a new PC and a few hours after everything was up and running the BSODs are back.
I have attched the ZIP files with the required disagostics from the sticky.
I hope someone can help shine a light on what is causing this as I'm getting close to binning it all and moving to a PS3

 

[paulmh5]

And another BSOD

 

[yowanvista]

Looks like there is a hardware problem with your CPU
http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

   Information

Run Prime 95 to test your CPU. Carefully the instructions in this tutorial: CPU - Stress Test with Prime95. Run 3 separate tests, one on each of the settings (Blend, Small FFTs, Large FFTs). Post back with your results.

If any errors are found you should get another CPU

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

*******************************************************************************
*                                                                             *
*                        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: fffffa80090de028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000005110a, 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:  f

STACK_TEXT:  
fffff880`009bbb58 fffff800`03413a3b : 00000000`00000124 00000000`00000000 fffffa80`090de028 00000000`be200000 : nt!KeBugCheckEx
fffff880`009bbb60 fffff800`035d7563 : 00000000`00000001 fffffa80`0b0d36d0 00000000`00000000 fffffa80`0b0d3720 : hal!HalBugCheckSystem+0x1e3
fffff880`009bbba0 fffff800`03413700 : 00000000`00000728 fffffa80`0b0d36d0 fffff880`009bbf30 fffff880`009bbf00 : nt!WheaReportHwError+0x263
fffff880`009bbc00 fffff800`03413052 : fffffa80`0b0d36d0 fffff880`009bbf30 fffffa80`0b0d36d0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009bbd50 fffff800`03412f0d : 00000000`00000008 00000000`00000001 fffff880`009bbfb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009bbd90 fffff800`03406e88 : 00000005`f5db56e6 fffff880`009b55c8 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009bbdc0 fffff800`034c85ec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009bbdf0 fffff800`034c8453 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009bbf30 fffff800`034d5395 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`0325baf0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiTimerExpiration+0x175


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

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

4: 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: fffffa80090de028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000005110a, 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:  f

STACK_TEXT:  
fffff880`009bbb58 fffff800`03413a3b : 00000000`00000124 00000000`00000000 fffffa80`090de028 00000000`be200000 : nt!KeBugCheckEx
fffff880`009bbb60 fffff800`035d7563 : 00000000`00000001 fffffa80`0b0d36d0 00000000`00000000 fffffa80`0b0d3720 : hal!HalBugCheckSystem+0x1e3
fffff880`009bbba0 fffff800`03413700 : 00000000`00000728 fffffa80`0b0d36d0 fffff880`009bbf30 fffff880`009bbf00 : nt!WheaReportHwError+0x263
fffff880`009bbc00 fffff800`03413052 : fffffa80`0b0d36d0 fffff880`009bbf30 fffffa80`0b0d36d0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009bbd50 fffff800`03412f0d : 00000000`00000008 00000000`00000001 fffff880`009bbfb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009bbd90 fffff800`03406e88 : 00000005`f5db56e6 fffff880`009b55c8 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009bbdc0 fffff800`034c85ec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009bbdf0 fffff800`034c8453 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009bbf30 fffff800`034d5395 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`0325baf0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiTimerExpiration+0x175


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

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

 

[paulmh5]

Hello.
I have run those tests briefly and it seems to be ok. How long should I be running them for, at the time my PC BSOD'd I wasn't doing anything intensive on the CPU or RAM.
I do have a Corsair Force 3 SSD at my C drive which since buying I've read some horror stories about even though mine claims to be from the fixed batch, are the BSOD reports defiantly pointing toward the CPU?

 

[yowanvista]

Hello.
I have run those tests briefly and it seems to be ok. How long should I be running them for, at the time my PC BSOD'd I wasn't doing anything intensive on the CPU or RAM.
I do have a Corsair Force 3 SSD at my C drive which since buying I've read some horror stories about even though mine claims to be from the fixed batch, are the BSOD reports defiantly pointing toward the CPU?

Yes it points to the CPU Cache

 

[paulmh5]

Thanks for the reply.
I managed to run for about 6 hours (not with prime95) with no issues after the initial 3 BSODs I suffered from. Is this likely to be one of those horrible intermittent issues?
How long should I run prime95 for to be sure, or is there no real way to be sure the CPU is ok?

 

[yowanvista]

Thanks for the reply.
I managed to run for about 6 hours (not with prime95) with no issues after the initial 3 BSODs I suffered from. Is this likely to be one of those horrible intermittent issues?
How long should I run prime95 for to be sure, or is there no real way to be sure the CPU is ok?

Either your CPU is overheating then use SpeedFan to check the temps. If not your board itself could be faulty
Are you overclocking?

 

[paulmh5]

The PC was bought pre-overclocked from the supplier. I have emailed them enquiring about the next step but I prefer the impartial advice from these forums first. I have speed fan running and at idle its around 40 degrees but in the OC'd mode and running prime it goes as high as 80-90 which is why I didn't run it for long. I switched the motherboard profile back to stock and it runs cooler but I managed to play a game and run backups for 6ish hours on the OC'd profile without issues and temp was lower as it wasn't as intensive so its left me a little confused.

 

[paulmh5]

Hi.

I've been talking to the supplier and they provided new OC settings but the PC is still blue screening.

Would someone be able to take a look at the last minidump and confirm the cause is still the CPU so I can try and get it RMA'd. They are very reluctant to take it back as it runs fine at the stock speed of 3.4-3.8Ghz so they claim it cant be hardware.......

 

[fseal]

Ugh, I would go to the BIOS and set the CPU and memory settings/timings all to "Auto" and go from there... ALL hardware, CPUs, chipsets, RAM vary in how much overclocking stress they can take, from batch to batch and even chip to chip, anywhere from none to a lot. Set everything back to defaults and see if it goes away for good.

 

[paulmh5]

Well I've been running at stock settings for a week without issues so its got to be something around the CPU/OC settings. Id just like to know if the last BSOD also says CPU cache the same as the original one did.

 

[yowanvista]

Well I've been running at stock settings for a week without issues so its got to be something around the CPU/OC settings. Id just like to know if the last BSOD also says CPU cache the same as the original one did.

Please stop any overclocking. Same cause the CPU Cache
You should RMA that CPU

*******************************************************************************
*                                                                             *
*                        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: fffffa80082c5028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000005110a, 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:  EC Simulator.e

CURRENT_IRQL:  f

STACK_TEXT:  
fffff800`00ba8a98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

 

[paulmh5]

Thanks. I'm trying to get an RMA number from the supplier now. Id like to have the CPU overclocked which is why I bought that bundle so I guess I'll have to see if thats still possible when the CPU is swapped.