Video scheduler internal error Mavi ekran sorunları

C

cfunkvcy

Centipat
Katılım
28 Ocak 2020
Mesajlar
2
Selam, iki gündür dizüstü bilgisayarimda mavi ekran hatalari almaya basladim. Hatalar farkli durumlarda geliyor, bazen browserda iken, bazen herhangi bir oyunu açtığımda, bazen bilgisayari hareket ettirince.
  • Aldığım hatalalar: Video scheduler internal error.
  • Bad pool caller.
  • DPC watchdog violation.
Grafik sürücülerimi aygıt yöneticisinden güncelledim, diskleri ve sistemi taradim, Windows güncellemelerini kontrol ettim sorunlar devam ediyor. Yazilimsal mi donanimsal mi anlayamadim. Nereye bakmam gerekiyor bilmiyorum yardimci olabilirseniz süper olur, halamin desteği hepimizle.
Minidump klasörüm: minibump.rar
 
Son düzenleyen: Moderatör:
Tarihe göre sırala Puana göre sırala
Ekran kartı (NVIDIA) arızası. Muhtemel lehim atması. Cihaz çok eski değilse reablling yaptırılabilir.

Kod: 
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: ffff94857a57f860
Arg4: ffffb58fc883d9d0

Debugging Details:
------------------

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 4

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-1IBQR0U

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 20

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 72

    Key  : Analysis.System
    Value: CreateObject


ADDITIONAL_XML: 1

BUGCHECK_CODE:  119

BUGCHECK_P1: 2

BUGCHECK_P2: ffffffffc000000d

BUGCHECK_P3: ffff94857a57f860

BUGCHECK_P4: ffffb58fc883d9d0

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
ffff9485`7a57f788 fffff807`791e41a0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffff9485`7a57f860 : nt!KeBugCheckEx
ffff9485`7a57f790 fffff807`795dabf8 : 00000000`00000000 ffffb58f`c883a000 ffffb58f`c883a000 ffffb58f`c883d9d0 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffff9485`7a57f7d0 fffff807`79638684 : ffffb58f`00000000 ffffb58f`c883d9d0 ffffb58f`c96ab000 ffffb58f`cd084010 : dxgmms2!VidSchiSendToExecutionQueue+0x14a08
ffff9485`7a57f900 fffff807`79649ad5 : ffffb58f`c96a8360 ffffb58f`c96ab000 00000000`00000000 ffffb58f`c884c620 : dxgmms2!VidSchiSubmitPagingCommand+0x2f4
ffff9485`7a57fa80 fffff807`7964994a : ffffb58f`c96ab400 fffff807`79649880 ffffb58f`c96ab000 00000000`00000000 : dxgmms2!VidSchiRun_PriorityTable+0x175
ffff9485`7a57fad0 fffff807`5fb2a7a5 : ffffb58f`c95d80c0 fffff807`00000001 ffffb58f`c96ab000 000025ef`bd9bbfff : dxgmms2!VidSchiWorkerThread+0xca
ffff9485`7a57fb10 fffff807`5fbc8b2a : fffff807`59d24180 ffffb58f`c95d80c0 fffff807`5fb2a750 64b94100`0000a483 : nt!PspSystemThreadStartup+0x55
ffff9485`7a57fb60 00000000`00000000 : ffff9485`7a580000 ffff9485`7a579000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a


SYMBOL_NAME:  dxgmms2!VidSchiSendToExecutionQueue+14a08

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

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

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
---------
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: fffff587e3df7860
Arg4: ffff8c04e1b5abd0

Debugging Details:
------------------

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 4

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-1IBQR0U

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 26

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 72

    Key  : Analysis.System
    Value: CreateObject


ADDITIONAL_XML: 1

BUGCHECK_CODE:  119

BUGCHECK_P1: 2

BUGCHECK_P2: ffffffffc000000d

BUGCHECK_P3: fffff587e3df7860

BUGCHECK_P4: ffff8c04e1b5abd0

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
fffff587`e3df7788 fffff807`9d3441a0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d fffff587`e3df7860 : nt!KeBugCheckEx
fffff587`e3df7790 fffff807`9aa1abf8 : 00000000`00000000 ffff8c04`e1b58000 fffff587`e3df7899 ffff8c04`e1b58000 : watchdog!WdLogEvent5_WdCriticalError+0xe0
fffff587`e3df77d0 fffff807`9aa78684 : ffff8c04`00000000 ffff8c04`e1b5abd0 ffff8c04`e1ade000 ffff8c04`e1b884a0 : dxgmms2!VidSchiSendToExecutionQueue+0x14a08
fffff587`e3df7900 fffff807`9aa89ad5 : ffff8c04`e1b0e3a0 ffff8c04`c80f4380 00000000`00000000 fffff807`9aa89880 : dxgmms2!VidSchiSubmitPagingCommand+0x2f4
fffff587`e3df7a80 fffff807`9aa8994a : ffff8c04`e1ade400 fffff807`9aa89880 ffff8c04`e1ade000 00000000`00000000 : dxgmms2!VidSchiRun_PriorityTable+0x175
fffff587`e3df7ad0 fffff807`8112a7a5 : ffff8c04`e1a18080 fffff807`00000001 ffff8c04`e1ade000 000025ef`bd9bbfff : dxgmms2!VidSchiWorkerThread+0xca
fffff587`e3df7b10 fffff807`811c8b2a : fffff807`7d8e7180 ffff8c04`e1a18080 fffff807`8112a750 741e92d7`731fc05a : nt!PspSystemThreadStartup+0x55
fffff587`e3df7b60 00000000`00000000 : fffff587`e3df8000 fffff587`e3df1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a


SYMBOL_NAME:  dxgmms2!VidSchiSendToExecutionQueue+14a08

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

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

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: fffff80541573358, 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 checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 4

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-1IBQR0U

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 65

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 71

    Key  : Analysis.System
    Value: CreateObject


