R5 2600X ve GTX 1660 Super sistemde mavi ekran hatası

Katılım
1 Haziran 2016
Mesajlar
1.596
Çözümler
7
Yer
Afyonkarahisar
Daha fazla  
Cinsiyet
Erkek
Meslek
Yurtiçi Kargo- Operatör
Son günlerde mavi ekran almaya başladım.

Anakart: Gigabyte B450 AORUS M İşlemci: AMD Ryzen 5 2600x İşlemci Soğtucu: Cougar Aqua 240 ARGB SSD: Kioxia 500gb Exceria HDD: Western Digital(1TB)
RAM: Corsair Vengeance RGB PRO 32GB (4x8GB) 3200MHz DDR4 PSU: Sharkoon SilentStorm Cool Zero 850W 80+ Gold
Ekran Kartı: GTX1660 Süper 6GB Kasa: CM MasterBox 520 Monitör: Rampage RM-165 27" 1ms Curved Monitor

minidump dosyası:
 
[CODE title="1. dosya"]
9: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff52624c650fe, Address of the instruction which caused the BugCheck
Arg3: ffff938052e4bca0, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 5593

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 12414

Key : Analysis.Init.CPU.mSec
Value: 499

Key : Analysis.Init.Elapsed.mSec
Value: 3080

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

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: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff52624c650fe

BUGCHECK_P3: ffff938052e4bca0

BUGCHECK_P4: 0

