Windows 10 BSOD 124 during gameplay

Erup777 · Jan 29, 2016

My PC was running fine before (It's a build from last Black Friday) and today, I am getting BSOD WHEA_UNCORRECTABLE_ERROR on Windows 10 Home 64 during gameplay on WoW. (It boots up fine, but when I click something to go to a different loading screen, it gives me BSOD)

Parts are:
i5 Skylake 6600K CPU
GA Z170X-UD5 Mobo
MSI R9 390 GPU
G.Skill Ripjaws V Series 2x8GB DDR4 2400 RAM
Corsair HX 750i PSU
Samsung 850 EVO 500 GB SSD (WoW installed on SSD)
2TB WD Black HD
Cooler Master Hyper 212 EVO cooler

Never overclocked before.

I've used CPUID to monitor heat and CPU is around 23-40C and GPU goes from 40-65C

I looked at other posts about the same error, and I have checked for hardware errors (no bent cpu pins, remove and plug back in everything, check bios, reset bios, stressing CPU-4hr, reinstalled drivers for GPU) If there are other checks I should do, please let me know

PLEASE HELP ME!

Below is the most recent dump info

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

Loading Dump File [C:\Windows\Minidump\012916-15562-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 10586.63.amd64fre.th2_release.160104-1513
Machine Name:
Kernel base = 0xfffff802`d687f000 PsLoadedModuleList = 0xfffff802`d6b5dc70
Debug session time: Fri Jan 29 15:19:33.727 2016 (UTC - 8:00)
System Uptime: 0 days 1:08:05.363
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, ffffe001cc9fe028, f2000000, 14}

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

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

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10586.63.amd64fre.th2_release.160104-1513

SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME: Z170X-UD5

SYSTEM_SKU: To be filled by O.E.M.

SYSTEM_VERSION: To be filled by O.E.M.

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: F4

BIOS_DATE: 10/21/2015

BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT: Z170X-UD5-CF

BASEBOARD_VERSION: x.x

DUMP_TYPE: 2

BUGCHECK_P1: 0

BUGCHECK_P2: ffffe001cc9fe028

BUGCHECK_P3: f2000000

BUGCHECK_P4: 14

BUGCHECK_STR: 0x124_GenuineIntel

CPU_COUNT: 4

CPU_MHZ: db0

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: 39'00000000 (cache) 39'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: Wow-64.exe

CURRENT_IRQL: f

ANALYSIS_SESSION_HOST: BRANDY

ANALYSIS_SESSION_TIME: 01-29-2016 15:21:27.0260

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

STACK_TEXT:
ffffd001`ed8a35f8 fffff802`d6841f1f : 00000000`00000124 00000000`00000000 ffffe001`cc9fe028 00000000`f2000000 : nt!KeBugCheckEx
ffffd001`ed8a3600 fffff802`d6a8fe48 : ffffe001`cc9fe028 ffffe001`ca8cbc60 ffffe001`ca8cbc60 ffffe001`ca8cbc60 : hal!HalBugCheckSystem+0xcf
ffffd001`ed8a3640 fffff802`d684240c : 00000000`00000728 00000000`00000003 ffffd001`ed8a3a30 00000000`00000000 : nt!WheaReportHwError+0x258
ffffd001`ed8a36a0 fffff802`d6842764 : ffffe001`00000010 ffffe001`ca8cbc60 ffffd001`ed8a3848 ffffe001`ca8cbc60 : hal!HalpMcaReportError+0x50
ffffd001`ed8a37f0 fffff802`d684264e : ffffe001`ca8cb870 00000000`00000001 00000000`00000003 00000000`00000000 : hal!HalpMceHandlerCore+0xe8
ffffd001`ed8a3840 fffff802`d684288e : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xda
ffffd001`ed8a3880 fffff802`d6842a10 : ffffe001`ca8cb870 ffffd001`ed8a3ab0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
ffffd001`ed8a38b0 fffff802`d69cb27b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
ffffd001`ed8a38e0 fffff802`d69cb031 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
ffffd001`ed8a3a20 fffff802`d68a95eb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171
ffffd001`f2f18f90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiReturnCommit+0xb

STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: d5fcad8132b2f6285c3cfe98ad39e0042822b60f

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 2974f34d8086b7c28d67931aff94674c2afdfe4a

THREAD_SHA1_HASH_MOD: bba6629b38ee48af58586b1285e003efb528212b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION:

FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_TLB

BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_TLB

PRIMARY_PROBLEM_CLASS: 0x124_GenuineIntel_PROCESSOR_TLB

TARGET_TIME: 2016-01-29T23:19:33.000Z

OSBUILD: 10586

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2016-01-04 17:28:56

BUILDDATESTAMP_STR: 160104-1513

BUILDLAB_STR: th2_release

BUILDOSVER_STR: 10.0.10586.63.amd64fre.th2_release.160104-1513

ANALYSIS_SESSION_ELAPSED_TIME: 33c

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x124_genuineintel_processor_tlb

FAILURE_ID_HASH: {03e060e2-37bb-3e02-4bd4-77932f0be153}

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

Andrei-Florin Gogan · Jan 29, 2016

Are power saving features disable in BIOS? make sure they are.

Erup777 · Jan 29, 2016

Andrei-Florin Gogan :

Most of the power options (voltage options actually) are in Auto and settings in power management tab is disabled.

Do you recommend me putting up the voltage manually? I am not overclocking and I do not want to burn the cpu.

Let me know ^^

Andrei-Florin Gogan · Jan 29, 2016

Erup777 :

I do not recommend you do OC or putting more voltage through your CPU if you don't know what you are doing.I would clear the CMOS as a first solution. Reseting the BIOS to default does not clear the CMOS while reseting the CMOS does reset the BIOS as well.

Erup777 · Jan 29, 2016

I've researched a little more. There was a BIOS update on my motherboard about two weeks ago and although it is a Beta update, it has "Fix Intel Skylake CPU Prime 95 issue" on it and I will update the post if I get further BSOD.

Also, I put PCH core on High. Hopefully that might be what Andrei-Florin Gogan addressed.

Andrei-Florin Gogan · Jan 29, 2016

Erup777 :

I highly doubt a single patch on motherboard driver version will make your system unstable. Try clearing the CMOS from your motherboard after you're done updating the driver

Erup777 · Jan 29, 2016

Andrei-Florin Gogan :

Erup777 :

I highly doubt a single patch on motherboard driver version will make your system unstable. Try clearing the CMOS from your motherboard after you're done updating the driver

Will do!

Erup777 · Jan 29, 2016

Cleared CMOS, I tried running wow for about 10 minutes, changing loading screens. Will update if there are further BSOD. If I don't get anything in 24 hours will go for your answer!

Thanks so far!

Andrei-Florin Gogan · Jan 29, 2016

No problem mate. glad to have helped and enjoy your PC.

Erup777 · Jan 30, 2016

A crash today...
I wonder why it's WoW. Other heavy load games like fallout 4 works perfectly.

Will reinstall wow

Andrei-Florin Gogan · Jan 30, 2016

A clean install will probably help yes....

Erup777 · Jan 30, 2016

Still happens. It doesn't happen when it's on High quality video setting but happens almost immediately after Ultra setting. My hardware should support it.

Did a clean GPU driver install again using DDU

Sigh... thinking if I should send it CPU back in for warranty

Andrei-Florin Gogan · Jan 30, 2016

Well, you can try that if you want sure......to me somehow it still sounds like a driver issue but then again, if you've done every step correctly, I'm a bit lost now haha

Erup777 · Feb 6, 2016

Got replacement CPU today. Works fine. I guess I am the VERY FEW unlucky person with a faulty CPU.

Thanks for trying to help Andrei-Florin Gogan

Search

Windows 10 BSOD 124 during gameplay

Erup777

Reputable

Andrei-Florin Gogan

Reputable

Erup777

Reputable

Andrei-Florin Gogan

Reputable

Erup777

Reputable

Andrei-Florin Gogan

Reputable

Erup777

Reputable

Erup777

Reputable

Andrei-Florin Gogan

Reputable

Erup777

Reputable

Andrei-Florin Gogan

Reputable

Erup777

Reputable

Andrei-Florin Gogan

Reputable

Erup777

Reputable

TRENDING THREADS

Latest posts

Moderators online

Share this page