ADDITIONAL_XML: 1

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff80541573358

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
fffff805`45c3ab08 fffff805`411eeac1 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff805`41573358 : nt!KeBugCheckEx
fffff805`45c3ab10 fffff805`4101f61c : 0000014d`d1e54d07 fffff805`3be4d180 00000000`0000820f 00000000`0000820f : nt!KeAccumulateTicks+0x1cc061
fffff805`45c3ab70 fffff805`41ab74b7 : fffff805`41591400 fffff805`45c2a920 fffff805`45c2a9a0 00000000`00000002 : nt!KeClockInterruptNotify+0x98c
fffff805`45c3af30 fffff805`41002a25 : 00000001`362d563b fffff805`41b250e0 fffff805`41b25190 ffff123d`12025c06 : hal!HalpTimerClockInterrupt+0xf7
fffff805`45c3af60 fffff805`411c2f7a : fffff805`45c2a9a0 fffff805`41b250e0 00000000`00000005 00000000`00002100 : nt!KiCallInterruptServiceRoutine+0xa5
fffff805`45c3afb0 fffff805`411c34e7 : fffff805`4158c360 fffff805`41ab92cb fffff805`6194a000 fffff805`61090000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff805`45c2a920 fffff805`410c606e : fffff805`611af36a 00000000`00000008 ffffffff`00000001 fffff805`000001c4 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff805`45c2aab0 fffff805`410c382b : 00000000`00000000 fffff805`45c2ac48 00000000`00000000 00000000`00000000 : nt!RtlpLookupFunctionEntryForStackWalks+0xae
fffff805`45c2ab30 fffff805`410e21d2 : fffff805`45c25000 00000000`00000000 00000000`00000001 ffffba84`c86f2000 : nt!RtlpWalkFrameChain+0x25b
fffff805`45c2b220 fffff805`410e2122 : 00000000`00000003 fffff805`45c2b2b8 00000000`00000000 00000000`00000001 : nt!RtlWalkFrameChain+0x72
fffff805`45c2b250 fffff805`611af36a : ffffba84`c7371000 fffff805`45c2b3b0 00000000`0000ffff 00000000`00000000 : nt!RtlCaptureStackBackTrace+0x42
fffff805`45c2b280 ffffba84`c7371000 : fffff805`45c2b3b0 00000000`0000ffff 00000000`00000000 fffff805`61297ea7 : nvlddmkm+0x11f36a
fffff805`45c2b288 fffff805`45c2b3b0 : 00000000`0000ffff 00000000`00000000 fffff805`61297ea7 fffff805`611aabdb : 0xffffba84`c7371000
fffff805`45c2b290 00000000`0000ffff : 00000000`00000000 fffff805`61297ea7 fffff805`611aabdb fffff805`41591400 : 0xfffff805`45c2b3b0
fffff805`45c2b298 00000000`00000000 : fffff805`61297ea7 fffff805`611aabdb fffff805`41591400 00000000`00000000 : 0xffff


SYMBOL_NAME:  nvlddmkm+11f36a

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  11f36a

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
---------

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: fffff80042f73358, 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 checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 5

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-1IBQR0U

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 60

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 71

    Key  : Analysis.System
    Value: CreateObject


ADDITIONAL_XML: 1

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff80042f73358

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
fffff800`4a43ab08 fffff800`42beeac1 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff800`42f73358 : nt!KeBugCheckEx
fffff800`4a43ab10 fffff800`42a1f897 : 000005bc`f7599a25 fffff800`4077a180 00000000`00000286 fffff800`4a433520 : nt!KeAccumulateTicks+0x1cc061
fffff800`4a43ab70 fffff800`429601e1 : 00000000`00000004 fffff800`429cbfe0 fffff800`4a4335a0 fffff800`429cc090 : nt!KeClockInterruptNotify+0xc07
fffff800`4a43af30 fffff800`42a02a25 : fffff800`429cbfe0 00000000`00000000 00000000`00000000 ffff2c76`05ca94f8 : hal!HalpTimerClockIpiRoutine+0x21
fffff800`4a43af60 fffff800`42bc2f7a : fffff800`4a4335a0 fffff800`429cbfe0 00000000`00002100 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff800`4a43afb0 fffff800`42bc34e7 : 00000000`00000000 00000000`00000000 fffff800`42a00000 fffff800`42a33966 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff800`4a433520 fffff800`65450da1 : fffff800`6546a423 ffffcd81`8b115000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff800`4a4336b8 fffff800`6546a423 : ffffcd81`8b115000 00000000`00000000 00000000`00000000 fffff800`656aea40 : nvlddmkm+0x110da1
fffff800`4a4336c0 ffffcd81`8b115000 : 00000000`00000000 00000000`00000000 fffff800`656aea40 ffffcd81`00000020 : nvlddmkm+0x12a423
fffff800`4a4336c8 00000000`00000000 : 00000000`00000000 fffff800`656aea40 ffffcd81`00000020 fffff800`4a433700 : 0xffffcd81`8b115000


SYMBOL_NAME:  nvlddmkm+110da1

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  110da1

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
---------

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: fffff30f17d77860
Arg4: ffffad8b63205bd0

Debugging Details:
------------------

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 4

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-1IBQR0U

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 19

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 72

    Key  : Analysis.System
    Value: CreateObject


ADDITIONAL_XML: 1

BUGCHECK_CODE:  119

BUGCHECK_P1: 2

BUGCHECK_P2: ffffffffc000000d

BUGCHECK_P3: fffff30f17d77860

