Çözüldü RX 5700 sistemde IRQL_NOT_LESS_OR_EQUAL hatası

Bu konu çözüldü olarak işaretlenmiştir. Çözülmediğini düşünüyorsanız konuyu rapor edebilirsiniz.

Belgarath

Hectopat
Katılım
21 Mart 2019
Mesajlar
154
Daha fazla  
Cinsiyet
Erkek
Ryzen 5 3600 - MSI AMD Radeon RX 5700 - Corsair DDR4 1800 2 RAM CL18 - PNY CS3030 - MSI B450M Gaming Plus
Bütün driverlar Update. RAM ve Disk testleri yapıldı ama gene de aşağıda ki gibi mavi ekranlar alıyorum. Bir ara 6 gün olmadı, o süre zarfında XMP kapalıydı, onunla ilgisi var mı bilmiyorum. Virüs programı Kaspersky. Malwerbyte da vardı, onu sildim. Bütün BIOS sürümlerinde denedim bu arada.

Ekran Görüntüsü (117).png


Ryzen 5 3600 - MSI AMD Radeon RX 5700 - Corsair DDR4 1800 2 RAM CL18 - PNY CS3030 - MSI B450M Gaming Plus
Sonuncu bu:

Ekran Görüntüsü (118).png
 
Son düzenleyen: Moderatör:
Çözüm
Ekran kartını DDU ile kaldırdığına rağmen ekran kartı ile alakalı mavi ekran almışsın. Ekran kartın arızalı olabilir hatta VRAM arızası olabileceğini düşünüyorum.
Radeon Software üzerinden voltaj oynaması yapmayın. Şu adımları dene;
AMD Cleanup Utility ile aynı DDU gibi ekran kartı sürücüsünü tekrar kaldırın. Bazen DDU tam temizleme yapmadığına şahit olduğumdan DDU yerine AMD yazılımı ile kaldırın.
En güncel sürücüyü tekrar AMD sitesinden indirin. Radeon ayarları ile hiç oynama yapmayın. Voltaj değerleri ile vs... Birkaç mesaj önce yap demiştim ya artık ellemeyin.
Timespy testi indirip testi gerçekleştirin. Test 10-15 dk civarı sürmektedir ayrıca test bittikten sonra tekrar test işlemini çalıştırın. İki kere üst üste yapın yani yeniden başlatma, siyah ekran veya mavi ekran sorunu olup olmadığını bildirin.
Tüm bu adımları yaptıktan sonra son olarak OCCT üzerinden VRAM testi gerçekleştirin.

1625649846903.png


Not: 10-15 Dakika civarı yeterlidir. Güç kaynağı yerine VRAM seçeceksin.
Kod:
9: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8065b24790a, The address that the exception occurred at
Arg3: fffffe81a9a52be8, Exception Record Address
Arg4: fffffe81a9a52400, Context Record Address

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


KEY_VALUES_STRING: 1

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 2952

    Key  : Analysis.Elapsed.mSec
    Value: 3007

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1000007e

    Key  : Failure.Bucket
    Value: AV_amdkmdag!unknown_function

    Key  : Failure.Hash
    Value: {c753a2f9-94a6-448f-1d0e-e079b3442215}

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Version
    Value: 10.0.22621.1


BUGCHECK_CODE:  7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8065b24790a

BUGCHECK_P3: fffffe81a9a52be8

BUGCHECK_P4: fffffe81a9a52400

FILE_IN_CAB:  062023-4875-01.dmp

EXCEPTION_RECORD:  fffffe81a9a52be8 -- (.exr 0xfffffe81a9a52be8)
ExceptionAddress: fffff8065b24790a (amdkmdag+0x000000000011790a)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 00000000000008aa
Attempt to read from address 00000000000008aa

CONTEXT:  fffffe81a9a52400 -- (.cxr 0xfffffe81a9a52400)
rax=0000000000000000 rbx=ffffb58cfc456900 rcx=000000000000088a
rdx=0000000000000000 rsi=fffffe81a9a53080 rdi=0000000000000000
rip=fffff8065b24790a rsp=fffffe81a9a52e28 rbp=000000000000088a
 r8=ffffd985f0dc4f10  r9=0000000000000014 r10=0000fffff8065b22
r11=ffffb6ff2ba00000 r12=ffffb58cfbed2000 r13=00000000c0000001
r14=fffffe81a9a530b8 r15=0000000000000000
iopl=0         nv up ei ng nz ac po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050297
amdkmdag+0x11790a:
fffff806`5b24790a 488b44c120      mov     rax,qword ptr [rcx+rax*8+20h] ds:002b:00000000`000008aa=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

