Windows 10 mavi ekran hatası

Windows 10 20H2 sürümüne geçin.

DDU ile ekran kartı sürücüsünü kaldırıp yeniden kurun.

Aşağıdaki rehberi uygulayın.

Hata almaya devam ederseniz dosyaları paylaşın.

[CODE title="Kod"]
Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\maksu\Downloads\Compressed\Minidump\011121-50875-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff803`63400000 PsLoadedModuleList = 0xfffff803`638461b0
Debug session time: Mon Jan 11 18:04:24.290 2021 (UTC + 3:00)
System Uptime: 0 days 0:11:36.044
Loading Kernel Symbols
...............................................................
................................................................
..............................................................
Loading User Symbols
Loading unloaded module list
..........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`635c3b20 48894c2408 mov qword ptr [rsp+8],rcx ss:fffff803`67073bd0=000000000000009f
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe0051e108060, Physical Device Object of the stack
Arg3: fffff80367073c00, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe0051fb9db20, The blocked IRP

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 7406

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

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 34098

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: 9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffe0051e108060

BUGCHECK_P3: fffff80367073c00

BUGCHECK_P4: ffffe0051fb9db20

DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: pci.sys

MODULE_NAME: pci

FAULTING_MODULE: fffff80365e40000 pci

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

DPC_STACK_BASE: FFFFF80367073FB0

STACK_TEXT:
fffff803`67073bc8 fffff803`636edc57 : 00000000`0000009f 00000000`00000003 ffffe005`1e108060 fffff803`67073c00 : nt!KeBugCheckEx
fffff803`67073bd0 fffff803`636edb61 : ffffe005`20998538 ffffe005`1a4a3000 fffff803`5f59b100 fffff803`5f59b180 : nt!PopIrpWatchdogBugcheck+0xef
fffff803`67073c40 fffff803`634c3559 : ffffe005`20998570 fffff803`6af87580 1a5f800f`00000003 00000001`9edf2c62 : nt!PopIrpWatchdog+0x31
fffff803`67073c90 fffff803`634c22b9 : 00000000`00000018 00000000`00989680 00000000`000067b7 00000000`000000cf : nt!KiProcessExpiredTimerList+0x169
fffff803`67073d80 fffff803`635cab25 : 00000000`00000000 fffff803`5f59b180 fffff803`63f25100 fffff803`6bb646f8 : nt!KiRetireDpcList+0x4e9
fffff803`67073fb0 fffff803`635ca910 : fffff803`63eceb20 fffff803`63eb837a 00000000`00000000 fffff803`635ca1c5 : nt!KxRetireDpcList+0x5
ffffa18b`b69f0200 fffff803`635ca1c5 : fffff803`6bb646f8 fffff803`635c5b91 00000000`0000000a ffffa18b`b69f02c0 : nt!KiDispatchInterruptContinue
ffffa18b`b69f0230 fffff803`635c5b91 : 00000000`0000000a ffffa18b`b69f02c0 fffff803`63f25100 fffff803`63eb837a : nt!KiDpcInterruptBypass+0x25
ffffa18b`b69f0240 fffff803`634182e5 : fffff803`6bd2023c ffffa18b`b69f04e8 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0xb1
ffffa18b`b69f03d0 fffff803`634172a2 : ffffa18b`b69ec000 00000000`00000000 00000000`00000001 fffff803`634c300d : nt!RtlpWalkFrameChain+0x435
ffffa18b`b69f0ac0 fffff803`634171b2 : 00000000`00000009 ffffa18b`b69f0b58 00000000`00000000 00000000`00000001 : nt!RtlWalkFrameChain+0x72
ffffa18b`b69f0af0 fffff803`6b58bba2 : ffffe005`1e0628a0 ffffa18b`b69f0c50 ffffe005`205aa000 00000000`00000001 : nt!RtlCaptureStackBackTrace+0x42
ffffa18b`b69f0b20 ffffe005`1e0628a0 : ffffa18b`b69f0c50 ffffe005`205aa000 00000000`00000001 ffffe005`205aa000 : nvlddmkm+0x1dbba2
ffffa18b`b69f0b28 ffffa18b`b69f0c50 : ffffe005`205aa000 00000000`00000001 ffffe005`205aa000 fffff803`6b57043d : 0xffffe005`1e0628a0
ffffa18b`b69f0b30 ffffe005`205aa000 : 00000000`00000001 ffffe005`205aa000 fffff803`6b57043d ffffe005`1ae19040 : 0xffffa18b`b69f0c50
ffffa18b`b69f0b38 00000000`00000001 : ffffe005`205aa000 fffff803`6b57043d ffffe005`1ae19040 00000000`00000000 : 0xffffe005`205aa000
ffffa18b`b69f0b40 ffffe005`205aa000 : fffff803`6b57043d ffffe005`1ae19040 00000000`00000000 ffffe005`205aa000 : 0x1
ffffa18b`b69f0b48 fffff803`6b57043d : ffffe005`1ae19040 00000000`00000000 ffffe005`205aa000 ffffa18b`b69f0c28 : 0xffffe005`205aa000
ffffa18b`b69f0b50 ffffe005`1ae19040 : 00000000`00000000 ffffe005`205aa000 ffffa18b`b69f0c28 ffffe005`00000001 : nvlddmkm+0x1c043d
ffffa18b`b69f0b58 00000000`00000000 : ffffe005`205aa000 ffffa18b`b69f0c28 ffffe005`00000001 ffffa18b`b69f0bb4 : 0xffffe005`1ae19040


IMAGE_VERSION: 10.0.18362.1085

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x9F_3_nvlddmkm_IMAGE_pci.sys

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {a47222af-fbac-bc49-47e0-2cf5d31cc673}

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


Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\maksu\Downloads\Compressed\Minidump\010221-56578-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff802`16000000 PsLoadedModuleList = 0xfffff802`164461b0
Debug session time: Sat Jan 2 19:25:37.441 2021 (UTC + 3:00)
System Uptime: 0 days 4:08:10.194
Loading Kernel Symbols
...............................................................
................................................................
...............................................................
Loading User Symbols
Loading unloaded module list
.............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`161c3b20 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff802`1c26c880=000000000000009f
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffc10d0c307060, Physical Device Object of the stack
Arg3: fffff8021c26c8b0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffc10d0dc1e9a0, The blocked IRP

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

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nvpmi.inf_amd64_14da220f3c8d2e26\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: 6546

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

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 14520

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: 9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffc10d0c307060

BUGCHECK_P3: fffff8021c26c8b0

BUGCHECK_P4: ffffc10d0dc1e9a0

DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: pci.sys

MODULE_NAME: pci

FAULTING_MODULE: fffff8021b040000 pci

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff802`1c26c878 fffff802`162edc57 : 00000000`0000009f 00000000`00000003 ffffc10d`0c307060 fffff802`1c26c8b0 : nt!KeBugCheckEx
fffff802`1c26c880 fffff802`162edb61 : ffffc10d`0ea33538 ffffc10d`11c06250 fffff802`14732100 fffff802`14732180 : nt!PopIrpWatchdogBugcheck+0xef
fffff802`1c26c8f0 fffff802`160c3559 : ffffc10d`0ea33570 00000000`00000080 00000000`00000004 ffffc10d`00000002 : nt!PopIrpWatchdog+0x31
fffff802`1c26c940 fffff802`160c22b9 : 00000000`00000018 00000000`00989680 00000000`0008aacf 00000000`000000e7 : nt!KiProcessExpiredTimerList+0x169
fffff802`1c26ca30 fffff802`161c764e : 00000000`00000000 fffff802`14732180 fffff802`1658f400 ffffc10d`12b62080 : nt!KiRetireDpcList+0x4e9
fffff802`1c26cc60 00000000`00000000 : fffff802`1c26d000 fffff802`1c267000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x7e


IMAGE_VERSION: 10.0.18362.1085

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x9F_3_nvlddmkm_IMAGE_pci.sys

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {a47222af-fbac-bc49-47e0-2cf5d31cc673}

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

Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\maksu\Downloads\Compressed\Minidump\011121-48828-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff803`1e800000 PsLoadedModuleList = 0xfffff803`1ec461b0
Debug session time: Mon Jan 11 19:07:13.054 2021 (UTC + 3:00)
System Uptime: 0 days 0:20:55.808
Loading Kernel Symbols
...............................................................
................................................................
..............................................................
Loading User Symbols
Loading unloaded module list
............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`1e9c3b20 48894c2408 mov qword ptr [rsp+8],rcx ss:fffff803`24472b20=0000000000000119
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000005, The subtype of the bugcheck:
Arg2: ffffe28260355000
Arg3: ffffe28260d8b5e0
Arg4: 0000000000003705

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 9436

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

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 81914

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

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

BUGCHECK_P2: ffffe28260355000

BUGCHECK_P3: ffffe28260d8b5e0

BUGCHECK_P4: 3705

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: League of Legends.exe

DPC_STACK_BASE: FFFFF80324473FB0

STACK_TEXT:
fffff803`24472b18 fffff803`26664210 : 00000000`00000119 00000000`00000005 ffffe282`60355000 ffffe282`60d8b5e0 : nt!KeBugCheckEx
fffff803`24472b20 fffff803`1d77f1b2 : ffffe282`619e3000 ffffe282`60355000 0004ddd8`0110d000 00000000`00000000 : watchdog!WdLogEvent5_WdCriticalError+0xe0
fffff803`24472b60 fffff803`1d76dbea : ffffe282`6198f000 ffffe282`60355000 fffff803`24472e20 fffff803`1d76ddf3 : dxgmms2!VidSchiProcessIsrFaultedPacket+0x26a
fffff803`24472be0 fffff803`1d75b421 : ffffe282`00003705 fffff803`24472d99 ffffe282`6198f000 00020000`00950000 : dxgmms2!VidSchDdiNotifyInterruptWorker+0x1278a
fffff803`24472c40 fffff803`262f3d33 : ffffe282`5fd0d030 00020000`00950000 fffff803`284220ec 00000000`00000000 : dxgmms2!VidSchDdiNotifyInterrupt+0xd1
fffff803`24472c90 fffff803`2844ac1f : ffffe282`5fd0d030 fffff803`24472d99 fffff803`24472e20 ffffe282`5fde2000 : dxgkrnl!DxgNotifyInterruptCB+0x93
fffff803`24472cc0 ffffe282`5fd0d030 : fffff803`24472d99 fffff803`24472e20 ffffe282`5fde2000 fffff803`2844abaf : nvlddmkm+0x11ac1f
fffff803`24472cc8 fffff803`24472d99 : fffff803`24472e20 ffffe282`5fde2000 fffff803`2844abaf ffffe282`5fde2000 : 0xffffe282`5fd0d030
fffff803`24472cd0 fffff803`24472e20 : ffffe282`5fde2000 fffff803`2844abaf ffffe282`5fde2000 00000000`00000000 : 0xfffff803`24472d99
fffff803`24472cd8 ffffe282`5fde2000 : fffff803`2844abaf ffffe282`5fde2000 00000000`00000000 00000000`00000000 : 0xfffff803`24472e20
fffff803`24472ce0 fffff803`2844abaf : ffffe282`5fde2000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffe282`5fde2000
fffff803`24472ce8 ffffe282`5fde2000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x11abaf
fffff803`24472cf0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffe282`5fd0d030 : 0xffffe282`5fde2000


SYMBOL_NAME: nvlddmkm+11ac1f

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 11ac1f

FAILURE_BUCKET_ID: 0x119_5_DRIVER_FAULTED_SYSTEM_COMMAND_nvlddmkm!unknown_function

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {55a61c3c-91b1-e527-dcff-f2f0d7348227}

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

Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\maksu\Downloads\Compressed\Minidump\011121-52312-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff801`0ea00000 PsLoadedModuleList = 0xfffff801`0ee461b0
Debug session time: Mon Jan 11 18:44:52.496 2021 (UTC + 3:00)
System Uptime: 0 days 0:39:29.249
Loading Kernel Symbols
...............................................................
................................................................
...............................................................
Loading User Symbols
Loading unloaded module list
.................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`0ebc3b20 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffb98b`566ed890=0000000000000119
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000002, The driver failed upon the submission of a command.
Arg2: ffffffffc000000d
Arg3: ffffb98b566ed960
Arg4: ffffd30fbf66b2d0

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 5312

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

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 24350

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

BUGCHECK_P4: ffffd30fbf66b2d0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffb98b`566ed888 fffff801`13784210 : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffffb98b`566ed960 : nt!KeBugCheckEx
ffffb98b`566ed890 fffff801`156aaf38 : 00000000`00000000 ffffd30f`bf668000 ffffd30f`bf668000 ffffd30f`bf66b2d0 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffffb98b`566ed8d0 fffff801`15708d54 : ffffd30f`00000000 ffffd30f`bf66b2d0 ffffd30f`c3396000 ffffd30f`c0a86500 : dxgmms2!VidSchiSendToExecutionQueue+0x14d48
ffffb98b`566eda00 fffff801`1571a315 : ffffd30f`be2729a0 ffffd30f`c3396000 00000000`00000000 ffffd30f`c2520010 : dxgmms2!VidSchiSubmitPagingCommand+0x2f4
ffffb98b`566edb80 fffff801`1571a18a : ffffd30f`c3396400 fffff801`1571a0c0 ffffd30f`c3396000 00000000`00000000 : dxgmms2!VidSchiRun_PriorityTable+0x175
ffffb98b`566edbd0 fffff801`0eb33585 : ffffd30f`c3394040 fffff801`00000001 ffffd30f`c3396000 00000000`00000001 : dxgmms2!VidSchiWorkerThread+0xca
ffffb98b`566edc10 fffff801`0ebcb128 : fffff801`0a482180 ffffd30f`c3394040 fffff801`0eb33530 00000000`00000246 : nt!PspSystemThreadStartup+0x55
ffffb98b`566edc60 00000000`00000000 : ffffb98b`566ee000 ffffb98b`566e8000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+14d48

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.18362.1191

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

[/CODE]
 
Uyarı! Bu konu 5 yıl önce açıldı.
Muhtemelen daha fazla tartışma gerekli değildir ki bu durumda yeni bir konu başlatmayı öneririz. Eğer yine de cevabınızın gerekli olduğunu düşünüyorsanız buna rağmen cevap verebilirsiniz.

Technopat Haberler

Yeni konular

Geri
Yukarı