X550JX VIDEO_SCHEDULER_INTERNAL_ERROR hatası

cancancan

Hectopat
Katılım
3 Temmuz 2019
Mesajlar
66
Dün bilgisayarım sürekli mavi ekran veriyordu. Ben de format attım, temiz kurulum yapmak istiyordum bahane oldu diye ama hala bu hataları alıyorum. Yardımcı olursanız sevinirim.

Hatalar: DPC_WATCHDOG_VIOLATION
VIDEO_SCHEDULER_INTERNAL_ERROR
VIDEO_TDR_FAILURE

Minidump dosyası: Yeni klasör (2).zip
5 dakika kullanılamaz oldu PC. Donanım kaynaklı bir sorun mu var yoksa?
 
Son düzenleyen: Moderatör:
Abi konuyu açalı 5 dakika olmuş sakin ol...

Cihazın GPU'su arızalanmış gibi. Garantisi devam ediyorsa yollayın. Etmiyorsa reballing için fiyat alın.


Kod:
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above. The offending component can usually be
    identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff80623efb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding the cumulative timeout
Arg4: 0000000000000000

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

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 5624

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 69589

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

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

    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


FILE_IN_CAB:  010122-12000-01.dmp

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff80623efb320

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME:  fffff8062647c630 -- (.trap 0xfffff8062647c630)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000001171a0a2 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80634c5e420 rsp=fffff8062647c7c0 rbp=fffff8062647c840
 r8=fffff8062647c808  r9=0000000000000000 r10=ffffc988f6bd52c0
r11=000000000000000c r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nvlddmkm+0x8e420:
fffff806`34c5e420 488b5c2430      mov     rbx,qword ptr [rsp+30h] ss:fffff806`2647c7f0=ffffc988f6bd3000
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Teams.exe

