AnsweredAssumed Answered

r9 290 device stuck in infinite loop and black screen problem

Question asked by maxime506 on Sep 9, 2017

Hi,

 

I have a ASUS reference 290x, I was planning to sell the card, so I detach the watercooling kit (Kraken G10 + Corsair H55) and put back the stock cooler.

 

When testing, if I put my card in the primary PCI-E x16 slot, I have blackscreen, with the monitor giving "No Signal" with HDMI

 

if I put my card in the secondary PCI-E, boot with a RX 480, it can be detected, and I can install the 17.7.1 driver. However, if I start benchmarking, open a mining software on the R9 290, it results in instant BSOD "device stuck in infinite loop, 0X00000EA"

 

Anyway someone can help?

 

My rig specs:

 

FX-8300 stock,

 

16GB Crucial RAM

 

Gigabyte 970A-DS3P

 

CORSAIR CX750M PSU

 

 

Minidump file:

 

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: ffff9989a1718028, Address of the WHEA_ERROR_RECORD structure.

Arg3: 00000000b6000000, High order 32-bits of the MCi_STATUS value.

Arg4: 0000000000100153, Low order 32-bits of the MCi_STATUS value.

 

 

Debugging Details:

------------------

 

 

 

 

DUMP_CLASS: 1

 

 

DUMP_QUALIFIER: 400

 

 

BUILD_VERSION_STRING:  10.0.14393.1480 (rs1_release.170706-2004)

 

 

DUMP_TYPE:  2

 

 

DUMP_FILE_ATTRIBUTES: 0x9

  Hiber Crash Dump

  Kernel Generated Triage Dump

 

 

BUGCHECK_P1: 0

 

 

BUGCHECK_P2: ffff9989a1718028

 

 

BUGCHECK_P3: b6000000

 

 

BUGCHECK_P4: 100153

 

 

BUGCHECK_STR:  0x124_AuthenticAMD

 

 

CPU_COUNT: 8

 

 

CPU_MHZ: e85

 

 

CPU_VENDOR:  AuthenticAMD

 

 

CPU_FAMILY: 15

 

 

CPU_MODEL: 2

 

 

CPU_STEPPING: 0

 

 

CUSTOMER_CRASH_COUNT:  1

 

 

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

 

 

CURRENT_IRQL:  f

 

 

ANALYSIS_SESSION_HOST:  MAX-PC

 

 

ANALYSIS_SESSION_TIME:  09-09-2017 23:34:53.0139

 

 

ANALYSIS_VERSION: 10.0.15063.468 amd64fre

 

 

STACK_TEXT: 

ffffb100`8a64a728 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx

 

 

 

 

STACK_COMMAND:  kb

 

 

THREAD_SHA1_HASH_MOD_FUNC:  81a83ae0317433a47fcc36991983df3b6e638b71

 

 

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  6e16edd8c7dd677734fdbcd2397a2e35e9fae964

 

 

THREAD_SHA1_HASH_MOD:  76cd06466d098060a9eb26e5fd2a25cb1f3fe0a3

 

 

FOLLOWUP_NAME:  MachineOwner

 

 

MODULE_NAME: AuthenticAMD

 

 

IMAGE_NAME:  AuthenticAMD

 

 

DEBUG_FLR_IMAGE_TIMESTAMP:  0

 

 

FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_CACHE

 

 

BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_CACHE

 

 

PRIMARY_PROBLEM_CLASS:  0x124_AuthenticAMD_PROCESSOR_CACHE

 

 

TARGET_TIME:  2017-09-08T19:46:40.000Z

 

 

OSBUILD:  14393

 

 

OSSERVICEPACK:  1480

 

 

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-07-07 03:26:09

 

 

BUILDDATESTAMP_STR:  170706-2004

 

 

BUILDLAB_STR:  rs1_release

 

 

BUILDOSVER_STR:  10.0.14393.1480

 

 

ANALYSIS_SESSION_ELAPSED_TIME:  ab7

 

 

ANALYSIS_SOURCE:  KM

 

 

FAILURE_ID_HASH_STRING:  km:0x124_authenticamd_processor_cache

 

 

FAILURE_ID_HASH:  {b533751b-676e-7546-bcdc-24e6c40d0064}

 

 

Followup:     MachineOwner

---------

Outcomes