help with Minidump analysis

[lost_maniac_]

Hi.! can you help me with the minidumb analisys?
Here is the Text:

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 17134 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff801`7f604000 PsLoadedModuleList = 0xfffff801`7f9b2210
Debug session time: Thu Sep 27 11:28:05.656 2018 (UTC - 4:00)
System Uptime: 0 days 0:00:56.408
*******************************************************************************
* *
* 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: ffffdf0a0d2e7860
Arg4: ffffaa0bd3d02230

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x119

PROCESS_NAME: System

CURRENT_IRQL: 0

BAD_PAGES_DETECTED: b58f

LAST_CONTROL_TRANSFER: from fffff8066b45331e to fffff8017f7ad380

STACK_TEXT:
ffffdf0a`0d2e7788 fffff806`6b45331e : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffffdf0a`0d2e7860 : nt!KeBugCheckEx
ffffdf0a`0d2e7790 fffff806`6bcdb51b : 00000000`00000000 ffffaa0b`d3d00000 ffffdf0a`0d2e7899 ffffaa0b`d3d00000 : watchdog!WdLogEvent5_WdCriticalError+0xce
ffffdf0a`0d2e77d0 fffff806`6bd3484e : ffffaa0b`00000000 ffffaa0b`d3d02230 ffffaa0b`d3d00000 ffffaa0b`d5db7c00 : dxgmms2!VidSchiSendToExecutionQueue+0x132fb
ffffdf0a`0d2e7900 fffff806`6bd40ee4 : ffffaa0b`d5db7c00 ffffaa0b`d39eea00 00000000`00000000 ffffaa0b`d39eeac0 : dxgmms2!VidSchiSubmitPagingCommand+0x2ae
ffffdf0a`0d2e7a80 fffff806`6bd40d5e : ffffaa0b`d32c5500 fffff806`6bd40cd0 ffffaa0b`d32c5000 00000000`00000000 : dxgmms2!VidSchiRun_PriorityTable+0x174
ffffdf0a`0d2e7ad0 fffff801`7f6774f7 : ffffaa0b`d32c2700 fffff806`6bd40cd0 ffff9701`2c200180 000004ed`bd9bbfff : dxgmms2!VidSchiWorkerThread+0x8e
ffffdf0a`0d2e7b10 fffff801`7f7b47f6 : ffff9701`2c200180 ffffaa0b`d32c2700 fffff801`7f6774b0 00000000`00000000 : nt!PspSystemThreadStartup+0x47
ffffdf0a`0d2e7b60 00000000`00000000 : ffffdf0a`0d2e8000 ffffdf0a`0d2e1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

SYMBOL_NAME: PAGE_NOT_ZERO

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: PAGE_NOT_ZERO

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

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

 

[Colif]

What GPU do you have? VIDEO_SCHEDULER_INTERNAL_ERROR can be caused by GPU drivers, so depending what card you have, try running DDU in safe mode and remove the currentr drivers and install new ones - http://www.tomshardware.com/faq/id-2767677/perform-clean-install-video-card-drivers.html

Can you follow option one on the following link - here
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump after the next BSOD
copy that file to documents
upload the copy from documents to a cloud server and share the link here and I will get someone to convert file into a format I can read