CONTEXT: ffff938052e4bca0 -- (.cxr 0xffff938052e4bca0)
rax=000000039dce2880 rbx=ffffa08b88c11360 rcx=fffff7c0c0003000
rdx=00000003a82f4912 rsi=fffff54600657ad8 rdi=0000000000000000
rip=fffff52624c650fe rsp=ffff938052e4c6a0 rbp=ffff938052e4c7a0
r8=fffffffff59edf6e r9=0000000000000001 r10=0000fffff8072e16
r11=ffffcd7c40a00000 r12=fffff54600657050 r13=0000000000000000
r14=0000000000000003 r15=fffff54600657000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050246
win32kbase!EtwTraceStartProcessQueuedMouseEvents+0x60e:
fffff526`24c650fe 0f57c0 xorps xmm0,xmm0
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: dwm.exe

STACK_TEXT:
ffff9380`52e4c6a0 fffff526`24c64ad6 : fffff807`2e1f3530 00000000`00000000 fffff526`24e470c0 00000000`00000000 : win32kbase!EtwTraceStartProcessQueuedMouseEvents+0x60e
ffff9380`52e4c910 fffff526`24fb39cc : 00000000`00000002 ffffffff`8000174c fffff526`24e470c0 00000000`00000000 : win32kbase!ProcessMouseEvent+0x16
ffff9380`52e4c940 fffff526`24c6497c : ffff9380`52e4c9a0 00000000`00000000 00000000`00000002 ffff9380`00000000 : win32kfull!EditionHandleMitSignal+0x5c
ffff9380`52e4c980 fffff526`24c648ee : fffff546`007e5a20 fffff546`007e5010 00000000`00000000 00000000`00000000 : win32kbase!IOCPDispatcher::Dispatch+0x12c
ffff9380`52e4c9c0 fffff526`24c6486f : 00000000`00000000 00000000`00000000 fffff526`24e470c0 00000000`00000000 : win32kbase!IOCPDispatcher::Dispatch+0x9e
ffff9380`52e4ca00 fffff526`24c64811 : 00000000`00000000 00000248`00000000 fffff546`00613ca0 000000e9`6b8ff6b8 : win32kbase!IOCPDispatcher::Dispatch+0x1f
ffff9380`52e4ca60 fffff526`24c64795 : 00000000`000006fc fffff546`00613ca0 00000000`000006fc 00000000`00000000 : win32kbase!NtMITDispatchCompletion+0x101
ffff9380`52e4caa0 fffff526`256ff8a9 : ffffa08b`88ff5080 ffff9380`52e4cb80 00000248`41f0b350 00000000`00000020 : win32kbase!NtMITDispatchCompletion+0x85
ffff9380`52e4cad0 fffff807`2e2077b8 : 00000248`459dfd20 ffffa08b`88f11e60 ffff9380`00000000 ffffa08b`00000000 : win32k!NtMITDispatchCompletion+0x15
ffff9380`52e4cb00 00007ffc`6c5176e4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000e9`6b8ff768 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`6c5176e4


SYMBOL_NAME: win32kbase!EtwTraceStartProcessQueuedMouseEvents+60e

MODULE_NAME: win32kbase

IMAGE_NAME: win32kbase.sys

IMAGE_VERSION: 10.0.19041.928

STACK_COMMAND: .cxr 0xffff938052e4bca0 ; kb

BUCKET_ID_FUNC_OFFSET: 60e

FAILURE_BUCKET_ID: 0x3B_c0000005_win32kbase!EtwTraceStartProcessQueuedMouseEvents

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {116ae1b5-1659-b630-d8db-3e211f24e7c9}

Followup: MachineOwner
---------
[/CODE]

[CODE title="2. dosya"]
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 000000003a423208, memory referenced
Arg2: 0000000000000006, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8043a38efd4, address which referenced memory

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3953

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 12571

Key : Analysis.Init.CPU.mSec
Value: 406

Key : Analysis.Init.Elapsed.mSec
Value: 3110

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

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

BUGCHECK_P1: 3a423208

BUGCHECK_P2: 6

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8043a38efd4

READ_ADDRESS: fffff804282fa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
000000003a423208

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: fffff8042ae6b430 -- (.trap 0xfffff8042ae6b430)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000003a422670 rbx=0000000000000000 rcx=ffffb28608277000
rdx=0000000000007102 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8043a38efd4 rsp=fffff8042ae6b5c0 rbp=fffff8042ae6b620
r8=fffff8042ae6b5e4 r9=0000000000000001 r10=000000000011cc40
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nvlddmkm+0x79efd4:
fffff804`3a38efd4 ff90980b0000 call qword ptr [rax+0B98h] ds:00000000`3a423208=????????????????
Resetting default scope

STACK_TEXT:
fffff804`2ae6b2e8 fffff804`27a09169 : 00000000`0000000a 00000000`3a423208 00000000`00000006 00000000`00000000 : nt!KeBugCheckEx
fffff804`2ae6b2f0 fffff804`27a05469 : ffffb286`08277000 fffff804`3a3ad59d ffffb286`0a50a000 fffff804`3a3896d7 : nt!KiBugCheckDispatch+0x69
fffff804`2ae6b430 fffff804`3a38efd4 : ffffb286`08277000 00000000`00000000 fffff804`2ae6b729 ffffb286`08277000 : nt!KiPageFault+0x469
fffff804`2ae6b5c0 ffffb286`08277000 : 00000000`00000000 fffff804`2ae6b729 ffffb286`08277000 ffffffff`00000000 : nvlddmkm+0x79efd4
fffff804`2ae6b5c8 00000000`00000000 : fffff804`2ae6b729 ffffb286`08277000 ffffffff`00000000 00000001`00000000 : 0xffffb286`08277000


SYMBOL_NAME: nvlddmkm+79efd4

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 79efd4

FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {7eea5677-f68d-2154-717e-887e07e55cd3}

Followup: MachineOwner
---------
[/CODE]

[CODE title="3. dosya"]11: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000002, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 0000000000000002, address which referenced memory

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3358

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 9793

Key : Analysis.Init.CPU.mSec
Value: 421

Key : Analysis.Init.Elapsed.mSec
Value: 2210

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

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

BUGCHECK_P1: 2

BUGCHECK_P2: 2

BUGCHECK_P3: 8

BUGCHECK_P4: 2

READ_ADDRESS: fffff8061f2fa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
0000000000000002

PROCESS_NAME: GoldRushTheGame.exe

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

DPC_STACK_BASE: FFFFFA0A2AABCFB0

