Somebody to analyze minidump file

[mrsotok]

Hey guys!

Just a few minutes ago, I got a BSOD saying: VIDEO_SCHEDULER_INTERNAL_ERROR.
The thing is, that I already have reinstalled-updated drivers, etc. and I haven't OC'ed anything.
Can somebody analyze this minidump for me and tell me any possible causes?


*******************************************************************************
* *
* 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: 0000000000000002, The driver failed upon the submission of a command.
Arg2: ffffffffc000000d
Arg3: ffff91898ed77960
Arg4: ffffb682905abcf0

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


KEY_VALUES_STRING: 1


STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804

SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME: AB350-Gaming 3

SYSTEM_SKU: Default string

SYSTEM_VERSION: Default string

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: F23d

BIOS_DATE: 04/17/2018

BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT: AB350-Gaming 3-CF

BASEBOARD_VERSION: x.x

DUMP_TYPE: 1

BUGCHECK_P1: 2

BUGCHECK_P2: ffffffffc000000d

BUGCHECK_P3: ffff91898ed77960

BUGCHECK_P4: ffffb682905abcf0

CPU_COUNT: 4

CPU_MHZ: c16

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 1

CPU_STEPPING: 1

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


DEFAULT_BUCKET_ID: PAGE_NOT_ZERO_0x119

BUGCHECK_STR: 0x119

PROCESS_NAME: System

CURRENT_IRQL: 0

BAD_PAGES_DETECTED: c

ANALYSIS_SESSION_HOST: DESKTOP-N4OOIDI

ANALYSIS_SESSION_TIME: 09-09-2018 16:04:32.0222

ANALYSIS_VERSION: 10.0.18206.1001 amd64fre

LAST_CONTROL_TRANSFER: from fffff8009674331e to fffff802bbe35ca0

STACK_TEXT:
ffff9189`8ed77888 fffff800`9674331e : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffff9189`8ed77960 : nt!KeBugCheckEx
ffff9189`8ed77890 fffff800`9969b51b : 00000000`00000000 ffffb682`905aa000 ffffb682`905aa000 ffffb682`90528400 : watchdog!WdLogEvent5_WdCriticalError+0xce
ffff9189`8ed778d0 fffff800`996f484e : ffffb682`00000000 ffffb682`905abcf0 ffffb682`905aa000 ffffb682`944f4c00 : dxgmms2!VidSchiSendToExecutionQueue+0x132fb
ffff9189`8ed77a00 fffff800`99700ee4 : ffffb682`944f4c00 ffffb682`905a0a00 00000000`00000000 ffffb682`905a0ac0 : dxgmms2!VidSchiSubmitPagingCommand+0x2ae
ffff9189`8ed77b80 fffff800`99700d5e : ffffb682`9047b500 fffff800`99700cd0 ffffb682`9047b000 00000000`00000000 : dxgmms2!VidSchiRun_PriorityTable+0x174
ffff9189`8ed77bd0 fffff802`bbd86e37 : ffffb682`90478700 fffff800`99700cd0 fffff802`bbb75180 00000065`b4bbbdff : dxgmms2!VidSchiWorkerThread+0x8e
ffff9189`8ed77c10 fffff802`bbe3d116 : fffff802`bbb75180 ffffb682`90478700 fffff802`bbd86df0 00000000`00000000 : nt!PspSystemThreadStartup+0x47
ffff9189`8ed77c60 00000000`00000000 : ffff9189`8ed78000 ffff9189`8ed72000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


THREAD_SHA1_HASH_MOD_FUNC: 3c3aefa711a40e43478598e53abd6873e0c9ed57

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: e9024ed4940a1bba2ed93298e3d12ca95be5601d

THREAD_SHA1_HASH_MOD: 8bc3a1490ebecb3d757d5cd2041e6cd7da5819c4

SYMBOL_NAME: PAGE_NOT_ZERO

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID: PAGE_NOT_ZERO_0x119

PRIMARY_PROBLEM_CLASS: PAGE_NOT_ZERO_0x119

FAILURE_BUCKET_ID: PAGE_NOT_ZERO_0x119

TARGET_TIME: 2018-09-09T12:52:06.000Z

OSBUILD: 17134

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: 2018-08-03 06:10:45

BUILDDATESTAMP_STR: 180410-1804

BUILDLAB_STR: rs4_release

BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804

ANALYSIS_SESSION_ELAPSED_TIME: 62b

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km😛age_not_zero_0x119

FAILURE_ID_HASH: {ad2cb3d0-e791-863f-31d1-c36d87697848}

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

*** Memory manager detected 12 instance(s) of page corruption, target is likely to have memory corruption.

 

[zero_l0gic]

restart the computer see if it works normal after, bsod was because of "bad drivers" try to reinstall the whole driver for the gpu, clean install and try again. if after restart it works normally it would be just bug in the driver.

 

[mrsotok]

I'll try that. Could it be a hardware issue? Like memory or graphics card?

 

[zero_l0gic]

It can be a hardware issue, but if it the first tiime this happend i would suspect drivers or windows