GTX1060 6G sistem nvlddmkm.sys mavi ekran hatası

İşletim sistemi
Windows 10

Schlaken

Hectopat
Katılım
28 Haziran 2018
Mesajlar
162
League of Legends oynuyordum ve 60-70 FPS. Sistemim GTX1060 6G Ryzen 1600 ve 16 GB 3000MHz RAM normalde 150 FPS falan almam gerekiyordu fakat arkada 2 tane Metin2 açıktı. O yüzden kafaya takmadım ama oyun bittiği anda mavi ekran yedim, uzun zamandır League of Legends oynamıyordum. Büyük ihtimal 2 tane Metin2'nin açık olmasından kaynaklı ama ben genede minidump dosyalarını atıyorum. Yardımcı olur musunuz? Bu arada minidump dosyalarıma baktıgımda sabah bilgisayarı açtığımda da yemiş ama ben onu görmedim. Bu linkte ikisi de var Minidump.rar
 
Son düzenleyen: Moderatör:
Valorant Vanguard dolayısıyla hata almışsınız. Vanguardı kaldırınız.
Bir de ekran kartı sürücünüz hata vermiş. Onu da DDU ile kaldırıp yeni ekran kartı sürücüsünü kurunuz.
Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\hazar\AppData\Local\Temp\7zO8B718325\020721-40250-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 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 = 0xfffff800`83600000 PsLoadedModuleList = 0xfffff800`8422a2f0
Debug session time: Sun Feb 7 13:04:31.184 2021 (UTC + 3:00)
System Uptime: 0 days 2:03:24.220
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
.........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`839f5780 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff800`88a335c0=000000000000000a
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: 0000000000003838, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80097a0580c, address which referenced memory

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 6593

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on VOSTRO-5468

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 70260

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

Key : Analysis.System
Value: CreateObject

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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: d1

BUGCHECK_P1: 3838

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80097a0580c

READ_ADDRESS: fffff800842fa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8008420f330: Unable to get Flags value from nt!KdVersionBlock
fffff8008420f330: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
0000000000003838

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

DPC_STACK_BASE: FFFFF80088A33FB0

TRAP_FRAME: fffff80088a33700 -- (.trap 0xfffff80088a33700)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffff9a8cac4c59b0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80097a0580c rsp=fffff80088a33890 rbp=00000000000289a5
r8=00000000000289a5 r9=00000000000289c4 r10=0000000000000002
r11=ffffd17bb7800000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nvlddmkm+0x82580c:
fffff800`97a0580c 488b9838380000 mov rbx,qword ptr [rax+3838h] ds:00000000`00003838=????????????????
Resetting default scope

STACK_TEXT:
fffff800`88a335b8 fffff800`83a07769 : 00000000`0000000a 00000000`00003838 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`88a335c0 fffff800`83a03a69 : 00000000`00000000 fffff800`9500a3b0 ffff9a8c`ac7e6602 fffff800`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`88a33700 fffff800`97a0580c : 00000000`ffffffff 00000000`00000000 ffffd17b`b7800000 00000000`00000000 : nt!KiPageFault+0x469
fffff800`88a33890 00000000`ffffffff : 00000000`00000000 ffffd17b`b7800000 00000000`00000000 ffff9a8c`aa694000 : nvlddmkm+0x82580c
fffff800`88a33898 00000000`00000000 : ffffd17b`b7800000 00000000`00000000 ffff9a8c`aa694000 fffff800`979fcb9c : 0xffffffff


SYMBOL_NAME: nvlddmkm+82580c

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 82580c

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