TRAP_FRAME: fffffa0a2aabc590 -- (.trap 0xfffffa0a2aabc590)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000001
rdx=0000000000000154 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000002 rsp=fffffa0a2aabc728 rbp=0f0f0f0f00000000
r8=ffffbd01649dc180 r9=0000000000000000 r10=0000fffff8061e96
r11=ffffacfb91a00000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
00000000`00000002 ?? ???
Resetting default scope

FAILED_INSTRUCTION_ADDRESS:
+0
00000000`00000002 ?? ???

STACK_TEXT:
fffffa0a`2aabc448 fffff806`1ea09169 : 00000000`0000000a 00000000`00000002 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffffa0a`2aabc450 fffff806`1ea05469 : ffffac03`2a4ad670 00000000`00000000 00000001`00000000 00000000`00000002 : nt!KiBugCheckDispatch+0x69
fffffa0a`2aabc590 00000000`00000002 : 0000001b`a6a070d4 00000000`00000000 ffffac03`340f0c90 00000000`ffffffff : nt!KiPageFault+0x469
fffffa0a`2aabc728 0000001b`a6a070d4 : 00000000`00000000 ffffac03`340f0c90 00000000`ffffffff fffff806`23903475 : 0x2
fffffa0a`2aabc730 00000000`00000000 : ffffac03`340f0c90 00000000`ffffffff fffff806`23903475 ffffac03`34078990 : 0x0000001b`a6a070d4


SYMBOL_NAME: nt!KiPageFault+469

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.1237

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 469

FAILURE_BUCKET_ID: AV_CODE_AV_NULL_IP_nt!KiPageFault

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {4ce35ff9-c5cf-d66d-0323-0f05e33f6692}

Followup: MachineOwner
---------[/CODE]

[CODE title="4. dosya"]: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8031323efcd, address which referenced memory

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 5405

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 9225

Key : Analysis.Init.CPU.mSec
Value: 483

Key : Analysis.Init.Elapsed.mSec
Value: 26298

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

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

BUGCHECK_P1: 0

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff8031323efcd

WRITE_ADDRESS: fffff80313cfb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
0000000000000000

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: ffffcb0fe0962520 -- (.trap 0xffffcb0fe0962520)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=00000000005840b8
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8031323efcd rsp=ffffcb0fe09626b0 rbp=ffffcb0fe0962859
r8=00000000000000b8 r9=00000000000000b8 r10=0000000fffffffff
r11=ffffcb0fe0962798 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!MiCoalesceFreePages+0x4d:
fffff803`1323efcd 0000 add byte ptr [rax],al ds:00000000`00000000=??
Resetting default scope

STACK_TEXT:
ffffcb0f`e09623d8 fffff803`13409169 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
ffffcb0f`e09623e0 fffff803`13405469 : 00000000`00000001 ffffaa00`00007000 ffffffff`ffffffff ffff9680`8d729dc0 : nt!KiBugCheckDispatch+0x69
ffffcb0f`e0962520 fffff803`1323efcd : 000f8067`bcbbbdff fffff803`00000001 00000000`00000000 00001f80`00000200 : nt!KiPageFault+0x469
ffffcb0f`e09626b0 fffff803`1323e5c5 : 00000000`00000000 00000000`00000000 ffffcb0f`e0962859 ffffa700`108c2280 : nt!MiCoalesceFreePages+0x4d
ffffcb0f`e09627a0 fffff803`1323d1e7 : 00000000`005840b8 00000000`00000000 ffffb682`00000000 fffff803`000000b8 : nt!MiInsertPageInFreeOrZeroedList+0x3d5
ffffcb0f`e09628c0 fffff803`1323c508 : ffffb682`2c4c0690 00000000`00000001 fffff803`13c50b00 ffffb682`2c4ae050 : nt!MiZeroPage+0xbf7
ffffcb0f`e0962a70 fffff803`133ab3c8 : ffffb682`2c4c0690 ffffcb0f`00000003 fffff803`00000000 00000000`00000008 : nt!MiZeroLargePages+0xd08
ffffcb0f`e0962b60 fffff803`13355855 : 00000000`00000000 ffffb682`2c4ae050 ffffaa00`00007000 fffff803`13c50b00 : nt!MiZeroLargePageThread+0x88
ffffcb0f`e0962c10 fffff803`133fe808 : ffff9680`8c4a2180 ffffb682`2c602080 fffff803`13355800 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffcb0f`e0962c60 00000000`00000000 : ffffcb0f`e0963000 ffffcb0f`e095d000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff8031323efc6 - nt!MiCoalesceFreePages+46
[ 89:81 ]
1 error : !nt (fffff8031323efc6)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

