Computer Crash (Black Screen) - WHEA_UNCORRECTABLE_ERROR

AntiAntiChrist

Reputable
Jul 4, 2015
4
0
4,510
For the past week, I have been having occasional crashes when playing games for a certain period of time (depending on the game). But instead of coming up as a BSoD, it just shows a black screen (on both monitors) and restarts. The audio also buzzes. It only started happening after I upgraded from a R7 260x to a GTX 960. Some games (e.g. Rust) crash as soon as it loads the actual 3D part of the game (not the main menu) but some (such as CS:GO) work perfectly fine in-game for quite a while but eventually end up crashing after 30 mins - 2+ hours. Gang Beasts crashes as soon as it loads up the start screen.

My graphics drivers are up-to-date.

PC Specs:
-Zotac 2GB GTX 960 (Non-Amp edition)
-AMD FX 6300 @ Default 3.5GHz
-Gigabyte 78LMT-USB3 Motherboard
-8GB of RAM (2x 4GB DDR3 sticks @ 1600Mhz)
-1TB HDD
-1TB HDD
-600W PSU
-Windows 10

Dump File:
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: ffffe000fcaa6038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10240.16644.amd64fre.th1.160104-1507

DUMP_TYPE: 2

BUGCHECK_P1: 0

BUGCHECK_P2: ffffe000fcaa6038

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BUGCHECK_STR: 0x124_AuthenticAMD

CPU_COUNT: 6

CPU_MHZ: dbc

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 2

CPU_STEPPING: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: DESKTOP-OFTMGCB

ANALYSIS_SESSION_TIME: 01-17-2016 14:59:46.0799

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

STACK_TEXT:
ffffd000`2b5d05a0 fffff801`7446c110 : 00000000`00000000 ffffe000`fcaa6010 fffff801`7438b600 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x81
ffffd000`2b5d0ad0 fffff801`742c7848 : ffffe000`fcaa6010 fffff801`742c8a24 fffff801`7438b6a0 fffff801`7444d340 : nt!WheapCreateTriageDumpFromPreviousSession+0x44
ffffd000`2b5d0b00 fffff801`742c8a49 : fffff801`7438b640 fffff801`742c8a24 fffff801`7438b6a0 fffff801`0c315b40 : nt!WheapProcessWorkQueueItem+0x48
ffffd000`2b5d0b40 fffff801`740eddd9 : fffff801`7444d340 ffffe000`fa1ad040 fffff801`7444d200 ffffe000`fc647860 : nt!WheapWorkQueueWorkerRoutine+0x25
ffffd000`2b5d0b70 fffff801`7415b758 : 00000000`00000000 00000000`00000080 fffff801`7444d340 ffffe000`fa1ad040 : nt!ExpWorkerThread+0xe9
ffffd000`2b5d0c00 fffff801`741c85b6 : ffffd000`2b707180 ffffe000`fa1ad040 ffffe000`fa103040 00000000`00000000 : nt!PspSystemThreadStartup+0x58
ffffd000`2b5d0c60 00000000`00000000 : ffffd000`2b5d1000 ffffd000`2b5cb000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 26acd050bd9f055d0a04825d57b9e0e6be9c1a07

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 0762d19c9707a7cb91fe916d5704b5d228ecfb6e

THREAD_SHA1_HASH_MOD: 30a3e915496deaace47137d5b90c3ecc03746bf6

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME: AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION:

FAILURE_BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV

PRIMARY_PROBLEM_CLASS: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV

TARGET_TIME: 2016-01-17T14:43:34.000Z

OSBUILD: 10240

OSSERVICEPACK: 0

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: 2016-01-05 02:09:59

BUILDDATESTAMP_STR: 160104-1507

BUILDLAB_STR: th1

BUILDOSVER_STR: 10.0.10240.16644.amd64fre.th1.160104-1507

ANALYSIS_SESSION_ELAPSED_TIME: 446

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x124_authenticamd_processor_bus_prv

FAILURE_ID_HASH: {6fd7875b-9a1b-9e09-d6d6-816026a875c8}

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

011716-63250-01.zip
 
Solution
your memory dump shows that the system was running for 9 seconds. This means your CPU was reset and rebooted before the power was stable. Since it was a panic bugcheck, the BIOS info is not saved in the memory dump.

You should focus on finding out why the CPU was reset rather than looking into this bugcheck.


your memory dump shows that the system was running for 9 seconds. This means your CPU was reset and rebooted before the power was stable. Since it was a panic bugcheck, the BIOS info is not saved in the memory dump.

You should focus on finding out why the CPU was reset rather than looking into this bugcheck.


 
Solution