DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff80676b71358, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding this single DPC timeout
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: 8390
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on BORA
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 72331
Key : Analysis.Memory.CommitPeak.Mb
Value: 75
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: 0
BUGCHECK_P2: 501
BUGCHECK_P3: 500
BUGCHECK_P4: fffff80676b71358
DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED
TRAP_FRAME: fffff8067c067a10 -- (.trap 0xfffff8067c067a10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=ffffcf89825ec128
rdx=00000000c1d000ec rsi=0000000000000000 rdi=0000000000000000
rip=fffff80676685a40 rsp=fffff8067c067ba0 rbp=fffff8067c067d00
r8=00000000ff020000 r9=00000000ff0e0000 r10=fffff806767041b0
r11=fffff80691edd26c r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!KxWaitForSpinLockAndAcquire+0x30:
fffff806`76685a40 488b07 mov rax,qword ptr [rdi] ds:00000000`00000000=????????????????
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff806`7c077b08 fffff806`767eefd9 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff806`7c077b10 fffff806`76626af7 : 000004f5`864e2e8e fffff806`74715180 00000000`00000286 fffff806`7c067a10 : nt!KeAccumulateTicks+0x1c5319
fffff806`7c077b70 fffff806`770b8291 : 00000000`ff0e0000 fffff806`77125000 fffff806`7c067a90 fffff806`771250b0 : nt!KeClockInterruptNotify+0xc07
fffff806`7c077f30 fffff806`76703b65 : fffff806`77125000 00000000`00000010 ffff4fa2`3f748459 ffffcf89`825ec128 : hal!HalpTimerClockIpiRoutine+0x21
fffff806`7c077f60 fffff806`767c476a : fffff806`7c067a90 fffff806`77125000 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff806`7c077fb0 fffff806`767c4cd7 : 00000000`00000000 00000030`875f5db0 00000000`00000022 ffffcf89`7e402280 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff806`7c067a10 fffff806`76685a40 : 00000000`00000000 00000000`000000c0 00000000`00000000 00000000`00000038 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff806`7c067ba0 fffff806`76685627 : ffffcf89`825ec128 fffff806`74715180 00000004`000000c8 fffff806`7696e06d : nt!KxWaitForSpinLockAndAcquire+0x30
fffff806`7c067bd0 fffff806`91edbff1 : 00000000`00000000 00000000`00000020 00000000`00000050 00000000`00000000 : nt!KeAcquireSpinLockRaiseToDpc+0x87
fffff806`7c067c00 00000000`00000000 : 00000000`00000020 00000000`00000050 00000000`00000000 ffffcf89`7e402000 : nvlddmkm+0xbbff1
SYMBOL_NAME: nvlddmkm+bbff1
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: bbff1
FAILURE_BUCKET_ID: 0x133_DPC_nvlddmkm!unknown_function
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {15c3af0e-5564-7a80-2e26-65b5115ecc4d}
Followup: MachineOwner
---------
VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000002, The driver failed upon the submission of a command.
Arg2: ffffffffc000000d
Arg3: ffff820051f42860
Arg4: ffffac03faa06570
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 5390
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on BORA
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 25399
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: 119
BUGCHECK_P1: 2
BUGCHECK_P2: ffffffffc000000d
BUGCHECK_P3: ffff820051f42860
BUGCHECK_P4: ffffac03faa06570
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffff8200`51f42788 fffff801`85d841a0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffff8200`51f42860 : nt!KeBugCheckEx
ffff8200`51f42790 fffff801`86abaf38 : 00000000`00000000 ffffac03`faa03000 ffffac03`faa03000 ffffac03`faa06570 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffff8200`51f427d0 fffff801`86b18d54 : ffffac03`00000000 ffffac03`faa06570 ffffac03`fa986000 ffffac03`fba7e9a0 : dxgmms2!VidSchiSendToExecutionQueue+0x14d48
ffff8200`51f42900 fffff801`86b2a315 : ffffac03`fa968950 ffffac03`fa986000 00000000`00000000 ffffac03`faa44a10 : dxgmms2!VidSchiSubmitPagingCommand+0x2f4
ffff8200`51f42a80 fffff801`86b2a18a : ffffac03`fa986400 fffff801`86b2a0c0 ffffac03`fa986000 00000000`00000000 : dxgmms2!VidSchiRun_PriorityTable+0x175
ffff8200`51f42ad0 fffff801`6eb31a85 : ffffac03`fa9ce680 fffff801`00000001 ffffac03`fa986000 000024ef`bd9bbfff : dxgmms2!VidSchiWorkerThread+0xca
ffff8200`51f42b10 fffff801`6ebca2e8 : ffff8680`90d00180 ffffac03`fa9ce680 fffff801`6eb31a30 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffff8200`51f42b60 00000000`00000000 : ffff8200`51f43000 ffff8200`51f3c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+14d48
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.18362.1110
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 14d48
FAILURE_BUCKET_ID: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {9a11bf9c-270e-962e-7a82-3efdab93c10e}
Followup: MachineOwner
---------
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff80406971358, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding this single DPC timeout
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: 8812
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on BORA
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 64680
Key : Analysis.Memory.CommitPeak.Mb
Value: 75
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: 0
BUGCHECK_P2: 501
BUGCHECK_P3: 500
BUGCHECK_P4: fffff80406971358
DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED
TRAP_FRAME: fffff80409067a10 -- (.trap 0xfffff80409067a10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=ffffdb08a81bf128
rdx=00000000c1d00263 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80406485a40 rsp=fffff80409067ba0 rbp=fffff80409067d00
r8=00000000ff020000 r9=00000000ff0e0000 r10=fffff804065041b0
r11=fffff8041e97d26c r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!KxWaitForSpinLockAndAcquire+0x30:
fffff804`06485a40 488b07 mov rax,qword ptr [rdi] ds:00000000`00000000=????????????????
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff804`09077b08 fffff804`065eefd9 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff804`09077b10 fffff804`06426af7 : 00000113`6e1c19e2 fffff804`017df180 00000000`00000286 fffff804`09067a10 : nt!KeAccumulateTicks+0x1c5319
fffff804`09077b70 fffff804`06eb8291 : 00000000`ff0e0000 fffff804`06f25000 fffff804`09067a90 fffff804`06f250b0 : nt!KeClockInterruptNotify+0xc07
fffff804`09077f30 fffff804`06503b65 : fffff804`06f25000 00000000`0000000c ffff809d`f35d862b ffffdb08`a81bf128 : hal!HalpTimerClockIpiRoutine+0x21
fffff804`09077f60 fffff804`065c476a : fffff804`09067a90 fffff804`06f25000 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff804`09077fb0 fffff804`065c4cd7 : 00000000`00000000 00000030`acb2add0 00000000`00000022 ffffdb08`a3e02280 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff804`09067a10 fffff804`06485a40 : 00000000`00000000 00000000`000000c0 00000000`00000000 00000000`00000038 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff804`09067ba0 fffff804`06485627 : ffffdb08`a81bf128 fffff804`017df180 00000034`000000c8 fffff804`0676e06d : nt!KxWaitForSpinLockAndAcquire+0x30
fffff804`09067bd0 fffff804`1e97bff1 : 00000000`00000000 00000000`00000020 00000000`00000050 00000000`00000000 : nt!KeAcquireSpinLockRaiseToDpc+0x87
fffff804`09067c00 00000000`00000000 : 00000000`00000020 00000000`00000050 00000000`00000000 ffffdb08`a3e02000 : nvlddmkm+0xbbff1
SYMBOL_NAME: nvlddmkm+bbff1
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: bbff1
FAILURE_BUCKET_ID: 0x133_DPC_nvlddmkm!unknown_function
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {15c3af0e-5564-7a80-2e26-65b5115ecc4d}
Followup: MachineOwner
---------
VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000002, The driver failed upon the submission of a command.
Arg2: ffffffffc000000d
Arg3: ffffa70afc88f860
Arg4: ffffb08129fdd1f0
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 4890
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on BORA
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 26170
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: 119
BUGCHECK_P1: 2
BUGCHECK_P2: ffffffffc000000d
BUGCHECK_P3: ffffa70afc88f860
BUGCHECK_P4: ffffb08129fdd1f0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffa70a`fc88f788 fffff800`89e341a0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffffa70a`fc88f860 : nt!KeBugCheckEx
ffffa70a`fc88f790 fffff800`8aa8af38 : 00000000`00000000 ffffb081`29fda000 ffffb081`29fda000 ffffb081`29fdd1f0 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffffa70a`fc88f7d0 fffff800`8aae8d54 : ffffb081`00000000 ffffb081`29fdd1f0 ffffb081`29f60000 ffffb081`2d95d010 : dxgmms2!VidSchiSendToExecutionQueue+0x14d48
ffffa70a`fc88f900 fffff800`8aafa315 : ffffb081`29f42950 ffffb081`29f60000 00000000`00000000 ffffb081`2b606620 : dxgmms2!VidSchiSubmitPagingCommand+0x2f4
ffffa70a`fc88fa80 fffff800`8aafa18a : ffffb081`29f60400 fffff800`8aafa0c0 ffffb081`29f60000 00000000`00000000 : dxgmms2!VidSchiRun_PriorityTable+0x175
ffffa70a`fc88fad0 fffff800`70b31a85 : ffffb081`29fa8680 fffff800`00000001 ffffb081`29f60000 000024ef`bd9bbfff : dxgmms2!VidSchiWorkerThread+0xca
ffffa70a`fc88fb10 fffff800`70bca2e8 : ffffc201`786d9180 ffffb081`29fa8680 fffff800`70b31a30 000000ff`ff087224 : nt!PspSystemThreadStartup+0x55
ffffa70a`fc88fb60 00000000`00000000 : ffffa70a`fc890000 ffffa70a`fc889000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+14d48
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.18362.1110
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 14d48
FAILURE_BUCKET_ID: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {9a11bf9c-270e-962e-7a82-3efdab93c10e}
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: fffff8063c771358, 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: 4108
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on BORA
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 7652
Key : Analysis.Memory.CommitPeak.Mb
Value: 75
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: fffff8063c771358
BUGCHECK_P4: 0
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
TRAP_FRAME: fffff80641e68080 -- (.trap 0xfffff80641e68080)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000020000000 rbx=0000000000000000 rcx=0000000000000840
rdx=ffffca0b4683d000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80657a6f899 rsp=fffff80641e68218 rbp=0000000000000000
r8=ffffca0b4683e2c8 r9=0000000000002100 r10=fffff80657d7b928
r11=fffff80641e68100 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nvlddmkm+0x10f899:
fffff806`57a6f899 c3 ret
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff806`41e77b08 fffff806`3c3ef05d : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff806`3c771358 : nt!KeBugCheckEx
fffff806`41e77b10 fffff806`3c226af7 : 00000331`dafc86bc fffff806`3a623180 00000000`00000286 fffff806`41e68080 : nt!KeAccumulateTicks+0x1c539d
fffff806`41e77b70 fffff806`3c15f291 : 00000000`00000000 fffff806`3c1cc000 fffff806`41e68100 fffff806`3c1cc0b0 : nt!KeClockInterruptNotify+0xc07
fffff806`41e77f30 fffff806`3c303b65 : fffff806`3c1cc000 00000000`00000010 ffff4712`1a0264f8 fffff806`41e67e60 : hal!HalpTimerClockIpiRoutine+0x21
fffff806`41e77f60 fffff806`3c3c476a : fffff806`41e68100 fffff806`3c1cc000 00000000`00000004 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff806`41e77fb0 fffff806`3c3c4cd7 : 00000000`00000000 00000000`00000000 ffffca0b`44d0c9a0 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff806`41e68080 fffff806`57a6f899 : fffff806`57a8ffed ffffca0b`4683d000 00000000`00000000 ffffca0b`43e17010 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff806`41e68218 fffff806`57a8ffed : ffffca0b`4683d000 00000000`00000000 ffffca0b`43e17010 00000000`00000000 : nvlddmkm+0x10f899
fffff806`41e68220 ffffca0b`4683d000 : 00000000`00000000 ffffca0b`43e17010 00000000`00000000 00000000`00000020 : nvlddmkm+0x12ffed
fffff806`41e68228 00000000`00000000 : ffffca0b`43e17010 00000000`00000000 00000000`00000020 fffff806`41e68260 : 0xffffca0b`4683d000
CHKIMG_EXTENSION: !chkimg -lo 50 -d !hal
fffff8063c15f35a-fffff8063c15f35f 6 bytes - hal!HalpTimerClockIpiRoutine+ea
[ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
fffff8063c15f3aa-fffff8063c15f3af 6 bytes - hal!HalPerformEndOfInterrupt+4a (+0x50)
[ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
fffff8063c15f3ca-fffff8063c15f3cf 6 bytes - hal!HalpProcessorPrepareForIdle+1a (+0x20)
[ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
fffff8063c15f3ea-fffff8063c15f3ef 6 bytes - hal!HalpProcessorResumeFromIdle+1a (+0x20)
[ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
fffff8063c15f47a - hal!HalPutScatterGatherList+8a (+0x90)
[ cc:4c ]
25 errors : !hal (fffff8063c15f35a-fffff8063c15f47a)
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
---------
wetransfer.com
Yükledi yardımcı olabilir misiniz? 