BUGCHECK_P4: ffffad8b63205bd0

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
fffff30f`17d77788 fffff804`9ca041a0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d fffff30f`17d77860 : nt!KeBugCheckEx
fffff30f`17d77790 fffff804`9e01abf8 : 00000000`00000000 ffffad8b`63203000 fffff30f`17d77899 ffffad8b`63203000 : watchdog!WdLogEvent5_WdCriticalError+0xe0
fffff30f`17d777d0 fffff804`9e078684 : ffffad8b`00000000 ffffad8b`63205bd0 ffffad8b`631bb000 ffffad8b`6328f670 : dxgmms2!VidSchiSendToExecutionQueue+0x14a08
fffff30f`17d77900 fffff804`9e089ad5 : ffffad8b`631a79a0 ffffad8b`49ac1300 00000000`00000000 fffff804`9e089880 : dxgmms2!VidSchiSubmitPagingCommand+0x2f4
fffff30f`17d77a80 fffff804`9e08994a : ffffad8b`631bb400 fffff804`9e089880 ffffad8b`631bb000 00000000`00000000 : dxgmms2!VidSchiRun_PriorityTable+0x175
fffff30f`17d77ad0 fffff804`82f2a7a5 : ffffad8b`631eb680 fffff804`00000001 ffffad8b`631bb000 000025ef`bd9bbfff : dxgmms2!VidSchiWorkerThread+0xca
fffff30f`17d77b10 fffff804`82fc8b2a : ffffbf80`597a5180 ffffad8b`631eb680 fffff804`82f2a750 377401e8`8307e083 : nt!PspSystemThreadStartup+0x55
fffff30f`17d77b60 00000000`00000000 : fffff30f`17d78000 fffff30f`17d71000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a


SYMBOL_NAME:  dxgmms2!VidSchiSendToExecutionQueue+14a08

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

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

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
---------
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 000000000000000d, Attempt to release quota on a corrupted pool allocation.
Arg2: ffff9502d91a9820, Address of pool
Arg3: 00000000ff000000, Pool allocation's tag
Arg4: 1e4f077671c1c3b6, Quota process pointer (bad).

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 2

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-1IBQR0U

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 5

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 68

    Key  : Analysis.System
    Value: CreateObject


ADDITIONAL_XML: 1

BUGCHECK_CODE:  c2

BUGCHECK_P1: d

BUGCHECK_P2: ffff9502d91a9820

BUGCHECK_P3: ff000000

BUGCHECK_P4: 1e4f077671c1c3b6

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  NVDisplay.Container.exe

STACK_TEXT:
ffff820b`bcfb7728 fffff807`349fad21 : 00000000`000000c2 00000000`0000000d ffff9502`d91a9820 00000000`ff000000 : nt!KeBugCheckEx
ffff820b`bcfb7730 fffff807`34b6f0a9 : ffffbe80`1d680180 ffff820b`bcfb79a0 00000000`00000000 01000000`00100000 : nt!ExFreeHeapPool+0x1b51a1
ffff820b`bcfb7850 fffff807`34dd5b4a : ffff9502`d5f646b0 ffff820b`bcfb7a80 00000000`00000000 ffffd982`91cce220 : nt!ExFreePool+0x9
ffff820b`bcfb7880 fffff807`34dfa0e0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SepTokenDeleteMethod+0xda
ffff820b`bcfb78b0 fffff807`348390c4 : 00000000`00000000 00000000`00000000 ffff820b`bcfb7a80 ffff9502`d5f646b0 : nt!ObpRemoveObjectRoutine+0x80
ffff820b`bcfb7910 fffff807`34dc7348 : ffff9502`d8f58d10 ffffd982`ae5dec60 ffffd982`ae5dec60 fffff807`34b70690 : nt!ObfDereferenceObject+0xa4
ffff820b`bcfb7950 fffff807`34dc4199 : ffff820b`bcfb7a80 fffff807`34dc42a9 ffff9502`00000000 ffff820b`00000000 : nt!AlpcSecurityDestroyProcedure+0x38
ffff820b`bcfb7980 fffff807`34dc40ef : ffffd982`ae5dec60 ffff9502`d8f58d10 00000000`00000000 ffff820b`bcfb7a80 : nt!AlpcpDereferenceBlobEx+0x59
ffff820b`bcfb79c0 fffff807`349d2d15 : ffffd982`ac1b3080 00007ffb`075efca4 00000000`00000000 ffffd982`ae5dec60 : nt!NtAlpcDeleteSecurityContext+0xaf
ffff820b`bcfb7a00 00007ffb`08a3d0d4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000039`14fff948 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`08a3d0d4


SYMBOL_NAME:  nt!SepTokenDeleteMethod+da

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.18362.592

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  da

FAILURE_BUCKET_ID:  0xc2_d_nt!SepTokenDeleteMethod

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {8c16cc8d-1bca-c349-5c3a-f63309ab9ee3}

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: ffff928345147860
Arg4: ffff9c81ed644ab0

Debugging Details:
------------------

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 4

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-1IBQR0U

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 23

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 71

    Key  : Analysis.System
    Value: CreateObject


ADDITIONAL_XML: 1

BUGCHECK_CODE:  119

BUGCHECK_P1: 2

BUGCHECK_P2: ffffffffc000000d

BUGCHECK_P3: ffff928345147860

BUGCHECK_P4: ffff9c81ed644ab0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
ffff9283`45147788 fffff800`21b841a0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffff9283`45147860 : nt!KeBugCheckEx
ffff9283`45147790 fffff800`0407abf8 : 00000000`00000000 ffff9c81`ed641000 ffff9c81`ed641000 ffff9c81`ed644ab0 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffff9283`451477d0 fffff800`040d8684 : ffff9c81`00000000 ffff9c81`ed644ab0 ffff9c81`ed5fc000 ffff9c81`f1dc39a0 : dxgmms2!VidSchiSendToExecutionQueue+0x14a08
ffff9283`45147900 fffff800`040e9ad5 : ffff9c81`ed5f29a0 ffff9c81`ed5fc000 00000000`00000000 ffff9c81`f10d8a30 : dxgmms2!VidSchiSubmitPagingCommand+0x2f4
ffff9283`45147a80 fffff800`040e994a : ffff9c81`ed5fc400 fffff800`040e9880 ffff9c81`ed5fc000 00000000`00000000 : dxgmms2!VidSchiRun_PriorityTable+0x175
ffff9283`45147ad0 fffff800`05f2a7a5 : ffff9c81`ed635680 fffff800`00000001 ffff9c81`ed5fc000 000025ef`bd9bbfff : dxgmms2!VidSchiWorkerThread+0xca
ffff9283`45147b10 fffff800`05fc8b2a : ffffb380`f6707180 ffff9c81`ed635680 fffff800`05f2a750 46dcbea2`f22c3951 : nt!PspSystemThreadStartup+0x55
ffff9283`45147b60 00000000`00000000 : ffff9283`45148000 ffff9283`45141000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a


SYMBOL_NAME:  dxgmms2!VidSchiSendToExecutionQueue+14a08

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

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

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
---------

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: fffffb02a89c7860
Arg4: ffffad01b98f4110

