problem with gig r9 285

ActionJaxon011 · October 3, 2014

after installing my new 285 i started experiencing bsod's, but only in video playback. all games play completely fine. bsod error is (video scheduler internal error). all drivers have been updated. i deleted the old graphics drives and reinstalled the new. Any information on my situation is greatly appreciated!

pc specs:

mobo- 760gm-p34(fx)

processor- fx-6300

ram- adata 1600

psu- evga 600B

dumpfiles.....

Microsoft ® Windows Debugger Version 6.3.9600.17237 AMD64

Loading Dump File [C:\Windows\MEMORY.DMP]

Kernel Bitmap Dump File: Only kernel address space is available

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 119, {1, 1ce7, 1cea, ffffe0010f52f010}

Probably caused by : watchdog.sys ( watchdog!WdLogEvent5_WdCriticalError+ce )

Followup: MachineOwner

---------

3: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

VIDEO_SCHEDULER_INTERNAL_ERROR (119)

The video scheduler has detected that fatal violation has occurred. This resulted

in a condition that video scheduler can no longer progress. Any other values after

parameter 1 must be individually examined according to the subtype.

Arguments:

Arg1: 0000000000000001, The driver has reported an invalid fence ID.

Arg2: 0000000000001ce7

Arg3: 0000000000001cea

Arg4: ffffe0010f52f010

Debugging Details:

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

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x119

PROCESS_NAME: System

CURRENT_IRQL: 9

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

LAST_CONTROL_TRANSFER: from fffff801d419e9ca to fffff8016d362ca0

STACK_TEXT:

ffffd001`71027488 fffff801`d419e9ca : 00000000`00000119 00000000`00000001 00000000`00001ce7 00000000`00001cea : nt!KeBugCheckEx

ffffd001`71027490 fffff801`d3faee28 : 00000000`00001ce6 00000000`00000000 ffffe001`0f8d9fc0 00000000`00000000 : watchdog!WdLogEvent5_WdCriticalError+0xce

ffffd001`710274d0 fffff801`d3fa15e2 : 00000000`00000001 ffffe001`0000000e 00000000`00000000 ffffe001`00000000 : dxgmms1!VidSchiProcessIsrCompletedPacket+0xd778

ffffd001`710275c0 fffff801`d3fb6f99 : ffffd001`00001ce7 ffffe001`0cd1c000 00000000`00000001 00000000`00001000 : dxgmms1!VidSchDdiNotifyInterruptWorker+0x382

ffffd001`71027620 fffff801`6d363932 : 00000000`00000000 fffff801`6d631022 ffffd001`71027690 ffffc001`06a23a10 : dxgmms1!VidSchiCallNotifyInterruptAtISR+0x55

ffffd001`71027650 fffff801`d402273f : ffffe001`0cd68598 fffff801`d3fb6f44 ffffd001`71027710 fffff801`d41a74e2 : nt!KeSynchronizeExecution+0x42

ffffd001`71027690 fffff801`d3fb721e : 00000000`00001ce7 ffffd001`71027739 ffffe001`0f8d9000 ffffe001`0cd1c000 : dxgkrnl!DpSynchronizeExecution+0xaf

ffffd001`710276e0 fffff801`d3fb59f9 : ffffe001`112c8500 ffffe001`112c85c8 ffffe001`0d2b8010 ffffe001`0f8d9000 : dxgmms1!VidSchiCompletePendingCommandInNodeHwQueue+0x10e

ffffd001`710277a0 fffff801`d3ff698b : ffffe001`0f8d9000 00000000`00000000 00000000`00000001 ffffe001`0f8d9001 : dxgmms1!VidSchiResetEngine+0x485

ffffd001`71027870 fffff801`d3fea39c : ffffe001`0f8d9000 00000000`0000000c 00000000`01312d00 ffffe001`0f8d9000 : dxgmms1!VidSchiResetEngines+0x83

ffffd001`710278b0 fffff801`d3fa3ba8 : ffffffff`ff676980 00000000`00000000 ffffd001`71027a40 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x1862c

ffffd001`71027940 fffff801`d3fded4a : ffffe001`0cd1c000 ffffe001`0cd1c000 ffffe001`0ff7b680 ffffe001`00000000 : dxgmms1!VidSchiScheduleCommandToRun+0x448

ffffd001`71027af0 fffff801`d3fded1d : ffffe001`0cd1c000 00000000`00000080 ffffe001`0f8f3880 ffffe001`00000000 : dxgmms1!VidSchiRun_PriorityTable+0x2a

ffffd001`71027b40 fffff801`6d2e8514 : fffff801`6d55ca00 ffffe001`0f8f3880 ffffd001`71027c10 fffff801`6d36607d : dxgmms1!VidSchiWorkerThread+0x8d

ffffd001`71027b80 fffff801`6d3692c6 : fffff801`6d4f5180 ffffe001`0f8f3880 fffff801`6d55ca00 ffffc000`fa839700 : nt!PspSystemThreadStartup+0x58

ffffd001`71027be0 00000000`00000000 : ffffd001`71028000 ffffd001`71021000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND: kb

FOLLOWUP_IP:

watchdog!WdLogEvent5_WdCriticalError+ce

fffff801`d419e9ca cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: watchdog!WdLogEvent5_WdCriticalError+ce

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: watchdog

IMAGE_NAME: watchdog.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 530894af

IMAGE_VERSION: 6.3.9600.17031

BUCKET_ID_FUNC_OFFSET: ce

FAILURE_BUCKET_ID: 0x119_1_DRIVER_REPORTED_INVALID_FENCE_ID_watchdog!WdLogEvent5_WdCriticalError

BUCKET_ID: 0x119_1_DRIVER_REPORTED_INVALID_FENCE_ID_watchdog!WdLogEvent5_WdCriticalError

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x119_1_driver_reported_invalid_fence_id_watchdog!wdlogevent5_wdcriticalerror

FAILURE_ID_HASH: {68b70bfc-2e86-47b4-b565-b2a669564552}

Followup: MachineOwner

---------

ActionJaxon011 · October 3, 2014

SOLVED! for whatever reason amd catalyst 14.9 does not agree with my setup. i reverted back to the beta version and all problems went away

Namekiano · October 8, 2014

hi ActionJaxon011.

What is the beta version installed you wear? I have the same problem as you, please tell me which version you take. the 14.9.1 beta? you help me a lot because I feel the same with the videos and I have a R9 285 also.

A greeting and help.