Windows 10 mavi ekran hatası

Bakıyorum hemen ama siz benden önce Driverların doğru ve güncel olduğundan emin olunuz.

@Ted Kaczynski .

zafer.aydn dedi:

Merhaba Monster Abra A5 v5.2 cihaza sahibim. Herhangi bir oyuna gireceğim zaman açtıktan bir 10 saniye sonra hoparlör cızırdıyor ve fare takılarak hareket edip bilgisayar kilitleniyor. Arada mavi ekran verip gidiyor ya da mavi ekran bile alamadan kilitleniyor. Bilgisayar yaklaşık 8-10 res yedikten sonra şans işi sorunsuz açıyor oyunları, ta ki bilgisayarı kapatana kadar. Bilgisayarı kapattıktan sonra tekrar kilitlenmeler başlıyor. Bu sorunu yaşayan oldu mu nasıl bir yol izlemeliyim. Yardımlarınız için şimdiden teşekkür ederim.

İşlemci: i7 5700HQ.
Ekran kartı: GTX 960M.
RAM: 8 GB 1600MHz CL11 1, 35v.
SSD: 240GB Kingston.

minidump dosyaları.RAR

Bugüne kadar birçok mavi ekran aldım fakat dosyaları silinmiş bulamadım.

Genişletmek için tıkla...

Ekran kartınız Nvidia mı? Sürücünüzü güvenli modda kaldırıp tekrar yükler misiniz?
[CODE title="Dump"]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffe38bb7635050, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8041f81a074, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 7874

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 20525

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

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

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

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: 116

BUGCHECK_P1: ffffe38bb7635050

BUGCHECK_P2: fffff8041f81a074

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffe38bb7635050
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.