Debugging Details:
------------------

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 4

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-1IBQR0U

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 20

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 72

    Key  : Analysis.System
    Value: CreateObject


ADDITIONAL_XML: 1

BUGCHECK_CODE:  119

BUGCHECK_P1: 2

BUGCHECK_P2: ffffffffc000000d

BUGCHECK_P3: fffffb02a89c7860

BUGCHECK_P4: ffffad01b98f4110

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
fffffb02`a89c7788 fffff800`1e0541a0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d fffffb02`a89c7860 : nt!KeBugCheckEx
fffffb02`a89c7790 fffff800`224dabf8 : 00000000`00000000 ffffad01`b98f1000 ffffad01`b98f1000 ffffad01`b98f4110 : watchdog!WdLogEvent5_WdCriticalError+0xe0
fffffb02`a89c77d0 fffff800`22538684 : ffffad01`00000000 ffffad01`b98f4110 ffffad01`b889d000 ffffad01`bcfae7d0 : dxgmms2!VidSchiSendToExecutionQueue+0x14a08
fffffb02`a89c7900 fffff800`22549ad5 : ffffad01`bc66d9a0 ffffad01`b889d000 00000000`00000000 ffffad01`b9d039a0 : dxgmms2!VidSchiSubmitPagingCommand+0x2f4
fffffb02`a89c7a80 fffff800`2254994a : ffffad01`b889d400 fffff800`22549880 ffffad01`b889d000 00000000`00000000 : dxgmms2!VidSchiRun_PriorityTable+0x175
fffffb02`a89c7ad0 fffff800`0332a7a5 : ffffad01`bb124040 fffff800`00000001 ffffad01`b889d000 00000000`00000001 : dxgmms2!VidSchiWorkerThread+0xca
fffffb02`a89c7b10 fffff800`033c8b2a : ffffe780`629a1180 ffffad01`bb124040 fffff800`0332a750 00000000`00000246 : nt!PspSystemThreadStartup+0x55
fffffb02`a89c7b60 00000000`00000000 : fffffb02`a89c8000 fffffb02`a89c1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a


SYMBOL_NAME:  dxgmms2!VidSchiSendToExecutionQueue+14a08

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

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

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: fffff80308173358, 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 checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 5

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-1IBQR0U

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 66

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 71

    Key  : Analysis.System
    Value: CreateObject


ADDITIONAL_XML: 1

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff80308173358

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
fffff803`0c63ab08 fffff803`07deeac1 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff803`08173358 : nt!KeBugCheckEx
fffff803`0c63ab10 fffff803`07c1f897 : 0000007f`8f2ae509 fffff803`0285c180 00000000`00000286 fffff803`0c6333a0 : nt!KeAccumulateTicks+0x1cc061
fffff803`0c63ab70 fffff803`086b91e1 : 00000000`ffffffff fffff803`08724fe0 fffff803`0c633420 fffff803`08725090 : nt!KeClockInterruptNotify+0xc07
fffff803`0c63af30 fffff803`07c02a25 : fffff803`08724fe0 00000000`00000000 00000000`00000000 fffff009`a97d3a89 : hal!HalpTimerClockIpiRoutine+0x21
fffff803`0c63af60 fffff803`07dc2f7a : fffff803`0c633420 fffff803`08724fe0 ffffe60b`0bc0a000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff803`0c63afb0 fffff803`07dc34e7 : 00000000`00000000 fffff803`294d7957 ffffe60b`0bc0b290 fffff803`294c8d07 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff803`0c6333a0 fffff803`294b14c9 : fffff803`294cade3 ffffe60b`0bc0a000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff803`0c633538 fffff803`294cade3 : ffffe60b`0bc0a000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x1114c9
fffff803`0c633540 ffffe60b`0bc0a000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000020 : nvlddmkm+0x12ade3
fffff803`0c633548 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000020 fffff803`0c633580 : 0xffffe60b`0bc0a000


SYMBOL_NAME:  nvlddmkm+1114c9

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1114c9

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
---------
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: ffff8286c9fc7860
Arg4: ffffe007c1cc5810

Debugging Details:
------------------

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 4

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-1IBQR0U

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 20

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 71

    Key  : Analysis.System
    Value: CreateObject


ADDITIONAL_XML: 1

BUGCHECK_CODE:  119

BUGCHECK_P1: 2

BUGCHECK_P2: ffffffffc000000d

BUGCHECK_P3: ffff8286c9fc7860

BUGCHECK_P4: ffffe007c1cc5810

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
ffff8286`c9fc7788 fffff804`2add41a0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffff8286`c9fc7860 : nt!KeBugCheckEx
ffff8286`c9fc7790 fffff804`2e0fabf8 : 00000000`00000000 ffffe007`c1cc2000 ffffe007`c1cc2000 ffffe007`c1cc5810 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffff8286`c9fc77d0 fffff804`2e158684 : ffffe007`00000000 ffffe007`c1cc5810 ffffe007`c1c72000 ffffe007`c3f0f010 : dxgmms2!VidSchiSendToExecutionQueue+0x14a08
ffff8286`c9fc7900 fffff804`2e169ad5 : ffffe007`c1c6b9a0 ffffe007`c1c72000 00000000`00000000 ffffe007`c1d1e260 : dxgmms2!VidSchiSubmitPagingCommand+0x2f4
ffff8286`c9fc7a80 fffff804`2e16994a : ffffe007`c1c72400 fffff804`2e169880 ffffe007`c1c72000 00000000`00000000 : dxgmms2!VidSchiRun_PriorityTable+0x175
ffff8286`c9fc7ad0 fffff804`10b2a7a5 : ffffe007`c1cb6680 fffff804`00000001 ffffe007`c1c72000 000025ef`bd9bbfff : dxgmms2!VidSchiWorkerThread+0xca
ffff8286`c9fc7b10 fffff804`10bc8b2a : fffff804`0a918180 ffffe007`c1cb6680 fffff804`10b2a750 4c402464`894c4824 : nt!PspSystemThreadStartup+0x55
ffff8286`c9fc7b60 00000000`00000000 : ffff8286`c9fc8000 ffff8286`c9fc1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a