READ_ADDRESS: fffff8062e11c468: 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
 00000000000008aa

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:  00000000000008aa

EXCEPTION_STR:  0xc0000005

STACK_TEXT: 
fffffe81`a9a52e28 fffff806`5b223ed4     : ffffb58c`fc456900 ffffb58d`03f33a20 00000000`00000001 fffff806`5b2246b7 : amdkmdag+0x11790a
fffffe81`a9a52e30 ffffb58c`fc456900     : ffffb58d`03f33a20 00000000`00000001 fffff806`5b2246b7 00000000`00000000 : amdkmdag+0xf3ed4
fffffe81`a9a52e38 ffffb58d`03f33a20     : 00000000`00000001 fffff806`5b2246b7 00000000`00000000 fffffe81`a9a53080 : 0xffffb58c`fc456900
fffffe81`a9a52e40 00000000`00000001     : fffff806`5b2246b7 00000000`00000000 fffffe81`a9a53080 fffffe81`a9a53260 : 0xffffb58d`03f33a20
fffffe81`a9a52e48 fffff806`5b2246b7     : 00000000`00000000 fffffe81`a9a53080 fffffe81`a9a53260 00000000`00000000 : 0x1
fffffe81`a9a52e50 00000000`00000000     : fffffe81`a9a53080 fffffe81`a9a53260 00000000`00000000 ffffb58d`03e57760 : amdkmdag+0xf46b7


SYMBOL_NAME:  amdkmdag+11790a

MODULE_NAME: amdkmdag

IMAGE_NAME:  amdkmdag.sys

STACK_COMMAND:  .cxr 0xfffffe81a9a52400 ; kb

BUCKET_ID_FUNC_OFFSET:  11790a

FAILURE_BUCKET_ID:  AV_amdkmdag!unknown_function

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c753a2f9-94a6-448f-1d0e-e079b3442215}

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

Kalkmıştır diye düşünüyorum, görev yöneticisinde herhangi bir işlem var mı MSI Center ile ilgili?

Microsoft Store uygulamasını mı kullanıyordunuz?

Eki Görüntüle 1826846


Eğer öyleyse aşağıdaki linkten kaldırma aracını indirebilirsiniz.

Tamamdır, tamamen sildim, görev yöneticisinden de kontrol ettim. Umarım sorun çözülmüştür. Bir süre bekleyelim, sonucu yazacağım. Cooler master masterbox mb511 kasayı mysticlight ile rgb ayarlıyordum, başka bir yol bulmak gerekecek şimdi.
 
Evet MSI Center bazı sistemler için yararlı bir uygulama ancak ismi Dragon Center'ken çıkardığı rezilliklerden haberdarsınızdır. Rezillik seviyesi eskisi kadar fazla olmasa da günümüzde de bazı problemler yaratmaya devam ediyor belli ki.

Dediğim gibi güncel olmayabilir, sürücüleri bozulmuş olabilir veya sisteminizdeki başka yazılım veya sürücülerden biriyle çakışıyor olabilir.

Emin olmak için de en mantıklı aksiyon bu yazılımı sistemden tamamen kaldırmak.
 
Arka planda WinRing0x64.sys, CorsairVHidD.sys var.

Biri Corsair araçlarına ait, diğeri ise tam olarak hangi araca ait bilmiyorum.

Name:WinRing0x64.sys
Info:many different programs that center around the using of the WinRing libraries (RealTemp, Corsair Link2, Razer GameBooster, Intel Processor Diagnostic Tool, Fusiontweaker (Google Code), etc)
Source:OEM - none at http://www.python.org/emacs/winring/

Bu sürücüyü kullanabilecek üçüncü parti araçları kaldırın.
Corsair araçlarını da kaldırın.

Hatta her ihtimale karşı diskinizde de aratın bu sürücüleri. Hepsini kaldırın gitsin.

Biliyorum kullandığınız programları kaldırmaya başladık ama sorunu net olarak anlamamız lazım.

Kaldırın.
Arka planda çalışmasınlar.
Görev yöneticisini de kontrol edin mutlaka.

Yine bir dxgmms2.sys timestamp hatası var ama bu sembol farklılığından kaynaklanıyor olabilir.

