Çözüldü R5 2400G sistemde mavi ekran hatası

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

talhapmkc

Femtopat
Katılım
7 Ekim 2020
Mesajlar
14
Daha fazla  
Cinsiyet
Erkek
Sistem özellikleri.
R5 2400G.
Sapphire Pulse RX570 8 GB.
8 GB Adata XPG 3000MHz.
ASUS Prime B350M-A.

Oyunlarda bir anda donmanın ardından mavi ekran hatası alıyorum, bunun sebebi nedir?

-BIOS ve Windows 10 güncel.
-RAM'i Memtest86 ile test ettim sorun çıkmadı.
-Çipset sürücüsünü güncelledim.
-Disk i CrystalDiskInfo test ettim sonuç iyi çıktı.

Minidump dosyaları
 
Ekran badsa.PNG

Bu adresten indirin daha sonra kurun. Run'a basın ve sensör sekmesine tıklayın. İşlemciyi bulup ekran görüntüsü alıp atın.
bu olabilirmi
dadadds.PNG

dasdadsdasda.PNG
 
Avast kaldırınız. DDU ile ses ve ekran kartı sürücünüzü kaldırıp güncelini yükleyiniz. Valorant Anti-Cheat kaldırın. Memtest86 ile bellek testi yapınız.
Bu içeriği görüntülemek için üçüncü taraf çerezlerini yerleştirmek için izninize ihtiyacımız olacak.
Daha detaylı bilgi için, çerezler sayfamıza bakınız.
HDD Sentinel ile sistemde takılı olan disklerin sağlık durumunu paylaşınız.
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: fffff8003495d23a, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 9421

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 91054

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

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

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8003495d23a

BUGCHECK_P3: 0

BUGCHECK_P4: ffffffffffffffff

READ_ADDRESS: fffff80024afa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff80024a0f2e0: Unable to get Flags value from nt!KdVersionBlock
fffff80024a0f2e0: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
 ffffffffffffffff

EXCEPTION_PARAMETER2:  ffffffffffffffff

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  ForzaHorizon4.exe

STACK_TEXT: 
fffff583`652bb498 fffff800`2424e5b9     : 00000000`0000001e ffffffff`c0000005 fffff800`3495d23a 00000000`00000000 : nt!KeBugCheckEx
fffff583`652bb4a0 fffff800`24205fac     : 00000000`00000000 fffff800`308e68a7 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x1caa59
fffff583`652bbb60 fffff800`24201ce0     : ffff9c03`32b909e0 fffff800`247b2019 fffff583`00000210 00000000`00000004 : nt!KiExceptionDispatch+0x12c
fffff583`652bbd40 fffff800`3495d23a     : ffffba01`d2606840 fffff583`652bbfd9 ffffba01`d2643000 00000000`00000001 : nt!KiGeneralProtectionFault+0x320
fffff583`652bbed0 ffffba01`d2606840     : fffff583`652bbfd9 ffffba01`d2643000 00000000`00000001 00000000`00000001 : amdkmdag+0xad23a
fffff583`652bbed8 fffff583`652bbfd9     : ffffba01`d2643000 00000000`00000001 00000000`00000001 fffff583`652bc110 : 0xffffba01`d2606840
fffff583`652bbee0 ffffba01`d2643000     : 00000000`00000001 00000000`00000001 fffff583`652bc110 00000000`00000000 : 0xfffff583`652bbfd9
fffff583`652bbee8 00000000`00000001     : 00000000`00000001 fffff583`652bc110 00000000`00000000 00000000`00000000 : 0xffffba01`d2643000
fffff583`652bbef0 00000000`00000001     : fffff583`652bc110 00000000`00000000 00000000`00000000 fffff583`652bc0b0 : 0x1
fffff583`652bbef8 fffff583`652bc110     : 00000000`00000000 00000000`00000000 fffff583`652bc0b0 00000000`00000002 : 0x1
fffff583`652bbf00 00000000`00000000     : 00000000`00000000 fffff583`652bc0b0 00000000`00000002 00000000`00000000 : 0xfffff583`652bc110


SYMBOL_NAME:  amdkmdag+ad23a

MODULE_NAME: amdkmdag

IMAGE_NAME:  amdkmdag.sys

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  ad23a

FAILURE_BUCKET_ID:  0x1E_c0000005_R_amdkmdag!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {d944e40b-d5d3-e12a-86f9-ddcb8cf0c80c}

Followup:     MachineOwner
---------
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff802618cddcc, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4656

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 11013

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

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

BUGCHECK_P1: 10

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff802618cddcc

READ_ADDRESS: fffff802622fa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8026220f2e0: Unable to get Flags value from nt!KdVersionBlock
fffff8026220f2e0: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
 0000000000000010

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Discord.exe

IRP_ADDRESS: ffffcc88cd0dc488

