*******************************************************************************
* *
* 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: ffff888531277860
Arg4: ffffe48bbb4efbb0
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1906
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 36519
Key : Analysis.Init.CPU.mSec
Value: 124
Key : Analysis.Init.Elapsed.mSec
Value: 50463
Key : Analysis.Memory.CommitPeak.Mb
Value: 139
Key : Bugcheck.Code.DumpHeader
Value: 0x119
Key : Bugcheck.Code.Register
Value: 0x119
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: 092422-17687-01.dmp
BUGCHECK_CODE: 119
BUGCHECK_P1: 2
BUGCHECK_P2: ffffffffc000000d
BUGCHECK_P3: ffff888531277860
BUGCHECK_P4: ffffe48bbb4efbb0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffff8885`31277788 fffff806`8a723ad0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffff8885`31277860 : nt!KeBugCheckEx
ffff8885`31277790 fffff806`6fb39cb9 : ffffe48b`bb4ec000 00000000`c000000d ffff8885`31277899 00000000`00000002 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffff8885`312777d0 fffff806`6fbb432d : ffffe48b`00000000 ffffe48b`bb4efbb0 ffffe48b`b972e000 ffffe48b`b835b510 : dxgmms2!VidSchiSendToExecutionQueue+0xa99
ffff8885`31277900 fffff806`6fbbd1aa : ffffe48b`b835b510 ffffe48b`b972e000 00000000`00000000 ffffe48b`b8e02050 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
ffff8885`31277a80 fffff806`6fbbd01a : ffffe48b`b972e400 fffff806`6fbbcf50 ffffe48b`b972e000 ffff9c00`7c700100 : dxgmms2!VidSchiRun_PriorityTable+0x17a
ffff8885`31277ad0 fffff806`73e71d25 : ffffe48b`b7731040 fffff806`00000001 ffffe48b`b972e000 00000000`00000000 : dxgmms2!VidSchiWorkerThread+0xca
ffff8885`31277b10 fffff806`74000628 : ffff9c00`7c700180 ffffe48b`b7731040 fffff806`73e71cd0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffff8885`31277b60 00000000`00000000 : ffff8885`31278000 ffff8885`31271000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+a99
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.19041.1940
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: a99
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
---------Maalesef hâlâ aynı hata devam ediyor.
Şu mesajda monitörle alakalı olabileceği söylenmiş. İkinci bir monitör kullanıyor musunuz?
VIDEO_SCHEDULER_INTERNAL_ERROR ve dxgmms2.sys mavi ekran hatası
Merhaba. En son beş gün önce yine aynı hata kodunda mavi ekran aldım. DDU ile ekran kartı sürücüsünü kaldırıp 20.4.2 WHQL sürücüsüne indim. 5 gündür sorun yaşamıyordum, şimdi aynı hatayı almaya başladım. BIOS sürümüm güncel değil, elektrik arada gidip geldiği için güncellemeyi düşünmüyorum. DDU...www.technopat.net
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: ffff888531277860. Arg4: ffffe48bbb4efbb0. Debugging Details: ------------------ *** WARNING: Unable to verify timestamp for win32k.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1906. Key : Analysis.DebugAnalysisManager Value: Create. Key : Analysis.Elapsed.mSec Value: 36519. Key : Analysis.Init.CPU.mSec Value: 124. Key : Analysis.Init.Elapsed.mSec Value: 50463. Key : Analysis.Memory.CommitPeak.Mb Value: 139. Key : Bugcheck.Code.DumpHeader Value: 0x119. Key : Bugcheck.Code.Register Value: 0x119. 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: 092422-17687-01.dmp BUGCHECK_CODE: 119. BUGCHECK_P1: 2 BUGCHECK_P2: ffffffffc000000d. BUGCHECK_P3: ffff888531277860. BUGCHECK_P4: ffffe48bbb4efbb0. BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System. STACK_TEXT: ffff8885`31277788 fffff806`8a723ad0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffff8885`31277860 : nt!KeBugCheckEx ffff8885`31277790 fffff806`6fb39cb9 : ffffe48b`bb4ec000 00000000`c000000d ffff8885`31277899 00000000`00000002 : watchdog!WdLogEvent5_WdCriticalError+0xe0 ffff8885`312777d0 fffff806`6fbb432d : ffffe48b`00000000 ffffe48b`bb4efbb0 ffffe48b`b972e000 ffffe48b`b835b510 : dxgmms2!VidSchiSendToExecutionQueue+0xa99 ffff8885`31277900 fffff806`6fbbd1aa : ffffe48b`b835b510 ffffe48b`b972e000 00000000`00000000 ffffe48b`b8e02050 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed ffff8885`31277a80 fffff806`6fbbd01a : ffffe48b`b972e400 fffff806`6fbbcf50 ffffe48b`b972e000 ffff9c00`7c700100 : dxgmms2!VidSchiRun_PriorityTable+0x17a ffff8885`31277ad0 fffff806`73e71d25 : ffffe48b`b7731040 fffff806`00000001 ffffe48b`b972e000 00000000`00000000 : dxgmms2!VidSchiWorkerThread+0xca ffff8885`31277b10 fffff806`74000628 : ffff9c00`7c700180 ffffe48b`b7731040 fffff806`73e71cd0 00000000`00000000 : nt!PspSystemThreadStartup+0x55 ffff8885`31277b60 00000000`00000000 : ffff8885`31278000 ffff8885`31271000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28 SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+a99 MODULE_NAME: dxgmms2. IMAGE_NAME: dxgmms2.sys IMAGE_VERSION: 10.0.19041.1940 STACK_COMMAND: .cxr; .ecxr ; kb. BUCKET_ID_FUNC_OFFSET: a99. 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. ---------
Maalesef hâlâ aynı hata devam ediyor.
Şu mesajda monitörle alakalı olabileceği söylenmiş. İkinci bir monitör kullanıyor musunuz?
VIDEO_SCHEDULER_INTERNAL_ERROR ve dxgmms2.sys mavi ekran hatası
Merhaba. En son beş gün önce yine aynı hata kodunda mavi ekran aldım. DDU ile ekran kartı sürücüsünü kaldırıp 20.4.2 WHQL sürücüsüne indim. 5 gündür sorun yaşamıyordum, şimdi aynı hatayı almaya başladım. BIOS sürümüm güncel değil, elektrik arada gidip geldiği için güncellemeyi düşünmüyorum. DDU...
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: ffff888531277860. Arg4: ffffe48bbb4efbb0. Debugging Details: ------------------ *** WARNING: Unable to verify timestamp for win32k.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1906. Key : Analysis.DebugAnalysisManager Value: Create. Key : Analysis.Elapsed.mSec Value: 36519. Key : Analysis.Init.CPU.mSec Value: 124. Key : Analysis.Init.Elapsed.mSec Value: 50463. Key : Analysis.Memory.CommitPeak.Mb Value: 139. Key : Bugcheck.Code.DumpHeader Value: 0x119. Key : Bugcheck.Code.Register Value: 0x119. 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: 092422-17687-01.dmp BUGCHECK_CODE: 119. BUGCHECK_P1: 2 BUGCHECK_P2: ffffffffc000000d. BUGCHECK_P3: ffff888531277860. BUGCHECK_P4: ffffe48bbb4efbb0. BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System. STACK_TEXT: ffff8885`31277788 fffff806`8a723ad0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffff8885`31277860 : nt!KeBugCheckEx ffff8885`31277790 fffff806`6fb39cb9 : ffffe48b`bb4ec000 00000000`c000000d ffff8885`31277899 00000000`00000002 : watchdog!WdLogEvent5_WdCriticalError+0xe0 ffff8885`312777d0 fffff806`6fbb432d : ffffe48b`00000000 ffffe48b`bb4efbb0 ffffe48b`b972e000 ffffe48b`b835b510 : dxgmms2!VidSchiSendToExecutionQueue+0xa99 ffff8885`31277900 fffff806`6fbbd1aa : ffffe48b`b835b510 ffffe48b`b972e000 00000000`00000000 ffffe48b`b8e02050 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed ffff8885`31277a80 fffff806`6fbbd01a : ffffe48b`b972e400 fffff806`6fbbcf50 ffffe48b`b972e000 ffff9c00`7c700100 : dxgmms2!VidSchiRun_PriorityTable+0x17a ffff8885`31277ad0 fffff806`73e71d25 : ffffe48b`b7731040 fffff806`00000001 ffffe48b`b972e000 00000000`00000000 : dxgmms2!VidSchiWorkerThread+0xca ffff8885`31277b10 fffff806`74000628 : ffff9c00`7c700180 ffffe48b`b7731040 fffff806`73e71cd0 00000000`00000000 : nt!PspSystemThreadStartup+0x55 ffff8885`31277b60 00000000`00000000 : ffff8885`31278000 ffff8885`31271000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28 SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+a99 MODULE_NAME: dxgmms2. IMAGE_NAME: dxgmms2.sys IMAGE_VERSION: 10.0.19041.1940 STACK_COMMAND: .cxr; .ecxr ; kb. BUCKET_ID_FUNC_OFFSET: a99. 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. ---------
Maalesef hâlâ aynı hata devam ediyor.
Şu mesajda monitörle alakalı olabileceği söylenmiş. İkinci bir monitör kullanıyor musunuz?
VIDEO_SCHEDULER_INTERNAL_ERROR ve dxgmms2.sys mavi ekran hatası
Merhaba. En son beş gün önce yine aynı hata kodunda mavi ekran aldım. DDU ile ekran kartı sürücüsünü kaldırıp 20.4.2 WHQL sürücüsüne indim. 5 gündür sorun yaşamıyordum, şimdi aynı hatayı almaya başladım. BIOS sürümüm güncel değil, elektrik arada gidip geldiği için güncellemeyi düşünmüyorum. DDU...
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: ffff888531277860. Arg4: ffffe48bbb4efbb0. Debugging Details: ------------------ *** WARNING: Unable to verify timestamp for win32k.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1906. Key : Analysis.DebugAnalysisManager Value: Create. Key : Analysis.Elapsed.mSec Value: 36519. Key : Analysis.Init.CPU.mSec Value: 124. Key : Analysis.Init.Elapsed.mSec Value: 50463. Key : Analysis.Memory.CommitPeak.Mb Value: 139. Key : Bugcheck.Code.DumpHeader Value: 0x119. Key : Bugcheck.Code.Register Value: 0x119. 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: 092422-17687-01.dmp BUGCHECK_CODE: 119. BUGCHECK_P1: 2 BUGCHECK_P2: ffffffffc000000d. BUGCHECK_P3: ffff888531277860. BUGCHECK_P4: ffffe48bbb4efbb0. BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System. STACK_TEXT: ffff8885`31277788 fffff806`8a723ad0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffff8885`31277860 : nt!KeBugCheckEx ffff8885`31277790 fffff806`6fb39cb9 : ffffe48b`bb4ec000 00000000`c000000d ffff8885`31277899 00000000`00000002 : watchdog!WdLogEvent5_WdCriticalError+0xe0 ffff8885`312777d0 fffff806`6fbb432d : ffffe48b`00000000 ffffe48b`bb4efbb0 ffffe48b`b972e000 ffffe48b`b835b510 : dxgmms2!VidSchiSendToExecutionQueue+0xa99 ffff8885`31277900 fffff806`6fbbd1aa : ffffe48b`b835b510 ffffe48b`b972e000 00000000`00000000 ffffe48b`b8e02050 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed ffff8885`31277a80 fffff806`6fbbd01a : ffffe48b`b972e400 fffff806`6fbbcf50 ffffe48b`b972e000 ffff9c00`7c700100 : dxgmms2!VidSchiRun_PriorityTable+0x17a ffff8885`31277ad0 fffff806`73e71d25 : ffffe48b`b7731040 fffff806`00000001 ffffe48b`b972e000 00000000`00000000 : dxgmms2!VidSchiWorkerThread+0xca ffff8885`31277b10 fffff806`74000628 : ffff9c00`7c700180 ffffe48b`b7731040 fffff806`73e71cd0 00000000`00000000 : nt!PspSystemThreadStartup+0x55 ffff8885`31277b60 00000000`00000000 : ffff8885`31278000 ffff8885`31271000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28 SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+a99 MODULE_NAME: dxgmms2. IMAGE_NAME: dxgmms2.sys IMAGE_VERSION: 10.0.19041.1940 STACK_COMMAND: .cxr; .ecxr ; kb. BUCKET_ID_FUNC_OFFSET: a99. 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. ---------
BiosVersion = 211
BiosReleaseDate = 01/05/2016
SystemManufacturer = ARCELIK A.S.
SystemProductName = GNB 1574 V1 i5
BaseBoardVersion = 1.0
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
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: fffff80546afb320, 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 ***
*** ***
*************************************************************************
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2671
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 41859
Key : Analysis.Init.CPU.mSec
Value: 187
Key : Analysis.Init.Elapsed.mSec
Value: 1907
Key : Analysis.Memory.CommitPeak.Mb
Value: 129
Key : Bugcheck.Code.DumpHeader
Value: 0x133
Key : Bugcheck.Code.Register
Value: 0x133
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: 092622-31968-01.dmp
BUGCHECK_CODE: 133
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff80546afb320
BUGCHECK_P4: 0
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
TRAP_FRAME: fffff8054a079120 -- (.trap 0xfffff8054a079120)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000000b0 rbx=0000000000000000 rcx=ffffaa0372347000
rdx=fffff8054a079310 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8057b81175b rsp=fffff8054a0792b0 rbp=fffff8054a0793e0
r8=000000000000000c r9=ffffaa03790ca080 r10=000000006331ed52
r11=000000000000000c r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nvlddmkm+0x9175b:
fffff805`7b81175b 488b01 mov rax,qword ptr [rcx] ds:ffffaa03`72347000=fffff8057b811610
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff805`4a080e18 fffff805`46259782 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff805`46afb320 : nt!KeBugCheckEx
fffff805`4a080e20 fffff805`460d2973 : 0000f404`8b9c3cb0 fffff805`414ff180 00000000`00000000 fffff805`414ff180 : nt!KeAccumulateTicks+0x1845b2
fffff805`4a080e80 fffff805`460d245a : fffff805`46af38c0 fffff805`4a0791a0 fffff805`5de0d800 00000000`00005102 : nt!KeClockInterruptNotify+0x453
fffff805`4a080f30 fffff805`46008a45 : fffff805`46af38c0 fffff805`4a080f40 00000000`00000010 ffffe931`dcac8283 : nt!HalpTimerClockIpiRoutine+0x1a
fffff805`4a080f60 fffff805`461faa4a : fffff805`4a0791a0 fffff805`46af38c0 00000000`0000000e 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff805`4a080fb0 fffff805`461fafb7 : ffffe931`dca31df3 fffff805`7b82a46a 00000000`00000000 fffff805`4a079310 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff805`4a079120 fffff805`7b81175b : 00000000`00000003 fffff805`4a079310 00000000`00000010 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff805`4a0792b0 00000000`00000003 : fffff805`4a079310 00000000`00000010 00000000`00000000 00000000`00000000 : nvlddmkm+0x9175b
fffff805`4a0792b8 fffff805`4a079310 : 00000000`00000010 00000000`00000000 00000000`00000000 fffff805`7b8115c3 : 0x3
fffff805`4a0792c0 00000000`00000010 : 00000000`00000000 00000000`00000000 fffff805`7b8115c3 00000000`00000002 : 0xfffff805`4a079310
fffff805`4a0792c8 00000000`00000000 : 00000000`00000000 fffff805`7b8115c3 00000000`00000002 00000000`00000001 : 0x10
SYMBOL_NAME: nvlddmkm+9175b
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 9175b
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
---------BIOS güncellemesi var mı diye kontrol ettiniz mi daha önce?
Yüklü BIOS detayları:
Kod:BiosVersion = 211. BiosReleaseDate = 01/05/2016 SystemManufacturer = ARCELIK A.S. SystemProductName = GNB 1574 V1 i5. BaseBoardVersion = 1.0
Yeni 517.48 sürücüsü çıktı bu arada. Grafik Sürücüsü - GeForce Game Ready Sürücüsü | NVIDIA
Gerçi farklı sürücülerle bile hata alıyorsunuz sürekli. Bu yenisi pek bir şey katmayabilir.
Bunların dışında daha ne yapılabilir bilmiyorum. Daha önce bu problemle uğraşmış ve çözüme ulaşmış tecrübeli birisinin veya biraz daha detaylı analiz yapabilecek, farklı açılardan yaklaşabilecek birilerinin yorum yapması lazım.
Kod:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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: fffff80546afb320, 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 *** *** *** ************************************************************************* *** WARNING: Unable to verify timestamp for win32k.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2671. Key : Analysis.DebugAnalysisManager Value: Create. Key : Analysis.Elapsed.mSec Value: 41859. Key : Analysis.Init.CPU.mSec Value: 187. Key : Analysis.Init.Elapsed.mSec Value: 1907. Key : Analysis.Memory.CommitPeak.Mb Value: 129. Key : Bugcheck.Code.DumpHeader Value: 0x133. Key : Bugcheck.Code.Register Value: 0x133. 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: 092622-31968-01.dmp BUGCHECK_CODE: 133. BUGCHECK_P1: 1 BUGCHECK_P2: 1e00. BUGCHECK_P3: fffff80546afb320. BUGCHECK_P4: 0 DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED TRAP_FRAME: fffff8054a079120 -- (.trap 0xfffff8054a079120) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=00000000000000b0 rbx=0000000000000000 rcx=ffffaa0372347000 rdx=fffff8054a079310 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8057b81175b rsp=fffff8054a0792b0 rbp=fffff8054a0793e0 r8=000000000000000c r9=ffffaa03790ca080 r10=000000006331ed52 r11=000000000000000c r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc. nvlddmkm+0x9175b: fffff805`7b81175b 488b01 mov rax,qword ptr [rcx] ds:ffffaa03`72347000=fffff8057b811610 Resetting default scope. CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System. STACK_TEXT: fffff805`4a080e18 fffff805`46259782 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff805`46afb320 : nt!KeBugCheckEx fffff805`4a080e20 fffff805`460d2973 : 0000f404`8b9c3cb0 fffff805`414ff180 00000000`00000000 fffff805`414ff180 : nt!KeAccumulateTicks+0x1845b2 fffff805`4a080e80 fffff805`460d245a : fffff805`46af38c0 fffff805`4a0791a0 fffff805`5de0d800 00000000`00005102 : nt!KeClockInterruptNotify+0x453 fffff805`4a080f30 fffff805`46008a45 : fffff805`46af38c0 fffff805`4a080f40 00000000`00000010 ffffe931`dcac8283 : nt!HalpTimerClockIpiRoutine+0x1a fffff805`4a080f60 fffff805`461faa4a : fffff805`4a0791a0 fffff805`46af38c0 00000000`0000000e 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5 fffff805`4a080fb0 fffff805`461fafb7 : ffffe931`dca31df3 fffff805`7b82a46a 00000000`00000000 fffff805`4a079310 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa fffff805`4a079120 fffff805`7b81175b : 00000000`00000003 fffff805`4a079310 00000000`00000010 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37 fffff805`4a0792b0 00000000`00000003 : fffff805`4a079310 00000000`00000010 00000000`00000000 00000000`00000000 : nvlddmkm+0x9175b fffff805`4a0792b8 fffff805`4a079310 : 00000000`00000010 00000000`00000000 00000000`00000000 fffff805`7b8115c3 : 0x3. fffff805`4a0792c0 00000000`00000010 : 00000000`00000000 00000000`00000000 fffff805`7b8115c3 00000000`00000002 : 0xfffff805`4a079310 fffff805`4a0792c8 00000000`00000000 : 00000000`00000000 fffff805`7b8115c3 00000000`00000002 00000000`00000001 : 0x10. SYMBOL_NAME: nvlddmkm+9175b MODULE_NAME: nvlddmkm. IMAGE_NAME: nvlddmkm.sys STACK_COMMAND: .cxr; .ecxr ; kb. BUCKET_ID_FUNC_OFFSET: 9175b. 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. ---------
BIOS güncellemesi var mı diye kontrol ettiniz mi daha önce?
Yüklü BIOS detayları:
Kod:BiosVersion = 211. BiosReleaseDate = 01/05/2016 SystemManufacturer = ARCELIK A.S. SystemProductName = GNB 1574 V1 i5. BaseBoardVersion = 1.0
Yeni 517.48 sürücüsü çıktı bu arada. Grafik Sürücüsü - GeForce Game Ready Sürücüsü | NVIDIA
Gerçi farklı sürücülerle bile hata alıyorsunuz sürekli. Bu yenisi pek bir şey katmayabilir.
Bunların dışında daha ne yapılabilir bilmiyorum. Daha önce bu problemle uğraşmış ve çözüme ulaşmış tecrübeli birisinin veya biraz daha detaylı analiz yapabilecek, farklı açılardan yaklaşabilecek birilerinin yorum yapması lazım.
Kod:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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: fffff80546afb320, 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 *** *** *** ************************************************************************* *** WARNING: Unable to verify timestamp for win32k.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2671. Key : Analysis.DebugAnalysisManager Value: Create. Key : Analysis.Elapsed.mSec Value: 41859. Key : Analysis.Init.CPU.mSec Value: 187. Key : Analysis.Init.Elapsed.mSec Value: 1907. Key : Analysis.Memory.CommitPeak.Mb Value: 129. Key : Bugcheck.Code.DumpHeader Value: 0x133. Key : Bugcheck.Code.Register Value: 0x133. 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: 092622-31968-01.dmp BUGCHECK_CODE: 133. BUGCHECK_P1: 1 BUGCHECK_P2: 1e00. BUGCHECK_P3: fffff80546afb320. BUGCHECK_P4: 0 DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED TRAP_FRAME: fffff8054a079120 -- (.trap 0xfffff8054a079120) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=00000000000000b0 rbx=0000000000000000 rcx=ffffaa0372347000 rdx=fffff8054a079310 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8057b81175b rsp=fffff8054a0792b0 rbp=fffff8054a0793e0 r8=000000000000000c r9=ffffaa03790ca080 r10=000000006331ed52 r11=000000000000000c r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc. nvlddmkm+0x9175b: fffff805`7b81175b 488b01 mov rax,qword ptr [rcx] ds:ffffaa03`72347000=fffff8057b811610 Resetting default scope. CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System. STACK_TEXT: fffff805`4a080e18 fffff805`46259782 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff805`46afb320 : nt!KeBugCheckEx fffff805`4a080e20 fffff805`460d2973 : 0000f404`8b9c3cb0 fffff805`414ff180 00000000`00000000 fffff805`414ff180 : nt!KeAccumulateTicks+0x1845b2 fffff805`4a080e80 fffff805`460d245a : fffff805`46af38c0 fffff805`4a0791a0 fffff805`5de0d800 00000000`00005102 : nt!KeClockInterruptNotify+0x453 fffff805`4a080f30 fffff805`46008a45 : fffff805`46af38c0 fffff805`4a080f40 00000000`00000010 ffffe931`dcac8283 : nt!HalpTimerClockIpiRoutine+0x1a fffff805`4a080f60 fffff805`461faa4a : fffff805`4a0791a0 fffff805`46af38c0 00000000`0000000e 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5 fffff805`4a080fb0 fffff805`461fafb7 : ffffe931`dca31df3 fffff805`7b82a46a 00000000`00000000 fffff805`4a079310 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa fffff805`4a079120 fffff805`7b81175b : 00000000`00000003 fffff805`4a079310 00000000`00000010 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37 fffff805`4a0792b0 00000000`00000003 : fffff805`4a079310 00000000`00000010 00000000`00000000 00000000`00000000 : nvlddmkm+0x9175b fffff805`4a0792b8 fffff805`4a079310 : 00000000`00000010 00000000`00000000 00000000`00000000 fffff805`7b8115c3 : 0x3. fffff805`4a0792c0 00000000`00000010 : 00000000`00000000 00000000`00000000 fffff805`7b8115c3 00000000`00000002 : 0xfffff805`4a079310 fffff805`4a0792c8 00000000`00000000 : 00000000`00000000 fffff805`7b8115c3 00000000`00000002 00000000`00000001 : 0x10. SYMBOL_NAME: nvlddmkm+9175b MODULE_NAME: nvlddmkm. IMAGE_NAME: nvlddmkm.sys STACK_COMMAND: .cxr; .ecxr ; kb. BUCKET_ID_FUNC_OFFSET: 9175b. 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. ---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
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: fffff8076ccfb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000
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: TickPeriods ***
*** ***
*************************************************************************
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2124
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 43702
Key : Analysis.Init.CPU.mSec
Value: 202
Key : Analysis.Init.Elapsed.mSec
Value: 161283
Key : Analysis.Memory.CommitPeak.Mb
Value: 127
Key : Bugcheck.Code.DumpHeader
Value: 0x133
Key : Bugcheck.Code.Register
Value: 0x133
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: 100122-16687-01.dmp
BUGCHECK_CODE: 133
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff8076ccfb320
BUGCHECK_P4: 0
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
TRAP_FRAME: fffff8076f870750 -- (.trap 0xfffff8076f870750)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff807a00c10d1 rbx=0000000000000000 rcx=fffff8076f871178
rdx=fffff8076f871178 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8076c279a7c rsp=fffff8076f8708e0 rbp=0000000000000017
r8=0000000000000004 r9=0000000000000000 r10=fffff8076f871150
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe cy
nt!RtlpUnwindPrologue+0x1bc:
fffff807`6c279a7c 488d4108 lea rax,[rcx+8]
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff807`6f880e18 fffff807`6c459782 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff807`6ccfb320 : nt!KeBugCheckEx
fffff807`6f880e20 fffff807`6c2d2973 : 000030db`1ecbda84 fffff807`66c38180 00000000`00000000 fffff807`66c38180 : nt!KeAccumulateTicks+0x1845b2
fffff807`6f880e80 fffff807`6c2d245a : fffff807`6ccf38c0 fffff807`6f8707d0 fffff807`6e1a3c00 00000000`0000b202 : nt!KeClockInterruptNotify+0x453
fffff807`6f880f30 fffff807`6c208a45 : fffff807`6ccf38c0 fffff807`6f880f40 00000000`0000000c ffff5a33`dc1be720 : nt!HalpTimerClockIpiRoutine+0x1a
fffff807`6f880f60 fffff807`6c3faa4a : fffff807`6f8707d0 fffff807`6ccf38c0 fffff807`a0b0c94c 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff807`6f880fb0 fffff807`6c3fafb7 : ffff800e`e2496770 fffff807`6c322d7a 00007fff`fffeffff fffff807`6c322d7a : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff807`6f870750 fffff807`6c279a7c : 1ac77bf2`d729ab22 295084ad`3052f970 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff807`6f8708e0 fffff807`6c279574 : fffff807`a0010000 fffff807`00000000 fffff807`6f871150 00007fff`fffeffff : nt!RtlpUnwindPrologue+0x1bc
fffff807`6f870940 fffff807`6c278930 : 00000000`00000000 fffff807`00000001 fffff807`6f871150 fffff807`a0b0c94c : nt!RtlpxVirtualUnwind+0x104
fffff807`6f8709c0 fffff807`6c27851c : 00000000`0000000a 00000000`0000000b ffff800e`00000000 00000000`00000000 : nt!RtlpWalkFrameChain+0x3e0
fffff807`6f8710d0 fffff807`6c2783b2 : 00000000`00000009 fffff807`6f871188 00000000`00000000 fffff807`6f86b000 : nt!RtlWalkFrameChain+0x11c
fffff807`6f871120 fffff807`a00e079b : 00000000`00000005 fffff807`6f871280 00000000`00000000 fffff807`6f871200 : nt!RtlCaptureStackBackTrace+0x42
fffff807`6f871150 00000000`00000005 : fffff807`6f871280 00000000`00000000 fffff807`6f871200 ffff800e`db5a8000 : nvlddmkm+0xd079b
fffff807`6f871158 fffff807`6f871280 : 00000000`00000000 fffff807`6f871200 ffff800e`db5a8000 fffff807`a00c10d1 : 0x5
fffff807`6f871160 00000000`00000000 : fffff807`6f871200 ffff800e`db5a8000 fffff807`a00c10d1 fffff807`6cd27a00 : 0xfffff807`6f871280
SYMBOL_NAME: nvlddmkm+d079b
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: d079b
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
---------
