Neler Yeni

Yeni Bilgisayarda mavi ekran hatası

28554

80+ Bronze
Katılım
18 Temmuz 2020
Mesajlar
538
En İyi Cevap
4
DDU ile ekran kartı sürücülerinizi kaldırıp en güncel WHQL olanı kurun: https://www.technopat.net/sosyal/konu/ddu-ile-sueruecue-kaldirma-rehberi.44964/

Kablosuz ağ sürücülerinizi güncelleyin.

Kod:
*******************************************************************************
*                                                                             *
*                        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: ffffca01c9e61960
Arg4: ffffe00f94e4dbf0

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

*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2514

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 49521

    Key  : Analysis.Init.CPU.mSec
    Value: 405

    Key  : Analysis.Init.Elapsed.mSec
    Value: 5496

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 75

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  119

BUGCHECK_P1: 2

BUGCHECK_P2: ffffffffc000000d

BUGCHECK_P3: ffffca01c9e61960

BUGCHECK_P4: ffffe00f94e4dbf0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT: 
ffffca01`c9e61888 fffff803`35203ad0     : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffffca01`c9e61960 : nt!KeBugCheckEx
ffffca01`c9e61890 fffff803`374eb3cb     : 00000000`00000000 ffffe00f`94e4b000 ffffca01`c9e61999 ffffe00f`94e4b000 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffffca01`c9e618d0 fffff803`37554b6d     : ffffe00f`00000000 ffffe00f`94e4dbf0 ffffe00f`90997000 ffffe00f`97c0a010 : dxgmms2!VidSchiSendToExecutionQueue+0x1306b
ffffca01`c9e61a00 fffff803`3755cd1a     : ffffe00f`97c0a010 ffffe00f`90997000 00000000`00000000 ffffe00f`9b0396e0 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
ffffca01`c9e61b80 fffff803`3755cb8a     : ffffe00f`90997400 fffff803`3755cac0 ffffe00f`90997000 ffff9381`39de0100 : dxgmms2!VidSchiRun_PriorityTable+0x17a
ffffca01`c9e61bd0 fffff803`26117e85     : ffffe00f`913350c0 fffff803`00000001 ffffe00f`90997000 000f8067`b4bbbdff : dxgmms2!VidSchiWorkerThread+0xca
ffffca01`c9e61c10 fffff803`261fd2a8     : ffff9381`39de0180 ffffe00f`913350c0 fffff803`26117e30 000c6b76`ffffffd8 : nt!PspSystemThreadStartup+0x55
ffffca01`c9e61c60 00000000`00000000     : ffffca01`c9e62000 ffffca01`c9e5c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  dxgmms2!VidSchiSendToExecutionQueue+1306b

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.19041.870

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1306b

FAILURE_BUCKET_ID:  0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {9a11bf9c-270e-962e-7a82-3efdab93c10e}

Followup:     MachineOwner
---------
*******************************************************************************
*                                                                             *
*                        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: ffffa70cd1a22960
Arg4: ffffc30774e4c130

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

*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2811

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 47001

    Key  : Analysis.Init.CPU.mSec
    Value: 358

    Key  : Analysis.Init.Elapsed.mSec
    Value: 7078

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 84

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  119

BUGCHECK_P1: 2

BUGCHECK_P2: ffffffffc000000d

BUGCHECK_P3: ffffa70cd1a22960

BUGCHECK_P4: ffffc30774e4c130

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT: 
ffffa70c`d1a22888 fffff803`827b3ad0     : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffffa70c`d1a22960 : nt!KeBugCheckEx
ffffa70c`d1a22890 fffff803`839fb3cb     : 00000000`00000000 ffffc307`74e49000 ffffa70c`d1a22999 ffffc307`74e49000 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffffa70c`d1a228d0 fffff803`83a64b6d     : ffffc307`00000000 ffffc307`74e4c130 ffffc307`74d55000 ffffc307`7db312a0 : dxgmms2!VidSchiSendToExecutionQueue+0x1306b
ffffa70c`d1a22a00 fffff803`83a6cd1a     : ffffc307`7db312a0 ffffc307`74d55000 00000000`00000000 ffffc307`7cddc4a0 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
ffffa70c`d1a22b80 fffff803`83a6cb8a     : ffffc307`74d55400 fffff803`83a6cac0 ffffc307`74d55000 ffff8300`b2328100 : dxgmms2!VidSchiRun_PriorityTable+0x17a
ffffa70c`d1a22bd0 fffff803`72917e85     : ffffc307`74d8d380 fffff803`00000001 ffffc307`74d55000 000f8067`b4bbbdff : dxgmms2!VidSchiWorkerThread+0xca
ffffa70c`d1a22c10 fffff803`729fd2a8     : ffff8300`b2328180 ffffc307`74d8d380 fffff803`72917e30 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffa70c`d1a22c60 00000000`00000000     : ffffa70c`d1a23000 ffffa70c`d1a1d000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  dxgmms2!VidSchiSendToExecutionQueue+1306b

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.19041.870

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1306b

FAILURE_BUCKET_ID:  0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {9a11bf9c-270e-962e-7a82-3efdab93c10e}

Followup:     MachineOwner
---------
*******************************************************************************
*                                                                             *
*                        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: ffffc80b29a76960
Arg4: ffffca86ff49d590

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

*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2702

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 57913

    Key  : Analysis.Init.CPU.mSec
    Value: 421

    Key  : Analysis.Init.Elapsed.mSec
    Value: 7332

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 75

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  119

BUGCHECK_P1: 2

BUGCHECK_P2: ffffffffc000000d

BUGCHECK_P3: ffffc80b29a76960

BUGCHECK_P4: ffffca86ff49d590

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT: 
ffffc80b`29a76888 fffff802`80483ad0     : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffffc80b`29a76960 : nt!KeBugCheckEx
ffffc80b`29a76890 fffff802`8106b3cb     : 00000000`00000000 ffffca86`ff49a000 ffffc80b`29a76999 ffffca86`ff49a000 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffffc80b`29a768d0 fffff802`810d4b6d     : ffffca86`00000000 ffffca86`ff49d590 ffffca86`f9f0f000 ffffca87`03bb7010 : dxgmms2!VidSchiSendToExecutionQueue+0x1306b
ffffc80b`29a76a00 fffff802`810dcd1a     : ffffca87`03bb7010 ffffca86`f9f0f000 00000000`00000000 ffffca86`fb59b720 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
ffffc80b`29a76b80 fffff802`810dcb8a     : ffffca86`f9f0f400 fffff802`810dcac0 ffffca86`f9f0f000 ffffb800`6ad28100 : dxgmms2!VidSchiRun_PriorityTable+0x17a
ffffc80b`29a76bd0 fffff802`72317e85     : ffffca86`fb0460c0 fffff802`00000001 ffffca86`f9f0f000 000f8067`b4bbbdff : dxgmms2!VidSchiWorkerThread+0xca
ffffc80b`29a76c10 fffff802`723fd2a8     : ffffb800`6ad28180 ffffca86`fb0460c0 fffff802`72317e30 ebd62dc7`6840ee99 : nt!PspSystemThreadStartup+0x55
ffffc80b`29a76c60 00000000`00000000     : ffffc80b`29a77000 ffffc80b`29a71000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  dxgmms2!VidSchiSendToExecutionQueue+1306b

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.19041.870

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1306b

