VIDEO_TDR_FAILURE hatası genellikle GPU sorununa işaret eder. Kod 43 de GPU'nuzun veya sürücünüzün düzgün çalışmadığına dair bir hatadır.
Minidump Dosyalarını Paylaşın
Minidump dosyaları, bilgisayarınız mavi ekran verdiğinde belleğin ufak bir dökümünü barındıran dosyalardır. Bunları analiz ederek mavi ekran hatalarının nedenini öğrenebiliriz. Minidump dosyaları C:\Windows\Minidump klasöründe bulunur ve DMP uzantılıdır. Bu dosyaları sizden istediğimizde...www.technopat.net
Minidump dosyasını paylaş.
Birçok kez kaldırıp yeniden yükledim. GT 540M en son sürücüsü olan 391.35 sürücüsünü kurdum fakat o sürücüde sürekli kod 43 veriyor. Şu anda 353.62 sürümlü driver ile sorunsuz kullanıyorumVIDEO_TDR_FAILUREhatası genellikle GPU sorununa işaret eder. Kod 43 de GPU'nuzun veya sürücünüzün düzgün çalışmadığına dair bir hatadır.
DDU ile GPU sürücünüzü kaldırıp yeniden kurmak bir çözüm yolu olabilir.
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...
Ama yine de kesin analiz için dosyaları paylaşın.
Minidump Dosyalarını Paylaşın
Minidump dosyaları, bilgisayarınız mavi ekran verdiğinde belleğin ufak bir dökümünü barındıran dosyalardır. Bunları analiz ederek mavi ekran hatalarının nedenini öğrenebiliriz. Minidump dosyaları C:\Windows\Minidump klasöründe bulunur ve DMP uzantılıdır. Bu dosyaları sizden istediğimizde...
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: fffff8022cb71358, 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 ***
*** ***
*************************************************************************
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 4765
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-62N06FT
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 92642
Key : Analysis.Memory.CommitPeak.Mb
Value: 76
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: 19h1_release
Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z
Key : WER.OS.Version
Value: 10.0.18362.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 133
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff8022cb71358
BUGCHECK_P4: 0
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
TRAP_FRAME: fffff8023026e020 -- (.trap 0xfffff8023026e020)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000106b22
rdx=ffffe40ad23ec000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80233468b81 rsp=fffff8023026e1b8 rbp=ffffe40ad1677350
r8=ffffe40ad23ece48 r9=000000000041ac88 r10=fffff802336be3a0
r11=fffff8023026e2e0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nvlddmkm+0x1c8b81:
fffff802`33468b81 c3 ret
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
DPC_STACK_BASE: FFFFF8023026EFB0
STACK_TEXT:
fffff802`30275b08 fffff802`2c7ef05d : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff802`2cb71358 : nt!KeBugCheckEx
fffff802`30275b10 fffff802`2c62687c : 0000007b`41bd4c60 fffff802`27e02180 00000000`000034c7 00000000`000034c7 : nt!KeAccumulateTicks+0x1c539d
fffff802`30275b70 fffff802`2d0b6567 : 00000000`00000000 fffff802`3026e020 fffff802`3026e0a0 00000000`00000002 : nt!KeClockInterruptNotify+0x98c
fffff802`30275f30 fffff802`2c703b65 : 00000000`7dec0291 fffff802`2d125100 fffff802`2d1251b0 00000000`0000000a : hal!HalpTimerClockInterrupt+0xf7
fffff802`30275f60 fffff802`2c7c476a : fffff802`3026e0a0 fffff802`2d125100 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff802`30275fb0 fffff802`2c7c4cd7 : 00000000`0000023a fffff802`33499817 00000000`0000000c fffff802`2c62b62c : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff802`3026e020 fffff802`33468b81 : fffff802`336be428 ffffe40a`cdf608a0 00000000`00000020 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff802`3026e1b8 fffff802`336be428 : ffffe40a`cdf608a0 00000000`00000020 00000000`00000000 fffff802`33505147 : nvlddmkm+0x1c8b81
fffff802`3026e1c0 ffffe40a`cdf608a0 : 00000000`00000020 00000000`00000000 fffff802`33505147 ffffe40a`d23ec000 : nvlddmkm+0x41e428
fffff802`3026e1c8 00000000`00000020 : 00000000`00000000 fffff802`33505147 ffffe40a`d23ec000 fffff802`33488358 : 0xffffe40a`cdf608a0
fffff802`3026e1d0 00000000`00000000 : fffff802`33505147 ffffe40a`d23ec000 fffff802`33488358 ffffe40a`d23ece48 : 0x20
SYMBOL_NAME: nvlddmkm+1c8b81
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 1c8b81
FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {f97493a5-ea2b-23ca-a808-8602773c2a86}
Followup: MachineOwner
---------
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000002, The exception code that was not handled
Arg2: fffff80663c0ae62, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 5421
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-62N06FT
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 25657
Key : Analysis.Memory.CommitPeak.Mb
Value: 74
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: 19h1_release
Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z
Key : WER.OS.Version
Value: 10.0.18362.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 1e
BUGCHECK_P1: ffffffffc0000002
BUGCHECK_P2: fffff80663c0ae62
BUGCHECK_P3: 0
BUGCHECK_P4: 0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffffd00`3b036b78 fffff806`63ea5f1e : 00000000`0000001e ffffffff`c0000002 fffff806`63c0ae62 00000000`00000000 : nt!KeBugCheckEx
fffffd00`3b036b80 fffff806`63dcbad2 : fffff806`6410f000 fffff806`63c00000 0005e1a0`00ab5000 00000000`000000e4 : nt!KiFatalExceptionHandler+0x22
fffffd00`3b036bc0 fffff806`63c0cca5 : 00000000`00000000 00000000`00000000 fffffd00`3b037130 00007fff`ffff0000 : nt!RtlpExecuteHandlerForException+0x12
fffffd00`3b036bf0 fffff806`63c0ae93 : 00000000`00000002 00000000`00000002 00000000`c0000002 00000000`00000000 : nt!RtlDispatchException+0x4a5
fffffd00`3b037340 fffff806`63f3c6be : 00000000`00000000 ffffa601`7552c1c8 00000000`00000000 00000000`00000008 : nt!RtlRaiseStatus+0x63
fffffd00`3b0378e0 fffff806`614d2e2f : fffffd00`3b037b10 00000000`000000e4 fffff806`60125800 00000000`00000005 : nt!purecall+0xe
fffffd00`3b037910 fffffd00`3b037b10 : 00000000`000000e4 fffff806`60125800 00000000`00000005 00000000`00000004 : nvlddmkm+0xb2e2f
fffffd00`3b037918 00000000`000000e4 : fffff806`60125800 00000000`00000005 00000000`00000004 fffff806`63c8dff9 : 0xfffffd00`3b037b10
fffffd00`3b037920 fffff806`60125800 : 00000000`00000005 00000000`00000004 fffff806`63c8dff9 ffffa601`7552c210 : 0xe4
fffffd00`3b037928 00000000`00000005 : 00000000`00000004 fffff806`63c8dff9 ffffa601`7552c210 00000000`00000002 : 0xfffff806`60125800
fffffd00`3b037930 00000000`00000004 : fffff806`63c8dff9 ffffa601`7552c210 00000000`00000002 00000000`00000080 : 0x5
fffffd00`3b037938 fffff806`63c8dff9 : ffffa601`7552c210 00000000`00000002 00000000`00000080 ffffa601`00000002 : 0x4
fffffd00`3b037940 fffff806`63c8cd59 : 00000000`00000000 00000000`00989680 00000000`000057cc 00000000`000000e4 : nt!KiProcessExpiredTimerList+0x169
fffffd00`3b037a30 fffff806`63dc680e : 00000000`00000000 ffff9081`a6080180 ffff9081`a6091140 ffffa601`74274080 : nt!KiRetireDpcList+0x4e9
fffffd00`3b037c60 00000000`00000000 : fffffd00`3b038000 fffffd00`3b032000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x7e
SYMBOL_NAME: nvlddmkm+b2e2f
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: b2e2f
FAILURE_BUCKET_ID: 0x1E_c0000002_nvlddmkm!unknown_function
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {c8f880e3-0963-4ac0-03d5-e2cbddbe7c16}
Followup: MachineOwner
---------
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: fffff8076867ee50
Arg3: fffff80768668df0
Arg4: fffff80761ded004
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3796
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-62N06FT
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 11190
Key : Analysis.Memory.CommitPeak.Mb
Value: 74
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: 19h1_release
Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z
Key : WER.OS.Version
Value: 10.0.18362.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 7f
BUGCHECK_P1: 8
BUGCHECK_P2: fffff8076867ee50
BUGCHECK_P3: fffff80768668df0
BUGCHECK_P4: fffff80761ded004
TRAP_FRAME: fffff8076867ee50 -- (.trap 0xfffff8076867ee50)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff7452c93fbc41 rbx=0000000000000000 rcx=fffff80768669231
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80761ded004 rsp=fffff80768668df0 rbp=fffff80768668ef0
r8=0000000000000023 r9=fffff807686692d0 r10=fffff80761e0ad00
r11=fffff807686691f0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nvlddmkm+0x1bd004:
fffff807`61ded004 897c2428 mov dword ptr [rsp+28h],edi ss:0018:fffff807`68668e18=????????
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
DPC_STACK_BASE: FFFFF8076866EFB0
STACK_OVERFLOW: Stack Limit: fffff80768668fb0. Use (kF) and (!stackusage) to investigate stack usage.
STACK_TEXT:
fffff807`6867ed08 fffff807`64fd4b29 : 00000000`0000007f 00000000`00000008 fffff807`6867ee50 fffff807`68668df0 : nt!KeBugCheckEx
fffff807`6867ed10 fffff807`64fcf983 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff807`6867ee50 fffff807`61ded004 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0x2c3
fffff807`68668df0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x1bd004
CHKIMG_EXTENSION: !chkimg -lo 50 -d !hal
fffff80764d5ddda-fffff80764d5dddf 6 bytes - hal!HalpApicRequestInterrupt+17a
[ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
fffff80764d5f26a-fffff80764d5f26f 6 bytes - hal!HalpApic1WriteIcr+3a (+0x1490)
[ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
fffff80764d60f3a-fffff80764d60f3f 6 bytes - hal!HalpTscQueryCounterOrdered+1a (+0x1cd0)
[ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
18 errors : !hal (fffff80764d5ddda-fffff80764d60f3f)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
MEMORY_CORRUPTOR: LARGE
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {e29154ac-69a4-0eb8-172a-a860f73c0a3c}
Followup: memory_corruption
---------
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: fffff08f3c2fb960
Arg4: ffff800f8981abd0
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 4343
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-62N06FT
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 8842
Key : Analysis.Memory.CommitPeak.Mb
Value: 77
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: 19h1_release
Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z
Key : WER.OS.Version
Value: 10.0.18362.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 119
BUGCHECK_P1: 2
BUGCHECK_P2: ffffffffc000000d
BUGCHECK_P3: fffff08f3c2fb960
BUGCHECK_P4: ffff800f8981abd0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff08f`3c2fb888 fffff802`445741a0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d fffff08f`3c2fb960 : nt!KeBugCheckEx
fffff08f`3c2fb890 fffff802`46bbaf38 : 00000000`00000000 ffff800f`89818000 fffff08f`3c2fb999 ffff800f`89818000 : watchdog!WdLogEvent5_WdCriticalError+0xe0
fffff08f`3c2fb8d0 fffff802`46c18d54 : ffff800f`00000000 ffff800f`8981abd0 ffff800f`89789000 ffff800f`8985d930 : dxgmms2!VidSchiSendToExecutionQueue+0x14d48
fffff08f`3c2fba00 fffff802`46c2a315 : ffff800f`897838a0 ffff800f`83c67080 00000000`00000000 fffff802`46c2a0c0 : dxgmms2!VidSchiSubmitPagingCommand+0x2f4
fffff08f`3c2fbb80 fffff802`46c2a18a : ffff800f`89789400 fffff802`46c2a0c0 ffff800f`89789000 00000000`00000000 : dxgmms2!VidSchiRun_PriorityTable+0x175
fffff08f`3c2fbbd0 fffff802`3c531a85 : ffff800f`897d9680 fffff802`00000001 ffff800f`89789000 00000404`ad9bbffe : dxgmms2!VidSchiWorkerThread+0xca
fffff08f`3c2fbc10 fffff802`3c5ca2e8 : ffffda01`2ba00180 ffff800f`897d9680 fffff802`3c531a30 c085ffe1`f5bae8d8 : nt!PspSystemThreadStartup+0x55
fffff08f`3c2fbc60 00000000`00000000 : fffff08f`3c2fc000 fffff08f`3c2f6000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff8023c4ee542-fffff8023c4ee547 6 bytes - nt!PspReaper+a2
[ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
fffff8023c531ab2-fffff8023c531ab7 6 bytes - nt!PspSystemThreadStartup+82 (+0x43570)
[ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
fffff8023c5764ea-fffff8023c5764ef 6 bytes - nt!EmpCheckErrataList+a (+0x44a38)
[ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
fffff8023c576526-fffff8023c57652b 6 bytes - nt!IoAllocateErrorLogEntry+36 (+0x3c)
[ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
fffff8023c5c2cba-fffff8023c5c2cbb 2 bytes - nt!ZwLoadKey3+2a (+0x4c794)
[ 84 00:4c 87 ]
fffff8023c5c2cbd-fffff8023c5c2cbf 3 bytes - nt!ZwLoadKey3+2d (+0x03)
[ 00 00 00:98 c3 90 ]
fffff8023c5c2cda-fffff8023c5c2cdb 2 bytes - nt!KiBugCheckReturn+16 (+0x1d)
[ 84 00:4c 87 ]
fffff8023c5c2cdd-fffff8023c5c2cdf 3 bytes - nt!KiBugCheckReturn+19 (+0x03)
[ 00 00 00:98 c3 90 ]
fffff8023c5c2e0a-fffff8023c5c2e0b 2 bytes - nt!KeBugCheckEx+12a (+0x12d)
[ 84 00:4c 87 ]
fffff8023c5c2e0d-fffff8023c5c2e0f 3 bytes - nt!KeBugCheckEx+12d (+0x03)
[ 00 00 00:98 c3 90 ]
fffff8023c5c2f0a-fffff8023c5c2f0b 2 bytes - nt!KeContextToKframes+fa (+0xfd)
[ 84 00:4c 87 ]
fffff8023c5c2f0d-fffff8023c5c2f0f 3 bytes - nt!KeContextToKframes+fd (+0x03)
[ 00 00 00:98 c3 90 ]
fffff8023c5c2f5a-fffff8023c5c2f5b 2 bytes - nt!KiSaveInitialProcessorControlState+4a (+0x4d)
[ 84 00:4c 87 ]
fffff8023c5c2f5d-fffff8023c5c2f5f 3 bytes - nt!KiSaveInitialProcessorControlState+4d (+0x03)
[ 00 00 00:98 c3 90 ]
fffff8023c5ca2fa-fffff8023c5ca2ff 6 bytes - nt!KiStartSystemThread+3a (+0x739d)
[ cc cc 0f 1f 40 00:4c 87 00 98 c3 90 ]
fffff8023c6b28da-fffff8023c6b28df 6 bytes - nt!KiForceIdleStopDpcRoutine+ea (+0xe85e0)
[ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
fffff8023ccc9c4a-fffff8023ccc9c4f 6 bytes - nt!PspProcessRundownWorker+aa
[ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
fffff8023ccc9cb2-fffff8023ccc9cb7 6 bytes - nt!PspProcessRundownWorkerSingle+62 (+0x68)
[ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
73 errors : !nt (fffff8023c4ee542-fffff8023ccc9cb7)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
MEMORY_CORRUPTOR: LARGE
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {e29154ac-69a4-0eb8-172a-a860f73c0a3c}
Followup: memory_corruption
---------
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffb403c153d010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8044af427dc, 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\nvaci.inf_amd64_944bfe06c9417196\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: 4562
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-62N06FT
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 27682
Key : Analysis.Memory.CommitPeak.Mb
Value: 82
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: 19h1_release
Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z
Key : WER.OS.Version
Value: 10.0.18362.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 116
BUGCHECK_P1: ffffb403c153d010
BUGCHECK_P2: fffff8044af427dc
BUGCHECK_P3: ffffffffc000009a
BUGCHECK_P4: 4
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffff8c85`423e08a8 fffff804`4798ecea : 00000000`00000116 ffffb403`c153d010 fffff804`4af427dc ffffffff`c000009a : nt!KeBugCheckEx
ffff8c85`423e08b0 fffff804`479460a4 : fffff804`4af427dc ffffb403`be014460 00000000`01000000 ffffb403`be0144f8 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffff8c85`423e08f0 fffff804`4793eefd : ffffb403`be016000 ffffb403`be0169e0 00000000`00000001 00000000`00000001 : dxgkrnl!ADAPTER_RENDER::Reset+0x174
ffff8c85`423e0920 fffff804`4798e425 : 00000000`00000100 ffffffff`fffe7960 ffffb403`c1360460 ffffb403`be05c6c0 : dxgkrnl!DXGADAPTER::Reset+0x4bd
ffff8c85`423e0990 fffff804`4d028b70 : ffffb403`c1360460 ffffb403`c1360840 00000000`00000001 ffffb403`be018000 : dxgkrnl!TdrResetFromTimeout+0x15
ffff8c85`423e09c0 fffff804`4d014a68 : ffffb403`be018000 ffffb403`be018000 ffffb403`c1360460 ffffb403`c1360840 : dxgmms1!VidSchiRecoverFromTDR+0x140
ffff8c85`423e0b80 fffff804`4d0146e3 : ffffb403`be018000 00000000`00000080 fffff804`4d014630 ffffb403`be018000 : dxgmms1!VidSchiRun_PriorityTable+0x378
ffff8c85`423e0bd0 fffff804`4151e155 : ffffb403`be05c6c0 fffff804`4d014630 ffffb403`be018000 00000404`ad9bbffe : dxgmms1!VidSchiWorkerThread+0xb3
ffff8c85`423e0c10 fffff804`415c99c8 : ffffd800`111a0180 ffffb403`be05c6c0 fffff804`4151e100 ce8b49c7`8b4cc292 : nt!PspSystemThreadStartup+0x55
ffff8c85`423e0c60 00000000`00000000 : ffff8c85`423e1000 ffff8c85`423db000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: nvlddmkm+ae27dc
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}
Followup: MachineOwner
---------
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffff998a337c2010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8032ad827dc, 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\nvaci.inf_amd64_944bfe06c9417196\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: 4171
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-62N06FT
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 15487
Key : Analysis.Memory.CommitPeak.Mb
Value: 83
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: 19h1_release
Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z
Key : WER.OS.Version
Value: 10.0.18362.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 116
BUGCHECK_P1: ffff998a337c2010
BUGCHECK_P2: fffff8032ad827dc
BUGCHECK_P3: ffffffffc000009a
BUGCHECK_P4: 4
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffff8a0a`d13bc8a8 fffff803`278eecea : 00000000`00000116 ffff998a`337c2010 fffff803`2ad827dc ffffffff`c000009a : nt!KeBugCheckEx
ffff8a0a`d13bc8b0 fffff803`278a60a4 : fffff803`2ad827dc ffff998a`2dca97f0 00000000`01000000 ffff998a`2dca9888 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffff8a0a`d13bc8f0 fffff803`2789eefd : ffff998a`2dcab000 ffff998a`2dcab9e0 00000000`00000001 00000000`00000001 : dxgkrnl!ADAPTER_RENDER::Reset+0x174
ffff8a0a`d13bc920 fffff803`278ee425 : 00000000`00000100 00000000`00000001 ffff998a`337c07d0 ffff998a`2dd0f080 : dxgkrnl!DXGADAPTER::Reset+0x4bd
ffff8a0a`d13bc990 fffff803`2a158b70 : ffff998a`337c07d0 ffff998a`33889660 00000000`00000001 ffff998a`2dcbf000 : dxgkrnl!TdrResetFromTimeout+0x15
ffff8a0a`d13bc9c0 fffff803`2a144a68 : ffff998a`2dcbf000 ffff998a`2dcbf000 ffff998a`337c07d0 ffff998a`33889660 : dxgmms1!VidSchiRecoverFromTDR+0x140
ffff8a0a`d13bcb80 fffff803`2a1446e3 : ffff998a`2dcbf000 00000000`00000080 fffff803`2a144630 ffff998a`2dcbf000 : dxgmms1!VidSchiRun_PriorityTable+0x378
ffff8a0a`d13bcbd0 fffff803`23b1e155 : ffff998a`2dd0f080 fffff803`2a144630 ffff998a`2dcbf000 00000404`ad9bbffe : dxgmms1!VidSchiWorkerThread+0xb3
ffff8a0a`d13bcc10 fffff803`23bc99c8 : ffffd300`5ff20180 ffff998a`2dd0f080 fffff803`23b1e100 4800c000`80021c03 : nt!PspSystemThreadStartup+0x55
ffff8a0a`d13bcc60 00000000`00000000 : ffff8a0a`d13bd000 ffff8a0a`d13b7000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: nvlddmkm+ae27dc
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}
Followup: MachineOwner
---------
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffff8681fc3f2010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff801512141ac, 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\nvaci.inf_amd64_f658c3ebd2a88192\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: 4437
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-62N06FT
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 17553
Key : Analysis.Memory.CommitPeak.Mb
Value: 82
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: 19h1_release
Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z
Key : WER.OS.Version
Value: 10.0.18362.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 116
BUGCHECK_P1: ffff8681fc3f2010
BUGCHECK_P2: fffff801512141ac
BUGCHECK_P3: ffffffffc000009a
BUGCHECK_P4: 4
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffee87`0cb868a8 fffff801`4dcaec7a : 00000000`00000116 ffff8681`fc3f2010 fffff801`512141ac ffffffff`c000009a : nt!KeBugCheckEx
ffffee87`0cb868b0 fffff801`4dc66034 : fffff801`512141ac ffff8681`fb45a660 00000000`01000000 ffff8681`fb45a6f8 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffffee87`0cb868f0 fffff801`4dc5ee8d : ffff8681`fb453000 ffff8681`fb4539e0 00000000`00000001 00000000`00000001 : dxgkrnl!ADAPTER_RENDER::Reset+0x174
ffffee87`0cb86920 fffff801`4dcae3b5 : 00000000`00000100 00000000`00000001 ffff8681`ffb91c10 ffff8681`fb19e080 : dxgkrnl!DXGADAPTER::Reset+0x4bd
ffffee87`0cb86990 fffff801`53498ba0 : ffff8681`ffb91c10 ffff8681`ff9609a0 00000000`00000001 ffff8681`fb45b000 : dxgkrnl!TdrResetFromTimeout+0x15
ffffee87`0cb869c0 fffff801`53484a98 : ffff8681`fb45b000 ffff8681`fb45b000 ffff8681`ffb91c10 ffff8681`ff9609a0 : dxgmms1!VidSchiRecoverFromTDR+0x140
ffffee87`0cb86b80 fffff801`53484713 : ffff8681`fb45b000 00000000`00000080 fffff801`53484660 ffff8681`fb45b000 : dxgmms1!VidSchiRun_PriorityTable+0x378
ffffee87`0cb86bd0 fffff801`4a91e235 : ffff8681`fb19e080 fffff801`53484660 ffff8681`fb45b000 00000404`ad9bbffe : dxgmms1!VidSchiWorkerThread+0xb3
ffffee87`0cb86c10 fffff801`4a9c9f98 : fffff801`450e2180 ffff8681`fb19e080 fffff801`4a91e1e0 45000000`c0978b41 : nt!PspSystemThreadStartup+0x55
ffffee87`0cb86c60 00000000`00000000 : ffffee87`0cb87000 ffffee87`0cb81000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: nvlddmkm+ae41ac
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}
Followup: MachineOwner
---------
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffce0629cbd010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8023ad741ac, 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\nvaci.inf_amd64_f658c3ebd2a88192\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: 4046
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-62N06FT
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 15216
Key : Analysis.Memory.CommitPeak.Mb
Value: 82
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: 19h1_release
Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z
Key : WER.OS.Version
Value: 10.0.18362.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 116
BUGCHECK_P1: ffffce0629cbd010
BUGCHECK_P2: fffff8023ad741ac
BUGCHECK_P3: ffffffffc000009a
BUGCHECK_P4: 4
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffff9f8b`b5d908a8 fffff802`41c5ec7a : 00000000`00000116 ffffce06`29cbd010 fffff802`3ad741ac ffffffff`c000009a : nt!KeBugCheckEx
ffff9f8b`b5d908b0 fffff802`41c16034 : fffff802`3ad741ac ffffce06`29eef460 00000000`01000000 ffffce06`29eef4f8 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffff9f8b`b5d908f0 fffff802`41c0ee8d : ffffce06`29ef1000 ffffce06`29ef19e0 00000000`00000001 00000000`00000001 : dxgkrnl!ADAPTER_RENDER::Reset+0x174
ffff9f8b`b5d90920 fffff802`41c5e3b5 : 00000000`00000100 00000000`00000001 ffffce06`2b86ec10 ffffce06`2b5b5040 : dxgkrnl!DXGADAPTER::Reset+0x4bd
ffff9f8b`b5d90990 fffff802`44b58ba0 : ffffce06`2b86ec10 ffffce06`2df809a0 00000000`00000001 ffffce06`29ef3000 : dxgkrnl!TdrResetFromTimeout+0x15
ffff9f8b`b5d909c0 fffff802`44b44a98 : ffffce06`29ef3000 ffffce06`29ef3000 ffffce06`2b86ec10 ffffce06`2df809a0 : dxgmms1!VidSchiRecoverFromTDR+0x140
ffff9f8b`b5d90b80 fffff802`44b44713 : ffffce06`29ef3000 00000000`00000080 fffff802`44b44660 ffffce06`29ef3000 : dxgmms1!VidSchiRun_PriorityTable+0x378
ffff9f8b`b5d90bd0 fffff802`3d31e235 : ffffce06`2b5b5040 fffff802`44b44660 ffffce06`29ef3000 ffff975c`00000001 : dxgmms1!VidSchiWorkerThread+0xb3
ffff9f8b`b5d90c10 fffff802`3d3c9f98 : ffff8181`e1280180 ffffce06`2b5b5040 fffff802`3d31e1e0 00000000`0000029e : nt!PspSystemThreadStartup+0x55
ffff9f8b`b5d90c60 00000000`00000000 : ffff9f8b`b5d91000 ffff9f8b`b5d8b000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: nvlddmkm+ae41ac
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}
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: fffff80232971358, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000
Debugging Details:
------------------
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 30
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-62N06FT
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 26
Key : Analysis.Memory.CommitPeak.Mb
Value: 44
Key : Analysis.System
Value: CreateObject
Key : WER.CorruptModuleList
Value: 1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 133
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff80232971358
BUGCHECK_P4: 0
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
CUSTOMER_CRASH_COUNT: 1
STACK_TEXT:
fffff802`36475b08 fffff802`325ef05d : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff802`32971358 : 0xfffff802`325c2ce0
fffff802`36475b10 00000000`00000133 : 00000000`00000001 00000000`00001e00 fffff802`32971358 00000000`00000000 : 0xfffff802`325ef05d
fffff802`36475b18 00000000`00000001 : 00000000`00001e00 fffff802`32971358 00000000`00000000 00000000`00000000 : 0x133
fffff802`36475b20 00000000`00001e00 : fffff802`32971358 00000000`00000000 00000000`00000000 00000000`00008886 : 0x1
fffff802`36475b28 fffff802`32971358 : 00000000`00000000 00000000`00000000 00000000`00008886 ffff9180`b7c77830 : 0x1e00
fffff802`36475b30 00000000`00000000 : 00000000`00000000 00000000`00008886 ffff9180`b7c77830 fffff780`00000320 : 0xfffff802`32971358
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: CORRUPT_MODULELIST_0x133
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {13e3c9ef-8526-da41-b41d-06d8277b0319}
Followup: MachineOwner
---------
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8002b48ce63, address which referenced memory
Debugging Details:
------------------
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 30
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-62N06FT
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 26
Key : Analysis.Memory.CommitPeak.Mb
Value: 44
Key : Analysis.System
Value: CreateObject
Key : WER.CorruptModuleList
Value: 1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: a
BUGCHECK_P1: 8
BUGCHECK_P2: 2
BUGCHECK_P3: 0
BUGCHECK_P4: fffff8002b48ce63
READ_ADDRESS: Unable to get size of nt!_MMPTE - probably bad symbols
0000000000000008
CUSTOMER_CRASH_COUNT: 1
STACK_TEXT:
ffffb305`fbe29758 fffff800`2b5d4b29 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : 0xfffff800`2b5c2ce0
ffffb305`fbe29760 00000000`0000000a : 00000000`00000008 00000000`00000002 00000000`00000000 fffff800`2b48ce63 : 0xfffff800`2b5d4b29
ffffb305`fbe29768 00000000`00000008 : 00000000`00000002 00000000`00000000 fffff800`2b48ce63 00000000`00000000 : 0xa
ffffb305`fbe29770 00000000`00000002 : 00000000`00000000 fffff800`2b48ce63 00000000`00000000 00000000`00000000 : 0x8
ffffb305`fbe29778 00000000`00000000 : fffff800`2b48ce63 00000000`00000000 00000000`00000000 00000000`00000000 : 0x2
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: CORRUPT_MODULELIST_AV
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {fc259191-ef0c-6215-476f-d32e5dcaf1b7}
Followup: MachineOwner
---------
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80621691102, The address that the exception occurred at
Arg3: ffff818e00f71dd8, Exception Record Address
Arg4: ffff818e00f71620, Context Record Address
Debugging Details:
------------------
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 46
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-62N06FT
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 36
Key : Analysis.Memory.CommitPeak.Mb
Value: 44
Key : Analysis.System
Value: CreateObject
Key : WER.CorruptModuleList
Value: 1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff80621691102
BUGCHECK_P3: ffff818e00f71dd8
BUGCHECK_P4: ffff818e00f71620
EXCEPTION_RECORD: ffff818e00f71dd8 -- (.exr 0xffff818e00f71dd8)
ExceptionAddress: fffff80621691102
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000010
Attempt to read from address 0000000000000010
CONTEXT: ffff818e00f71620 -- (.cxr 0xffff818e00f71620)
rax=0000000000000000 rbx=ffffc1049cdd4110 rcx=ffffc1049cdd4110
rdx=0000000000000000 rsi=0000000000000000 rdi=ffffc1049cdd4110
rip=fffff80621691102 rsp=ffff818e00f72018 rbp=0000000020020004
r8=0000000020020004 r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000001 r13=ffffc1049ea54000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
fffff806`21691102 ?? ???
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
ffff818e`00f70db8 fffff806`1ffdc65c : 00000000`0000007e ffffffff`c0000005 fffff806`21691102 ffff818e`00f71dd8 : 0xfffff806`1ffc2ce0
ffff818e`00f70dc0 00000000`0000007e : ffffffff`c0000005 fffff806`21691102 ffff818e`00f71dd8 ffff818e`00f71620 : 0xfffff806`1ffdc65c
ffff818e`00f70dc8 ffffffff`c0000005 : fffff806`21691102 ffff818e`00f71dd8 ffff818e`00f71620 fffff806`2176d6ab : 0x7e
ffff818e`00f70dd0 fffff806`21691102 : ffff818e`00f71dd8 ffff818e`00f71620 fffff806`2176d6ab 00000000`00131a85 : 0xffffffff`c0000005
ffff818e`00f70dd8 ffff818e`00f71dd8 : ffff818e`00f71620 fffff806`2176d6ab 00000000`00131a85 fffff806`1ff9da7c : 0xfffff806`21691102
ffff818e`00f70de0 ffff818e`00f71620 : fffff806`2176d6ab 00000000`00131a85 fffff806`1ff9da7c ffff818e`00000003 : 0xffff818e`00f71dd8
ffff818e`00f70de8 fffff806`2176d6ab : 00000000`00131a85 fffff806`1ff9da7c ffff818e`00000003 ffff818e`00f72c10 : 0xffff818e`00f71620
ffff818e`00f70df0 00000000`00131a85 : fffff806`1ff9da7c ffff818e`00000003 ffff818e`00f72c10 ffff818e`00f6d000 : 0xfffff806`2176d6ab
ffff818e`00f70df8 fffff806`1ff9da7c : ffff818e`00000003 ffff818e`00f72c10 ffff818e`00f6d000 ffff818e`00f73000 : 0x131a85
ffff818e`00f70e00 ffff818e`00000003 : ffff818e`00f72c10 ffff818e`00f6d000 ffff818e`00f73000 ffff818e`00f70ee0 : 0xfffff806`1ff9da7c
ffff818e`00f70e08 ffff818e`00f72c10 : ffff818e`00f6d000 ffff818e`00f73000 ffff818e`00f70ee0 fffff806`27e9beed : 0xffff818e`00000003
ffff818e`00f70e10 ffff818e`00f6d000 : ffff818e`00f73000 ffff818e`00f70ee0 fffff806`27e9beed ffff818e`00f71dd8 : 0xffff818e`00f72c10
ffff818e`00f70e18 ffff818e`00f73000 : ffff818e`00f70ee0 fffff806`27e9beed ffff818e`00f71dd8 ffff818e`00f71620 : 0xffff818e`00f6d000
ffff818e`00f70e20 ffff818e`00f70ee0 : fffff806`27e9beed ffff818e`00f71dd8 ffff818e`00f71620 fffff806`2031d2bc : 0xffff818e`00f73000
ffff818e`00f70e28 fffff806`27e9beed : ffff818e`00f71dd8 ffff818e`00f71620 fffff806`2031d2bc ffff818e`00f72c00 : 0xffff818e`00f70ee0
ffff818e`00f70e30 ffff818e`00f71dd8 : ffff818e`00f71620 fffff806`2031d2bc ffff818e`00f72c00 ffff818e`00f70ee0 : 0xfffff806`27e9beed
ffff818e`00f70e38 ffff818e`00f71620 : fffff806`2031d2bc ffff818e`00f72c00 ffff818e`00f70ee0 fffff806`1ff31a85 : 0xffff818e`00f71dd8
ffff818e`00f70e40 fffff806`2031d2bc : ffff818e`00f72c00 ffff818e`00f70ee0 fffff806`1ff31a85 00000000`00000000 : 0xffff818e`00f71620
ffff818e`00f70e48 ffff818e`00f72c00 : ffff818e`00f70ee0 fffff806`1ff31a85 00000000`00000000 fffff806`1ffcbad2 : 0xfffff806`2031d2bc
ffff818e`00f70e50 ffff818e`00f70ee0 : fffff806`1ff31a85 00000000`00000000 fffff806`1ffcbad2 ffff818e`00f72c10 : 0xffff818e`00f72c00
ffff818e`00f70e58 fffff806`1ff31a85 : 00000000`00000000 fffff806`1ffcbad2 ffff818e`00f72c10 ffff818e`00f713e0 : 0xffff818e`00f70ee0
ffff818e`00f70e60 00000000`00000000 : fffff806`1ffcbad2 ffff818e`00f72c10 ffff818e`00f713e0 00000000`00000000 : 0xfffff806`1ff31a85
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: CORRUPT_MODULELIST_AV
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {fc259191-ef0c-6215-476f-d32e5dcaf1b7}
Followup: MachineOwner
---------
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffff968d70642010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8060dc9c4f4, 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:
------------------
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 30
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-62N06FT
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 32
Key : Analysis.Memory.CommitPeak.Mb
Value: 44
Key : Analysis.System
Value: CreateObject
Key : WER.CorruptModuleList
Value: 1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 116
BUGCHECK_P1: ffff968d70642010
BUGCHECK_P2: fffff8060dc9c4f4
BUGCHECK_P3: ffffffffc000009a
BUGCHECK_P4: 4
CUSTOMER_CRASH_COUNT: 1
STACK_TEXT:
ffff8200`0d7698a8 00007ff9`1b6a18c0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff806`0efc2ce0
ffff8200`0d7698b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`1b6a18c0
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: BAD_STACK_0x116
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {08ad1cd5-cfef-0d1a-76f3-ef654e4f75c2}
Followup: MachineOwner
---------
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffde05ffbd9050, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff80176f7c4f4, 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:
------------------
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 31
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-62N06FT
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 31
Key : Analysis.Memory.CommitPeak.Mb
Value: 44
Key : Analysis.System
Value: CreateObject
Key : WER.CorruptModuleList
Value: 1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 116
BUGCHECK_P1: ffffde05ffbd9050
BUGCHECK_P2: fffff80176f7c4f4
BUGCHECK_P3: ffffffffc000009a
BUGCHECK_P4: 4
CUSTOMER_CRASH_COUNT: 1
STACK_TEXT:
ffffc702`cef2d8a8 fffff801`7d66ec3a : 00000000`00000116 ffffde05`ffbd9050 fffff801`76f7c4f4 ffffffff`c000009a : 0xfffff801`78fc2ce0
ffffc702`cef2d8b0 00000000`00000116 : ffffde05`ffbd9050 fffff801`76f7c4f4 ffffffff`c000009a 00000000`00000004 : 0xfffff801`7d66ec3a
ffffc702`cef2d8b8 ffffde05`ffbd9050 : fffff801`76f7c4f4 ffffffff`c000009a 00000000`00000004 00000000`00000004 : 0x116
ffffc702`cef2d8c0 fffff801`76f7c4f4 : ffffffff`c000009a 00000000`00000004 00000000`00000004 ffffde05`ffbd9050 : 0xffffde05`ffbd9050
ffffc702`cef2d8c8 ffffffff`c000009a : 00000000`00000004 00000000`00000004 ffffde05`ffbd9050 fffff801`7d625ff4 : 0xfffff801`76f7c4f4
ffffc702`cef2d8d0 00000000`00000004 : 00000000`00000004 ffffde05`ffbd9050 fffff801`7d625ff4 fffff801`76f7c4f4 : 0xffffffff`c000009a
ffffc702`cef2d8d8 00000000`00000004 : ffffde05`ffbd9050 fffff801`7d625ff4 fffff801`76f7c4f4 ffffde06`01af07c0 : 0x4
ffffc702`cef2d8e0 ffffde05`ffbd9050 : fffff801`7d625ff4 fffff801`76f7c4f4 ffffde06`01af07c0 00000000`01000000 : 0x4
ffffc702`cef2d8e8 fffff801`7d625ff4 : fffff801`76f7c4f4 ffffde06`01af07c0 00000000`01000000 ffffde06`01af0858 : 0xffffde05`ffbd9050
ffffc702`cef2d8f0 fffff801`76f7c4f4 : ffffde06`01af07c0 00000000`01000000 ffffde06`01af0858 00000000`00002000 : 0xfffff801`7d625ff4
ffffc702`cef2d8f8 ffffde06`01af07c0 : 00000000`01000000 ffffde06`01af0858 00000000`00002000 fffff801`7d61ee4d : 0xfffff801`76f7c4f4
ffffc702`cef2d900 00000000`01000000 : ffffde06`01af0858 00000000`00002000 fffff801`7d61ee4d ffffde06`00ee8000 : 0xffffde06`01af07c0
ffffc702`cef2d908 ffffde06`01af0858 : 00000000`00002000 fffff801`7d61ee4d ffffde06`00ee8000 ffffde06`00ee89e0 : 0x1000000
ffffc702`cef2d910 00000000`00002000 : fffff801`7d61ee4d ffffde06`00ee8000 ffffde06`00ee89e0 00000000`00000001 : 0xffffde06`01af0858
ffffc702`cef2d918 fffff801`7d61ee4d : ffffde06`00ee8000 ffffde06`00ee89e0 00000000`00000001 00000000`00000001 : 0x2000
ffffc702`cef2d920 ffffde06`00ee8000 : ffffde06`00ee89e0 00000000`00000001 00000000`00000001 fffff801`778e0000 : 0xfffff801`7d61ee4d
ffffc702`cef2d928 ffffde06`00ee89e0 : 00000000`00000001 00000000`00000001 fffff801`778e0000 00000000`00000000 : 0xffffde06`00ee8000
ffffc702`cef2d930 00000000`00000001 : 00000000`00000001 fffff801`778e0000 00000000`00000000 00004000`00000010 : 0xffffde06`00ee89e0
ffffc702`cef2d938 00000000`00000001 : fffff801`778e0000 00000000`00000000 00004000`00000010 00000000`00000000 : 0x1
ffffc702`cef2d940 fffff801`778e0000 : 00000000`00000000 00004000`00000010 00000000`00000000 00000000`00000000 : 0x1
ffffc702`cef2d948 00000000`00000000 : 00004000`00000010 00000000`00000000 00000000`00000000 ffffde06`00eea000 : 0xfffff801`778e0000
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x116_ANALYSIS_INCONCLUSIVE!unknown_function
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {d0ecd047-d84e-1626-7611-d54cbc1cd165}
Followup: MachineOwner
---------
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffc186cc023050, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff800657741ac, 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:
------------------
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 31
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-62N06FT
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 25
Key : Analysis.Memory.CommitPeak.Mb
Value: 44
Key : Analysis.System
Value: CreateObject
Key : WER.CorruptModuleList
Value: 1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 116
BUGCHECK_P1: ffffc186cc023050
BUGCHECK_P2: fffff800657741ac
BUGCHECK_P3: ffffffffc000009a
BUGCHECK_P4: 4
CUSTOMER_CRASH_COUNT: 1
STACK_TEXT:
ffffe986`7a8008a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff800`599c2990
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: ZEROED_STACK_0x116
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {3154f8e6-c4fa-03b5-6330-e2df673f8bf4}
Followup: MachineOwner
---------Selam;