PROCESS_OBJECT: 0000000000000004

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff940c`9dff29d8 fffff804`1cb4235e : 00000000`00000116 ffffe38b`b7635050 fffff804`1f81a074 ffffffff`c000009a : nt!KeBugCheckEx
ffff940c`9dff29e0 fffff804`1caf2b84 : fffff804`1f81a074 ffffe38b`b1d1c4e0 00000000`00002000 ffffe38b`b1d1c5a0 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffff940c`9dff2a20 fffff804`1caeb6bf : ffffe38b`b1d32000 00000000`01000000 00000000`00000002 00000000`00000002 : dxgkrnl!ADAPTER_RENDER::Reset+0x174
ffff940c`9dff2a50 fffff804`1cb41a85 : 00000000`00000100 ffffe38b`b1d32a58 00000000`00000000 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x4df
ffff940c`9dff2ad0 fffff804`1cb41bf7 : fffff804`13725440 00000000`00000000 00000000`00000000 00000000`00000300 : dxgkrnl!TdrResetFromTimeout+0x15
ffff940c`9dff2b00 fffff804`12c25975 : ffffe38b`b54b0040 fffff804`1cb41bd0 ffffe38b`ab6b7cf0 ffffe38b`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffff940c`9dff2b30 fffff804`12d17e25 : ffffe38b`b54b0040 00000000`00000080 ffffe38b`ab6731c0 000fa427`bd9bbfff : nt!ExpWorkerThread+0x105
ffff940c`9dff2bd0 fffff804`12dfd0d8 : ffff8000`a8714180 ffffe38b`b54b0040 fffff804`12d17dd0 00005d78`000032fc : nt!PspSystemThreadStartup+0x55
ffff940c`9dff2c20 00000000`00000000 : ffff940c`9dff3000 ffff940c`9dfec000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: nvlddmkm+97a074

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}

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

7: kd> lmvm nvlddmkm
Browse full module list
start end module name
fffff804`1eea0000 fffff804`1fcbd000 nvlddmkm T (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: \SystemRoot\System32\DriverStore\FileRepository\nvcvwu.inf_amd64_166fee8ea72cb783\nvlddmkm.sys
Image name: nvlddmkm.sys
Browse all global symbols functions data
Timestamp: Mon May 1 22:55:53 2017 (590792C9)
CheckSum: 00DD8D5A
ImageSize: 00E1D000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:
[/CODE]

Ekran kartı sürücünüzü DDU ile kaldırın ve NVIDIA'nın aşağıdaki websitesinden güncel sürücü kurun.



[CODE title="Dökümler"]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffb70874f10460, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff803170ca074, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

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

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nvcvwu.inf_amd64_166fee8ea72cb783\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 8030

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 30405

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

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

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

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: 116

BUGCHECK_P1: ffffb70874f10460

BUGCHECK_P2: fffff803170ca074

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffb70874f10460
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.

PROCESS_OBJECT: 0000000000000004

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff8a09`526829d8 fffff803`1366235e : 00000000`00000116 ffffb708`74f10460 fffff803`170ca074 ffffffff`c000009a : nt!KeBugCheckEx
ffff8a09`526829e0 fffff803`13612b84 : fffff803`170ca074 ffffb708`76046250 00000000`00002000 ffffb708`76046310 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffff8a09`52682a20 fffff803`1360b6bf : ffffb708`76047000 00000000`01000000 00000000`00000002 00000000`00000002 : dxgkrnl!ADAPTER_RENDER::Reset+0x174
ffff8a09`52682a50 fffff803`13661a85 : 00000000`00000100 ffffb708`76047a58 00000000`00000000 fffff803`08325440 : dxgkrnl!DXGADAPTER::Reset+0x4df
ffff8a09`52682ad0 fffff803`13661bf7 : fffff803`08325440 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!TdrResetFromTimeout+0x15
ffff8a09`52682b00 fffff803`07825975 : ffffb708`74153040 fffff803`13661bd0 ffffb708`6e8d8cd0 ffffb708`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffff8a09`52682b30 fffff803`07917e25 : ffffb708`74153040 00000000`00000080 ffffb708`6e8751c0 000fa427`bd9bbfff : nt!ExpWorkerThread+0x105
ffff8a09`52682bd0 fffff803`079fd0d8 : ffffd400`12bce180 ffffb708`74153040 fffff803`07917dd0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffff8a09`52682c20 00000000`00000000 : ffff8a09`52683000 ffff8a09`5267c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: nvlddmkm+97a074

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}

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

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffe38bb7635050, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8041f81a074, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

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

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nvcvwu.inf_amd64_166fee8ea72cb783\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 7234

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 34700

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

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

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

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: 116

BUGCHECK_P1: ffffe38bb7635050

BUGCHECK_P2: fffff8041f81a074

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffe38bb7635050
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.

PROCESS_OBJECT: 0000000000000004

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff940c`9dff29d8 fffff804`1cb4235e : 00000000`00000116 ffffe38b`b7635050 fffff804`1f81a074 ffffffff`c000009a : nt!KeBugCheckEx
ffff940c`9dff29e0 fffff804`1caf2b84 : fffff804`1f81a074 ffffe38b`b1d1c4e0 00000000`00002000 ffffe38b`b1d1c5a0 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffff940c`9dff2a20 fffff804`1caeb6bf : ffffe38b`b1d32000 00000000`01000000 00000000`00000002 00000000`00000002 : dxgkrnl!ADAPTER_RENDER::Reset+0x174
ffff940c`9dff2a50 fffff804`1cb41a85 : 00000000`00000100 ffffe38b`b1d32a58 00000000`00000000 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x4df
ffff940c`9dff2ad0 fffff804`1cb41bf7 : fffff804`13725440 00000000`00000000 00000000`00000000 00000000`00000300 : dxgkrnl!TdrResetFromTimeout+0x15
ffff940c`9dff2b00 fffff804`12c25975 : ffffe38b`b54b0040 fffff804`1cb41bd0 ffffe38b`ab6b7cf0 ffffe38b`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffff940c`9dff2b30 fffff804`12d17e25 : ffffe38b`b54b0040 00000000`00000080 ffffe38b`ab6731c0 000fa427`bd9bbfff : nt!ExpWorkerThread+0x105
ffff940c`9dff2bd0 fffff804`12dfd0d8 : ffff8000`a8714180 ffffe38b`b54b0040 fffff804`12d17dd0 00005d78`000032fc : nt!PspSystemThreadStartup+0x55
ffff940c`9dff2c20 00000000`00000000 : ffff940c`9dff3000 ffff940c`9dfec000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: nvlddmkm+97a074

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}

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: ffff92844211f920
Arg4: ffffb10497416cd0

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 7327

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 57748

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

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

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: ffff92844211f920