STACK_TEXT:
fffff806`2647c2b8 fffff806`2361f47e     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff806`23efb320 : nt!KeBugCheckEx
fffff806`2647c2c0 fffff806`2341c3cd     : 000000e8`ea798f6d fffff806`1e573180 00000000`00000246 00000000`000058d5 : nt!KeAccumulateTicks+0x2062ce
fffff806`2647c320 fffff806`2341c971     : 00000000`ffff000c 00000000`000034f2 fffff806`1e573180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
fffff806`2647c370 fffff806`234167e3     : fffff806`1e573180 00000000`00000000 fffff806`23e31450 00000000`00000000 : nt!KiUpdateTime+0x4a1
fffff806`2647c4b0 fffff806`2341f1a2     : fffff806`2647c630 fffff806`2647c6b0 fffff806`2647c600 00000000`0000000c : nt!KeClockInterruptNotify+0x2e3
fffff806`2647c560 fffff806`234de135     : 00000000`d3e19322 fffff806`23ef39a0 fffff806`23ef3a50 00000000`00002707 : nt!HalpTimerClockInterrupt+0xe2
fffff806`2647c590 fffff806`235f8b7a     : fffff806`2647c6b0 fffff806`23ef39a0 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff806`2647c5e0 fffff806`235f90e7     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff806`2647c630 fffff806`34c5e420     : 00000000`00000000 00000000`00000020 ffffc988`f6bd3001 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff806`2647c7c0 00000000`00000000     : 00000000`00000020 ffffc988`f6bd3001 00000000`00000000 00000000`00000000 : nvlddmkm+0x8e420


SYMBOL_NAME:  nvlddmkm+8e420

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  8e420

FAILURE_BUCKET_ID:  0x133_ISR_nvlddmkm!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f97493a5-ea2b-23ca-a808-8602773c2a86}

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffc58502636050, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8013481856c, 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\nvami.inf_amd64_39f6d2586ed0b7d9\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: 4608

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 21024

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

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

    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


FILE_IN_CAB:  010122-12234-01.dmp

BUGCHECK_CODE:  116

BUGCHECK_P1: ffffc58502636050

BUGCHECK_P2: fffff8013481856c

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffc58502636050
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: 
ffffd784`0fbfca18 fffff801`300f653e     : 00000000`00000116 ffffc585`02636050 fffff801`3481856c ffffffff`c000009a : nt!KeBugCheckEx
ffffd784`0fbfca20 fffff801`300a6cb4     : fffff801`3481856c ffffc585`02388770 00000000`00002000 ffffc585`02388830 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffffd784`0fbfca60 fffff801`3009f7ec     : ffffc585`02616000 00000000`01000000 00000000`00000004 00000000`00000004 : dxgkrnl!ADAPTER_RENDER::Reset+0x174
ffffd784`0fbfca90 fffff801`300f5c65     : 00000000`00000100 ffffc585`02616a70 00000000`00000001 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x4dc
ffffd784`0fbfcb10 fffff801`300f5dd7     : fffff801`21725440 00000000`00000000 00000000`00000000 00000000`00000100 : dxgkrnl!TdrResetFromTimeout+0x15
ffffd784`0fbfcb40 fffff801`20cb85f5     : ffffc585`0539b040 fffff801`300f5db0 ffffc584`fce88bb0 ffffc584`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffffd784`0fbfcb70 fffff801`20d55935     : ffffc585`0539b040 00000000`00000080 ffffc584`fcea6180 000fa425`bd9bbfff : nt!ExpWorkerThread+0x105
ffffd784`0fbfcc10 fffff801`20dfe728     : ffff8081`8abec180 ffffc585`0539b040 fffff801`20d558e0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffd784`0fbfcc60 00000000`00000000     : ffffd784`0fbfd000 ffffd784`0fbf7000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  nvlddmkm+df856c

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .cxr; .ecxr ; 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
---------
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: ffffec013d64c960
Arg4: ffffb403610c0cd0

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: dxgmms2!VIDSCH_DMA_PACKET                     ***
***                                                                   ***
*************************************************************************
*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4890

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 35710

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

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

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

    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


FILE_IN_CAB:  010122-12156-01.dmp

BUGCHECK_CODE:  119

BUGCHECK_P1: 2

BUGCHECK_P2: ffffffffc000000d

BUGCHECK_P3: ffffec013d64c960

BUGCHECK_P4: ffffb403610c0cd0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT: 
ffffec01`3d64c888 fffff807`498c3ad0     : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffffec01`3d64c960 : nt!KeBugCheckEx
ffffec01`3d64c890 fffff807`4b947b09     : ffffb403`610be000 00000000`c000000d ffffec01`3d64c999 00000000`00000001 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffffec01`3d64c8d0 fffff807`4b9c4b9d     : ffffb403`00000000 ffffb403`610c0cd0 ffffb403`61082000 ffffb403`611418a0 : dxgmms2+0x7b09
ffffec01`3d64ca00 fffff807`4b9cd51a     : ffffb403`611418a0 ffffb403`61082000 00000000`00000000 ffffb403`61111010 : dxgmms2!VidMmInterface+0x452bd
ffffec01`3d64cb80 fffff807`4b9cd38a     : ffffb403`61082400 fffff807`4b9cd2c0 ffffb403`61082000 ffffdc01`78bec100 : dxgmms2!VidMmInterface+0x4dc3a
ffffec01`3d64cbd0 fffff807`3b755935     : ffffb403`6084a140 fffff807`00000001 ffffb403`61082000 000fa425`bd9bbfff : dxgmms2!VidMmInterface+0x4daaa
ffffec01`3d64cc10 fffff807`3b7fe728     : ffffdc01`78bec180 ffffb403`6084a140 fffff807`3b7558e0 03a41f15`ff000002 : nt!PspSystemThreadStartup+0x55
ffffec01`3d64cc60 00000000`00000000     : ffffec01`3d64d000 ffffec01`3d647000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  dxgmms2+7b09

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.19041.1387

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  7b09

FAILURE_BUCKET_ID:  0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {a94318af-dd13-4d43-2ae8-8f2dd0117694}

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

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above. The offending component can usually be
    identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff80736afb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding the cumulative timeout
