Geralt Victarious
Centipat
- Katılım
- 31 Ocak 2023
- Mesajlar
- 475
- Çözümler
- 1
Daha fazla
- Cinsiyet
- Erkek
- SSD veya HDD modeli
- TEAM T253X1240G
- Ekran kartı
- NVIDIA RTX 2060 Super
- Anakart
- B450M H
- İşlemci
- AMD Ryzen 5 3600
VIDEO_ENGINE_TIMEOUT_DETECTED (141)
One of the display engines failed to respond in timely fashion.
(This code can never be used for a real BugCheck.)
Arguments:
Arg1: ffffe58f44ba3460, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8003f8e2298, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.
Debugging Details:
------------------
Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2187
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 7859
Key : Analysis.IO.Other.Mb
Value: 24
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 34
Key : Analysis.Init.CPU.mSec
Value: 280
Key : Analysis.Init.Elapsed.mSec
Value: 105147
Key : Analysis.Memory.CommitPeak.Mb
Value: 155
Key : Bugcheck.Code.DumpHeader
Value: 0x141
Key : Bugcheck.Code.Register
Value: 0xdbb4eac0
Key : Dump.Attributes.AsUlong
Value: 18
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
FILE_IN_CAB: WATCHDOG-20230203-1303.dmp
DUMP_FILE_ATTRIBUTES: 0x18
Kernel Generated Triage Dump
Live Generated Dump
BUGCHECK_CODE: 141
BUGCHECK_P1: ffffe58f44ba3460
BUGCHECK_P2: fffff8003f8e2298
BUGCHECK_P3: 0
BUGCHECK_P4: 0
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffe58f44ba3460
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.
PROCESS_NAME: System
STACK_TEXT:
ffffa884`61779610 fffff800`37948f24 : ffffe58f`3e317030 ffffe58f`3e317030 ffffe58f`3a4322c0 ffffe58f`44ba3460 : watchdog!WdpDbgCaptureTriageDump+0xb7
ffffa884`61779680 fffff800`377adb1d : ffffe58f`44ba3460 ffffa884`61779840 00000000`00000000 00000000`00000000 : watchdog!WdDbgReportRecreate+0xd4
ffffa884`617796e0 fffff800`4b295c33 : ffffe58f`00000000 ffffe58f`40ae7000 ffffe58f`40b6f000 00000000`00000000 : dxgkrnl!TdrUpdateDbgReport+0x11d
ffffa884`61779740 fffff800`4b355802 : ffffe58f`40b6f001 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms2!VidSchiResetHwEngine+0x493
ffffa884`617798f0 fffff800`4b3250e3 : ffffe58f`40ae7000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms2!VidSchiResetEngines+0xaa
ffffa884`61779940 fffff800`4b2f7e9f : 00000000`00000000 00000000`00000000 00000000`000e58d7 00000000`00989680 : dxgmms2!VidSchiCheckHwProgress+0x2d203
ffffa884`617799c0 fffff800`4b25b309 : 00000000`00000000 ffffe58f`40ae7000 ffffa884`61779af9 00000000`00000000 : dxgmms2!VidSchiWaitForSchedulerEvents+0x37f
ffffa884`61779a90 fffff800`4b303c95 : ffffe58f`476f9000 ffffe58f`40ae7000 ffffe58f`476f9010 ffffe58f`40b9c820 : dxgmms2!VidSchiScheduleCommandToRun+0x309
ffffa884`61779b60 fffff800`4b303c0a : 00000000`00000000 fffff800`4b303b40 ffffe58f`40ae7000 00000000`00000080 : dxgmms2!VidSchiRun_PriorityTable+0x35
ffffa884`61779bb0 fffff800`28a0f4a7 : ffffe58f`40afd480 fffff800`00000001 ffffe58f`40ae7000 000f807f`b4bbbdff : dxgmms2!VidSchiWorkerThread+0xca
ffffa884`61779bf0 fffff800`28c2de84 : ffff9880`e2e58180 ffffe58f`40afd480 fffff800`28a0f450 000d6b76`00000050 : nt!PspSystemThreadStartup+0x57
ffffa884`61779c40 00000000`00000000 : ffffa884`6177a000 ffffa884`61774000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34
SYMBOL_NAME: nvlddmkm+c82298
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: LKD_0x141_IMAGE_nvlddmkm.sys
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {341dd0b3-9ebd-47a8-9de8-23f4b00fabbc}
Followup: MachineOwner
---------
One of the display engines failed to respond in timely fashion.
(This code can never be used for a real BugCheck.)
Arguments:
Arg1: ffffe58f44ba3460, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8003f8e2298, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.
Debugging Details:
------------------
Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2187
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 7859
Key : Analysis.IO.Other.Mb
Value: 24
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 34
Key : Analysis.Init.CPU.mSec
Value: 280
Key : Analysis.Init.Elapsed.mSec
Value: 105147
Key : Analysis.Memory.CommitPeak.Mb
Value: 155
Key : Bugcheck.Code.DumpHeader
Value: 0x141
Key : Bugcheck.Code.Register
Value: 0xdbb4eac0
Key : Dump.Attributes.AsUlong
Value: 18
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
FILE_IN_CAB: WATCHDOG-20230203-1303.dmp
DUMP_FILE_ATTRIBUTES: 0x18
Kernel Generated Triage Dump
Live Generated Dump
BUGCHECK_CODE: 141
BUGCHECK_P1: ffffe58f44ba3460
BUGCHECK_P2: fffff8003f8e2298
BUGCHECK_P3: 0
BUGCHECK_P4: 0
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffe58f44ba3460
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.
PROCESS_NAME: System
STACK_TEXT:
ffffa884`61779610 fffff800`37948f24 : ffffe58f`3e317030 ffffe58f`3e317030 ffffe58f`3a4322c0 ffffe58f`44ba3460 : watchdog!WdpDbgCaptureTriageDump+0xb7
ffffa884`61779680 fffff800`377adb1d : ffffe58f`44ba3460 ffffa884`61779840 00000000`00000000 00000000`00000000 : watchdog!WdDbgReportRecreate+0xd4
ffffa884`617796e0 fffff800`4b295c33 : ffffe58f`00000000 ffffe58f`40ae7000 ffffe58f`40b6f000 00000000`00000000 : dxgkrnl!TdrUpdateDbgReport+0x11d
ffffa884`61779740 fffff800`4b355802 : ffffe58f`40b6f001 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms2!VidSchiResetHwEngine+0x493
ffffa884`617798f0 fffff800`4b3250e3 : ffffe58f`40ae7000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms2!VidSchiResetEngines+0xaa
ffffa884`61779940 fffff800`4b2f7e9f : 00000000`00000000 00000000`00000000 00000000`000e58d7 00000000`00989680 : dxgmms2!VidSchiCheckHwProgress+0x2d203
ffffa884`617799c0 fffff800`4b25b309 : 00000000`00000000 ffffe58f`40ae7000 ffffa884`61779af9 00000000`00000000 : dxgmms2!VidSchiWaitForSchedulerEvents+0x37f
ffffa884`61779a90 fffff800`4b303c95 : ffffe58f`476f9000 ffffe58f`40ae7000 ffffe58f`476f9010 ffffe58f`40b9c820 : dxgmms2!VidSchiScheduleCommandToRun+0x309
ffffa884`61779b60 fffff800`4b303c0a : 00000000`00000000 fffff800`4b303b40 ffffe58f`40ae7000 00000000`00000080 : dxgmms2!VidSchiRun_PriorityTable+0x35
ffffa884`61779bb0 fffff800`28a0f4a7 : ffffe58f`40afd480 fffff800`00000001 ffffe58f`40ae7000 000f807f`b4bbbdff : dxgmms2!VidSchiWorkerThread+0xca
ffffa884`61779bf0 fffff800`28c2de84 : ffff9880`e2e58180 ffffe58f`40afd480 fffff800`28a0f450 000d6b76`00000050 : nt!PspSystemThreadStartup+0x57
ffffa884`61779c40 00000000`00000000 : ffffa884`6177a000 ffffa884`61774000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34
SYMBOL_NAME: nvlddmkm+c82298
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: LKD_0x141_IMAGE_nvlddmkm.sys
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {341dd0b3-9ebd-47a8-9de8-23f4b00fabbc}
Followup: MachineOwner
---------
Hatayı çözmek için:
Format attım,
Harddisk ve SSD testi yaptım,
Furmark testi yaptım,
AIDA64 Extreme ile sistem kararlılık testi yaptım,
OCCT ile test yaptım,
Ekran kartı sürücüsünü değiştirdim.
Sistem kararlılık testinde(Stress Test) genellikle kilitlenmeden çıkıyor. Oyunlarda kilitleniyor hep.
Son düzenleyen: Moderatör: