Çözüldü Oyun oynarken nvlddmkm.sys mavi ekran hatası

Gnosis dedi:

Selam laptopum Valorant oynarken aniden mavi ekran verdi sebebini anlamadım daha sonra yeniden oynadım LoL vs de oynadım başka problem vermedi ama yeniden verebilir diye endişeleniyorum hatanın kaynaklandığı problemide merak ediyorum minudump dosyalarımı inceleyebilir misiniz acaba?

hata-dosyası.zip

Görüntüle ve Yandex Disk'ten indir

disk.yandex.com.tr

Kod:Panoya kopyala

10: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common BugCheck. Usually the exception address pinpoints.
the driver/function that caused the problem. Always note this address.
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard.
coded breakpoint or assertion was hit, but this system was booted.
/NODEBUG. This is not supposed to happen as developers should never have.
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the.
system is booted /DEBUG. This will let us see why this breakpoint is.
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled.
Arg2: fffff803518c7a6d, The address that the exception occurred at.
Arg3: ffffe108b179e878, Exception Record Address.
Arg4: ffffe108b179e090, Context Record Address.

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

KEY_VALUES_STRING: 1

 Key : AV.Fault
 Value: Read.

 Key : Analysis.CPU.mSec
 Value: 1171.

 Key : Analysis.DebugAnalysisManager
 Value: Create.

 Key : Analysis.Elapsed.mSec
 Value: 5264.

 Key : Analysis.IO.Other.Mb
 Value: 0

 Key : Analysis.IO.Read.Mb
 Value: 0

 Key : Analysis.IO.Write.Mb
 Value: 0

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

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

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

 Key : Bugcheck.Code.DumpHeader
 Value: 0x1000007e.

 Key : Bugcheck.Code.Register
 Value: 0x7e.

 Key : WER.OS.Branch
 Value: ni_release.

 Key : WER.OS.Timestamp
 Value: 2022-05-06T12:50:00Z

 Key : WER.OS.Version
 Value: 10.0.22621.1

FILE_IN_CAB: 111322-16234-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b.

BUGCHECK_CODE: 7e.

BUGCHECK_P1: ffffffffc0000005.

BUGCHECK_P2: fffff803518c7a6d.

BUGCHECK_P3: ffffe108b179e878.

BUGCHECK_P4: ffffe108b179e090.

EXCEPTION_RECORD: ffffe108b179e878 -- (.exr 0xffffe108b179e878)
ExceptionAddress: fffff803518c7a6d (nvlddmkm+0x0000000000937a6d)
 ExceptionCode: c0000005 (Access violation)
 ExceptionFlags: 00000000.
NumberParameters: 2
 Parameter[0]: 0000000000000000.
 Parameter[1]: ffffffffffffffff.
Attempt to read from address ffffffffffffffff.

CONTEXT: ffffe108b179e090 -- (.cxr 0xffffe108b179e090)
rax=00000000c0004980 rbx=0000000000000000 rcx=00030000204b1d1d
rdx=0000000000000000 rsi=ffffce86c24cb000 rdi=ffffce86d6292c10
rip=fffff803518c7a6d rsp=ffffe108b179eab0 rbp=ffffe108b179ef10
 r8=ffffe108b179eb30 r9=ffffce86ce1c3450 r10=fffff80350fac0c0
r11=0000000000000000 r12=ffffce86c79443bc r13=ffffce86cf924000
r14=ffffce86d0eac050 r15=ffffce86db354cd8
iopl=0 nv up ei ng nz na pe nc.
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050282
nvlddmkm+0x937a6d:
fffff803`518c7a6d 483b81f80d0000 cmp rax,qword ptr [rcx+0DF8h] ds:002b:00030000`204b2b15=????????????????
Resetting default scope.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System.

READ_ADDRESS: fffff8032231c468: 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
 ffffffffffffffff.

ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p adresindeki y nerge 0x%p adresindeki belle e ba vurdu. Bellek u olamaz %s.

EXCEPTION_CODE_STR: c0000005.

EXCEPTION_PARAMETER1: 0000000000000000.

EXCEPTION_PARAMETER2: ffffffffffffffff.

EXCEPTION_STR: 0xc0000005.

STACK_TEXT:
ffffe108`b179eab0 ffffce86`c24cb000 : ffffce86`d6292c10 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x937a6d
ffffe108`b179eab8 ffffce86`d6292c10 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffce86`c24cb000
ffffe108`b179eac0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffce86`d6292c10

SYMBOL_NAME: nvlddmkm+937a6d

MODULE_NAME: nvlddmkm.

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .cxr 0xffffe108b179e090 ; kb.

BUCKET_ID_FUNC_OFFSET: 937a6d.

FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function

OS_VERSION: 10.0.22621.1

BUILDLAB_STR: ni_release.

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

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

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

@claus üstadım sizin mavi ekran hata analizinde bilgi birikiminiz olağan üstü bir seviyede minidump dosyamı inceler misiniz bu işi çözse çözse siz çözersiniz.

Genişletmek için tıkla...