0: kd> lmvm nvlddmkm
Browse full module list
start end module name
fffff800`971e0000 fffff800`997d0000 nvlddmkm T (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_d67c20d727d4578c\nvlddmkm.sys
Image name: nvlddmkm.sys
Browse all global symbols functions data
Timestamp: Fri Jan 22 21:52:54 2021 (600B1F06)
CheckSum: 0255AB47
ImageSize: 025F0000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:


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


Loading Dump File [C:\Users\hazar\AppData\Local\Temp\7zO8B74D225\020721-34828-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 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 = 0xfffff805`83400000 PsLoadedModuleList = 0xfffff805`8402a2f0
Debug session time: Sun Feb 7 11:00:30.474 2021 (UTC + 3:00)
System Uptime: 0 days 0:00:09.157
Loading Kernel Symbols
...............................................................
.........
Loading User Symbols
Loading unloaded module list
..
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`837f5780 48894c2408 mov qword ptr [rsp+8],rcx ss:ffff8b84`26a05f00=0000000000000050
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffffa60f593fb845, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff805924bda5d, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

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


Could not read faulting driver name

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3609

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on VOSTRO-5468

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 31174

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

Key : Analysis.System
Value: CreateObject

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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: 50

BUGCHECK_P1: ffffa60f593fb845

BUGCHECK_P2: 0

BUGCHECK_P3: fffff805924bda5d

BUGCHECK_P4: 2

READ_ADDRESS: fffff805840fa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8058400f330: Unable to get Flags value from nt!KdVersionBlock
fffff8058400f330: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
ffffa60f593fb845

MM_INTERNAL_CODE: 2

BLACKBOXNTFS: 1 (!blackboxntfs)


CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: ffff8b8426a061a0 -- (.trap 0xffff8b8426a061a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000040282 rbx=0000000000000000 rcx=000000000003eab6
rdx=00000000000336bf rsi=0000000000000000 rdi=0000000000000000
rip=fffff805924bda5d rsp=ffff8b8426a06330 rbp=ffffa60f593fb845
r8=fffffffffff57b78 r9=ffff8b8426a06546 r10=ffff8b8426a06470
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
vgk+0x4bda5d:
fffff805`924bda5d 660fb6442500 movzx ax,byte ptr [rbp] ss:ffffa60f`593fb845=??
Resetting default scope

STACK_TEXT:
ffff8b84`26a05ef8 fffff805`8381e8bb : 00000000`00000050 ffffa60f`593fb845 00000000`00000000 ffff8b84`26a061a0 : nt!KeBugCheckEx
ffff8b84`26a05f00 fffff805`8360c960 : ffffa60f`11ee9880 00000000`00000000 ffff8b84`26a06220 00000000`00000000 : nt!MiSystemFault+0x1f40ab
ffff8b84`26a06000 fffff805`8380395e : ffffffff`fff8e3dd ffff8b84`26a06430 ffff8b84`26a06200 ffffa60f`0f4fd301 : nt!MmAccessFault+0x400
ffff8b84`26a061a0 fffff805`924bda5d : 00000000`00040282 fffff805`92044ac0 ffffa60f`593fb845 00000000`478820f5 : nt!KiPageFault+0x35e
ffff8b84`26a06330 00000000`00040282 : fffff805`92044ac0 ffffa60f`593fb845 00000000`478820f5 ffff8b84`26a065e9 : vgk+0x4bda5d
ffff8b84`26a06338 fffff805`92044ac0 : ffffa60f`593fb845 00000000`478820f5 ffff8b84`26a065e9 ffffa60f`0f48a400 : 0x40282
ffff8b84`26a06340 ffffa60f`593fb845 : 00000000`478820f5 ffff8b84`26a065e9 ffffa60f`0f48a400 fffff804`52000000 : vgk+0x44ac0
ffff8b84`26a06348 00000000`478820f5 : ffff8b84`26a065e9 ffffa60f`0f48a400 fffff804`52000000 00000000`478820f5 : 0xffffa60f`593fb845
ffff8b84`26a06350 ffff8b84`26a065e9 : ffffa60f`0f48a400 fffff804`52000000 00000000`478820f5 00000000`00000000 : 0x478820f5
ffff8b84`26a06358 ffffa60f`0f48a400 : fffff804`52000000 00000000`478820f5 00000000`00000000 ffff8b84`26a060f8 : 0xffff8b84`26a065e9
ffff8b84`26a06360 fffff804`52000000 : 00000000`478820f5 00000000`00000000 ffff8b84`26a060f8 00000000`00040282 : 0xffffa60f`0f48a400
ffff8b84`26a06368 00000000`478820f5 : 00000000`00000000 ffff8b84`26a060f8 00000000`00040282 7fffffff`fffffffc : 0xfffff804`52000000
ffff8b84`26a06370 00000000`00000000 : ffff8b84`26a060f8 00000000`00040282 7fffffff`fffffffc ffffa60f`593fb845 : 0x478820f5


SYMBOL_NAME: vgk+4bda5d

MODULE_NAME: vgk

IMAGE_NAME: vgk.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 4bda5d
@283156 hocam doğru incelemiş miyim bir bakabilir misiniz?
 
vgk.sys mavi ekranını genelde valorantı açarken alıyordum fakat bunun MSI Afterburner ile çakıştığı için olduğunu sanıyorum çünkü MSI Afterburner açıp girmezsem mavi ekran almıyorum size sorum ilk minidump vgk.sys den mi olmuş? Bir de normalde hiç oyunda mavi ekran almam 2 tane Metin2'den yoğunluk olup crash vermiş olabilir mi ilk defa oluyor böyle bir şey.
 
Hata veren dosyanın adı Riot Vanguard olarak geçiyor. Sorunun 1 nedeni bu diğeri dediğim gibi ekran kartı sürücüsü. Metin2den 2 tane açık olmasının hataya sebep olduğunu düşünmüyorum. RAM miktarınız yüksek olduğu için arka planda daha çok uygulama çalıştırır. Dediklerimden kaynaklı oluşmuş hatalar hocam.
vgk.sys mavi ekranını genelde valorantı açarken alıyordum fakat bunun MSI Afterburner ile çakıştığı için olduğunu sanıyorum çünkü MSI Afterburner açıp girmezsem mavi ekran almıyorum size sorum ilk minidump vgk.sys den mi olmuş? Bir de normalde hiç oyunda mavi ekran almam 2 tane Metin2'den yoğunluk olup crash vermiş olabilir mi ilk defa oluyor böyle bir şey.
Evet ilk minidump dosyası vgk.sys dosyasından oluşmuş. İlk analiz ettiğim dosyada vgk.sys dosyası bulunmaktaydı.
 

Geri
Yukarı