Monster Unexpected Store Exception mavi ekran hatası

İşletim sistemi
Windows 10

alperengnl

Hectopat
Katılım
9 Ocak 2021
Mesajlar
7
Daha fazla  
Cinsiyet
Erkek
Minidump dosyaları daha önce korsan Windows 10 kullanırken bu hatayı ve Critical Process Died hatasını almıştım. Şimdi ise orijinal Windows kullanıyorum.
Bugün yine bu hatayı aldım. Minidump dosyası okuyup analiz edemediğim için yardım edebilir misiniz?
 
1) Aşağıdaki sürücüyü indirip kurun. (Wi-Fi)

2) Aşağıdaki websiteden öncelikle sürücüyü indirin. Daha sonra DDU ile eski ekran kartı sürücünüzü kaldırıp PC yeniden başladığında bu indirdiğiniz sürücüyü kurun. Bu arada DDU kullanım rehberi de aşağıda yer alıyor.

Sürücü: Grafik Sürücüsü - GeForce Game Ready Driver | NVIDIA
Rehber: DDU ile Sürücü Kaldırma Rehberi

3) Aşağıdaki rehberi uygulayıp sonucun ekran alıntısını paylaşın.

NOT: Sorun çözülürse bildirmeyi unutmayın.

Kod:
Machine ID Information [From Smbios 3.2, DMIVersion 0, Size=4668]
BiosMajorRelease = 5
BiosMinorRelease = 17
FirmwareMajorRelease = 1
FirmwareMinorRelease = 19
BiosVendor = American Megatrends Inc.
BiosVersion = N.1.06
BiosReleaseDate = 08/04/2020
SystemManufacturer = MONSTER
SystemProductName = ABRA A7 V11.3
SystemFamily = CML
SystemVersion = Standard
SystemSKU = 0001
BaseBoardManufacturer = MONSTER
BaseBoardProduct = ABRA A7 V11.3
BaseBoardVersion = Standard

Kod:
*******************************************************************************
*                                                                             *
*                        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: fffff8045ba2299a, The address that the exception occurred at
Arg3: ffffe10f7b71ecc8, Exception Record Address
Arg4: ffffe10f7b71e500, Context Record Address

Debugging Details:
------------------
KEY_VALUES_STRING: 1

    Key  : AV.Dereference
    Value: NullClassPtr

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 11359

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-70T822T

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 101273

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

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

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8045ba2299a

BUGCHECK_P3: ffffe10f7b71ecc8

BUGCHECK_P4: ffffe10f7b71e500

EXCEPTION_RECORD:  ffffe10f7b71ecc8 -- (.exr 0xffffe10f7b71ecc8)
ExceptionAddress: fffff8045ba2299a (nvlddmkm+0x000000000016299a)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000080
Attempt to read from address 0000000000000080

CONTEXT:  ffffe10f7b71e500 -- (.cxr 0xffffe10f7b71e500)
rax=0000000000000000 rbx=ffff820df6280000 rcx=0000000000000000
rdx=0000000000000001 rsi=ffff820df62b9000 rdi=0000000000001000
rip=fffff8045ba2299a rsp=ffffe10f7b71ef00 rbp=0000000000000000
 r8=0000000000000001  r9=0000000000000020 r10=ffff820df0e6d5f0
r11=ffffe10f7b71edd0 r12=ffff820df62359a8 r13=0000000000000001
r14=ffff820df6002050 r15=ffff820df6270000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050286
nvlddmkm+0x16299a:
fffff804`5ba2299a 83b98000000001  cmp     dword ptr [rcx+80h],1 ds:002b:00000000`00000080=????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

READ_ADDRESS: fffff804402fa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8044020f330: Unable to get Flags value from nt!KdVersionBlock
fffff8044020f330: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
 0000000000000080

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

EXCEPTION_STR:  0xc0000005

STACK_TEXT: 
ffffe10f`7b71ef00 ffff820d`f6280000     : ffff820d`0f2e0000 00000000`00000000 00000000`00000001 ffff820d`f6280000 : nvlddmkm+0x16299a
ffffe10f`7b71ef08 ffff820d`0f2e0000     : 00000000`00000000 00000000`00000001 ffff820d`f6280000 fffff804`5be8dfc8 : 0xffff820d`f6280000
ffffe10f`7b71ef10 00000000`00000000     : 00000000`00000001 ffff820d`f6280000 fffff804`5be8dfc8 ffffe10f`7b71efa0 : 0xffff820d`0f2e0000


SYMBOL_NAME:  nvlddmkm+16299a

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .cxr 0xffffe10f7b71e500 ; kb

BUCKET_ID_FUNC_OFFSET:  16299a

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

*******************************************************************************
*                                                                             *
*                        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: fffff8057f3e299a, The address that the exception occurred at
Arg3: ffffea88b1df6cc8, Exception Record Address
Arg4: ffffea88b1df6500, Context Record Address

Debugging Details:
------------------
KEY_VALUES_STRING: 1

    Key  : AV.Dereference
    Value: NullClassPtr

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 11843

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-70T822T

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 91132

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

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

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8057f3e299a

BUGCHECK_P3: ffffea88b1df6cc8

BUGCHECK_P4: ffffea88b1df6500

EXCEPTION_RECORD:  ffffea88b1df6cc8 -- (.exr 0xffffea88b1df6cc8)
ExceptionAddress: fffff8057f3e299a (nvlddmkm+0x000000000016299a)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000080
Attempt to read from address 0000000000000080

CONTEXT:  ffffea88b1df6500 -- (.cxr 0xffffea88b1df6500)
rax=0000000000000000 rbx=ffffb0028baa8000 rcx=0000000000000000
rdx=0000000000000001 rsi=ffffb0028bad9000 rdi=0000000000001000
rip=fffff8057f3e299a rsp=ffffea88b1df6f00 rbp=0000000000000000
 r8=0000000000000001  r9=0000000000000020 r10=ffffb0028790ac80
r11=ffffea88b1df6dd0 r12=ffffb0028bb57b48 r13=0000000000000001
r14=ffffb0028b9fa820 r15=ffffb0028b9bf000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050286
nvlddmkm+0x16299a:
fffff805`7f3e299a 83b98000000001  cmp     dword ptr [rcx+80h],1 ds:002b:00000000`00000080=????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

READ_ADDRESS: fffff805646fa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8056460f330: Unable to get Flags value from nt!KdVersionBlock
fffff8056460f330: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
 0000000000000080

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

EXCEPTION_STR:  0xc0000005

STACK_TEXT: 
ffffea88`b1df6f00 ffffb002`8baa8000     : ffffb002`0f2e0000 00000000`00000000 00000000`00000001 ffffb002`8baa8000 : nvlddmkm+0x16299a
ffffea88`b1df6f08 ffffb002`0f2e0000     : 00000000`00000000 00000000`00000001 ffffb002`8baa8000 fffff805`7f84dfc8 : 0xffffb002`8baa8000
ffffea88`b1df6f10 00000000`00000000     : 00000000`00000001 ffffb002`8baa8000 fffff805`7f84dfc8 ffffea88`b1df6fa0 : 0xffffb002`0f2e0000


SYMBOL_NAME:  nvlddmkm+16299a

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .cxr 0xffffea88b1df6500 ; kb

BUCKET_ID_FUNC_OFFSET:  16299a

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
---------
 
En kısa zamanda yapıp göndereceğim ama gönderdiğiniz sürücü yerine laptop ile gelen USB bellekteki sürücüyü kursam.
 
Monster'ın sürücüleri pek iyi olmuyor. Verdiğim link direkt olarak üreticinin sürücüsü ve en güncel sürücü oluyor bu. Dediklerimi uygularsanız sorun kalmaması gerek. Ha bu arada "Monster Kontrol Merkezi" sorun çıkartmış ama kullanıyorsunuz diye düşündüm ve belirtmedim. Kullanmıyorsanız ve kaldırılabiliyorsa kaldırın.
 
Tamamdır attığınızı kuracağım.
Kontrol merkezini kullanıyorum ve şöyle bir sorun gördüm riot un vanguard uygulaması monster kontrol merkezine ait bir sürücüyü (inpotx64) engeliyor ve olay görüntüleyicisindeki sistem bölümünde inpotx64 başlatılmadı hatası da aliyordum.
Söylediğiniz adımları yaptım.
Sfc ekran alıntısı:
Bugün tekrar critical process died hatası ile mavi ekran aldım ama minidump klasöründe dosyalar yok. Bende başlangıç ayarlarından kayıt yerini değiştirdim direkt C:\ Yaptım bu çözüm ile kayıt eder mi?

Yardımcı olursanız sevinirim sınavlara 1 hafta kala çok kötü oldu
 

Dosya Ekleri

  • sfc.PNG
    15,8 KB · Görüntüleme: 54
Son düzenleme:
Bu siteyi kullanmak için çerezler gereklidir. Siteyi kullanmaya devam etmek için çerezleri kabul etmelisiniz. Daha Fazlasını Öğren.…