So im new to this forum, But I am getting this error and I have been sent a replacement CPU which fixed it for a month or so but as of yesterday its starting again, I dont know if im allowed to upload the dump file to an external site and post a link or what, So I will just wait for a response.

Also this error can happen at any time not just at 100% stress or whatever.

- Glenn

I saw someone else use this site and I hope this is a correct link to the dump file, https://onedrive.live.com/redir?resid=ee845d6802143e62%21472

• Edited by Glenn332 13 hours 10 minutes ago Link to dump file added.

Glenn

These are called BCC124 and are related to hardware.  Read how to diagnose and hopefully to fix them in this wiki   Since your references "genuine INtel" I would start with a cpu stress test

Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\zigza\Desktop\051015-6281-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17736.amd64fre.winblue_r9.150322-1500
Machine Name:
Kernel base = 0xfffff800`ffa12000 PsLoadedModuleList = 0xfffff800`ffceb850
Debug session time: Sun May 10 13:32:36.045 2015 (UTC - 4:00)
System Uptime: 1 days 16:59:05.165
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, ffffe000da726028, ba000000, 58000402}

Probably caused by : GenuineIntel

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

2: 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: ffffe000da726028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000ba000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000058000402, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

STACK_TEXT:  
ffffd001`9afdacf8 fffff801`001dd213 : 00000000`00000124 00000000`00000000 ffffe000`da726028 00000000`ba000000 : nt!KeBugCheckEx
ffffd001`9afdad00 fffff800`ffbd7f2d : 00000000`00000001 ffffe000`d96adbc0 ffffe000`d96adbc0 ffffe000`da726028 : hal!HalBugCheckSystem+0xcf
ffffd001`9afdad40 fffff801`001dd6a0 : 00000000`00000728 00000000`00000002 ffffd001`9afdb130 00000000`00000000 : nt!WheaReportHwError+0x22d
ffffd001`9afdada0 fffff801`001dda0d : ffffe000`00000010 ffffe000`d96adbc0 ffffd001`9afdaf48 ffffe000`d96adbc0 : hal!HalpMcaReportError+0x50
ffffd001`9afdaef0 fffff801`001dd8f8 : ffffe000`d96ad810 00000000`00000001 00000000`00000002 00000000`00000000 : hal!HalpMceHandlerCore+0xe1
ffffd001`9afdaf40 fffff801`001ddb42 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4
ffffd001`9afdaf80 fffff801`001ddccf : ffffe000`d96ad810 ffffd001`9afdb1b0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
ffffd001`9afdafb0 fffff800`ffb6d7bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
ffffd001`9afdafe0 fffff800`ffb6d571 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
ffffd001`9afdb120 fffff801`f20ba214 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171
ffffd001`9affa8e8 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

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_MAE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x124_genuineintel_processor_mae

FAILURE_ID_HASH:  {7c95de0c-286c-8226-45c2-422b4de101d6}

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

So you are saying that the CPU is faulty?

It says in the text you gave me:

 WIN8_DRIVER_FAULT
So it might be a driver fault?

• Edited by Glenn332 12 hours 57 minutes ago

Glenn

I am saying to diagnose which run a cpu stress test. I suspect it is the CPU

Im running prime 95 but after a minute or so the heat goes upto 80+ by then I stopped the test as im scared it will damage my system even more, Why did I had to do the stress test?

Update: The crashes happened again, I now set the voltage mode to fixed > Auto. Hope that helps as im pretty sure its the CPU, But the crash doesnt happen at 100% load it just happens whenever it wants, Its really frustrating.

• Edited by Glenn332 10 hours 33 minutes ago

Glenn

You have a hardware issue.  The fastest way to fix it is to replace the cpu but I figured you would like to try and confirm the CPU is the problem before spending money.  Given the results It does tend to lend credence to the cpu issue

Well I changed the bios settings and it worked again for a few hours, Not gonna say changing the settings did anything but this error just happens randomly, This is the second new CPU that goes into this machine, Im beginning to feel like its gonna continue to happen as I send the last broken CPU back and they tested it and said that there was nothing wrong with it?

Anyway I got a new dumpfile of the changed bios error, It might be the same would appreciate it if you would check it again..

https://onedrive.live.com/redir?resid=ee845d6802143e62%21473

Glenn

Still the same.  If this is the second CPU it may be the motherboard and not the CPU

Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\zigza\Desktop\051115-7484-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17736.amd64fre.winblue_r9.150322-1500
Machine Name:
Kernel base = 0xfffff802`0f81e000 PsLoadedModuleList = 0xfffff802`0faf7850
Debug session time: Sun May 10 21:30:26.019 2015 (UTC - 4:00)
System Uptime: 0 days 4:43:06.661
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, ffffe001239b7028, ba000000, 58000402}

Probably caused by : GenuineIntel

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: ffffe001239b7028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000ba000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000058000402, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

STACK_TEXT:  
ffffd001`4935fcf8 fffff802`0ffe9213 : 00000000`00000124 00000000`00000000 ffffe001`239b7028 00000000`ba000000 : nt!KeBugCheckEx
ffffd001`4935fd00 fffff802`0f9e3f2d : 00000000`00000001 ffffe001`228aea50 ffffe001`228aea50 ffffe001`239b7028 : hal!HalBugCheckSystem+0xcf
ffffd001`4935fd40 fffff802`0ffe96a0 : 00000000`00000728 00000000`00000001 ffffd001`49360130 00000000`00000000 : nt!WheaReportHwError+0x22d
ffffd001`4935fda0 fffff802`0ffe9a0d : ffffe001`00000010 ffffe001`228aea50 ffffd001`4935ff48 ffffe001`228aea50 : hal!HalpMcaReportError+0x50
ffffd001`4935fef0 fffff802`0ffe98f8 : ffffe001`228ae760 00000000`00000001 00000000`00000001 00000000`00000000 : hal!HalpMceHandlerCore+0xe1
ffffd001`4935ff40 fffff802`0ffe9b42 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4
ffffd001`4935ff80 fffff802`0ffe9ccf : ffffe001`228ae760 ffffd001`493601b0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
ffffd001`4935ffb0 fffff802`0f9797bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
ffffd001`4935ffe0 fffff802`0f979571 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
ffffd001`49360120 fffff800`8c3a0214 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171
ffffd001`4937f8e8 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

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_MAE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x124_genuineintel_processor_mae

FAILURE_ID_HASH:  {7c95de0c-286c-8226-45c2-422b4de101d6}

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

.

What could be wrong with motherboard, If you had to guess?