TRAP_FRAME:  ffff9e04669db3f0 -- (.trap 0xffff9e04669db3f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffcc88cace9eb8 rbx=0000000000000000 rcx=00000000000000c8
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff802618cddcc rsp=ffff9e04669db588 rbp=ffffcc88ca860eb8
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=ffffcc88ca860eb8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!RtlRbRemoveNode+0x31c:
fffff802`618cddcc f6421001        test    byte ptr [rdx+10h],1 ds:00000000`00000010=??
Resetting default scope

STACK_TEXT: 
ffff9e04`669db2a8 fffff802`61a05e69     : 00000000`0000000a 00000000`00000010 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffff9e04`669db2b0 fffff802`61a02169     : 00000000`00000000 00000001`00000058 ffffe100`b8892180 ffffcc88`c8e2b080 : nt!KiBugCheckDispatch+0x69
ffff9e04`669db3f0 fffff802`618cddcc     : 0000002a`00130000 00010061`002a0000 fffff802`618cd943 00000000`0000002a : nt!KiPageFault+0x469
ffff9e04`669db588 fffff802`618cd943     : 00000000`0000002a ffffcc88`cd416c10 00000000`00000000 ffffcc88`cd416eb0 : nt!RtlRbRemoveNode+0x31c
ffff9e04`669db5a0 fffff802`618cd2b8     : ffffcc88`bb010280 ffffcc88`cd413000 ffffcc88`bb010280 ffff9e04`669db6a8 : nt!RtlpHpVsChunkCoalesce+0x183
ffff9e04`669db600 fffff802`618cbc44     : 00000000`00000000 00000000`00000000 00000000`00000000 ffffcc88`00000000 : nt!RtlpHpVsContextFree+0x188
ffff9e04`669db6a0 fffff802`61fb2019     : 00000000`00000290 00000000`00000001 ffffcc88`ccd22080 01000000`00100000 : nt!ExFreeHeapPool+0x4d4
ffff9e04`669db780 fffff802`618d32f6     : ffffcc88`cedccc30 fffff802`61fb2019 00000000`00000000 00000000`00000038 : nt!ExFreePool+0x9
ffff9e04`669db7b0 fffff802`618c8e9b     : ffffcc88`cedccc30 ffffcc88`c8246140 ffffcc88`c8cf4620 fffff802`61fb2019 : nt!IopFreeIrp+0x136
ffff9e04`669db7f0 fffff802`618e70d3     : ffffcc88`cd0dc500 00000000`00000001 ffffcc88`cd0dc5c0 ffffcc88`cedccc30 : nt!IopCompleteRequest+0x70b
ffff9e04`669db8b0 fffff802`61c428fd     : 00000000`00000000 00000000`00000000 ffffe100`b85ea180 fffff802`618c92ea : nt!IoRemoveIoCompletion+0x393
ffff9e04`669db9e0 fffff802`61a058b8     : ffffcc88`ccd22080 00000000`0e01f078 ffff9e04`669dbaa8 00000000`0ebf361c : nt!NtRemoveIoCompletion+0x13d
ffff9e04`669dba90 00000000`773e1cfc     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`0e01f058 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773e1cfc


SYMBOL_NAME:  nt!ExFreePool+9

IMAGE_NAME:  Pool_Corruption

IMAGE_VERSION:  10.0.19041.508

MODULE_NAME: Pool_Corruption

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  9

FAILURE_BUCKET_ID:  AV_nt!ExFreePool

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {2ae0a97e-dcd7-47ef-dbfb-430f2cbf58a1}

Followup:     Pool_corruption
---------*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

INTERNAL_POWER_ERROR (a0)
The power policy manager experienced a fatal error.
Arguments:
Arg1: 0000000000000107, A data mismatch has occurred in the internal hibernation data
    structures.
Arg2: 000000000000000a
Arg3: ffff9c0123ff65f0, POP_HIBER_CONTEXT
Arg4: 0000000000000000, PO_MEMORY_RANGE_ARRAY

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4546

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 17116

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

    Key  : Analysis.System
    Value: CreateObject


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

DUMP_FILE_ATTRIBUTES: 0x9
  Hiber Crash Dump
  Kernel Generated Triage Dump

BUGCHECK_CODE:  a0

BUGCHECK_P1: 107

BUGCHECK_P2: a

BUGCHECK_P3: ffff9c0123ff65f0

BUGCHECK_P4: 0

CUSTOMER_CRASH_COUNT:  1

STACK_TEXT: 
ffffd882`4c037488 fffff804`3899fa2f     : 00000000`000000a0 00000000`00000107 00000000`0000000a ffff9c01`23ff65f0 : nt!KeBugCheckEx
ffffd882`4c037490 fffff804`3899085e     : ffff8681`7b540180 fffff804`38380444 00070106`00070106 00000000`00000001 : nt!PopDecompressHiberBlocks+0x11157
ffffd882`4c0376b0 fffff804`389905c0     : 00000000`00000000 00000000`00000000 00000000`00000025 00000000`00000000 : nt!PopRestoreHiberContext+0x146
ffffd882`4c037740 fffff804`38990383     : fffff804`38c50460 ffffd882`4c037960 ffffd882`4c037b20 ffff9c01`274eabd0 : nt!PopHandleNextState+0x210
ffffd882`4c037790 fffff804`382e9a3e     : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : nt!PopInvokeStateHandlerTargetProcessor+0x53
ffffd882`4c037860 fffff804`382e8d24     : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x30e
ffffd882`4c0379d0 fffff804`383f7a0e     : ffffffff`00000000 ffff8681`7b540180 ffff8681`7b54b240 ffff9c01`315d2480 : nt!KiRetireDpcList+0x1f4
ffffd882`4c037c60 00000000`00000000     : ffffd882`4c038000 ffffd882`4c032000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME:  nt!PopDecompressHiberBlocks+11157

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.508

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  11157

FAILURE_BUCKET_ID:  0xa0_107_nt!PopDecompressHiberBlocks

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {5d9c83f4-ef2e-05d6-286b-9d88881fdb2f}

Followup:     MachineOwner
---------
 
İşlemcinin voltajı ile alakası yok yeniden mavi ekran alacaksınız. Dediklerini yapınız. Dosyalarda ekran kartı hatası da var.
Tekrar mavi ekran alırsanız dediklerimi yapınız.
 
O zaman tekrar mavi ekran alırsanız bu mesajımdan sonra paylaşırsınız. Üst üste iki mesaj atınca siz bana bildirim gelmiyor o yüzden.
 

Geri
Yukarı