BUGCHECK_P4: ffffb10497416cd0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff9284`4211f848 fffff807`495b3ad0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffff9284`4211f920 : nt!KeBugCheckEx
ffff9284`4211f850 fffff807`4aabb44b : 00000000`00000000 ffffb104`97414000 ffffb104`9748d010 ffffb104`97414236 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffff9284`4211f890 fffff807`4ab2518d : ffffb104`00000000 ffffb104`97416cd0 ffffb104`973c7000 ffffb104`9cdf0010 : dxgmms2!VidSchiSendToExecutionQueue+0x130eb
ffff9284`4211f9c0 fffff807`4ab2d42a : ffffb104`9cdf0010 ffffb104`973c7000 00000000`00000000 ffffb104`9cdf58a0 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
ffff9284`4211fb40 fffff807`4ab2d29a : ffffb104`973c7400 fffff807`4ab2d1d0 ffffb104`973c7000 fffff807`3a3d9100 : dxgmms2!VidSchiRun_PriorityTable+0x17a
ffff9284`4211fb90 fffff807`3fd17e85 : ffffb104`973ca280 fffff807`00000001 ffffb104`973c7000 000fa427`bd9bbfff : dxgmms2!VidSchiWorkerThread+0xca
ffff9284`4211fbd0 fffff807`3fdfd408 : fffff807`3a3d9180 ffffb104`973ca280 fffff807`3fd17e30 0004e7f4`000b48a0 : nt!PspSystemThreadStartup+0x55
ffff9284`4211fc20 00000000`00000000 : ffff9284`42120000 ffff9284`42119000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+130eb

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.906

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 130eb

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: ffff91886db67920
Arg4: ffffbb89e8dd4e90

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 7733

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 59595

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

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

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

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: ffff91886db67920

BUGCHECK_P4: ffffbb89e8dd4e90

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff9188`6db67848 fffff805`67b43ad0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffff9188`6db67920 : nt!KeBugCheckEx
ffff9188`6db67850 fffff805`6abab44b : 00000000`00000000 ffffbb89`e8dd2000 ffff9188`6db67959 ffffbb89`e8dd2000 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffff9188`6db67890 fffff805`6ac1518d : ffffbb89`00000000 ffffbb89`e8dd4e90 ffffbb89`e8d94000 ffffbb89`f04f04a0 : dxgmms2!VidSchiSendToExecutionQueue+0x130eb
ffff9188`6db679c0 fffff805`6ac1d42a : ffffbb89`f04f04a0 ffffbb89`e8d94000 00000000`00000000 ffffbb89`e8e2c620 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
ffff9188`6db67b40 fffff805`6ac1d29a : ffffbb89`e8d94400 fffff805`6ac1d1d0 ffffbb89`e8d94000 ffff9a01`d9110100 : dxgmms2!VidSchiRun_PriorityTable+0x17a
ffff9188`6db67b90 fffff805`5d517e85 : ffffbb89`e8d97280 fffff805`00000001 ffffbb89`e8d94000 000fa427`bd9bbfff : dxgmms2!VidSchiWorkerThread+0xca
ffff9188`6db67bd0 fffff805`5d5fd408 : ffff9a01`d9110180 ffffbb89`e8d97280 fffff805`5d517e30 006e0065`00720072 : nt!PspSystemThreadStartup+0x55
ffff9188`6db67c20 00000000`00000000 : ffff9188`6db68000 ffff9188`6db61000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+130eb

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.906

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 130eb

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
---------[/CODE]

Enes3078 dedi:

Ekran kartı sürücünüzü DDU ile kaldırın ve NVIDIA'nın aşağıdaki websitesinden güncel sürücü kurun.

Rehber: DDU ile Sürücü Kaldırma Rehberi

Display Driver Uninstaller (DDU), zamanla bilgisayara takılan farklı monitörler, üst üste güncellenen sürücüler ve Windows güncellemeleri sonrası biriken kayıt defteri ve sürücü dosyalarını silerek temiz bir sürücü kurulumunun yolunu açan kullanışlı bir araçtır. Adım adım sürücü temizliği...

www.technopat.net

Download the latest official NVIDIA drivers

En son resmi NVIDIA sürücülerini indirin

www.nvidia.com.tr

[CODE title="Dökümler"]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffb70874f10460, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff803170ca074, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

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

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nvcvwu.inf_amd64_166fee8ea72cb783\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 8030

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 30405

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

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

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

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: 116

BUGCHECK_P1: ffffb70874f10460

BUGCHECK_P2: fffff803170ca074

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffb70874f10460
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.