MEMORY_CORRUPTOR: ONE_BIT

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}

Followup: memory_corruption
---------[/CODE]
[CODE title="5. dosya"]10: 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: ffffed00b000d960
Arg4: ffffca021eb61c90

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 6421

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 24797

Key : Analysis.Init.CPU.mSec
Value: 405

Key : Analysis.Init.Elapsed.mSec
Value: 2600

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

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

BUGCHECK_P4: ffffca021eb61c90

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffed00`b000d888 fffff804`6b1b3ad0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffffed00`b000d960 : nt!KeBugCheckEx
ffffed00`b000d890 fffff804`6bb27b09 : ffffca02`1eb5e000 00000000`c000000d ffffed00`b000d999 00000000`00000007 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffffed00`b000d8d0 fffff804`6bba4b9d : ffffca02`00000000 ffffca02`1eb61c90 ffffca02`1ea6d000 ffffca02`32acc350 : dxgmms2!VidSchiSendToExecutionQueue+0xa99
ffffed00`b000da00 fffff804`6bbad51a : ffffca02`32acc350 ffffca02`1ea6d000 00000000`00000000 ffffca02`1b8d2320 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
ffffed00`b000db80 fffff804`6bbad38a : ffffca02`1ea6d400 fffff804`6bbad2c0 ffffca02`1ea6d000 ffff9e01`9bfaa100 : dxgmms2!VidSchiRun_PriorityTable+0x17a
ffffed00`b000dbd0 fffff804`5dd55855 : ffffca02`1e827080 fffff804`00000001 ffffca02`1ea6d000 000f8067`bcbbbdff : dxgmms2!VidSchiWorkerThread+0xca
ffffed00`b000dc10 fffff804`5ddfe818 : ffff9e01`9bfaa180 ffffca02`1e827080 fffff804`5dd55800 2fe799ce`efd7644e : nt!PspSystemThreadStartup+0x55
ffffed00`b000dc60 00000000`00000000 : ffffed00`b000e000 ffffed00`b0008000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+a99

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.1261

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: a99

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]

@KojiroHyuga04
 
Son günlerde mavi ekran almaya başladım.

Anakart: Gigabyte B450 AORUS M İşlemci: AMD Ryzen 5 2600x İşlemci Soğtucu: Cougar Aqua 240 ARGB SSD: Kioxia 500gb Exceria HDD: Western Digital(1TB)
RAM: Corsair Vengeance RGB PRO 32GB (4x8GB) 3200MHz DDR4 PSU: Sharkoon SilentStorm Cool Zero 850W 80+ Gold
Ekran Kartı: GTX1660 Süper 6GB Kasa: CM MasterBox 520 Monitör: Rampage RM-165 27" 1ms Curved Monitor

minidump dosyası:


Önceden 16 GB ram vardı. Trendyol da aynı ramlar indirime girmiş bende kaçırmak istemedim. 16 GB daha ekledim totalde 32 GB ram oldu. Sonra bir kaç oyun indirdim steamdan satın alarak Nfs, gold Rush türü oyunlar bunlarda hatalar almaya başladım. Dün akşamda csgo oynarken aynı şey başıma geldi.

Temiz bir format attım Windows 10 tüm driverleri updateleri yaptım.

@Mithat Berhan hocam bilginiz varsa yardımcı olur musunuz?
 

Technopat Haberler

Yeni konular

Geri
Yukarı