FAILURE_BUCKET_ID:  0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {9a11bf9c-270e-962e-7a82-3efdab93c10e}

Followup:     MachineOwner
---------
*******************************************************************************
*                                                                             *
*                        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: ffffe9879623e960
Arg4: ffff9088fbaf3db0

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

*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2734

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 53532

    Key  : Analysis.Init.CPU.mSec
    Value: 296

    Key  : Analysis.Init.Elapsed.mSec
    Value: 10008

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 75

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  119

BUGCHECK_P1: 2

BUGCHECK_P2: ffffffffc000000d

BUGCHECK_P3: ffffe9879623e960

BUGCHECK_P4: ffff9088fbaf3db0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT: 
ffffe987`9623e888 fffff807`56c83ad0     : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffffe987`9623e960 : nt!KeBugCheckEx
ffffe987`9623e890 fffff807`58cbb3cb     : 00000000`00000000 ffff9088`fbaf1000 ffffe987`9623e999 ffff9088`fbaf1000 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffffe987`9623e8d0 fffff807`58d24b6d     : ffff9088`00000000 ffff9088`fbaf3db0 ffff9088`f75b9000 ffff9089`010e1010 : dxgmms2!VidSchiSendToExecutionQueue+0x1306b
ffffe987`9623ea00 fffff807`58d2cd1a     : ffff9089`010e1010 ffff9088`f75b9000 00000000`00000000 ffff9088`f75dc8f0 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
ffffe987`9623eb80 fffff807`58d2cb8a     : ffff9088`f75b9400 fffff807`58d2cac0 ffff9088`f75b9000 ffffb700`661e0100 : dxgmms2!VidSchiRun_PriorityTable+0x17a
ffffe987`9623ebd0 fffff807`49517e85     : ffff9088`f83790c0 fffff807`00000001 ffff9088`f75b9000 000f8067`b4bbbdff : dxgmms2!VidSchiWorkerThread+0xca
ffffe987`9623ec10 fffff807`495fd2a8     : ffffb700`661e0180 ffff9088`f83790c0 fffff807`49517e30 00000000`ffff0012 : nt!PspSystemThreadStartup+0x55
ffffe987`9623ec60 00000000`00000000     : ffffe987`9623f000 ffffe987`96239000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  dxgmms2!VidSchiSendToExecutionQueue+1306b

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.19041.870

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1306b

FAILURE_BUCKET_ID:  0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {9a11bf9c-270e-962e-7a82-3efdab93c10e}

Followup:     MachineOwner
---------
*******************************************************************************
*                                                                             *
*                        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: ffffc30a9ea84960
Arg4: ffffd80c065844b0

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

*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2796

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 50222

    Key  : Analysis.Init.CPU.mSec
    Value: 296

    Key  : Analysis.Init.Elapsed.mSec
    Value: 11045

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 74

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  119

BUGCHECK_P1: 2

BUGCHECK_P2: ffffffffc000000d

BUGCHECK_P3: ffffc30a9ea84960

BUGCHECK_P4: ffffd80c065844b0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT: 
ffffc30a`9ea84888 fffff801`185b3ad0     : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffffc30a`9ea84960 : nt!KeBugCheckEx
ffffc30a`9ea84890 fffff801`19a1b3cb     : 00000000`00000000 ffffd80c`06581000 ffffc30a`9ea84999 ffffd80c`06581000 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffffc30a`9ea848d0 fffff801`19a84b6d     : ffffd80c`00000000 ffffd80c`065844b0 ffffd80c`00f97000 ffffd80c`0aca7010 : dxgmms2!VidSchiSendToExecutionQueue+0x1306b
ffffc30a`9ea84a00 fffff801`19a8cd1a     : ffffd80c`0aca7010 ffffd80c`00f97000 00000000`00000000 ffffd80c`072d6050 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
ffffc30a`9ea84b80 fffff801`19a8cb8a     : ffffd80c`00f97400 fffff801`19a8cac0 ffffd80c`00f97000 ffffc481`6b528100 : dxgmms2!VidSchiRun_PriorityTable+0x17a
ffffc30a`9ea84bd0 fffff801`0b117e85     : ffffd80c`01b9b0c0 fffff801`00000001 ffffd80c`00f97000 000f8067`b4bbbdff : dxgmms2!VidSchiWorkerThread+0xca
ffffc30a`9ea84c10 fffff801`0b1fd2a8     : ffffc481`6b528180 ffffd80c`01b9b0c0 fffff801`0b117e30 007a0076`005e0047 : nt!PspSystemThreadStartup+0x55
ffffc30a`9ea84c60 00000000`00000000     : ffffc30a`9ea85000 ffffc30a`9ea7f000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  dxgmms2!VidSchiSendToExecutionQueue+1306b

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.19041.870

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1306b

FAILURE_BUCKET_ID:  0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {9a11bf9c-270e-962e-7a82-3efdab93c10e}

Followup:     MachineOwner
---------
 
Yeni mesajlar Yeni Konu Aç      

SON KONULAR

Forum istatistikleri

Konular
903,608
Mesajlar
8,277,076
Üyeler
140,226
Son üye
Ortahisar
Top Bottom