Arg4: 0000000000000000

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

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4921

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 54572

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

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

    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


FILE_IN_CAB:  010122-12109-01.dmp

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff80736afb320

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME:  fffff8073907c910 -- (.trap 0xfffff8073907c910)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffff828b3f24d1e0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80736014c2a rsp=fffff8073907caa8 rbp=fffff8073907cbf0
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000003
r11=fffff8073907cb30 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiInsertQueueDpc+0xa:
fffff807`36014c2a 4889542410      mov     qword ptr [rsp+10h],rdx ss:fffff807`3907cab8=fffff8074688fb9e
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Teams.exe

STACK_TEXT: 
fffff807`3907c598 fffff807`3621f47e     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff807`36afb320 : nt!KeBugCheckEx
fffff807`3907c5a0 fffff807`3601c3cd     : 000000de`2a837055 fffff807`31200180 00000000`00000246 00000000`00005470 : nt!KeAccumulateTicks+0x2062ce
fffff807`3907c600 fffff807`3601c971     : 00000000`00000000 00000000`00003254 fffff807`31200180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
fffff807`3907c650 fffff807`360167e3     : fffff807`31200180 00000000`00000000 fffff807`36a31468 00000000`00000000 : nt!KiUpdateTime+0x4a1
fffff807`3907c790 fffff807`3601f1a2     : fffff807`3907c910 fffff807`3907c990 fffff807`3907c900 00000000`0000000b : nt!KeClockInterruptNotify+0x2e3
fffff807`3907c840 fffff807`360de135     : 00000000`c9676096 fffff807`36af39a0 fffff807`36af3a50 fffff807`4689f0bb : nt!HalpTimerClockInterrupt+0xe2
fffff807`3907c870 fffff807`361f8b7a     : fffff807`3907c990 fffff807`36af39a0 00000000`00000000 ffff828b`41a706c0 : nt!KiCallInterruptServiceRoutine+0xa5
fffff807`3907c8c0 fffff807`361f90e7     : ffff828b`419e5a10 fffff807`4689e33f fffff807`3907cc50 fffff807`4689e33f : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff807`3907c910 fffff807`36014c2a     : fffff807`36014c11 ffff828b`3f8a4a98 fffff807`4688fb9e 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff807`3907caa8 fffff807`36014c11     : ffff828b`3f8a4a98 fffff807`4688fb9e 00000000`00000000 00000000`00000000 : nt!KiInsertQueueDpc+0xa
fffff807`3907cab0 fffff807`4688f53d     : fffff807`3907cc00 fffff807`3907cbf0 00000000`00000000 ffff828b`419e5000 : nt!KeInsertQueueDpc+0x11
fffff807`3907caf0 fffff807`3907cc00     : fffff807`3907cbf0 00000000`00000000 ffff828b`419e5000 fffff807`3907cb50 : nvlddmkm+0x8f53d
fffff807`3907caf8 fffff807`3907cbf0     : 00000000`00000000 ffff828b`419e5000 fffff807`3907cb50 fffff807`3120009b : 0xfffff807`3907cc00
fffff807`3907cb00 00000000`00000000     : ffff828b`419e5000 fffff807`3907cb50 fffff807`3120009b 00000000`00000201 : 0xfffff807`3907cbf0


SYMBOL_NAME:  nvlddmkm+8f53d

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  8f53d

FAILURE_BUCKET_ID:  0x133_ISR_nvlddmkm!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f97493a5-ea2b-23ca-a808-8602773c2a86}

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

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above. The offending component can usually be
    identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff802528fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding the cumulative timeout
Arg4: 0000000000000000

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

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4780

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 60741

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

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

    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


FILE_IN_CAB:  010122-8671-01.dmp

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff802528fb320

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME:  fffff80257e75610 -- (.trap 0xfffff80257e75610)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000001171a0a2 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff802657fe420 rsp=fffff80257e757a0 rbp=0000000000000002
 r8=fffff80257e757e8  r9=0000000000000000 r10=ffffd181377d02c0
r11=000000000000000c r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nvlddmkm+0x8e420:
fffff802`657fe420 488b5c2430      mov     rbx,qword ptr [rsp+30h] ss:fffff802`57e757d0=0000000000000001
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Teams.exe

STACK_TEXT: 
fffff802`57e7cc88 fffff802`5201f47e     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff802`528fb320 : nt!KeBugCheckEx
fffff802`57e7cc90 fffff802`51e1c3cd     : 0000013d`d3fdb881 fffff802`50023180 00000000`00000246 00000000`00007978 : nt!KeAccumulateTicks+0x2062ce
fffff802`57e7ccf0 fffff802`51e1c971     : 00000000`00000001 00000000`00004866 fffff802`50023180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
fffff802`57e7cd40 fffff802`51e167e3     : fffff802`50023180 00000000`00000000 fffff802`52831510 00000000`00000000 : nt!KiUpdateTime+0x4a1
fffff802`57e7ce80 fffff802`51e1f1a2     : fffff802`57e75610 fffff802`57e75690 fffff802`57e75600 00000000`0000000c : nt!KeClockInterruptNotify+0x2e3
fffff802`57e7cf30 fffff802`51ede135     : 00000001`21b18f79 fffff802`528f39a0 fffff802`528f3a50 ffffc5fe`b7bf948b : nt!HalpTimerClockInterrupt+0xe2
fffff802`57e7cf60 fffff802`51ff8b7a     : fffff802`57e75690 fffff802`528f39a0 ffffd181`3b5af080 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff802`57e7cfb0 fffff802`51ff90e7     : 00000000`00000100 00000000`00000000 00000000`00000020 fffff802`51e93609 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff802`57e75610 fffff802`657fe420     : 00000000`00000000 00000000`00000001 00000000`00000000 fffff802`658ee45c : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff802`57e757a0 00000000`00000000     : 00000000`00000001 00000000`00000000 fffff802`658ee45c ffffd181`377ce000 : nvlddmkm+0x8e420