SYMBOL_NAME:  dxgmms2!VidSchiSendToExecutionQueue+14a08

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

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

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
---------

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: fffff30ea71af860
Arg4: ffffcf89295973b0

Debugging Details:
------------------

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 5

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-1IBQR0U

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 18

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 72

    Key  : Analysis.System
    Value: CreateObject


ADDITIONAL_XML: 1

BUGCHECK_CODE:  119

BUGCHECK_P1: 2

BUGCHECK_P2: ffffffffc000000d

BUGCHECK_P3: fffff30ea71af860

BUGCHECK_P4: ffffcf89295973b0

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
fffff30e`a71af788 fffff806`656241a0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d fffff30e`a71af860 : nt!KeBugCheckEx
fffff30e`a71af790 fffff806`6674abf8 : 00000000`00000000 ffffcf89`29594000 fffff30e`a71af899 ffffcf89`29594000 : watchdog!WdLogEvent5_WdCriticalError+0xe0
fffff30e`a71af7d0 fffff806`667a8684 : ffffcf89`00000000 ffffcf89`295973b0 ffffcf89`2954f000 ffffcf89`2e074930 : dxgmms2!VidSchiSendToExecutionQueue+0x14a08
fffff30e`a71af900 fffff806`667b9ad5 : ffffcf89`2954c9a0 ffffcf89`2954f000 00000000`00000000 ffffcf89`2955f360 : dxgmms2!VidSchiSubmitPagingCommand+0x2f4
fffff30e`a71afa80 fffff806`667b994a : ffffcf89`2954f400 fffff806`667b9880 ffffcf89`2954f000 00000000`00000000 : dxgmms2!VidSchiRun_PriorityTable+0x175
fffff30e`a71afad0 fffff806`4b92a7a5 : ffffcf89`29593680 fffff806`00000001 ffffcf89`2954f000 000025ef`bd9bbfff : dxgmms2!VidSchiWorkerThread+0xca
fffff30e`a71afb10 fffff806`4b9c8b2a : fffff806`47530180 ffffcf89`29593680 fffff806`4b92a750 f17f1be6`483d2778 : nt!PspSystemThreadStartup+0x55
fffff30e`a71afb60 00000000`00000000 : fffff30e`a71b0000 fffff30e`a71a9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a


SYMBOL_NAME:  dxgmms2!VidSchiSendToExecutionQueue+14a08

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

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

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
---------

NEXPECTED_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: fffff8016de43e50
Arg3: fffff8016de24f70
Arg4: fffff80167c3272b

Debugging Details:
------------------

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 3

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-1IBQR0U

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 7

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 81

    Key  : Analysis.System
    Value: CreateObject


ADDITIONAL_XML: 1

BUGCHECK_CODE:  7f

BUGCHECK_P1: 8

BUGCHECK_P2: fffff8016de43e50

BUGCHECK_P3: fffff8016de24f70

BUGCHECK_P4: fffff80167c3272b

TRAP_FRAME:  fffff8016de43e50 -- (.trap 0xfffff8016de43e50)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000200
rdx=0000000000000200 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80167c3272b rsp=fffff8016de24f70 rbp=fffff8016de25070
r8=0000000073556f49  r9=0000000000000000 r10=fffff80167d28990
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!ExAllocateHeapPool+0x2b:
fffff801`67c3272b 4889742440      mov     qword ptr [rsp+40h],rsi ss:0018:fffff801`6de24fb0=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_OVERFLOW: Stack Limit: fffff8016de25000. Use (kF) and (!stackusage) to investigate stack usage.

STACK_TEXT:
fffff801`6de43d08 fffff801`67dd32e9 : 00000000`0000007f 00000000`00000008 fffff801`6de43e50 fffff801`6de24f70 : nt!KeBugCheckEx
fffff801`6de43d10 fffff801`67dce145 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff801`6de43e50 fffff801`67c3272b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0x2c5
fffff801`6de24f70 fffff801`67f6f06d : ffffffff`ffffffff fffff801`6de251b0 00000000`00000000 00000000`00000020 : nt!ExAllocateHeapPool+0x2b
fffff801`6de250b0 fffff801`67d289e1 : ffffe607`a1309001 ffffe607`87299dc0 fffff801`6b718601 00000000`00000000 : nt!ExAllocatePoolWithTag+0x5d
fffff801`6de25100 fffff801`6b70ad71 : ffffe607`a1309010 ffffe607`a1309010 fffff801`6b718670 ffffe607`87299dc0 : nt!IoSetCompletionRoutineEx+0x51
fffff801`6de25140 fffff801`67c31f79 : ffffe607`a1309010 ffffe607`870eae10 00000034`00000000 00000000`00000000 : Wdf01000!FxDevice::DispatchWithLock+0x2b1 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1391]
fffff801`6de251a0 fffff801`6b8814ad : ffffe607`870eae10 ffffe607`a1309010 00000000`00000000 ffffffff`ffffffff : nt!IofCallDriver+0x59
fffff801`6de251e0 fffff801`6b8810d8 : ffffe607`847b3bc0 00000000`00000007 ffffe607`a1309560 00000000`00000000 : ACPI!ACPIIrpDispatchDeviceControl+0xad
fffff801`6de25220 fffff801`67c31f79 : 00000000`00000007 ffffe607`a1309010 00000000`00000000 ffffe607`870f1cb0 : ACPI!ACPIDispatchIrp+0xc8
fffff801`6de252a0 fffff801`87d00b2a : 00000000`00000000 00000040`00000000 fffff801`6bf8b008 00000000`00000020 : nt!IofCallDriver+0x59
fffff801`6de252e0 00000000`00000000 : 00000040`00000000 fffff801`6bf8b008 00000000`00000020 00000000`00000000 : jmccgp+0xb2a


SYMBOL_NAME:  jmccgp+b2a

MODULE_NAME: jmccgp

IMAGE_NAME:  jmccgp.sys

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  b2a

FAILURE_BUCKET_ID:  0x7f_8_jmccgp!unknown_function

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {7db9fe2b-55a5-6389-f51e-c587e2646ef4}

Followup:     MachineOwner
---------

0: kd> lmvm jmccgp
Browse full module list
start             end                 module name
fffff801`87d00000 fffff801`87d02880   jmccgp   T (no symbols)          
    Loaded symbol image file: jmccgp.sys
    Image path: \SystemRoot\system32\DRIVERS\jmccgp.sys
    Image name: jmccgp.sys
    Browse all global symbols  functions  data
    Timestamp:        Tue Jul 28 15:26:44 2009 (4A6EEE84)
    CheckSum:         000114D2
    ImageSize:        00002880
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:
 
Artı 0 Eksi
Ekran kartını DDU ile temizle tekrar yükle sonuç aynı ise donanım arıza olabilir, ayrıca kamera sürücüsü de bir kere çökmüş, onuda kaldır tekrar yükle.
BIOS güncellemesi yap.

laptops and netbooks :: 300 series :: 320 15ikb - Lenovo Support US

pcsupport.lenovo.com
Kod: 
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: fffff8016de43e50
Arg3: fffff8016de24f70
Arg4: fffff80167c3272b

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for jmccgp.sys
*** WARNING: Unable to verify timestamp for win32k.sys

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:  18362.1.amd64fre.19h1_release.190318-1202

DUMP_TYPE:  2

BUGCHECK_P1: 8

BUGCHECK_P2: fffff8016de43e50

BUGCHECK_P3: fffff8016de24f70

BUGCHECK_P4: fffff80167c3272b

BUGCHECK_STR:  0x7f_8

TRAP_FRAME:  fffff8016de43e50 -- (.trap 0xfffff8016de43e50)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000200
rdx=0000000000000200 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80167c3272b rsp=fffff8016de24f70 rbp=fffff8016de25070
r8=0000000073556f49  r9=0000000000000000 r10=fffff80167d28990
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!ExAllocateHeapPool+0x2b:
fffff801`67c3272b 4889742440      mov     qword ptr [rsp+40h],rsi ss:0018:fffff801`6de24fb0=????????????????
Resetting default scope

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

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  01-28-2020 16:35:36.0722

ANALYSIS_VERSION: 10.0.18362.1 x86fre

STACK_OVERFLOW: Stack Limit: fffff8016de25000. Use (kF) and (!stackusage) to investigate stack usage.

LAST_CONTROL_TRANSFER:  from fffff80167dd32e9 to fffff80167dc14e0

STACK_TEXT:
fffff801`6de43d08 fffff801`67dd32e9 : 00000000`0000007f 00000000`00000008 fffff801`6de43e50 fffff801`6de24f70 : nt!KeBugCheckEx
fffff801`6de43d10 fffff801`67dce145 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff801`6de43e50 fffff801`67c3272b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0x2c5
fffff801`6de24f70 fffff801`67f6f06d : ffffffff`ffffffff fffff801`6de251b0 00000000`00000000 00000000`00000020 : nt!ExAllocateHeapPool+0x2b
fffff801`6de250b0 fffff801`67d289e1 : ffffe607`a1309001 ffffe607`87299dc0 fffff801`6b718601 00000000`00000000 : nt!ExAllocatePoolWithTag+0x5d
fffff801`6de25100 fffff801`6b70ad71 : ffffe607`a1309010 ffffe607`a1309010 fffff801`6b718670 ffffe607`87299dc0 : nt!IoSetCompletionRoutineEx+0x51
fffff801`6de25140 fffff801`67c31f79 : ffffe607`a1309010 ffffe607`870eae10 00000034`00000000 00000000`00000000 : Wdf01000!FxDevice::DispatchWithLock+0x2b1 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1391]
fffff801`6de251a0 fffff801`6b8814ad : ffffe607`870eae10 ffffe607`a1309010 00000000`00000000 ffffffff`ffffffff : nt!IofCallDriver+0x59
fffff801`6de251e0 fffff801`6b8810d8 : ffffe607`847b3bc0 00000000`00000007 ffffe607`a1309560 00000000`00000000 : ACPI!ACPIIrpDispatchDeviceControl+0xad
fffff801`6de25220 fffff801`67c31f79 : 00000000`00000007 ffffe607`a1309010 00000000`00000000 ffffe607`870f1cb0 : ACPI!ACPIDispatchIrp+0xc8
fffff801`6de252a0 fffff801`87d00b2a : 00000000`00000000 00000040`00000000 fffff801`6bf8b008 00000000`00000020 : nt!IofCallDriver+0x59
fffff801`6de252e0 00000000`00000000 : 00000040`00000000 fffff801`6bf8b008 00000000`00000020 00000000`00000000 : jmccgp+0xb2a


THREAD_SHA1_HASH_MOD_FUNC:  1655be58d712fdb80ed285a2fcee20ee6a3334cd

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  e65770be7787a6b485255eb8e4a730f156f5828b

THREAD_SHA1_HASH_MOD:  09190735ce5a4ab5f32d5cd347cc0851b035ed05

FOLLOWUP_IP:
jmccgp+b2a
fffff801`87d00b2a 488d8ec0010000  lea     rcx,[rsi+1C0h]

FAULT_INSTR_CODE:  c08e8d48

SYMBOL_STACK_INDEX:  b

SYMBOL_NAME:  jmccgp+b2a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: jmccgp

IMAGE_NAME:  jmccgp.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a6eee84

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  b2a

FAILURE_BUCKET_ID:  0x7f_8_jmccgp!unknown_function

BUCKET_ID:  0x7f_8_jmccgp!unknown_function

PRIMARY_PROBLEM_CLASS:  0x7f_8_jmccgp!unknown_function

TARGET_TIME:  2019-11-25T16:27:04.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:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  395d

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x7f_8_jmccgp!unknown_function

FAILURE_ID_HASH:  {7db9fe2b-55a5-6389-f51e-c587e2646ef4}

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: ffff928345147860
Arg4: ffff9c81ed644ab0

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for win32k.sys

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:  18362.1.amd64fre.19h1_release.190318-1202

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:  4WCN43WW

BIOS_DATE:  12/22/2018

BASEBOARD_MANUFACTURER:  LENOVO

BASEBOARD_PRODUCT:  LNVNB161216

BASEBOARD_VERSION:  SDK0J40679 WIN

DUMP_TYPE:  2

BUGCHECK_P1: 2

BUGCHECK_P2: ffffffffc000000d

BUGCHECK_P3: ffff928345147860

BUGCHECK_P4: ffff9c81ed644ab0

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:  0x119

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  01-28-2020 16:36:21.0649

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from fffff80021b841a0 to fffff80005fc14e0

STACK_TEXT:
ffff9283`45147788 fffff800`21b841a0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffff9283`45147860 : nt!KeBugCheckEx
ffff9283`45147790 fffff800`0407abf8 : 00000000`00000000 ffff9c81`ed641000 ffff9c81`ed641000 ffff9c81`ed644ab0 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffff9283`451477d0 fffff800`040d8684 : ffff9c81`00000000 ffff9c81`ed644ab0 ffff9c81`ed5fc000 ffff9c81`f1dc39a0 : dxgmms2!VidSchiSendToExecutionQueue+0x14a08
ffff9283`45147900 fffff800`040e9ad5 : ffff9c81`ed5f29a0 ffff9c81`ed5fc000 00000000`00000000 ffff9c81`f10d8a30 : dxgmms2!VidSchiSubmitPagingCommand+0x2f4
ffff9283`45147a80 fffff800`040e994a : ffff9c81`ed5fc400 fffff800`040e9880 ffff9c81`ed5fc000 00000000`00000000 : dxgmms2!VidSchiRun_PriorityTable+0x175
ffff9283`45147ad0 fffff800`05f2a7a5 : ffff9c81`ed635680 fffff800`00000001 ffff9c81`ed5fc000 000025ef`bd9bbfff : dxgmms2!VidSchiWorkerThread+0xca
ffff9283`45147b10 fffff800`05fc8b2a : ffffb380`f6707180 ffff9c81`ed635680 fffff800`05f2a750 46dcbea2`f22c3951 : nt!PspSystemThreadStartup+0x55
ffff9283`45147b60 00000000`00000000 : ffff9283`45148000 ffff9283`45141000 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
fffff800`0407abf8 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:  2020-01-27T18:05:05.000Z

OSBUILD:  18362

OSSERVICEPACK:  592

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:  1972-08-22 03:24:00

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  8405

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
---------
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 000000000000000d, Attempt to release quota on a corrupted pool allocation.
Arg2: ffff9502d91a9820, Address of pool
Arg3: 00000000ff000000, Pool allocation's tag
Arg4: 1e4f077671c1c3b6, Quota process pointer (bad).

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:  18362.1.amd64fre.19h1_release.190318-1202

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:  4WCN43WW

BIOS_DATE:  12/22/2018

BASEBOARD_MANUFACTURER:  LENOVO

BASEBOARD_PRODUCT:  LNVNB161216

BASEBOARD_VERSION:  SDK0J40679 WIN

DUMP_TYPE:  2

BUGCHECK_P1: d

BUGCHECK_P2: ffff9502d91a9820

BUGCHECK_P3: ff000000

BUGCHECK_P4: 1e4f077671c1c3b6

FAULTING_IP:
nt!SepTokenDeleteMethod+da
fffff807`34dd5b4a 4883bb1803000000 cmp     qword ptr [rbx+318h],0

BUGCHECK_STR:  0xc2_d

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)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  NVDisplay.Container.exe

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  01-28-2020 16:35:41.0512

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from fffff807349fad21 to fffff807349c14e0

STACK_TEXT:
ffff820b`bcfb7728 fffff807`349fad21 : 00000000`000000c2 00000000`0000000d ffff9502`d91a9820 00000000`ff000000 : nt!KeBugCheckEx
ffff820b`bcfb7730 fffff807`34b6f0a9 : ffffbe80`1d680180 ffff820b`bcfb79a0 00000000`00000000 01000000`00100000 : nt!ExFreeHeapPool+0x1b51a1
ffff820b`bcfb7850 fffff807`34dd5b4a : ffff9502`d5f646b0 ffff820b`bcfb7a80 00000000`00000000 ffffd982`91cce220 : nt!ExFreePool+0x9
ffff820b`bcfb7880 fffff807`34dfa0e0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SepTokenDeleteMethod+0xda
ffff820b`bcfb78b0 fffff807`348390c4 : 00000000`00000000 00000000`00000000 ffff820b`bcfb7a80 ffff9502`d5f646b0 : nt!ObpRemoveObjectRoutine+0x80
ffff820b`bcfb7910 fffff807`34dc7348 : ffff9502`d8f58d10 ffffd982`ae5dec60 ffffd982`ae5dec60 fffff807`34b70690 : nt!ObfDereferenceObject+0xa4
ffff820b`bcfb7950 fffff807`34dc4199 : ffff820b`bcfb7a80 fffff807`34dc42a9 ffff9502`00000000 ffff820b`00000000 : nt!AlpcSecurityDestroyProcedure+0x38
ffff820b`bcfb7980 fffff807`34dc40ef : ffffd982`ae5dec60 ffff9502`d8f58d10 00000000`00000000 ffff820b`bcfb7a80 : nt!AlpcpDereferenceBlobEx+0x59
ffff820b`bcfb79c0 fffff807`349d2d15 : ffffd982`ac1b3080 00007ffb`075efca4 00000000`00000000 ffffd982`ae5dec60 : nt!NtAlpcDeleteSecurityContext+0xaf
ffff820b`bcfb7a00 00007ffb`08a3d0d4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000039`14fff948 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`08a3d0d4


THREAD_SHA1_HASH_MOD_FUNC:  eca4d9e87dcb92e7532a2496c29c4b6c69206cd5

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  958aa60fbb3ade1ccd958dbf27d53821aaa20736

THREAD_SHA1_HASH_MOD:  bc100a5647b828107ac4e18055e00abcbe1ec406

FOLLOWUP_IP:
nt!SepTokenDeleteMethod+da
fffff807`34dd5b4a 4883bb1803000000 cmp     qword ptr [rbx+318h],0

FAULT_INSTR_CODE:  18bb8348

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!SepTokenDeleteMethod+da

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4f6eba0

IMAGE_VERSION:  10.0.18362.592

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  da

FAILURE_BUCKET_ID:  0xc2_d_nt!SepTokenDeleteMethod

BUCKET_ID:  0xc2_d_nt!SepTokenDeleteMethod