PROCESS_OBJECT: 0000000000000004

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff8a09`526829d8 fffff803`1366235e : 00000000`00000116 ffffb708`74f10460 fffff803`170ca074 ffffffff`c000009a : nt!KeBugCheckEx
ffff8a09`526829e0 fffff803`13612b84 : fffff803`170ca074 ffffb708`76046250 00000000`00002000 ffffb708`76046310 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffff8a09`52682a20 fffff803`1360b6bf : ffffb708`76047000 00000000`01000000 00000000`00000002 00000000`00000002 : dxgkrnl!ADAPTER_RENDER::Reset+0x174
ffff8a09`52682a50 fffff803`13661a85 : 00000000`00000100 ffffb708`76047a58 00000000`00000000 fffff803`08325440 : dxgkrnl!DXGADAPTER::Reset+0x4df
ffff8a09`52682ad0 fffff803`13661bf7 : fffff803`08325440 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!TdrResetFromTimeout+0x15
ffff8a09`52682b00 fffff803`07825975 : ffffb708`74153040 fffff803`13661bd0 ffffb708`6e8d8cd0 ffffb708`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffff8a09`52682b30 fffff803`07917e25 : ffffb708`74153040 00000000`00000080 ffffb708`6e8751c0 000fa427`bd9bbfff : nt!ExpWorkerThread+0x105
ffff8a09`52682bd0 fffff803`079fd0d8 : ffffd400`12bce180 ffffb708`74153040 fffff803`07917dd0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffff8a09`52682c20 00000000`00000000 : ffff8a09`52683000 ffff8a09`5267c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: nvlddmkm+97a074

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}

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

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffe38bb7635050, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8041f81a074, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

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

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nvcvwu.inf_amd64_166fee8ea72cb783\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 7234

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 34700

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

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

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

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: 116

BUGCHECK_P1: ffffe38bb7635050

BUGCHECK_P2: fffff8041f81a074

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffe38bb7635050
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.

PROCESS_OBJECT: 0000000000000004

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff940c`9dff29d8 fffff804`1cb4235e : 00000000`00000116 ffffe38b`b7635050 fffff804`1f81a074 ffffffff`c000009a : nt!KeBugCheckEx
ffff940c`9dff29e0 fffff804`1caf2b84 : fffff804`1f81a074 ffffe38b`b1d1c4e0 00000000`00002000 ffffe38b`b1d1c5a0 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffff940c`9dff2a20 fffff804`1caeb6bf : ffffe38b`b1d32000 00000000`01000000 00000000`00000002 00000000`00000002 : dxgkrnl!ADAPTER_RENDER::Reset+0x174
ffff940c`9dff2a50 fffff804`1cb41a85 : 00000000`00000100 ffffe38b`b1d32a58 00000000`00000000 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x4df
ffff940c`9dff2ad0 fffff804`1cb41bf7 : fffff804`13725440 00000000`00000000 00000000`00000000 00000000`00000300 : dxgkrnl!TdrResetFromTimeout+0x15
ffff940c`9dff2b00 fffff804`12c25975 : ffffe38b`b54b0040 fffff804`1cb41bd0 ffffe38b`ab6b7cf0 ffffe38b`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffff940c`9dff2b30 fffff804`12d17e25 : ffffe38b`b54b0040 00000000`00000080 ffffe38b`ab6731c0 000fa427`bd9bbfff : nt!ExpWorkerThread+0x105
ffff940c`9dff2bd0 fffff804`12dfd0d8 : ffff8000`a8714180 ffffe38b`b54b0040 fffff804`12d17dd0 00005d78`000032fc : nt!PspSystemThreadStartup+0x55
ffff940c`9dff2c20 00000000`00000000 : ffff940c`9dff3000 ffff940c`9dfec000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: nvlddmkm+97a074

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}

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: ffff92844211f920
Arg4: ffffb10497416cd0

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 7327

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 57748

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

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

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: ffff92844211f920

BUGCHECK_P4: ffffb10497416cd0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff9284`4211f848 fffff807`495b3ad0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffff9284`4211f920 : nt!KeBugCheckEx
ffff9284`4211f850 fffff807`4aabb44b : 00000000`00000000 ffffb104`97414000 ffffb104`9748d010 ffffb104`97414236 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffff9284`4211f890 fffff807`4ab2518d : ffffb104`00000000 ffffb104`97416cd0 ffffb104`973c7000 ffffb104`9cdf0010 : dxgmms2!VidSchiSendToExecutionQueue+0x130eb
ffff9284`4211f9c0 fffff807`4ab2d42a : ffffb104`9cdf0010 ffffb104`973c7000 00000000`00000000 ffffb104`9cdf58a0 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
ffff9284`4211fb40 fffff807`4ab2d29a : ffffb104`973c7400 fffff807`4ab2d1d0 ffffb104`973c7000 fffff807`3a3d9100 : dxgmms2!VidSchiRun_PriorityTable+0x17a
ffff9284`4211fb90 fffff807`3fd17e85 : ffffb104`973ca280 fffff807`00000001 ffffb104`973c7000 000fa427`bd9bbfff : dxgmms2!VidSchiWorkerThread+0xca
ffff9284`4211fbd0 fffff807`3fdfd408 : fffff807`3a3d9180 ffffb104`973ca280 fffff807`3fd17e30 0004e7f4`000b48a0 : nt!PspSystemThreadStartup+0x55
ffff9284`4211fc20 00000000`00000000 : ffff9284`42120000 ffff9284`42119000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+130eb

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.906

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 130eb

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: ffff91886db67920
Arg4: ffffbb89e8dd4e90

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 7733

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 59595

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

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

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

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: ffff91886db67920