SYMBOL_NAME:  nvlddmkm+8e420

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  8e420

FAILURE_BUCKET_ID:  0x133_ISR_nvlddmkm!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f97493a5-ea2b-23ca-a808-8602773c2a86}

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

0: kd> !sysinfo machineid
Machine ID Information [From Smbios 2.7, DMIVersion 0, Size=1563]
BiosMajorRelease = 4
BiosMinorRelease = 6
BiosVendor = American Megatrends Inc.
BiosVersion = X550JX.210
BiosReleaseDate = 04/22/2019
SystemManufacturer = ASUSTeK COMPUTER INC.
SystemProductName = X550JX
SystemFamily = X
SystemVersion = 1.0      
SystemSKU = ASUS-NotebookSKU
BaseBoardManufacturer = ASUSTeK COMPUTER INC.
BaseBoardProduct = X550JX
BaseBoardVersion = 1.0
 
Son düzenleme:
Asus aradım yapmıyorlar maalesef. İzmir'de güvenilir teknik servis var mı bildiğiniz?
Bugün iki yerle görüştüm. Anakart değişecek dedi birisi, birisi de ekran kartını iptal ederiz anakart üzerinden Intel ile devam edersin dedi. Şimdi araştırdım da DDU ile ben silsem ekran kartını sonrasında düzelir mi? Yoksa konuştuğum adam mı yapsın?
 
Son düzenleme:
Asus aradım yapmıyorlar maalesef. İzmir'de güvenilir teknik servis var mı bildiğiniz?
Bugün iki yerle görüştüm. Anakart değişecek dedi birisi, birisi de ekran kartını iptal ederiz anakart üzerinden Intel ile devam edersin dedi. Şimdi araştırdım da DDU ile ben silsem ekran kartını sonrasında düzelir mi? Yoksa konuştuğum adam mı yapsın?
Arkadaşım sence donanımsal bir sorunu yazılımla çözebilir misin? Hayır, çözemezsin.

Reballing işlemi yapılmayacaksa en iyisi kartı iptal ettirin. Intel ile devam edin
 

Yeni konular

Geri
Yukarı