Warzone oynarken mavi ekran hatası

TheWhitess · 24 Haziran 2023

Warzone oynarken mavi ekran alıyorum. Yardımcı olursanız sevinirim. Şimdiden teşekkürler.

062123-11281-01.dmp

drive.google.com

062323-10234-01.dmp

drive.google.com

EgeN7 · 24 Haziran 2023

Belirli bir süre oynadıktan sonra mı mavi ekran alıyorsunuz?

İşlemci / ekran kartı sıcaklıklarında bir problem var mı oyun içinde kontrol ettiniz mi?

İlk etapta oyun dosyalarının bütünlüğünü doğrulayın.

* Realtek ethernet sürücünüz 2019'dan kalma.

Rich (BB code):

start             end                 module name
fffff800`13140000 fffff800`131ed000   rt640x64   (deferred)         
    Mapped memory image file: C:\ProgramData\Dbg\sym\rt640x64.sys\5CE7AF86ad000\rt640x64.sys
    Image path: rt640x64.sys
    Image name: rt640x64.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri May 24 11:47:02 2019 (5CE7AF86)

Anakartınızda Realtek® 8111H ethernet kontrolcü var.

* Şu linkten güncel Windows 10 Realtek ethernet sürücüsünü indirin. Ama kurmayın.

Directly Download - REALTEK

* Denetim masası > program ekle/kaldırdan eski Realtek ethernet sürücüsünü silin.
* PC'yi yeniden başlatın.
* İndirdiğiniz güncel sürücüyü kurun.

* Ayrıca Windows eski görünüyor. Windows Update aracılığıyla tüm güncellemelerinizi tamamlayın.

* Windows güncellemesinden sonra CMD'yi yönetici olarak çalıştırıp şu komutları yazın:

SFC /scannow
DISM /Online /Cleanup-Image /RestoreHealth

Son olarak chkdsk /f /r komutunu yazın. Gelen soruya Y deyip enterlayın. PC'yi yeniden başlatın, tarama yapacak.

* Bu işlemlerden sonra tekrar mavi ekran alırsanız yeni dökümleri paylaşın.

Dökümler:

Kod:

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

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


KEY_VALUES_STRING: 1

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 1609

    Key  : Analysis.Elapsed.mSec
    Value: 2944

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1000007e

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: AV_nt!RtlCompressBufferXpressLzStandard

    Key  : Failure.Hash
    Value: {ecd29322-2063-7ed6-1d71-1cd65a0a5eee}


BUGCHECK_CODE:  7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80005cee5b4

BUGCHECK_P3: ffff8d0981cfb758

BUGCHECK_P4: ffff8d0981cfaf90

FILE_IN_CAB:  062123-11281-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

EXCEPTION_RECORD:  ffff8d0981cfb758 -- (.exr 0xffff8d0981cfb758)
ExceptionAddress: fffff80005cee5b4 (nt!RtlCompressBufferXpressLzStandard+0x0000000000000144)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  ffff8d0981cfaf90 -- (.cxr 0xffff8d0981cfaf90)
rax=000000000000041e rbx=ffffa484879544bb rcx=0000000000000081
rdx=ffffa48487945430 rsi=0000000000001000 rdi=000000000000020f
rip=fffff80005cee5b4 rsp=ffff8d0981cfb990 rbp=ffffa48485caf67c
 r8=8f613cb787953f4f  r9=ffffa48487954f29 r10=ffffa48485caf67c
r11=ffffa48485cb0000 r12=ffffa48487954f29 r13=ffffa48485caffd7
r14=ffffa48485caf68c r15=ffffa48487945028
iopl=0         nv up ei pl nz ac po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050216
nt!RtlCompressBufferXpressLzStandard+0x144:
fffff800`05cee5b4 413808          cmp     byte ptr [r8],cl ds:002b:8f613cb7`87953f4f=??
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  MemCompression

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

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

EXCEPTION_STR:  0xc0000005