BUGCHECK_P4: ffffbb89e8dd4e90

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff9188`6db67848 fffff805`67b43ad0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffff9188`6db67920 : nt!KeBugCheckEx
ffff9188`6db67850 fffff805`6abab44b : 00000000`00000000 ffffbb89`e8dd2000 ffff9188`6db67959 ffffbb89`e8dd2000 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffff9188`6db67890 fffff805`6ac1518d : ffffbb89`00000000 ffffbb89`e8dd4e90 ffffbb89`e8d94000 ffffbb89`f04f04a0 : dxgmms2!VidSchiSendToExecutionQueue+0x130eb
ffff9188`6db679c0 fffff805`6ac1d42a : ffffbb89`f04f04a0 ffffbb89`e8d94000 00000000`00000000 ffffbb89`e8e2c620 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
ffff9188`6db67b40 fffff805`6ac1d29a : ffffbb89`e8d94400 fffff805`6ac1d1d0 ffffbb89`e8d94000 ffff9a01`d9110100 : dxgmms2!VidSchiRun_PriorityTable+0x17a
ffff9188`6db67b90 fffff805`5d517e85 : ffffbb89`e8d97280 fffff805`00000001 ffffbb89`e8d94000 000fa427`bd9bbfff : dxgmms2!VidSchiWorkerThread+0xca
ffff9188`6db67bd0 fffff805`5d5fd408 : ffff9a01`d9110180 ffffbb89`e8d97280 fffff805`5d517e30 006e0065`00720072 : nt!PspSystemThreadStartup+0x55
ffff9188`6db67c20 00000000`00000000 : ffff9188`6db68000 ffff9188`6db61000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+130eb

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.906

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 130eb

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
---------[/CODE]

Genişletmek için tıkla...

Tam düzenledim o sırada siz geldiniz.

@as_not_found @Enes3078
Hocam DDU kullanarak grafik sürülerini kökten temizleyip geriye dönük en sondan başlayıp güncellemelerin hepsini kurarak denedim yine aynı mavi ekranı alıyorum. Problem sizce kartta mıdır yoksa yazılımsal mı

zafer.aydn dedi:

@as_not_found @Enes3078
Hocam DDU kullanarak grafik sürülerini kökten temizleyip geriye dönük en sondan başlayıp güncellemelerin hepsini kurarak denedim yine aynı mavi ekranı alıyorum. Problem sizce kartta mıdır yoksa yazılımsal mı

Genişletmek için tıkla...

Emin değilim kartta sıkıntı olabilir. @The G.O.A.T bu işi benden daha iyi biliyor.

zafer.aydn dedi:

@as_not_found @Enes3078
Hocam DDU kullanarak grafik sürülerini kökten temizleyip geriye dönük en sondan başlayıp güncellemelerin hepsini kurarak denedim yine aynı mavi ekranı alıyorum. Problem sizce kartta mıdır yoksa yazılımsal mı?

Genişletmek için tıkla...

Yeni dump dosyasını paylaş. Şu an mobildeyim bakamıyorum.

@The G.O.A.T Hocam taze taze yeni dosya yükledim. Üstüne farklı olarak mavi değil pembe ekran hatası aldım.

Pembe ekran : resim

Yeni Dump dosyası : dump