Kod:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8024cc358bb, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ExceptionRecord                               ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ContextRecord                                 ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ExceptionRecord                               ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ContextRecord                                 ***
***                                                                   ***
*************************************************************************
*** WARNING: Check Image - Checksum mismatch - Dump: 0x127dc4, File: 0x127c0e - C:\ProgramData\Dbg\sym\dxgmms2.sys\FF1BB511117000\dxgmms2.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2906

    Key  : Analysis.Elapsed.mSec
    Value: 4235

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

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

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

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0x1e

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1e

    Key  : Failure.Bucket
    Value: AV_R_nt!SwapContext

    Key  : Failure.Hash
    Value: {73940a07-e238-0cb7-73a8-c9e01fdee4d3}

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Version
    Value: 10.0.22621.1


BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8024cc358bb

BUGCHECK_P3: 0

BUGCHECK_P4: ffffffffffffffff

FILE_IN_CAB:  061923-5093-01.dmp

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: fffff8024d51c468: 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

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  FallGuys_client_game.exe

STACK_TEXT:
ffffa401`626c60e8 fffff802`4cd651ea     : 00000000`0000001e ffffffff`c0000005 fffff802`4cc358bb 00000000`00000000 : nt!KeBugCheckEx
ffffa401`626c60f0 fffff802`4cc374f2     : ffffa401`626c6900 ffffa401`626c61c0 fffff802`4c800000 fffff802`4cc31156 : nt!HvlpVtlCallExceptionHandler+0x22
ffffa401`626c6130 fffff802`4ca4a0d3     : ffffb40e`450e6c00 ffffb40e`450e69c8 fffff802`4cc31156 fffff802`4c8f2fd0 : nt!RtlpExecuteHandlerForException+0x12
ffffa401`626c6160 fffff802`4cb13efe     : ffffffff`ffffffff ffffb40e`450e6a70 ffffb40e`450e6a70 ffffa401`626c6900 : nt!RtlDispatchException+0x2f3
ffffa401`626c68d0 fffff802`4cc2d442     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x1ae
ffffa401`626c6fb0 fffff802`4cc2d410     : fffff802`4cc419f5 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxExceptionDispatchOnExceptionStack+0x12
ffffb40e`450e6888 fffff802`4cc419f5     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatchOnExceptionStackContinue
ffffb40e`450e6890 fffff802`4cc3ca83     : fffff802`4cc281a0 fffff802`4cb2244a 00000080`46c1212c 00000000`00000000 : nt!KiExceptionDispatch+0x135
ffffb40e`450e6a70 fffff802`4cc358bb     : ffffa401`626a2180 ffffb88f`859a5080 ffffb88f`7c8663c0 fffff802`4cc3103a : nt!KiGeneralProtectionFault+0x343
ffffb40e`450e6c00 fffff802`4cc31156     : 00000000`00001440 00000000`00000000 ffffb88f`73d79040 ffffb88f`859a5080 : nt!SwapContext+0xcb
ffffb40e`450e6c40 00000000`00000000     : ffffb40e`450e7000 ffffb40e`450e1000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x176


SYMBOL_NAME:  nt!SwapContext+cb

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.1848

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  cb

FAILURE_BUCKET_ID:  AV_R_nt!SwapContext

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {73940a07-e238-0cb7-73a8-c9e01fdee4d3}

Followup:     MachineOwner
---------
 
Son düzenleme:
Ekran kartını DDU ile kaldırdığına rağmen ekran kartı ile alakalı mavi ekran almışsın. Ekran kartın arızalı olabilir hatta VRAM arızası olabileceğini düşünüyorum.
Radeon Software üzerinden voltaj oynaması yapmayın. Şu adımları dene;
AMD Cleanup Utility ile aynı DDU gibi ekran kartı sürücüsünü tekrar kaldırın. Bazen DDU tam temizleme yapmadığına şahit olduğumdan DDU yerine AMD yazılımı ile kaldırın.
En güncel sürücüyü tekrar AMD sitesinden indirin. Radeon ayarları ile hiç oynama yapmayın. Voltaj değerleri ile vs... Birkaç mesaj önce yap demiştim ya artık ellemeyin.
Timespy testi indirip testi gerçekleştirin. Test 10-15 dk civarı sürmektedir ayrıca test bittikten sonra tekrar test işlemini çalıştırın. İki kere üst üste yapın yani yeniden başlatma, siyah ekran veya mavi ekran sorunu olup olmadığını bildirin.
Tüm bu adımları yaptıktan sonra son olarak OCCT üzerinden VRAM testi gerçekleştirin.

1625649846903.png


Not: 10-15 Dakika civarı yeterlidir. Güç kaynağı yerine VRAM seçeceksin.
Kod:
9: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8065b24790a, The address that the exception occurred at
Arg3: fffffe81a9a52be8, Exception Record Address
Arg4: fffffe81a9a52400, Context Record Address

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


KEY_VALUES_STRING: 1

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 2952

    Key  : Analysis.Elapsed.mSec
    Value: 3007

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1000007e

    Key  : Failure.Bucket
    Value: AV_amdkmdag!unknown_function

    Key  : Failure.Hash
    Value: {c753a2f9-94a6-448f-1d0e-e079b3442215}

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Version
    Value: 10.0.22621.1


BUGCHECK_CODE:  7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8065b24790a

BUGCHECK_P3: fffffe81a9a52be8

BUGCHECK_P4: fffffe81a9a52400

FILE_IN_CAB:  062023-4875-01.dmp

EXCEPTION_RECORD:  fffffe81a9a52be8 -- (.exr 0xfffffe81a9a52be8)
ExceptionAddress: fffff8065b24790a (amdkmdag+0x000000000011790a)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 00000000000008aa
Attempt to read from address 00000000000008aa

CONTEXT:  fffffe81a9a52400 -- (.cxr 0xfffffe81a9a52400)
rax=0000000000000000 rbx=ffffb58cfc456900 rcx=000000000000088a
rdx=0000000000000000 rsi=fffffe81a9a53080 rdi=0000000000000000
rip=fffff8065b24790a rsp=fffffe81a9a52e28 rbp=000000000000088a
 r8=ffffd985f0dc4f10  r9=0000000000000014 r10=0000fffff8065b22
r11=ffffb6ff2ba00000 r12=ffffb58cfbed2000 r13=00000000c0000001
r14=fffffe81a9a530b8 r15=0000000000000000
iopl=0         nv up ei ng nz ac po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050297
amdkmdag+0x11790a:
fffff806`5b24790a 488b44c120      mov     rax,qword ptr [rcx+rax*8+20h] ds:002b:00000000`000008aa=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

READ_ADDRESS: fffff8062e11c468: 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
 00000000000008aa

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:  00000000000008aa

EXCEPTION_STR:  0xc0000005

STACK_TEXT: 
fffffe81`a9a52e28 fffff806`5b223ed4     : ffffb58c`fc456900 ffffb58d`03f33a20 00000000`00000001 fffff806`5b2246b7 : amdkmdag+0x11790a
fffffe81`a9a52e30 ffffb58c`fc456900     : ffffb58d`03f33a20 00000000`00000001 fffff806`5b2246b7 00000000`00000000 : amdkmdag+0xf3ed4
fffffe81`a9a52e38 ffffb58d`03f33a20     : 00000000`00000001 fffff806`5b2246b7 00000000`00000000 fffffe81`a9a53080 : 0xffffb58c`fc456900
fffffe81`a9a52e40 00000000`00000001     : fffff806`5b2246b7 00000000`00000000 fffffe81`a9a53080 fffffe81`a9a53260 : 0xffffb58d`03f33a20
fffffe81`a9a52e48 fffff806`5b2246b7     : 00000000`00000000 fffffe81`a9a53080 fffffe81`a9a53260 00000000`00000000 : 0x1
fffffe81`a9a52e50 00000000`00000000     : fffffe81`a9a53080 fffffe81`a9a53260 00000000`00000000 ffffb58d`03e57760 : amdkmdag+0xf46b7


SYMBOL_NAME:  amdkmdag+11790a

MODULE_NAME: amdkmdag

IMAGE_NAME:  amdkmdag.sys

STACK_COMMAND:  .cxr 0xfffffe81a9a52400 ; kb

BUCKET_ID_FUNC_OFFSET:  11790a

FAILURE_BUCKET_ID:  AV_amdkmdag!unknown_function

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c753a2f9-94a6-448f-1d0e-e079b3442215}

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

 
Çözüm
Hocam senin bellekte sorun var, durduk yere her programda çökemez bilgisayar.

Memtest86 yap, bize at.

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

Bazı programlarda da fonksiyon çağıramamış.

En sonda da RadeonSoftware.exe'den gitmişsiniz.

XMP ayarlarını değiştirdim demişsiniz, geri çekin bakalım ne olacak. Düzensizlik yaratıyor olabilir.
 
Son düzenleme:

Yeni konular

Geri
Yukarı