Monster Abra A5 v17.1 laptop güncellemeden sonra mavi ekran hatası

emirhancopoglu

Decapat
Katılım
28 Aralık 2021
Mesajlar
44
Daha fazla  
Cinsiyet
Erkek
RAM
8GB (1x8GB) DDR4 1.2V 3200MHz SODIMM
SSD veya HDD modeli
500 GB CRUCIAL P2 SSD
Ekran kartı
Nvidia RTX3050 Max-Performance 4GB GDDR6
İşlemci
11th Gen Intel(R) Core(TM) i5-11400H @ 2.70GHz
Merhaba 26.12.2021'de Windows güncellemelerini yaptım. Akşam olduğunda Metin2 oynamak için oyuna girdim ve 3 defa aralıklarla mavi ekran hatası verdi. Minidump dosyalarını aşağıya bırakıyorum yardımcı olursanız çok sevinirim.

Minidump Dosyaları
 
Raporunuzu inceledim. Sorun hem dahili grafik sürücünüzden hem harici grafik sürücünüzden kaynaklanıyor. DDU yazılımı ile temizledikten sonra grafik sürücülerinizi güncelleyin.

DDU : DDU ile Sürücü Kaldırma Rehberi

Intel HD Grafik : https://www.monstersdriver.com/drivers/abra/A5_V17_1/Intel_Vga.zip

Nvidia 3050 : https://tr.download.nvidia.com/Wind...-win10-win11-64bit-international-dch-whql.exe

Umarım çözülür. Gözlemledikten sonra bizlere geri bildirimde bulunun.

Kod:
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: ffffe4017a3c0000, memory referenced.
Arg2: 0000000000000002, value 0 = read operation, 1 = write operation.
Arg3: fffff801494f89bf, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000000, (reserved)

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

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

KEY_VALUES_STRING: 1

    Key  : AV.Type
    Value: Write

    Key  : Analysis.CPU.mSec
    Value: 5734

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 39405

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

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

    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


FILE_IN_CAB:  122721-14359-02.dmp

BUGCHECK_CODE:  50

BUGCHECK_P1: ffffe4017a3c0000

BUGCHECK_P2: 2

BUGCHECK_P3: fffff801494f89bf

BUGCHECK_P4: 0

READ_ADDRESS: fffff801300fb390: 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
 ffffe4017a3c0000

MM_INTERNAL_CODE:  0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  2

PROCESS_NAME:  System

TRAP_FRAME:  ffffe2869ea1ea10 -- (.trap 0xffffe2869ea1ea10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffe4017a3bf000 rbx=0000000000000000 rcx=ffffaa063df0b0d0
rdx=000000000001f3fd rsi=0000000000000000 rdi=0000000000000000
rip=fffff801494f89bf rsp=ffffe2869ea1eba0 rbp=0000000000000007
 r8=0000000000000400  r9=000000000001e033 r10=0000000000000000
r11=ffffe2869ea1ebc0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nvlddmkm+0x7a89bf:
fffff801`494f89bf 42891480        mov     dword ptr [rax+r8*4],edx ds:ffffe401`7a3c0000=????????
Resetting default scope

STACK_TEXT: 
ffffe286`9ea1e768 fffff801`2f84a61f     : 00000000`00000050 ffffe401`7a3c0000 00000000`00000002 ffffe286`9ea1ea10 : nt!KeBugCheckEx
ffffe286`9ea1e770 fffff801`2f69f470     : 00000000`0000ffff 00000000`00000002 ffffe286`9ea1ea90 00000000`00000000 : nt!MiSystemFault+0x18d18f
ffffe286`9ea1e870 fffff801`2f80525e     : ffffb08b`beda8055 00000000`00000007 ffffe286`00000000 00000000`00000080 : nt!MmAccessFault+0x400
ffffe286`9ea1ea10 fffff801`494f89bf     : ffffaa06`3df0b0d0 00000000`00002cae ffffb08b`beda83e5 ffffaa06`3df02000 : nt!KiPageFault+0x35e
ffffe286`9ea1eba0 ffffaa06`3df0b0d0     : 00000000`00002cae ffffb08b`beda83e5 ffffaa06`3df02000 00000000`00000007 : nvlddmkm+0x7a89bf
ffffe286`9ea1eba8 00000000`00002cae     : ffffb08b`beda83e5 ffffaa06`3df02000 00000000`00000007 fffff801`498c5812 : 0xffffaa06`3df0b0d0
ffffe286`9ea1ebb0 ffffb08b`beda83e5     : ffffaa06`3df02000 00000000`00000007 fffff801`498c5812 00000000`00000003 : 0x2cae
ffffe286`9ea1ebb8 ffffaa06`3df02000     : 00000000`00000007 fffff801`498c5812 00000000`00000003 ffffaa06`35c75000 : 0xffffb08b`beda83e5
ffffe286`9ea1ebc0 00000000`00000007     : fffff801`498c5812 00000000`00000003 ffffaa06`35c75000 ffffaa06`35c75003 : 0xffffaa06`3df02000
ffffe286`9ea1ebc8 fffff801`498c5812     : 00000000`00000003 ffffaa06`35c75000 ffffaa06`35c75003 00000000`0000000f : 0x7
ffffe286`9ea1ebd0 00000000`00000003     : ffffaa06`35c75000 ffffaa06`35c75003 00000000`0000000f 00000000`00000000 : nvlddmkm+0xb75812
ffffe286`9ea1ebd8 ffffaa06`35c75000     : ffffaa06`35c75003 00000000`0000000f 00000000`00000000 00000000`00000001 : 0x3
ffffe286`9ea1ebe0 ffffaa06`35c75003     : 00000000`0000000f 00000000`00000000 00000000`00000001 00000001`00000000 : 0xffffaa06`35c75000
ffffe286`9ea1ebe8 00000000`0000000f     : 00000000`00000000 00000000`00000001 00000001`00000000 00000000`00000000 : 0xffffaa06`35c75003
ffffe286`9ea1ebf0 00000000`00000000     : 00000000`00000001 00000001`00000000 00000000`00000000 ffffaa06`3df0b1b0 : 0xf


SYMBOL_NAME:  nvlddmkm+7a89bf

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  7a89bf

FAILURE_BUCKET_ID:  AV_W_(null)_nvlddmkm!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {838100fa-f28b-2ef7-d702-e31713cb338c}

Followup:     MachineOwner

Kod:
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: fffff8029c8177ae, The address that the exception occurred at
Arg3: ffffb70bc616e768, Exception Record Address
Arg4: ffffb70bc616dfa0, Context Record Address

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

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

KEY_VALUES_STRING: 1

    Key  : AV.Dereference
    Value: NullClassPtr

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 3562

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 9321

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

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

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

    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


FILE_IN_CAB:  122721-13375-01.dmp

BUGCHECK_CODE:  7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8029c8177ae

BUGCHECK_P3: ffffb70bc616e768

BUGCHECK_P4: ffffb70bc616dfa0

EXCEPTION_RECORD:  ffffb70bc616e768 -- (.exr 0xffffb70bc616e768)
ExceptionAddress: fffff8029c8177ae (igdkmdn64+0x00000000004477ae)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000008
Attempt to read from address 0000000000000008

CONTEXT:  ffffb70bc616dfa0 -- (.cxr 0xffffb70bc616dfa0)
rax=0000000000000000 rbx=0000000000000000 rcx=ffffcd0bdb200010
rdx=ffffcd0be27f1a20 rsi=ffffcd0bd3f32000 rdi=ffffcd0bdb200010
rip=fffff8029c8177ae rsp=ffffb70bc616e9a0 rbp=ffffcd0bdb200010
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=ffffcd0bdb080000 r15=ffffcd0bdb200000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050286
igdkmdn64+0x4477ae:
fffff802`9c8177ae 4c8b4808        mov     r9,qword ptr [rax+8] ds:002b:00000000`00000008=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

READ_ADDRESS: fffff8027eefb390: 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
 0000000000000008

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

EXCEPTION_STR:  0xc0000005

STACK_TEXT: 
ffffb70b`c616e9a0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : igdkmdn64+0x4477ae


SYMBOL_NAME:  igdkmdn64+4477ae

MODULE_NAME: igdkmdn64

IMAGE_NAME:  igdkmdn64.sys

STACK_COMMAND:  .cxr 0xffffb70bc616dfa0 ; kb

BUCKET_ID_FUNC_OFFSET:  4477ae

FAILURE_BUCKET_ID:  AV_igdkmdn64!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {12102b79-db74-3949-6de5-0951c15a29fa}

Followup:     MachineOwner
 
Merhabalar yardımcı olduğunuz için teşekkür ederim. NVIDIA GeForce Experience ile grafik kartımı güncelledim ve Intel driver Support assistant indirip bilgisayarımı tarattım. Dediğiniz gibi Intel HD grafik driver güncel değilmiş, Driver'ı güncelledikten sonra sorun ortadan kalktı. Yardımınız için teşekkürler.
 
Merhabalar. 07.01.2022 tarihinde Windows güncellemelerini yapıyordum, güncellemeleri indirdim ve kurmak için yeniden başlatmamı istedi. Ben de yeniden başlattım ancak güncellemeyi kurarken yüzde %30 civarlarında mavi ekran verdi. Minidump dosyasını arşivleyemiyorum. WinRAR sıkıştırmıyor, hata veriyor. Bunun için paylaşamıyorum ama mavi ekranda DRIVER_VERIFIER_DMA_VIOLATION hatasını görmüştüm.

Ayrıca şu an Windows Update kısmında bekleyen bir güncelleme var ve yeniden başlatmamı istiyor ancak 10 kere yeniden başlatmama rağmen hala yazı duruyor. Yeniden başlatmama rağmen kurmuyor.

Merhaba minidump dosyalarımı arşivlemeyi başardım. İşte burada, yardımcı olursanız sevinirim.
Minidump
Merhaba bilgisayarım yine mavi ekran vermeye başladı yardımcı olursanız sevinirim.
minidump dosyaları
@@KojiroHyuga04
 
Son düzenleme:

Yeni konular

Geri
Yukarı