STACK_TEXT:
ffff8d09`81cfb990 fffff800`05cee461     : ffffa484`87954f29 ffff8d09`81cfb900 ffffa484`85caf070 ffffa484`87953f4f : nt!RtlCompressBufferXpressLzStandard+0x144
ffff8d09`81cfba40 fffff800`05c583ef     : 00000000`c0000055 ffffbadd`6eb75a48 ffffa484`84481000 ffffa484`85edfe10 : nt!RtlCompressBufferXpressLz+0x61
ffff8d09`81cfbaa0 fffff800`05c550a2     : fffff800`06723eb0 00000000`84481070 ffffa484`84481028 ffffbad2`423f0128 : nt!RtlCompressBuffer+0x6f
ffff8d09`81cfbb00 fffff800`05c54eb6     : fffff800`06723eb0 fffff800`067239c0 fffff800`06723eb0 ffffa484`7e80d100 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmCompressCtxProcessEntry+0x92
ffff8d09`81cfbb90 fffff800`05d268f5     : ffffffff`fd050f80 ffffa484`83e44080 fffff800`05c54d40 ffffa484`87945000 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmCompressCtxWorkerThread+0x176
ffff8d09`81cfbc10 fffff800`05e04c68     : fffff800`00d43180 ffffa484`83e44080 fffff800`05d268a0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffff8d09`81cfbc60 00000000`00000000     : ffff8d09`81cfc000 ffff8d09`81cf6000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  nt!RtlCompressBufferXpressLzStandard+144

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.3086

STACK_COMMAND:  .cxr 0xffff8d0981cfaf90 ; kb

BUCKET_ID_FUNC_OFFSET:  144

FAILURE_BUCKET_ID:  AV_nt!RtlCompressBufferXpressLzStandard

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {ecd29322-2063-7ed6-1d71-1cd65a0a5eee}

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: ffffffffffffffb8, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 00000000000000ff, 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: fffff8050e084bcd, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1530

    Key  : Analysis.Elapsed.mSec
    Value: 1579

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xa

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: AV_CODE_AV_nt!PpmIdlePrepare

    Key  : Failure.Hash
    Value: {0722116b-c23b-c6c2-0c96-05693152d11a}


BUGCHECK_CODE:  a

BUGCHECK_P1: ffffffffffffffb8

BUGCHECK_P2: ff

BUGCHECK_P3: ff

BUGCHECK_P4: fffff8050e084bcd

FILE_IN_CAB:  062323-10234-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

WRITE_ADDRESS: fffff8050eafb390: 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
 ffffffffffffffb8

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  fffff98246a8b770 -- (.trap 0xfffff98246a8b770)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8050e084bcd rsp=fffff98246a8b900 rbp=0000000000000000
 r8=00000000ffffffff  r9=0000000000000000 r10=ffffa10727f0c200
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl zr na po nc
nt!PpmIdlePrepare+0x42d:
fffff805`0e084bcd 488b45b8        mov     rax,qword ptr [rbp-48h] ss:0018:ffffffff`ffffffb8=????????????????
Resetting default scope

STACK_TEXT:
fffff982`46a8b628 fffff805`0e210029     : 00000000`0000000a ffffffff`ffffffb8 00000000`000000ff 00000000`000000ff : nt!KeBugCheckEx
fffff982`46a8b630 fffff805`0e20bbe3     : fffff805`00000003 0000000c`1c9501e4 00000000`00000000 00000000`ffffffff : nt!KiBugCheckDispatch+0x69
fffff982`46a8b770 fffff805`0e084bcd     : ffffffff`ffffffff 00000000`00000000 00000000`0001312d ffffffff`ffffffff : nt!KiPageFault+0x463
fffff982`46a8b900 fffff805`0e0819f7     : 00000000`00000000 00001f80`00000008 00000000`00000000 00000000`00000000 : nt!PpmIdlePrepare+0x42d
fffff982`46a8baf0 fffff805`0e2008e4     : ffffffff`00000000 00000000`00000000 ffffd700`13d9b340 00000000`00001fb0 : nt!PoIdle+0x1f7
fffff982`46a8bc60 00000000`00000000     : fffff982`46a8c000 fffff982`46a86000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54


SYMBOL_NAME:  nt!PpmIdlePrepare+42d

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.3086

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  42d

FAILURE_BUCKET_ID:  AV_CODE_AV_nt!PpmIdlePrepare

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {0722116b-c23b-c6c2-0c96-05693152d11a}

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

alperyuksel4141 · 28 Ekim 2023

Sa geçmiş olsun, aynı sorunu bende yaşıyordum sorunun kaynağını buldum.
İşlemcim Ryzen 5 3600, BIOS'tan işlemci expert alınca mavi ekran, crash. Vb hatalar alıyordum, normale çekdim hiç sorun yaşamadım ancak işlemciyi tam performansda olmuyor oyunda FPS sorun oluyor bu sefer de, çözüm olarak uygun overclock ile olacağını zannediyorum. Bir denemende fayda var bana da garip geldi biraz, BIOS'u default yaparak çözdüm.İşlemcimiz aynıymış bu arada.

01arif · 24 Nisan 2025

************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToChakraJsProvider : false

-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

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

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.281 seconds

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

----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 44

Microsoft (R) Windows Debugger Version 10.0.27829.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\AseL\Desktop\042425-7031-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff807`5f400000 PsLoadedModuleList = 0xfffff807`6002a350
Debug session time: Thu Apr 24 17:39:47.056 2025 (UTC + 3:00)
System Uptime: 0 days 23:24:21.690
Loading Kernel Symbols
...............................................................
................................................................
................................................
Loading User Symbols

Loading unloaded module list
...............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`5f7fdf30 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffd0e`a988b630=000000000000000a
8: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
................................................
Loading User Symbols

Loading unloaded module list
...............
*******************************************************************************

*
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: 00000000000001f0, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 00000000000000ff, 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: fffff8075f6415e7, address which referenced memory

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1328

Key : Analysis.Elapsed.mSec
Value: 5839

Key : Analysis.IO.Other.Mb
Value: 17

Key : Analysis.IO.Read.Mb
Value: 1

Key : Analysis.IO.Write.Mb
Value: 19

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

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

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

Key : Analysis.Version.DbgEng
Value: 10.0.27829.1001

Key : Analysis.Version.Description
Value: 10.2503.24.01 amd64fre

Key : Analysis.Version.Ext
Value: 1.2503.24.1

Key : Bugcheck.Code.LegacyAPI
Value: 0xa

Key : Bugcheck.Code.TargetModel
Value: 0xa

Key : Dump.Attributes.AsUlong
Value: 0x8

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Failure.Bucket
Value: AV_CODE_AV_nt!PpmIdlePrepare

Key : Failure.Exception.IP.Address
Value: 0xfffff8075f6415e7

Key : Failure.Exception.IP.Module
Value: nt

Key : Failure.Exception.IP.Offset
Value: 0x2415e7

Key : Failure.Hash
Value: {0722116b-c23b-c6c2-0c96-05693152d11a}

BUGCHECK_CODE: a

BUGCHECK_P1: 1f0

BUGCHECK_P2: ff

BUGCHECK_P3: ff

BUGCHECK_P4: fffff8075f6415e7

FILE_IN_CAB: 042425-7031-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

FAULTING_THREAD: ffffc281199f6340

WRITE_ADDRESS: fffff807600fb390: 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
00000000000001f0

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffffd0e`a988b628 fffff807`5f8127a9 : 00000000`0000000a 00000000`000001f0 00000000`000000ff 00000000`000000ff : nt!KeBugCheckEx
fffffd0e`a988b630 fffff807`5f80e178 : 00000003`00000000 000000c4`3111a1b6 00000000`00000000 ffffe583`10cbd100 : nt!KiBugCheckDispatch+0x69
fffffd0e`a988b770 fffff807`5f6415e7 : 00000000`00000000 00000000`00989680 00000000`00000000 00000000`02cbad82 : nt!KiPageFault+0x478
fffffd0e`a988b900 fffff807`5f63e6b7 : 00000000`00000000 00001f80`00000000 00000000`00000003 00000000`00000002 : nt!PpmIdlePrepare+0x167
fffffd0e`a988baf0 fffff807`5f8029e4 : ffffffff`00000000 ffffc281`199f6340 ffffe583`164bb080 00000000`00000948 : nt!PoIdle+0x1f7
fffffd0e`a988bc60 00000000`00000000 : fffffd0e`a988c000 fffffd0e`a9886000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54

SYMBOL_NAME: nt!PpmIdlePrepare+167

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.5737

STACK_COMMAND: .process /r /p 0xfffff80760124a00; .thread 0xffffc281199f6340 ; kb

BUCKET_ID_FUNC_OFFSET: 167

FAILURE_BUCKET_ID: AV_CODE_AV_nt!PpmIdlePrepare

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {0722116b-c23b-c6c2-0c96-05693152d11a}

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

8: kd> .process /r /p 0xfffff80760124a00; .thread 0xffffc281199f6340 ; kb
Implicit process is now fffff807`60124a00
Loading User Symbols
Unable to get PEB pointer
Implicit thread is now ffffc281`199f6340
*** Stack trace for last set context - .thread/.cxr resets it
# RetAddr : Args to Child : Call Site
00 fffff807`5f8127a9 : 00000000`0000000a 00000000`000001f0 00000000`000000ff 00000000`000000ff : nt!KeBugCheckEx
01 fffff807`5f80e178 : 00000003`00000000 000000c4`3111a1b6 00000000`00000000 ffffe583`10cbd100 : nt!KiBugCheckDispatch+0x69
02 fffff807`5f6415e7 : 00000000`00000000 00000000`00989680 00000000`00000000 00000000`02cbad82 : nt!KiPageFault+0x478
03 fffff807`5f63e6b7 : 00000000`00000000 00001f80`00000000 00000000`00000003 00000000`00000002 : nt!PpmIdlePrepare+0x167
04 fffff807`5f8029e4 : ffffffff`00000000 ffffc281`199f6340 ffffe583`164bb080 00000000`00000948 : nt!PoIdle+0x1f7
05 00000000`00000000 : fffffd0e`a988c000 fffffd0e`a9886000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54
8: kd> .thread /r /p ffffc281199f6340
Implicit thread is now ffffc281`199f6340
Implicit process is now ffffe583`0a8d0080
Loading User Symbols

arkadaslar bunu okuyabilen varsa yardımcı olabilir mi sürekli mavi ekran veriyor hata neyden kaynaklı acaba

Warzone oynarken mavi ekran hatası

Ayrıntılı düzenleme

TheWhitess

Hectopat

062123-11281-01.dmp

062323-10234-01.dmp

EgeN7

Gigapat

alperyuksel4141

Femtopat

01arif

Yoctopat

Benzer konular

Technopat Haberler

Yeni konular

Yeni mesajlar

Gizliliğinize önem veriyoruz