BSOD with new hw

hello

today i bought a new motherboard + new cpu 

(from i5 750 to i5 3570k for cpu and asus p5p77 lx (i broken it -.-) TO Asrock Z77 EXTREME4 )

first i tried to change the hw without format.. and i got BSOD ... after a memtest86 and other tests i did a format and reinstalled win8...

but during the install i got another BSOD... i turned off the computer and removed 6gb of ram (4x2gb) try another time and still BSOD

changed the ram with another and got a full install... but i got BSOD during windows update....

so i think isn't a ram problem.... 

what is left is my new cpu and my new mb.... but the crashlog don't help me....

BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

STACK_TEXT:  
fffff801`c97f3a28 fffff801`ca24a93d : 00000000`00000124 00000000`00000000 fffffa80`08585028 00000000`be200000 : nt!KeBugCheckEx
fffff801`c97f3a30 fffff801`ca3e2c09 : 00000000`00000001 fffffa80`06babe10 00000000`00000000 fffffa80`08585028 : hal!HalBugCheckSystem+0xf9
fffff801`c97f3a70 fffff801`ca24a6e3 : 00000000`00000728 00000000`00000000 fffff801`c97f3bd0 fffffa80`06babe10 : nt!WheaReportHwError+0x249
fffff801`c97f3ad0 fffff801`ca24a00c : 00000000`00000010 fffffa80`06babe10 fffff801`c97f3c88 fffffa80`06babe10 : hal!HalpMcaReportError+0x53
fffff801`c97f3c30 fffff801`ca249f07 : fffffa80`06a746b0 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xd4
fffff801`c97f3c80 fffff801`ca249d64 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe3
fffff801`c97f3cc0 fffff801`ca24aedb : fffffa80`06a746b0 fffff801`c97f3ef0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4
fffff801`c97f3cf0 fffff801`ca30237b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff801`c97f3d20 fffff801`ca30212e : 00000000`00000000 fffff801`ca3020af 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
fffff801`c97f3e60 fffff880`03f8c984 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x16e
fffff801`c97e78c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x18


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE

Followup: MachineOwner

BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`02a67868 fffff801`9079393d : 00000000`00000124 00000000`00000000 fffffa80`0810f028 00000000`be200000 : nt!KeBugCheckEx
fffff880`02a67870 fffff801`90177c09 : 00000000`00000001 fffffa80`069e9490 00000000`00000000 fffffa80`0810f028 : hal!HalBugCheckSystem+0xf9
fffff880`02a678b0 fffff801`907936e3 : 00000000`00000728 00000000`00000002 fffff880`02a67a10 fffffa80`069e9490 : nt!WheaReportHwError+0x249
fffff880`02a67910 fffff801`9079300c : 00000000`00000010 fffffa80`069e9490 fffff880`02a67ac8 fffffa80`069e9490 : hal!HalpMcaReportError+0x53
fffff880`02a67a70 fffff801`90792f07 : fffffa80`06a70810 00000000`00000001 00000000`00000002 00000000`00000000 : hal!HalpMceHandlerCore+0xd4
fffff880`02a67ac0 fffff801`90792d64 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe3
fffff880`02a67b00 fffff801`90793edb : fffffa80`06a70810 fffff880`02a67d30 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4
fffff880`02a67b30 fffff801`9009737b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`02a67b60 fffff801`9009712e : 00000000`00000000 fffff801`900970af 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
fffff880`02a67ca0 fffff880`03f7f984 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x16e
fffff880`02a878c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x18


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE

Followup: MachineOwner

this are my last 2 crash..  btw they are all the same....

any1 can help?


August 23rd, 2013 7:04pm

Stop 0x124 is a hardware error
If you are overclocking try resetting your processor to standard settings and see if that helps. If you continue to get BSODs here are some more things you may want to consider.
This is usually heat related, defective hardware, memory or even processor though it is"possible" that it is driver related (rare).

Stop 0x124 - what it means and what to try

Synopsis:
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.


 Generic "Stop 0x124" Troubleshooting Strategy:

1) Ensure that none of the hardware components are overclocked. Hardware that is driven beyond its design specifications - by overclocking - can malfunction in unpredictable ways.
2) Ensure that the machine is adequately cooled.
 If there is any doubt, open up the side of the PC case (be mindful of any relevant warranty conditions!) and point a mains fan squarely at the motherboard. That will rule out most (lack of) cooling issues.
3) Update all hardware-related drivers: video, sound, RAID (if any), NIC... anything that interacts with a piece of hardware.
It is good practice to run the latest drivers anyway.
4) Update the motherboard BIOS according to the manufacturer's instructions and clear the CMOS.
Their website should provide detailed instructions as to the brand and model-specific procedure.
5) Rarely, bugs in the OS may cause "false positive" 0x124 events where the hardware wasn't complaining but Windows thought otherwise (because of the bug).
At the time of writing, Windows 7 is not known to suffer from any such defects, but it is nevertheless important to always keep Windows itself updated.
6) Attempt to (stress) test those hardware components which can be put through their paces artificially.
The most obvious examples are the RAM and HDD(s).
For the RAM, use the 3rd-party memtest86 utility to run many hours worth of testing. (6-8 passes to stress the ram out)
For hard drives, check whether CHKDSK /R finds any problems on the drive(s), notably "bad sectors".
Unreliable RAM, in particular, is deadly as far as software is concerned, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result from the diagnostics utilities does not guarantee that the RAM is free from defects - only that none were encountered during the test passes.
7) As the last of the non-invasive troubleshooting steps, perform a "vanilla" reinstallation of Windows: just the OS itself without any additional applications, games, utilities, updates, or new drivers - NOTHING AT ALL that is not sourced from the Windows 7 disc.
Should that fail to mitigate the 0x124 problem, jump to the next steps.
If you run the "vanilla" installation long enough to convince yourself that not a single 0x124 crash has occurred, start installing updates and applications slowly, always pausing between successive additions long enough to get a feel for whether the machine is still free from 0x124 crashes.
Should the crashing resume, obviously the very last software addition(s) may be somehow linked to the root cause.
If stop 0x124 errors persist despite the steps above, and the hardware is under warranty, consider returning it and requesting a replacement which does not suffer periodic MCE events.
Be aware that attempting the subsequent hardware troubleshooting steps may, in some cases, void your warranty:
8) Clean and carefully remove any dust from the inside of the machine.
Reseat all connectors and memory modules.
Use a can of compressed air to clean out the RAM DIMM sockets as much as possible.
9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed.
Obviously, this type of testing is a lot easier if you've got access to equivalent components in order to perform swaps.

Should you find yourself in the situation of having performed all of the steps above without a resolution of the symptom, unfortunately the most likely reason is because the error message is literally correct - something is fundamentally wrong with the machine's hardware.
Free Windows Admin Tool Kit Click here and download it now
August 23rd, 2013 9:04pm

I need the dmp file to see more details which cache issue you have.
August 24th, 2013 2:46am

i have default setting of the bios ... no overclock...

i tried to stress the cpu and after 5min the max temp was at 60C

it's hard to update the drivers .... when i launch windows update i get always BSOD

the minidumps are here https://www.dropbox.com/sh/u77lk3arjwyxpa8/DlB4XzEFpv

u need the memorydump too?

PS during the time for write this post i got 3 BSOD
Free Windows Admin Tool Kit Click here and download it now
August 24th, 2013 3:36am

You have an Instruction Cache error

===============================================================================
Common Platform Error Record @ fffffa80085ce028
-------------------------------------------------------------------------------
Record Id     : 01cea068696db9f8
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 8/24/2013 1:54:17 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa80085ce0a8
Section       @ fffffa80085ce180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Instruction Execute
Flags         : 0x00
Level         : 2
CPU Version   : 0x00000000000306a9
Processor ID  : 0x0000000000000002

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa80085ce0f0
Section       @ fffffa80085ce240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000002
CPU Id        : a9 06 03 00 00 08 10 02 - bf e3 9a 7f ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa80085ce240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa80085ce138
Section       @ fffffa80085ce2c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : ICACHEL2_IRD_ERR (Proc 1 Bank 7)
  Status      : 0xfe20000000021152
  Address     : 0x00000001815df640
  Misc.       : 0x0000007026000086





CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3400





  Speed                         1333MHz
  Manufacturer                  Kingston              
  Part Number                   9905403-011.A03LF 


BiosVersion = P2.70
BiosReleaseDate = 11/28/2012
BaseBoardManufacturer = ASRock
BaseBoardProduct = Z77 Extreme4              

update the BIOS to version 2.90 and look if the Kingston RAM is compatible to your ASRock board. If this doesn't fix it, RMA the CPU.

August 24th, 2013 4:24pm

i have already updated to 2.90 but still not solved... for the ram i have  kvr1333d3n9/2g and from here is compatible www.asrock.com/mb/Intel/Z77%20Extreme4/index.it.asp?cat=Memory


so i think the only thing left is the RMA...

btw the MB can't cause the problem right?

Free Windows Admin Tool Kit Click here and download it now
August 24th, 2013 5:05pm

ok last question....

i'm uploading right now a zip with a few photo of my chipset... i think i have 2 broken pins.... (i named a file target and edited the img for show the position)

the file is in the same folder of the dumps.... the holes are normal or this can be the problem?

upload complete 

August 24th, 2013 8:32pm

This is possible. This picture from Wikipedia doesn't have those holes:

Free Windows Admin Tool Kit Click here and download it now
August 25th, 2013 3:07am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics