Jump to content

BSOD WHEA_UNCORRECTABLE_ERROR

Hi guys, Few days ago I built my new rig. Unfortunately since yesterday I am getting BSOD almost every time when I open 3Ds Max or Adobe Photoshop. I read tons of forums, did stress tests, error checks, overclock, removing overclocks, updating BIOS,  installing new chipset drivers and everything. At least I learn something new. How to read a dump file :D I still cant get it work properly. Some people say its heating problem, but HWMonitor shows not higher temps than 40 degrees in Prime95 stress test. 
My rig is :


CPU - Intel I9 - 7940x
MOBO - Asus Rampage Apex 6
DDR4 - Corsair Vengeance LP 3446 mhz ( or something like this)
PSU - EVGA 1000W G2
HDD/SSD - 850 EVO, 960 PRO, WD Black 4TB, WD Blue 2TB, WD Green 1TB
GPU - 1x 1080ti Hybrid and 1x 1080 FTW both EVGA
Cooler - EVGA CLC 280 

 

 

 


What dmp file contains is: 

 

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, ffffe585f4b18028, b2000000, 70005}

Probably caused by : GenuineIntel

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

nt!KeBugCheckEx:
fffff801`acf680e0 48894c2408      mov     qword ptr [rsp+8],rcx ss:fffff801`af052a10=0000000000000124
0: 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: ffffe585f4b18028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000070005, Low order 32-bits of the MCi_STATUS value.

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


KEY_VALUES_STRING: 1


TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.16299.125 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER:  System manufacturer

SYSTEM_PRODUCT_NAME:  System Product Name

SYSTEM_SKU:  SKU

SYSTEM_VERSION:  System Version

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  0702

BIOS_DATE:  08/08/2017

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  ROG RAMPAGE VI APEX

BASEBOARD_VERSION:  Rev 1.xx

DUMP_TYPE:  2

BUGCHECK_P1: 0

BUGCHECK_P2: ffffe585f4b18028

BUGCHECK_P3: b2000000

BUGCHECK_P4: 70005

BUGCHECK_STR:  0x124_GenuineIntel

CPU_COUNT: 1c

CPU_MHZ: c18

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 55

CPU_STEPPING: 4

CPU_MICROCODE: 6,55,4,0 (F,M,S,R)  SIG: 2000026'00000000 (cache) 2000026'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  3dsmax.exe

CURRENT_IRQL:  f

ANALYSIS_SESSION_HOST:  DESKTOP-DN9J836

ANALYSIS_SESSION_TIME:  12-18-2017 23:42:24.0221

ANALYSIS_VERSION: 10.0.17061.1000 amd64fre

STACK_TEXT:  
fffff801`af052a08 fffff801`ad711f1f : 00000000`00000124 00000000`00000000 ffffe585`f4b18028 00000000`b2000000 : nt!KeBugCheckEx
fffff801`af052a10 fffff808`57aa148a : ffffe585`f4b18028 ffffe585`f49fe380 ffffe585`f49fe380 ffffe585`f49fe380 : hal!HalBugCheckSystem+0xcf
fffff801`af052a50 fffff801`ad084e11 : ffffe585`f4b18028 00000000`00000000 ffffe585`f49fe380 ffffe585`f49fe380 : PSHED!PshedBugCheckSystem+0xa
fffff801`af052a80 fffff801`ad712460 : 00000000`00000728 00000000`00000000 00000000`00000000 00000000`00000000 : nt!WheaReportHwError+0x261
fffff801`af052ae0 fffff801`ad7127c0 : 00000000`00000010 00000000`00000000 fffff801`af052c88 00000000`00000000 : hal!HalpMcaReportError+0x50
fffff801`af052c30 fffff801`ad7126ae : ffffe585`f2b82000 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xe0
fffff801`af052c80 fffff801`ad7128f2 : 00000000`0000001c 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xda
fffff801`af052cc0 fffff801`ad712a80 : ffffe585`f2b82000 fffff801`af052ef0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
fffff801`af052cf0 fffff801`acf727fb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff801`af052d20 fffff801`acf7256c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
fffff801`af052e60 fffff801`ace94e1b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x1ac
fffff801`af045b00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PpmPerfSnapUtility+0x13b


THREAD_SHA1_HASH_MOD_FUNC:  54e96836b8f28c3e60830c5b326a57e06bb5462c

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  279faae662b6739ae547698281b8ad5abb6a1162

THREAD_SHA1_HASH_MOD:  f54f37269c2ab6cbba1c51c2fcdb3923b9cd4be8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_MAE

PRIMARY_PROBLEM_CLASS:  0x124_GenuineIntel_PROCESSOR_MAE

TARGET_TIME:  2017-12-18T13:20:36.000Z

OSBUILD:  16299

OSSERVICEPACK:  125

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2017-12-07 23:55:32

BUILDDATESTAMP_STR:  160101.0800

BUILDLAB_STR:  WinBuild

BUILDOSVER_STR:  10.0.16299.125

ANALYSIS_SESSION_ELAPSED_TIME:  48a

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x124_genuineintel_processor_mae

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

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


I am pretty sure it's not the heat. Any idea what could it be ? I would really appreciate your help guys ! Thank you 

Link to comment
Share on other sites

Link to post
Share on other sites

99% of the time that error means an unstable CPU whether it's from overclocking/underclocking or if it is just faulty to begin with.

[Out-of-date] Want to learn how to make your own custom Windows 10 image?

 

Desktop: AMD R9 3900X | ASUS ROG Strix X570-F | Radeon RX 5700 XT | EVGA GTX 1080 SC | 32GB Trident Z Neo 3600MHz | 1TB 970 EVO | 256GB 840 EVO | 960GB Corsair Force LE | EVGA G2 850W | Phanteks P400S

Laptop: Intel M-5Y10c | Intel HD Graphics | 8GB RAM | 250GB Micron SSD | Asus UX305FA

Server 01: Intel Xeon D 1541 | ASRock Rack D1541D4I-2L2T | 32GB Hynix ECC DDR4 | 4x8TB Western Digital HDDs | 32TB Raw 16TB Usable

Server 02: Intel i7 7700K | Gigabye Z170N Gaming5 | 16GB Trident Z 3200MHz

Link to comment
Share on other sites

Link to post
Share on other sites

Try reseat everything. The fact that prime95 works without crashing suggests that it is not the voltage which is the issue. Try run Furmark to check the GPU, as far as I can tell 3dmax and Adobe Photoshop both use the GPU while P95 does not.

Link to comment
Share on other sites

Link to post
Share on other sites

I overclocked it at first. That blue screen started to appear 2 days after the clock. I removed all changes in bios. Everything is by default now.

Furmark works normally for about 10 min. Gpu was at 40 degrees max.

Maybe chipset driver doesnt work properly.

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×