PRIMARY_PROBLEM_CLASS:  0xc2_d_nt!SepTokenDeleteMethod

TARGET_TIME:  2020-01-28T11:52:22.000Z

OSBUILD:  18362

OSSERVICEPACK:  592

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:  1972-08-22 03:24:00

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  a66

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xc2_d_nt!septokendeletemethod

FAILURE_ID_HASH:  {8c16cc8d-1bca-c349-5c3a-f63309ab9ee3}

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: fffff80541573358, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding the cumulative timeout
Arg4: 0000000000000000

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************
*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

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:  4WCN43WW

BIOS_DATE:  12/22/2018

BASEBOARD_MANUFACTURER:  LENOVO

BASEBOARD_PRODUCT:  LNVNB161216

BASEBOARD_VERSION:  SDK0J40679 WIN

DUMP_TYPE:  2

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff80541573358

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)


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:  01-28-2020 16:36:10.0099

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from fffff805411eeac1 to fffff805411c14e0

STACK_TEXT:
fffff805`45c3ab08 fffff805`411eeac1 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff805`41573358 : nt!KeBugCheckEx
fffff805`45c3ab10 fffff805`4101f61c : 0000014d`d1e54d07 fffff805`3be4d180 00000000`0000820f 00000000`0000820f : nt!KeAccumulateTicks+0x1cc061
fffff805`45c3ab70 fffff805`41ab74b7 : fffff805`41591400 fffff805`45c2a920 fffff805`45c2a9a0 00000000`00000002 : nt!KeClockInterruptNotify+0x98c
fffff805`45c3af30 fffff805`41002a25 : 00000001`362d563b fffff805`41b250e0 fffff805`41b25190 ffff123d`12025c06 : hal!HalpTimerClockInterrupt+0xf7
fffff805`45c3af60 fffff805`411c2f7a : fffff805`45c2a9a0 fffff805`41b250e0 00000000`00000005 00000000`00002100 : nt!KiCallInterruptServiceRoutine+0xa5
fffff805`45c3afb0 fffff805`411c34e7 : fffff805`4158c360 fffff805`41ab92cb fffff805`6194a000 fffff805`61090000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff805`45c2a920 fffff805`410c606e : fffff805`611af36a 00000000`00000008 ffffffff`00000001 fffff805`000001c4 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff805`45c2aab0 fffff805`410c382b : 00000000`00000000 fffff805`45c2ac48 00000000`00000000 00000000`00000000 : nt!RtlpLookupFunctionEntryForStackWalks+0xae
fffff805`45c2ab30 fffff805`410e21d2 : fffff805`45c25000 00000000`00000000 00000000`00000001 ffffba84`c86f2000 : nt!RtlpWalkFrameChain+0x25b
fffff805`45c2b220 fffff805`410e2122 : 00000000`00000003 fffff805`45c2b2b8 00000000`00000000 00000000`00000001 : nt!RtlWalkFrameChain+0x72
fffff805`45c2b250 fffff805`611af36a : ffffba84`c7371000 fffff805`45c2b3b0 00000000`0000ffff 00000000`00000000 : nt!RtlCaptureStackBackTrace+0x42
fffff805`45c2b280 ffffba84`c7371000 : fffff805`45c2b3b0 00000000`0000ffff 00000000`00000000 fffff805`61297ea7 : nvlddmkm+0x11f36a
fffff805`45c2b288 fffff805`45c2b3b0 : 00000000`0000ffff 00000000`00000000 fffff805`61297ea7 fffff805`611aabdb : 0xffffba84`c7371000
fffff805`45c2b290 00000000`0000ffff : 00000000`00000000 fffff805`61297ea7 fffff805`611aabdb fffff805`41591400 : 0xfffff805`45c2b3b0
fffff805`45c2b298 00000000`00000000 : fffff805`61297ea7 fffff805`611aabdb fffff805`41591400 00000000`00000000 : 0xffff


THREAD_SHA1_HASH_MOD_FUNC:  d4af88e456d39851b8acb6b6d3fa86a9be9a6100

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  05dccafe38221d04cc8e177f63996c9dc2eb33af

THREAD_SHA1_HASH_MOD:  2dcfc882ef7a9a16810a28e5db3852284c3a14c5

FOLLOWUP_IP:
nvlddmkm+11f36a
fffff805`611af36a 488b442438      mov     rax,qword ptr [rsp+38h]

FAULT_INSTR_CODE:  24448b48

SYMBOL_STACK_INDEX:  b

SYMBOL_NAME:  nvlddmkm+11f36a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5db15c63

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  11f36a

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:  2020-01-27T18:58:49.000Z

OSBUILD:  18362

OSSERVICEPACK:  592

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:  1972-08-22 03:24:00

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  12ff4

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x133_isr_nvlddmkm!unknown_function

FAILURE_ID_HASH:  {f97493a5-ea2b-23ca-a808-8602773c2a86}

Followup:     MachineOwner
---------
 
Artı 0 Eksi
Teşekkürler söylediklerinizi deneyeceğim. Bana da donanımsal bir problemmiş gibi geliyor. Servise götürebilirim.
 
Artı 0 Eksi
Mesaj yazmak için giriş yapmalı ya da kaydolmalısınız.

Benzer konular

  • Soru
''Video Scheduler Internal Error'' mavi ekran hatası
Mesaj
0
Görüntüleme
721
cme227
  • Soru
VIDEO SCHEDULER INTERNAL ERROR mavi ekran hatası
Mesaj
3
Görüntüleme
1.419
attila 123
B
  • Soru
"Video Scheduler Internal Error" Mavi ekran Hatası
Mesaj
3
Görüntüleme
1.687
patuaid
  • Soru
'Video Scheduler Internal Error' Mavi ekran hatası
2
Mesaj
17
Görüntüleme
4.631
cmakyzz
  • Soru
Video Scheduler Internal Error Mavi Ekran Hatası
Mesaj
4
Görüntüleme
990
Mr.Peanutbetter
Menü
Giriş yap
Kaydol
Bu siteyi kullanmak için çerezler gereklidir. Siteyi kullanmaya devam etmek için çerezleri kabul etmelisiniz. Daha Fazlasını Öğren.…