Mavi Ekran hatası

HDD kullanıyorsanız HD Sentinel ile, SSD kullanıyorsanız Crystal Disk Info ile sağlık taraması yapın. HD Tune ile de Quick Scan ayarı kapalı bir şekilde hata taraması yapın. Wireless adaptörünüzün sürücülerini güncelleyin, modeli nedir? EAC'i kaldırın. Ayrıca belleklere de test yapın.

Daha dün yine yedim, bugün yine yedim. Artık oyunları kapatmaya başladı.

Minidump.rar

Bellek testi yaptınız mı yeni konu açmadan önce?

LesRich dedi:

Mavi ekran alıyorum, şu ana kadar 2 kere aldım. Minidump.rar

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

CrystalDiskInfo ile test yapın. Eğer sıkıntı yok ise belleklere hücüm edin. Tabii ki çoğu hatada olduğu gibi driver güncelleyin.

Recep Baltaş dedi:

Bellek testi yaptınız mı yeni konu açmadan önce?

Kod:Panoya kopyala

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

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


Could not read faulting driver name

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4327

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 7456

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

BUGCHECK_P1: fffffffffffffae8

BUGCHECK_P2: 0

BUGCHECK_P3: fffff806188e2b5b

BUGCHECK_P4: 2

READ_ADDRESS: fffff806192fa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8061920f2e0: Unable to get Flags value from nt!KdVersionBlock
fffff8061920f2e0: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
fffffffffffffae8

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Blitz.exe

TRAP_FRAME:  fffff38cd4013be0 -- (.trap 0xfffff38cd4013be0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffffffffffae8
rdx=000000006e457350 rsi=0000000000000000 rdi=0000000000000000
rip=fffff806188e2b5b rsp=fffff38cd4013d70 rbp=fffff38cd4014b80
r8=fffff38cd4013db0  r9=7fffcc0ddd8b7778 r10=7ffffffffffffffc
r11=000000000000003c r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
nt!ObReferenceObjectSafeWithTag+0xb:
fffff806`188e2b5b 488b01          mov     rax,qword ptr [rcx] ds:ffffffff`fffffae8=????????????????
Resetting default scope

STACK_TEXT:
fffff38c`d4013938 fffff806`18a86729     : 00000000`00000050 ffffffff`fffffae8 00000000`00000000 fffff38c`d4013be0 : nt!KeBugCheckEx
fffff38c`d4013940 fffff806`188eeb80     : 00000000`00000000 00000000`00000000 fffff38c`d4013c60 00000000`00000000 : nt!MiSystemFault+0x13faf9
fffff38c`d4013a40 fffff806`18a0205e     : 00000000`00000200 ffffcc0d`ce010340 00000000`00000110 00000000`00000000 : nt!MmAccessFault+0x400
fffff38c`d4013be0 fffff806`188e2b5b     : ffffcc0d`dd8b7920 ffffcc0d`dd8b7340 00000000`00028f80 00000000`00000000 : nt!KiPageFault+0x35e
fffff38c`d4013d70 fffff806`18cd3ec7     : ffffcc0d`d9e0e568 ffffcc0d`00000000 ffffcc0d`00000000 00000000`00000000 : nt!ObReferenceObjectSafeWithTag+0xb
fffff38c`d4013da0 fffff806`18cd6f13     : 00000000`00000000 fffff806`00010400 00000000`00000000 00000000`00000000 : nt!ExpGetProcessInformation+0xee7
fffff38c`d4014400 fffff806`18cd65f7     : fffff806`189eff90 fffff806`1883f03a ffffcc0d`dccd90c0 fffff38c`d4014b80 : nt!ExpQuerySystemInformation+0x7d3
fffff38c`d4014ac0 fffff806`18a058b8     : 00000000`00000000 00000000`0b5ef410 00000000`00000000 ffffcc0d`00000001 : nt!NtQuerySystemInformation+0x37
fffff38c`d4014b00 00007ffe`8a76c484     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`0039e0a8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`8a76c484


SYMBOL_NAME:  nt!ObReferenceObjectSafeWithTag+b

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.508

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  b

FAILURE_BUCKET_ID:  AV_R_INVALID_nt!ObReferenceObjectSafeWithTag

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {e0b9559d-d7ba-6fb0-6b40-14a8f2f2d0ac}

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: ffffe38089efde70
Arg3: ffff04e54ab800c0
Arg4: ffff81b39308c44c

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 5202

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 9392

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

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

BUGCHECK_P1: 8

BUGCHECK_P2: ffffe38089efde70

BUGCHECK_P3: ffff04e54ab800c0

BUGCHECK_P4: ffff81b39308c44c

TRAP_FRAME:  ffffe38089efde70 -- (.trap 0xffffe38089efde70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffbc040368c320 rbx=0000000000000000 rcx=ffffbc040351dea0
rdx=0000000000010000 rsi=0000000000000000 rdi=0000000000000000
rip=ffff81b39308c44c rsp=ffff04e54ab800c0 rbp=ffff830b4a54f120
r8=ffffbc040368c2c0  r9=0000000000000000 r10=0000ffff81b39309
r11=ffff830b4a54f400 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
win32kbase!CoreMessagingK::ServerPorts::Send+0x124:
ffff81b3`9308c44c 094c8b15        or      dword ptr [rbx+rcx*4+15h],ecx ds:fffef010`0d477a95=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  dwm.exe

BAD_STACK_POINTER:  ffff04e54ab800c0

MISALIGNED_IP:
win32kbase!CoreMessagingK::ServerPorts::Send+124
ffff81b3`9308c44c 094c8b15        or      dword ptr [rbx+rcx*4+15h],ecx

STACK_TEXT:
ffffe380`89efdd28 fffff801`83405e69     : 00000000`0000007f 00000000`00000008 ffffe380`89efde70 ffff04e5`4ab800c0 : nt!KeBugCheckEx
ffffe380`89efdd30 fffff801`83400c83     : 006f006c`0047005c 003f006c`00610062 cccccccc`0000003f cccccccc`cccccccc : nt!KiBugCheckDispatch+0x69
ffffe380`89efde70 ffff81b3`9308c44c     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0x2c3
ffff04e5`4ab800c0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32kbase!CoreMessagingK::ServerPorts::Send+0x124


SYMBOL_NAME:  win32kbase!CoreMessagingK::ServerPorts::Send+124

MODULE_NAME: hardware

IMAGE_NAME:  hardware

IMAGE_VERSION:  10.0.19041.508

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  IP_MISALIGNED_win32kbase.sys

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {1b8016c6-78a7-5881-8c18-2704f15d4870}

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

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

Bana da belleklerle ilgili geliyor.

Ya anlamıyorum bu aralar çok vermeye başladı bir ara RAM'leri çıkardım temizledim vs geri taktım sıkıntı yoktu bir süre sonra hata vermeye başladı hep farklı nedenlerle SSD vs HDD sağlam onlarda sıkıntı yok test yaptım şu an biraz işim var ondan sonra RAM'lere de test yapacağım
Driverlar güncel
Belleklerle ilgili herhangi bir problem yok neden olabilir yardımcı olur musunuz?
Bellekler sağlam