Çözüldü "DPC Watchdog Violation" Hatası
- Konuyu başlatan Jony Case
- Başlangıç Tarihi
- Mesaj 18
- Görüntüleme 2B
Bu konu çözüldü olarak işaretlenmiştir. Çözülmediğini düşünüyorsanız konuyu rapor edebilirsiniz.
Çözüm
BIOS güncelle.
pcsupport.lenovo.com
Ekran kartı sürücüsünü güvenli mod da DDU ile eski sürücüyü silip yeni ve en güncel olanını yükleyin, dikkat edin internetiniz kapalı olsun siz yeni sürücüyü kurar iken Windows arka da eski tarihten kalma bir sürücüyü yükler ve sizde sürücüyü yükleyince üst üste sürücü kurmuş olursunuz.
www.technopat.net
laptops and netbooks :: 300 series :: 320 15ikb - Lenovo Support US
pcsupport.lenovo.com
Ekran kartı sürücüsünü güvenli mod da DDU ile eski sürücüyü silip yeni ve en güncel olanını yükleyin, dikkat edin internetiniz kapalı olsun siz yeni sürücüyü kurar iken Windows arka da eski tarihten kalma bir sürücüyü yükler ve sizde sürücüyü yükleyince üst üste sürücü kurmuş olursunuz.
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...
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: fffff80524973358, 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
PROCESSES_ANALYSIS: 1
SERVICE_ANALYSIS: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.18362.476 (WinBuild.160101.0800)
SYSTEM_MANUFACTURER: LENOVO
SYSTEM_PRODUCT_NAME: 80XL
SYSTEM_SKU: LENOVO_MT_80XL_BU_idea_FM_ideapad 320-15IKB
SYSTEM_VERSION: Lenovo ideapad 320-15IKB
BIOS_VENDOR: LENOVO
BIOS_VERSION: 4WCN29WW
BIOS_DATE: 09/30/2017
BASEBOARD_MANUFACTURER: LENOVO
BASEBOARD_PRODUCT: LNVNB161216
BASEBOARD_VERSION: SDK0J40679 WIN
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
DUMP_TYPE: 2
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff80524973358
BUGCHECK_P4: 0
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
CPU_COUNT: 4
CPU_MHZ: a98
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 8e
CPU_STEPPING: 9
CPU_MICROCODE: 6,8e,9,0 (F,M,S,R) SIG: 8E'00000000 (cache) 8E'00000000 (init)
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x133
PROCESS_NAME: System
CURRENT_IRQL: d
ANALYSIS_SESSION_HOST: DESKTOP-18V31A3
ANALYSIS_SESSION_TIME: 12-10-2019 13:10:39.0594
ANALYSIS_VERSION: 10.0.18362.1 x86fre
LAST_CONTROL_TRANSFER: from fffff805245eeac1 to fffff805245c14e0
STACK_TEXT:
fffff805`2a17ab08 fffff805`245eeac1 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff805`24973358 : nt!KeBugCheckEx
fffff805`2a17ab10 fffff805`2441f897 : 0000050f`84c545b4 fffff805`214ad180 00000000`00000286 fffff805`2a172d70 : nt!KeAccumulateTicks+0x1cc061
fffff805`2a17ab70 fffff805`24eb91e1 : ffffd20f`c9b72080 fffff805`24f24fe0 fffff805`2a172df0 fffff805`24f25090 : nt!KeClockInterruptNotify+0xc07
fffff805`2a17af30 fffff805`24402a25 : fffff805`24f24fe0 00000000`00000000 00000000`00000000 ffffa8ce`cdeea873 : hal!HalpTimerClockIpiRoutine+0x21
fffff805`2a17af60 fffff805`245c2f7a : fffff805`2a172df0 fffff805`24f24fe0 00000000`00000008 fffff805`24f24fe0 : nt!KiCallInterruptServiceRoutine+0xa5
fffff805`2a17afb0 fffff805`245c34e7 : fffff805`2498c2d0 fffff805`24eb92cb fffff805`24911000 fffff805`24400000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff805`2a172d70 fffff805`244c649d : fffff805`41ffa99a fffff805`2451b8ee fffff805`00000001 fffff805`000001ee : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff805`2a172f00 fffff805`244c3c4b : 00000000`00000000 fffff805`2a173098 00000000`00000000 00000000`00000000 : nt!RtlpLookupFunctionEntryForStackWalks+0xbd
fffff805`2a172f80 fffff805`2449d572 : fffff805`2a16d000 00000000`00000000 00000000`00000001 ffffd20f`d1eb2000 : nt!RtlpWalkFrameChain+0x25b
fffff805`2a173670 fffff805`2449d4c2 : 00000000`00000006 fffff805`2a173708 00000000`00000000 00000000`00000001 : nt!RtlWalkFrameChain+0x72
fffff805`2a1736a0 fffff805`41ffa99a : ffffd20f`c8ec8000 fffff805`2a173800 00000000`0000ffff 00000000`00000000 : nt!RtlCaptureStackBackTrace+0x42
fffff805`2a1736d0 ffffd20f`c8ec8000 : fffff805`2a173800 00000000`0000ffff 00000000`00000000 fffff805`4229f63b : nvlddmkm+0x12a99a
fffff805`2a1736d8 fffff805`2a173800 : 00000000`0000ffff 00000000`00000000 fffff805`4229f63b fffff805`41ff6160 : 0xffffd20f`c8ec8000
fffff805`2a1736e0 00000000`0000ffff : 00000000`00000000 fffff805`4229f63b fffff805`41ff6160 ffffd20f`c9b72080 : 0xfffff805`2a173800
fffff805`2a1736e8 00000000`00000000 : fffff805`4229f63b fffff805`41ff6160 ffffd20f`c9b72080 00000000`00000000 : 0xffff
THREAD_SHA1_HASH_MOD_FUNC: 12242d49436d302c3aaebe18b192c17d715e2999
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 17fd6f4d4ad5d82b2d5af71e068a9e429da5cef0
THREAD_SHA1_HASH_MOD: 2dcfc882ef7a9a16810a28e5db3852284c3a14c5
FOLLOWUP_IP:
nvlddmkm+12a99a
fffff805`41ffa99a ?? ???
SYMBOL_STACK_INDEX: b
SYMBOL_NAME: nvlddmkm+12a99a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5d8d48d8
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 12a99a
FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function
BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function
PRIMARY_PROBLEM_CLASS: 0x133_ISR_nvlddmkm!unknown_function
TARGET_TIME: 2019-12-10T08:46:59.000Z
OSBUILD: 18362
OSSERVICEPACK: 476
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 784
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2011-12-30 02:28:41
BUILDDATESTAMP_STR: 160101.0800
BUILDLAB_STR: WinBuild
BUILDOSVER_STR: 10.0.18362.476
ANALYSIS_SESSION_ELAPSED_TIME: dbf
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x133_isr_nvlddmkm!unknown_function
FAILURE_ID_HASH: {f97493a5-ea2b-23ca-a808-8602773c2a86}
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: ffff98088eff5860
Arg4: ffffbb02b1bc6b90
Debugging Details:
------------------
KEY_VALUES_STRING: 1
PROCESSES_ANALYSIS: 1
SERVICE_ANALYSIS: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.18362.476 (WinBuild.160101.0800)
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
DUMP_TYPE: 2
BUGCHECK_P1: 2
BUGCHECK_P2: ffffffffc000000d
BUGCHECK_P3: ffff98088eff5860
BUGCHECK_P4: ffffbb02b1bc6b90
CPU_COUNT: 4
CPU_MHZ: a98
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 8e
CPU_STEPPING: 9
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x119
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: DESKTOP-18V31A3
ANALYSIS_SESSION_TIME: 12-10-2019 13:10:34.0726
ANALYSIS_VERSION: 10.0.18362.1 x86fre
LAST_CONTROL_TRANSFER: from fffff8032c1841a0 to fffff80312bc14e0
STACK_TEXT:
ffff9808`8eff5788 fffff803`2c1841a0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffff9808`8eff5860 : nt!KeBugCheckEx
ffff9808`8eff5790 fffff803`2c60abf8 : 00000000`00000000 ffffbb02`b1bc3000 ffff9808`8eff5899 ffffbb02`b1bc3000 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffff9808`8eff57d0 fffff803`2c668684 : ffffbb02`00000000 ffffbb02`b1bc6b90 ffffbb02`b1b98000 ffffbb02`b9b58b30 : dxgmms2!VidSchiSendToExecutionQueue+0x14a08
ffff9808`8eff5900 fffff803`2c679ad5 : ffffbb02`b1b879a0 ffffbb02`9bc9c040 00000000`00000000 fffff803`2c679880 : dxgmms2!VidSchiSubmitPagingCommand+0x2f4
ffff9808`8eff5a80 fffff803`2c67994a : ffffbb02`b1b98400 fffff803`2c679880 ffffbb02`b1b98000 00000000`00000000 : dxgmms2!VidSchiRun_PriorityTable+0x175
ffff9808`8eff5ad0 fffff803`12b2a7a5 : ffffbb02`b1ba3680 fffff803`00000001 ffffbb02`b1b98000 000025ef`b59bbfff : dxgmms2!VidSchiWorkerThread+0xca
ffff9808`8eff5b10 fffff803`12bc8b2a : fffff803`0fcaa180 ffffbb02`b1ba3680 fffff803`12b2a750 035893ff`cb8b48d2 : nt!PspSystemThreadStartup+0x55
ffff9808`8eff5b60 00000000`00000000 : ffff9808`8eff6000 ffff9808`8efef000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a
THREAD_SHA1_HASH_MOD_FUNC: 3c3aefa711a40e43478598e53abd6873e0c9ed57
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 2831a16f72eb580b94422779b5b1b484064cfb6f
THREAD_SHA1_HASH_MOD: 8bc3a1490ebecb3d757d5cd2041e6cd7da5819c4
FOLLOWUP_IP:
dxgmms2!VidSchiSendToExecutionQueue+14a08
fffff803`2c60abf8 cc int 3
FAULT_INSTR_CODE: b60f41cc
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+14a08
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION: 10.0.18362.449
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 14a08
FAILURE_BUCKET_ID: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue
BUCKET_ID: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue
PRIMARY_PROBLEM_CLASS: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue
TARGET_TIME: 2019-12-09T20:30:21.000Z
OSBUILD: 18362
OSSERVICEPACK: 476
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 784
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2011-12-30 02:28:41
BUILDDATESTAMP_STR: 160101.0800
BUILDLAB_STR: WinBuild
BUILDOSVER_STR: 10.0.18362.476
ANALYSIS_SESSION_ELAPSED_TIME: aad
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x119_2_driver_failed_submit_command_dxgmms2!vidschisendtoexecutionqueue
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: ffff9a83e7798860
Arg4: ffffb50f9ec7d570
Debugging Details:
------------------
KEY_VALUES_STRING: 1
PROCESSES_ANALYSIS: 1
SERVICE_ANALYSIS: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.18362.476 (WinBuild.160101.0800)
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
DUMP_TYPE: 2
BUGCHECK_P1: 2
BUGCHECK_P2: ffffffffc000000d
BUGCHECK_P3: ffff9a83e7798860
BUGCHECK_P4: ffffb50f9ec7d570
CPU_COUNT: 4
CPU_MHZ: a98
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 8e
CPU_STEPPING: 9
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x119
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: DESKTOP-18V31A3
ANALYSIS_SESSION_TIME: 12-10-2019 13:10:30.0471
ANALYSIS_VERSION: 10.0.18362.1 x86fre
LAST_CONTROL_TRANSFER: from fffff806448741a0 to fffff8062a7c14e0
STACK_TEXT:
ffff9a83`e7798788 fffff806`448741a0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffff9a83`e7798860 : nt!KeBugCheckEx
ffff9a83`e7798790 fffff806`2869abf8 : 00000000`00000000 ffffb50f`9ec7a000 ffff9a83`e7798899 ffffb50f`9ec7a000 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffff9a83`e77987d0 fffff806`286f8684 : ffffb50f`00000000 ffffb50f`9ec7d570 ffffb50f`9ec38000 ffffb50f`a4f2c010 : dxgmms2!VidSchiSendToExecutionQueue+0x14a08
ffff9a83`e7798900 fffff806`28709ad5 : ffffb50f`9ec2c9a0 ffffb50f`88cbf1c0 00000000`00000000 fffff806`28709880 : dxgmms2!VidSchiSubmitPagingCommand+0x2f4
ffff9a83`e7798a80 fffff806`2870994a : ffffb50f`9ec38400 fffff806`28709880 ffffb50f`9ec38000 00000000`00000000 : dxgmms2!VidSchiRun_PriorityTable+0x175
ffff9a83`e7798ad0 fffff806`2a72a7a5 : ffffb50f`9ec43680 fffff806`00000001 ffffb50f`9ec38000 000025ef`b59bbfff : dxgmms2!VidSchiWorkerThread+0xca
ffff9a83`e7798b10 fffff806`2a7c8b2a : ffffdc81`9b7dd180 ffffb50f`9ec43680 fffff806`2a72a750 000b57e0`058d4800 : nt!PspSystemThreadStartup+0x55
ffff9a83`e7798b60 00000000`00000000 : ffff9a83`e7799000 ffff9a83`e7792000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a
THREAD_SHA1_HASH_MOD_FUNC: 3c3aefa711a40e43478598e53abd6873e0c9ed57
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 2831a16f72eb580b94422779b5b1b484064cfb6f
THREAD_SHA1_HASH_MOD: 8bc3a1490ebecb3d757d5cd2041e6cd7da5819c4
FOLLOWUP_IP:
dxgmms2!VidSchiSendToExecutionQueue+14a08
fffff806`2869abf8 cc int 3
FAULT_INSTR_CODE: b60f41cc
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+14a08
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION: 10.0.18362.449
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 14a08
FAILURE_BUCKET_ID: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue
BUCKET_ID: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue
PRIMARY_PROBLEM_CLASS: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue
TARGET_TIME: 2019-12-09T19:39:51.000Z
OSBUILD: 18362
OSSERVICEPACK: 476
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 784
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2011-12-30 02:28:41
BUILDDATESTAMP_STR: 160101.0800
BUILDLAB_STR: WinBuild
BUILDOSVER_STR: 10.0.18362.476
ANALYSIS_SESSION_ELAPSED_TIME: abd
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x119_2_driver_failed_submit_command_dxgmms2!vidschisendtoexecutionqueue
FAILURE_ID_HASH: {9a11bf9c-270e-962e-7a82-3efdab93c10e}
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: fffff8057c773358, 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
PROCESSES_ANALYSIS: 1
SERVICE_ANALYSIS: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.18362.476 (WinBuild.160101.0800)
SYSTEM_MANUFACTURER: LENOVO
SYSTEM_PRODUCT_NAME: 80XL
SYSTEM_SKU: LENOVO_MT_80XL_BU_idea_FM_ideapad 320-15IKB
SYSTEM_VERSION: Lenovo ideapad 320-15IKB
BIOS_VENDOR: LENOVO
BIOS_VERSION: 4WCN29WW
BIOS_DATE: 09/30/2017
BASEBOARD_MANUFACTURER: LENOVO
BASEBOARD_PRODUCT: LNVNB161216
BASEBOARD_VERSION: SDK0J40679 WIN
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
DUMP_TYPE: 2
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff8057c773358
BUGCHECK_P4: 0
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
CPU_COUNT: 4
CPU_MHZ: a98
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 8e
CPU_STEPPING: 9
CPU_MICROCODE: 6,8e,9,0 (F,M,S,R) SIG: 8E'00000000 (cache) 8E'00000000 (init)
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x133
PROCESS_NAME: AppMarket.exe
CURRENT_IRQL: d
ANALYSIS_SESSION_HOST: DESKTOP-18V31A3
ANALYSIS_SESSION_TIME: 12-10-2019 13:10:26.0079
ANALYSIS_VERSION: 10.0.18362.1 x86fre
LAST_CONTROL_TRANSFER: from fffff8057c3eeac1 to fffff8057c3c14e0
STACK_TEXT:
fffff805`81757b08 fffff805`7c3eeac1 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff805`7c773358 : nt!KeBugCheckEx
fffff805`81757b10 fffff805`7c21f61c : 00000582`2f2b0dcf fffff805`78af2180 00000000`0002283d 00000000`0002283d : nt!KeAccumulateTicks+0x1cc061
fffff805`81757b70 fffff805`7ccb74b7 : fffff805`97990000 fffff805`8174fdf0 fffff805`8174fe70 00000000`00000002 : nt!KeClockInterruptNotify+0x98c
fffff805`81757f30 fffff805`7c202a25 : 00000005`24bab322 fffff805`7cd250e0 fffff805`7cd25190 ffff14de`76af53fb : hal!HalpTimerClockInterrupt+0xf7
fffff805`81757f60 fffff805`7c3c2f7a : fffff805`8174fe70 fffff805`7cd250e0 fffff805`97d5f63b fffff805`7cd250e0 : nt!KiCallInterruptServiceRoutine+0xa5
fffff805`81757fb0 fffff805`7c3c34e7 : 000533d0`015ba000 00000000`00000000 ffffb58d`ffe97c48 ffffb58d`fe208998 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff805`8174fdf0 fffff805`7c2c3cd2 : fffff805`982669e4 fffff805`81750098 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff805`8174ff80 fffff805`7c29d572 : fffff805`8174a000 00000000`00000000 00000000`00000001 ffffb58d`fcab1000 : nt!RtlpWalkFrameChain+0x2e2
fffff805`81750670 fffff805`7c29d4c2 : 00000000`00000006 fffff805`81750708 00000000`00000000 00000000`00000001 : nt!RtlWalkFrameChain+0x72
fffff805`817506a0 fffff805`97aba99a : ffffb58d`f4105000 fffff805`81750800 00000000`0000ffff 00000000`00000000 : nt!RtlCaptureStackBackTrace+0x42
fffff805`817506d0 ffffb58d`f4105000 : fffff805`81750800 00000000`0000ffff 00000000`00000000 fffff805`97d5f63b : nvlddmkm+0x12a99a
fffff805`817506d8 fffff805`81750800 : 00000000`0000ffff 00000000`00000000 fffff805`97d5f63b fffff805`97ab6160 : 0xffffb58d`f4105000
fffff805`817506e0 00000000`0000ffff : 00000000`00000000 fffff805`97d5f63b fffff805`97ab6160 ffffb58e`01bb76c0 : 0xfffff805`81750800
fffff805`817506e8 00000000`00000000 : fffff805`97d5f63b fffff805`97ab6160 ffffb58e`01bb76c0 00000000`00000000 : 0xffff
THREAD_SHA1_HASH_MOD_FUNC: 23c34aed0c62be1e1c076063787fd25eeed3cd96
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 235786e8e78aa5d73092f2e5b4ca92f3133f8b73
THREAD_SHA1_HASH_MOD: 2131cf11cab813b532d1229bd4dd270e2dbd5e0c
FOLLOWUP_IP:
nvlddmkm+12a99a
fffff805`97aba99a ?? ???
SYMBOL_STACK_INDEX: a
SYMBOL_NAME: nvlddmkm+12a99a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5d8d48d8
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 12a99a
FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function
BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function
PRIMARY_PROBLEM_CLASS: 0x133_ISR_nvlddmkm!unknown_function
TARGET_TIME: 2019-12-09T19:18:59.000Z
OSBUILD: 18362
OSSERVICEPACK: 476
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 784
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2011-12-30 02:28:41
BUILDDATESTAMP_STR: 160101.0800
BUILDLAB_STR: WinBuild
BUILDOSVER_STR: 10.0.18362.476
ANALYSIS_SESSION_ELAPSED_TIME: d9b
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x133_isr_nvlddmkm!unknown_function
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: fffff80472973358, 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
PROCESSES_ANALYSIS: 1
SERVICE_ANALYSIS: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.18362.476 (WinBuild.160101.0800)
SYSTEM_MANUFACTURER: LENOVO
SYSTEM_PRODUCT_NAME: 80XL
SYSTEM_SKU: LENOVO_MT_80XL_BU_idea_FM_ideapad 320-15IKB
SYSTEM_VERSION: Lenovo ideapad 320-15IKB
BIOS_VENDOR: LENOVO
BIOS_VERSION: 4WCN29WW
BIOS_DATE: 09/30/2017
BASEBOARD_MANUFACTURER: LENOVO
BASEBOARD_PRODUCT: LNVNB161216
BASEBOARD_VERSION: SDK0J40679 WIN
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
DUMP_TYPE: 2
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff80472973358
BUGCHECK_P4: 0
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
CPU_COUNT: 4
CPU_MHZ: a98
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 8e
CPU_STEPPING: 9
CPU_MICROCODE: 6,8e,9,0 (F,M,S,R) SIG: 8E'00000000 (cache) 8E'00000000 (init)
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x133
PROCESS_NAME: System
CURRENT_IRQL: d
ANALYSIS_SESSION_HOST: DESKTOP-18V31A3
ANALYSIS_SESSION_TIME: 12-10-2019 13:10:23.0419
ANALYSIS_VERSION: 10.0.18362.1 x86fre
LAST_CONTROL_TRANSFER: from fffff804725eeac1 to fffff804725c14e0
STACK_TEXT:
ffffc881`8edb6b08 fffff804`725eeac1 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff804`72973358 : nt!KeBugCheckEx
ffffc881`8edb6b10 fffff804`7241f61c : 000002fa`a689de9e ffffc881`8edc0180 00000000`00012ae5 00000000`00012ae5 : nt!KeAccumulateTicks+0x1cc061
ffffc881`8edb6b70 fffff804`7235e4b7 : 00000000`00000004 ffff8288`9422f0d0 ffff8288`9422f150 00000000`00000002 : nt!KeClockInterruptNotify+0x98c
ffffc881`8edb6f30 fffff804`72402a25 : 00000002`c8b5e34a ffffb88d`2a502500 ffffb88d`2a5025b0 00000000`00002100 : hal!HalpTimerClockInterrupt+0xf7
ffffc881`8edb6f60 fffff804`725c2f7a : ffff8288`9422f150 ffffb88d`2a502500 ffffb88d`3ae74050 ffffb88d`2a502500 : nt!KiCallInterruptServiceRoutine+0xa5
ffffc881`8edb6fb0 fffff804`725c34e7 : 00000000`00000000 00000000`00000000 fffff804`72400000 fffff804`72433966 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff8288`9422f0d0 fffff804`8edb6be1 : fffff804`8eddebf7 ffffb88d`3fa92000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff8288`9422f268 fffff804`8eddebf7 : ffffb88d`3fa92000 00000000`00000000 00000000`00000000 fffff804`8f012a6c : nvlddmkm+0x116be1
ffff8288`9422f270 ffffb88d`3fa92000 : 00000000`00000000 00000000`00000000 fffff804`8f012a6c ffffb88d`00000020 : nvlddmkm+0x13ebf7
ffff8288`9422f278 00000000`00000000 : 00000000`00000000 fffff804`8f012a6c ffffb88d`00000020 ffff8288`9422f2b0 : 0xffffb88d`3fa92000
THREAD_SHA1_HASH_MOD_FUNC: 73862278aea89c6e9afe926a97214e8bed469217
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: c89eb883832ecede116f258f899d6be31727eec3
THREAD_SHA1_HASH_MOD: b65638c546229c8b9c3693c2a82ed471ad9bee32
FOLLOWUP_IP:
nvlddmkm+116be1
fffff804`8edb6be1 ?? ???
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: nvlddmkm+116be1
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5d8d48d8
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 116be1
FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function
BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function
PRIMARY_PROBLEM_CLASS: 0x133_ISR_nvlddmkm!unknown_function
TARGET_TIME: 2019-12-09T09:00:20.000Z
OSBUILD: 18362
OSSERVICEPACK: 476
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 784
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2011-12-30 02:28:41
BUILDDATESTAMP_STR: 160101.0800
BUILDLAB_STR: WinBuild
BUILDOSVER_STR: 10.0.18362.476
ANALYSIS_SESSION_ELAPSED_TIME: 109d
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x133_isr_nvlddmkm!unknown_function
FAILURE_ID_HASH: {f97493a5-ea2b-23ca-a808-8602773c2a86}
Followup: MachineOwner
---------
KS
KS
Jony Case
Centipat
- Katılım
- 28 Temmuz 2019
- Mesajlar
- 287
Hayda. Orada da internatal error mu ne verdi. Tam hatirlamiyorum.
Son düzenleyen: Moderatör:
- Katılım
- 9 Ekim 2015
- Mesajlar
- 12.741
- Çözümler
- 610
Daha fazla
- Cinsiyet
- Erkek
Yeni dosyayı gönderin.
KS
KS
Jony Case
Centipat
- Katılım
- 28 Temmuz 2019
- Mesajlar
- 287
VİDEO SCHEDULER INTERNAL ERROR bunu veriyor hocam orada da.
Laptop şu an kapalı hocam. Sabah atsam olur mu? Sizce sorun ne olabilir?
Son düzenleyen: Moderatör:
- Katılım
- 9 Ekim 2015
- Mesajlar
- 12.741
- Çözümler
- 610
Daha fazla
- Cinsiyet
- Erkek
Olur.
KS
KS
Jony Case
Centipat
- Katılım
- 28 Temmuz 2019
- Mesajlar
- 287
Ben MSI afterbunerda her şeyi sona çekmiştim Core clock falan ondan olabilir mi?
He bir de Windows güncellemesi sonra oldu bunlar.
Ilk kez Windows güncelleştirdim olanlar oldu.
Son düzenleyen: Moderatör:
Saat ayarlarıyla ilgili zaten. Kafanıza göre bilmediğiniz programı kullanarak ayar yaparak bozmaya çalışıyorsunuz.
Size ekran kartıyla ilgili bir şey söylediğim yok dediğimi yaptın mı?
KS
KS
Jony Case
Centipat
- Katılım
- 28 Temmuz 2019
- Mesajlar
- 287
Ama bundan öncede öyleydi. Windows guncelledim olanlar oldu. Simdi sorun BIOS, ekran kartı, Windows hangisi?
MSI aftetbuner acarken de ayni hatayı veriyordu. İcimde artık 920 MX öldü gibi bir his var ya.
Son düzenleyen: Moderatör:
- Katılım
- 9 Ekim 2015
- Mesajlar
- 12.741
- Çözümler
- 610
Daha fazla
- Cinsiyet
- Erkek
Yeni dosyayı gönderin bakalım, kontrol edelim.
Son düzenleme:
KS
KS
Jony Case
Centipat
- Katılım
- 28 Temmuz 2019
- Mesajlar
- 287
Dediklerinizi yaptıktan sonra düzeldi. Artık hata almıyorum çok teşekkürler.
Ama artık son 2 gündür ara ara laptoptan bip sesi geliyor.
Son düzenleyen: Moderatör:
