Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

New CPU fails (Solved)


  • Please log in to reply

#1
Machiavelli

Machiavelli

    Expert

  • Expert
  • 3,512 posts

Oh no! The worst day I ever had! 

 

I get a "BlueScreen" (not the standard blue screen - I would call it a Windows 8 Blue Screen, something like that: http://www.sysnative...ctable-bsod.jpg) with the error: WHEA_UNCORRECTABLE_ERROR

 

I thought I did something wrong in UEFI, so I have reset it now to the default values. 

 

I ran Prime95 and directly at the beginning my system crashed (again BlueScreen). 

 

So I thought the temperatures may be too high, so I watched with CoreTemp.exe the idle temperatures and it showed me Max 53 C (I was just surfing a little bit) (Bute the avg of all cores may be 31 C)

 

I'm really, really sad about it, why must this happen to me.

 

System:

Intel Core I7 4790K

ASUS GTX 770

8 GB DDR3 RAM 1600 MHZ

256 GB SSD + 1 TB HDD


  • 0

Advertisements


#2
Machiavelli

Machiavelli

    Expert

  • Topic Starter
  • Expert
  • 3,512 posts

But maybe this is causing it: Windows notifies me that my chipset driver is not installed. Where do I get it? 

 

Mainboard: Asrock Fatality Z97X

 

EDIT: Found the driver, but it didn't solved my problem. Still getting a BSOD when starting Prime95 (better say I get a BSOD after 1 minute)

And when running Prime I get a max temp of 78 C


  • 0

#3
Machiavelli

Machiavelli

    Expert

  • Topic Starter
  • Expert
  • 3,512 posts

I realized now that one power cable wasn't correctly inserted into the mainboard ... so I inserted it now correctly but still get a BSOD. :( I will keep you up to date what I do.


  • 0

#4
Machiavelli

Machiavelli

    Expert

  • Topic Starter
  • Expert
  • 3,512 posts

Update: I'm reinstalling Windows 8. I want to make sure that it is not software related.


  • 0

#5
Machiavelli

Machiavelli

    Expert

  • Topic Starter
  • Expert
  • 3,512 posts
After reinstalling my system still getting BSOD when running Prime. So it is not driver related. So should I send my CPU back to the online store where I bought it?

I'm sorry for posting 5 posts, but just want to make sure that no one oversees it.
  • 0

#6
Machiavelli

Machiavelli

    Expert

  • Topic Starter
  • Expert
  • 3,512 posts

Bios Update didn't solve my Problem.


  • 0

#7
Machiavelli

Machiavelli

    Expert

  • Topic Starter
  • Expert
  • 3,512 posts
This is what I get when I use WinDbg
 
Microsoft ® Windows Debugger Version 6.3.9600.17298 AMD64
Copyright © Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\Windows\Minidump\022015-5656-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
 
 
************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsof...ownload/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsof...ownload/symbols
Executable search path is: 
Windows 8 Kernel Version 9200 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9200.16384.amd64fre.win8_rtm.120725-1247
Machine Name:
Kernel base = 0xfffff802`e321d000 PsLoadedModuleList = 0xfffff802`e34e7a60
Debug session time: Fri Feb 20 02:44:44.461 2015 (UTC + 1:00)
System Uptime: 0 days 0:00:54.067
Loading Kernel Symbols
.
 
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
 
..............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 124, {0, fffffa8007e29028, ba000000, 58000402}
 
Probably caused by : GenuineIntel
 
Followup: MachineOwner
---------
 
3: 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: fffffa8007e29028, 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:  prime95.exe
 
CURRENT_IRQL:  f
 
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
 
STACK_TEXT:  
fffff880`02eda968 fffff802`e399293d : 00000000`00000124 00000000`00000000 fffffa80`07e29028 00000000`ba000000 : nt!KeBugCheckEx
fffff880`02eda970 fffff802`e3376c09 : 00000000`00000001 fffffa80`06a046e0 00000000`00000000 fffffa80`07e29028 : hal!HalBugCheckSystem+0xf9
fffff880`02eda9b0 fffff802`e39926e3 : 00000000`00000728 00000000`00000003 fffff880`02edab10 fffffa80`06a046e0 : nt!WheaReportHwError+0x249
fffff880`02edaa10 fffff802`e399200c : 00000000`00000010 fffffa80`06a046e0 fffff880`02edabc8 fffffa80`06a046e0 : hal!HalpMcaReportError+0x53
fffff880`02edab70 fffff802`e3991f07 : fffffa80`0678ad50 00000000`00000001 00000000`00000003 00000000`00000000 : hal!HalpMceHandlerCore+0xd4
fffff880`02edabc0 fffff802`e3991d64 : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe3
fffff880`02edac00 fffff802`e3992edb : fffffa80`0678ad50 fffff880`02edae30 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4
fffff880`02edac30 fffff802`e329637b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`02edac60 fffff802`e329612e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
fffff880`02edada0 00000001`41b3a337 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x16e
00000000`0410e5f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00000001`41b3a337
 
 
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
---------
 
3: 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: fffffa8007e29028, 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:  prime95.exe
 
CURRENT_IRQL:  f
 
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
 
STACK_TEXT:  
fffff880`02eda968 fffff802`e399293d : 00000000`00000124 00000000`00000000 fffffa80`07e29028 00000000`ba000000 : nt!KeBugCheckEx
fffff880`02eda970 fffff802`e3376c09 : 00000000`00000001 fffffa80`06a046e0 00000000`00000000 fffffa80`07e29028 : hal!HalBugCheckSystem+0xf9
fffff880`02eda9b0 fffff802`e39926e3 : 00000000`00000728 00000000`00000003 fffff880`02edab10 fffffa80`06a046e0 : nt!WheaReportHwError+0x249
fffff880`02edaa10 fffff802`e399200c : 00000000`00000010 fffffa80`06a046e0 fffff880`02edabc8 fffffa80`06a046e0 : hal!HalpMcaReportError+0x53
fffff880`02edab70 fffff802`e3991f07 : fffffa80`0678ad50 00000000`00000001 00000000`00000003 00000000`00000000 : hal!HalpMceHandlerCore+0xd4
fffff880`02edabc0 fffff802`e3991d64 : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe3
fffff880`02edac00 fffff802`e3992edb : fffffa80`0678ad50 fffff880`02edae30 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4
fffff880`02edac30 fffff802`e329637b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`02edac60 fffff802`e329612e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
fffff880`02edada0 00000001`41b3a337 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x16e
00000000`0410e5f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00000001`41b3a337
 
 
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
---------
 
3: 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: fffffa8007e29028, 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:  prime95.exe
 
CURRENT_IRQL:  f
 
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
 
STACK_TEXT:  
fffff880`02eda968 fffff802`e399293d : 00000000`00000124 00000000`00000000 fffffa80`07e29028 00000000`ba000000 : nt!KeBugCheckEx
fffff880`02eda970 fffff802`e3376c09 : 00000000`00000001 fffffa80`06a046e0 00000000`00000000 fffffa80`07e29028 : hal!HalBugCheckSystem+0xf9
fffff880`02eda9b0 fffff802`e39926e3 : 00000000`00000728 00000000`00000003 fffff880`02edab10 fffffa80`06a046e0 : nt!WheaReportHwError+0x249
fffff880`02edaa10 fffff802`e399200c : 00000000`00000010 fffffa80`06a046e0 fffff880`02edabc8 fffffa80`06a046e0 : hal!HalpMcaReportError+0x53
fffff880`02edab70 fffff802`e3991f07 : fffffa80`0678ad50 00000000`00000001 00000000`00000003 00000000`00000000 : hal!HalpMceHandlerCore+0xd4
fffff880`02edabc0 fffff802`e3991d64 : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe3
fffff880`02edac00 fffff802`e3992edb : fffffa80`0678ad50 fffff880`02edae30 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4
fffff880`02edac30 fffff802`e329637b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`02edac60 fffff802`e329612e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
fffff880`02edada0 00000001`41b3a337 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x16e
00000000`0410e5f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00000001`41b3a337
 
 
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
---------
 
3: 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: fffffa8007e29028, 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:  prime95.exe
 
CURRENT_IRQL:  f
 
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
 
STACK_TEXT:  
fffff880`02eda968 fffff802`e399293d : 00000000`00000124 00000000`00000000 fffffa80`07e29028 00000000`ba000000 : nt!KeBugCheckEx
fffff880`02eda970 fffff802`e3376c09 : 00000000`00000001 fffffa80`06a046e0 00000000`00000000 fffffa80`07e29028 : hal!HalBugCheckSystem+0xf9
fffff880`02eda9b0 fffff802`e39926e3 : 00000000`00000728 00000000`00000003 fffff880`02edab10 fffffa80`06a046e0 : nt!WheaReportHwError+0x249
fffff880`02edaa10 fffff802`e399200c : 00000000`00000010 fffffa80`06a046e0 fffff880`02edabc8 fffffa80`06a046e0 : hal!HalpMcaReportError+0x53
fffff880`02edab70 fffff802`e3991f07 : fffffa80`0678ad50 00000000`00000001 00000000`00000003 00000000`00000000 : hal!HalpMceHandlerCore+0xd4
fffff880`02edabc0 fffff802`e3991d64 : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe3
fffff880`02edac00 fffff802`e3992edb : fffffa80`0678ad50 fffff880`02edae30 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4
fffff880`02edac30 fffff802`e329637b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`02edac60 fffff802`e329612e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
fffff880`02edada0 00000001`41b3a337 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x16e
00000000`0410e5f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00000001`41b3a337
 
 
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
---------
 
3: 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: fffffa8007e29028, 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:  prime95.exe
 
CURRENT_IRQL:  f
 
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
 
STACK_TEXT:  
fffff880`02eda968 fffff802`e399293d : 00000000`00000124 00000000`00000000 fffffa80`07e29028 00000000`ba000000 : nt!KeBugCheckEx
fffff880`02eda970 fffff802`e3376c09 : 00000000`00000001 fffffa80`06a046e0 00000000`00000000 fffffa80`07e29028 : hal!HalBugCheckSystem+0xf9
fffff880`02eda9b0 fffff802`e39926e3 : 00000000`00000728 00000000`00000003 fffff880`02edab10 fffffa80`06a046e0 : nt!WheaReportHwError+0x249
fffff880`02edaa10 fffff802`e399200c : 00000000`00000010 fffffa80`06a046e0 fffff880`02edabc8 fffffa80`06a046e0 : hal!HalpMcaReportError+0x53
fffff880`02edab70 fffff802`e3991f07 : fffffa80`0678ad50 00000000`00000001 00000000`00000003 00000000`00000000 : hal!HalpMceHandlerCore+0xd4
fffff880`02edabc0 fffff802`e3991d64 : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe3
fffff880`02edac00 fffff802`e3992edb : fffffa80`0678ad50 fffff880`02edae30 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4
fffff880`02edac30 fffff802`e329637b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`02edac60 fffff802`e329612e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
fffff880`02edada0 00000001`41b3a337 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x16e
00000000`0410e5f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00000001`41b3a337
 
 
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
---------
 
3: 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: fffffa8007e29028, 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:  prime95.exe
 
CURRENT_IRQL:  f
 
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
 
STACK_TEXT:  
fffff880`02eda968 fffff802`e399293d : 00000000`00000124 00000000`00000000 fffffa80`07e29028 00000000`ba000000 : nt!KeBugCheckEx
fffff880`02eda970 fffff802`e3376c09 : 00000000`00000001 fffffa80`06a046e0 00000000`00000000 fffffa80`07e29028 : hal!HalBugCheckSystem+0xf9
fffff880`02eda9b0 fffff802`e39926e3 : 00000000`00000728 00000000`00000003 fffff880`02edab10 fffffa80`06a046e0 : nt!WheaReportHwError+0x249
fffff880`02edaa10 fffff802`e399200c : 00000000`00000010 fffffa80`06a046e0 fffff880`02edabc8 fffffa80`06a046e0 : hal!HalpMcaReportError+0x53
fffff880`02edab70 fffff802`e3991f07 : fffffa80`0678ad50 00000000`00000001 00000000`00000003 00000000`00000000 : hal!HalpMceHandlerCore+0xd4
fffff880`02edabc0 fffff802`e3991d64 : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe3
fffff880`02edac00 fffff802`e3992edb : fffffa80`0678ad50 fffff880`02edae30 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4
fffff880`02edac30 fffff802`e329637b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`02edac60 fffff802`e329612e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
fffff880`02edada0 00000001`41b3a337 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x16e
00000000`0410e5f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00000001`41b3a337
 
 
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
---------

  • 0

#8
Machiavelli

Machiavelli

    Expert

  • Topic Starter
  • Expert
  • 3,512 posts

OK, I think I may solve this myself. One positive side, I gain new experience. 

 

What I did so far:

 

  • Updates all drivers. => BSOD under Prime
  • Reinstalled the system if the BSOD is software related => still BSOD => Hardware related
  • Updated my BIOS to the newest version => Still BSOD
  • Updated all Drivers via UEFI => Still BSOD

 

What I will do soon:

 

  • Running Memtest to see if my RAM is okay
  • Running chkdsk and other tools to see if my HDD and SSD is okay
  • Running other CPU Benchmarks and watch temperature

And I will also check if all cables fit correctly.

 

I expect that Memtest will show me 0 errors as well as the HDD/SSD checks. 

 

So we have two possibilties, which can cause my problem:

  • CPU
  • Mainboard

The temps are OK, my research shows that the BSOD indicates that the L2 Cache of the processor tells Windows that it is damaged. My research also shows that the Mainboard could be the cause as well as the CPU itself.

 

So, if in case all checks are coming back "clean" (HDD/SSD Check + Memtest) what should I send back to the online store where I bought the hardware? Mainboard or CPU? Or both?


  • 0

#9
iammykyl

iammykyl

    Tech Staff

  • Technician
  • 6,754 posts

Gday Machiavelli.

I would arrange RMAs and send both parts back, because.

If you get a replacement CPU, you will need to reassemble and test, if you have the same problem, you will need to disassemble, get a replacement MB, reassemble and test again.

A lot less trouble to get both parts replaced, assemble and test, once.   Less chance of damage instilling the CPU.

 

Regardless of which you choose, inspect the MB socket for any damage, bent pins.   Don't forget to reinstall the CPU socket safety cap before shipping back. 


  • 0

#10
Machiavelli

Machiavelli

    Expert

  • Topic Starter
  • Expert
  • 3,512 posts

SMART Datas of both Hard drives are attached. 

Memtest ran 60 minutes, 0 Errors

Run Chkdsk, but how do I get a result (if something was found) as I wasn't always at my system

 

So, what I know now:

 

  • RAM is OK
  • Hard Drives are OK

What I do now:

  • Run one Graphic card benchmark to see if Graphic card is damaged (Graphic card is NOT damaged!)
  • Run further CPU benchmarks to see the temps (if it is a temperature problem)
  • Collect all data I have (evidential material may be needed for later) (Done)
  • Contacting the support where I bought the Hardware (Done)

Attached Thumbnails

  • HDD SMART.jpg
  • SSD SMART.jpg

  • 0

Advertisements


#11
iammykyl

iammykyl

    Tech Staff

  • Technician
  • 6,754 posts

There are three methods to get your log on this page, > http://answers.micro...58-32d2fbf92361

 

Edit.

 

Sorry, just noticed the topic title.   Is this actually a new CPU install? or has it been running for a while and just started to give problems.?


  • 0

#12
Machiavelli

Machiavelli

    Expert

  • Topic Starter
  • Expert
  • 3,512 posts

No hope, the system freezes from time to time. I will send both parts back to the online store and let it replace. :)

 

Many thanks, my friend iammykyl. :)


  • 0

#13
iammykyl

iammykyl

    Tech Staff

  • Technician
  • 6,754 posts

Please look at reply 11 again, made edit.


  • 0

#14
Fusionbomb

Fusionbomb

    GeekU Junior

  • GeekU Junior
  • 633 posts

Machiavelli,

    Just in case you didn't notice iammykyl's edited response:
 

Sorry, just noticed the topic title.   Is this actually a new CPU install? or has it been running for a while and just started to give problems.?



Also, one thing I would recommend before sending the parts in for replacement...  maybe try removing the CMOS battery [temporarily] from the motherboard (this will reset CMOS/BIOS).  While this is certainly not a guaranteed fix, I have often seen it fix some pretty strange issues (including unexplainable BSoDs).  It's not hard to do, doesn't take long, and may end up saving you the hassle of returning the parts.

 

Good luck!


  • 0

#15
Machiavelli

Machiavelli

    Expert

  • Topic Starter
  • Expert
  • 3,512 posts

iammykyl,

I have installed the new CPU yesterday and realized at evening that it gives BSOD when it is a high usage. I will try to remove CMOS Battery


  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP