adam gibi adam
Femtopat
- Katılım
- 23 Eylül 2020
- Mesajlar
- 28
Merhabalar. Bilgisayarımda oyun oynarken mavi ekran verdi. Minidump dosyasını açtım. Bu şekilde bir yazı verdi, acaba sorun nedir?
[CODE title="Minidump"]Microsoft (R) Windows Debugger Version 10.0.21306.1007 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\041421-6281-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff803`1ce00000 PsLoadedModuleList = 0xfffff803`1da2a490
Debug session time: Wed Apr 14 14:43:04.509 2021 (UTC + 3:00)
System Uptime: 0 days 2:42:02.131
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
..............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`1d1f5c50 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffa08`b5661890=0000000000000119
2: 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: fffffa08b5661960
Arg4: ffff9a864e870670
Debugging Details:
------------------
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 4155
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 58677
Key : Analysis.Init.CPU.mSec
Value: 467
Key : Analysis.Init.Elapsed.mSec
Value: 37402
Key : Analysis.Memory.CommitPeak.Mb
Value: 83
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
BUGCHECK_CODE: 119
BUGCHECK_P1: 2
BUGCHECK_P2: ffffffffc000000d
BUGCHECK_P3: fffffa08b5661960
BUGCHECK_P4: ffff9a864e870670
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffffa08`b5661888 fffff803`23ce3ad0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d fffffa08`b5661960 : nt!KeBugCheckEx
fffffa08`b5661890 fffff803`2478b3cb : 00000000`00000000 ffff9a86`4e86d000 fffffa08`b5661999 ffff9a86`4e86d000 : watchdog!WdLogEvent5_WdCriticalError+0xe0
fffffa08`b56618d0 fffff803`247f4b6d : ffff9a86`00000000 ffff9a86`4e870670 ffff9a86`4e172000 ffff9a86`4aea1010 : dxgmms2!VidSchiSendToExecutionQueue+0x1306b
fffffa08`b5661a00 fffff803`247fcd1a : ffff9a86`4aea1010 ffff9a86`4e172000 00000000`00000000 ffff9a86`51486620 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
fffffa08`b5661b80 fffff803`247fcb8a : ffff9a86`4e172400 fffff803`247fcac0 ffff9a86`4e172000 ffff8980`54498100 : dxgmms2!VidSchiRun_PriorityTable+0x17a
fffffa08`b5661bd0 fffff803`1d117e85 : ffff9a86`4e107080 fffff803`00000001 ffff9a86`4e172000 000f8067`b4bbbdff : dxgmms2!VidSchiWorkerThread+0xca
fffffa08`b5661c10 fffff803`1d1fd2a8 : ffff8980`54498180 ffff9a86`4e107080 fffff803`1d117e30 7c505b37`001e5558 : nt!PspSystemThreadStartup+0x55
fffffa08`b5661c60 00000000`00000000 : fffffa08`b5662000 fffffa08`b565c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+1306b
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.19041.870
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 1306b
FAILURE_BUCKET_ID: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {9a11bf9c-270e-962e-7a82-3efdab93c10e}
Followup: MachineOwner
---------[/CODE]
Şimdiden yardımlarınız için teşekkür ederim
[CODE title="Minidump"]Microsoft (R) Windows Debugger Version 10.0.21306.1007 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\041421-6281-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff803`1ce00000 PsLoadedModuleList = 0xfffff803`1da2a490
Debug session time: Wed Apr 14 14:43:04.509 2021 (UTC + 3:00)
System Uptime: 0 days 2:42:02.131
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
..............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`1d1f5c50 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffa08`b5661890=0000000000000119
2: 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: fffffa08b5661960
Arg4: ffff9a864e870670
Debugging Details:
------------------
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 4155
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 58677
Key : Analysis.Init.CPU.mSec
Value: 467
Key : Analysis.Init.Elapsed.mSec
Value: 37402
Key : Analysis.Memory.CommitPeak.Mb
Value: 83
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
BUGCHECK_CODE: 119
BUGCHECK_P1: 2
BUGCHECK_P2: ffffffffc000000d
BUGCHECK_P3: fffffa08b5661960
BUGCHECK_P4: ffff9a864e870670
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffffa08`b5661888 fffff803`23ce3ad0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d fffffa08`b5661960 : nt!KeBugCheckEx
fffffa08`b5661890 fffff803`2478b3cb : 00000000`00000000 ffff9a86`4e86d000 fffffa08`b5661999 ffff9a86`4e86d000 : watchdog!WdLogEvent5_WdCriticalError+0xe0
fffffa08`b56618d0 fffff803`247f4b6d : ffff9a86`00000000 ffff9a86`4e870670 ffff9a86`4e172000 ffff9a86`4aea1010 : dxgmms2!VidSchiSendToExecutionQueue+0x1306b
fffffa08`b5661a00 fffff803`247fcd1a : ffff9a86`4aea1010 ffff9a86`4e172000 00000000`00000000 ffff9a86`51486620 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
fffffa08`b5661b80 fffff803`247fcb8a : ffff9a86`4e172400 fffff803`247fcac0 ffff9a86`4e172000 ffff8980`54498100 : dxgmms2!VidSchiRun_PriorityTable+0x17a
fffffa08`b5661bd0 fffff803`1d117e85 : ffff9a86`4e107080 fffff803`00000001 ffff9a86`4e172000 000f8067`b4bbbdff : dxgmms2!VidSchiWorkerThread+0xca
fffffa08`b5661c10 fffff803`1d1fd2a8 : ffff8980`54498180 ffff9a86`4e107080 fffff803`1d117e30 7c505b37`001e5558 : nt!PspSystemThreadStartup+0x55
fffffa08`b5661c60 00000000`00000000 : fffffa08`b5662000 fffffa08`b565c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+1306b
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.19041.870
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 1306b
FAILURE_BUCKET_ID: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {9a11bf9c-270e-962e-7a82-3efdab93c10e}
Followup: MachineOwner
---------[/CODE]
Şimdiden yardımlarınız için teşekkür ederim
