Çözüldü R5 2600X FiveM oynarken mavi ekran hatası

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

Thursy

Megapat
Katılım
12 Ağustos 2016
Mesajlar
164
Çözümler
1
Selam, son birkaç gündür FiveM oynarken bazı noktalarda mavi ekran veriyor. Her türlü şeyi denedim ancak bir türlü çözüme kavuşamadım. Aşağıya sistem özelliklerini ve minidump dosyasını bırakıyorum.

Not: Aynı sistemde oyunu geçen senelerde sorunsuz bir şekilde oynuyordum ancak bu sene oynayamıyorum.

Sistem:
  • Ryzen 5 2600X
  • ASUS B450F
  • GTX 1060
  • G.Skill tridnet Z 2x8 3200 MHz RAM
  • Samsuns EVO 970 Plus
  • Windows 10 22H2 19045


Ekleme: Funmark ile 10 dakika hem ekran kartı, hem işlemci stress testi yaptım hiç bir problem yok.

Minidump
************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true AllowNugetMSCredentialProviderInstall : true AllowParallelInitializationOfLocalRepositories : true -- Configuring repositories ----> Repository : LocalInstalled, Enabled: true ----> Repository : UserExtensions, Enabled: true >>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds ************* Waiting for Debugger Extensions Gallery to Initialize ************** >>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.032 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 36 Microsoft (R) Windows Debugger Version 10.0.25921.1001 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\020424-7562-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 Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Kernel base = 0xfffff800`51400000 PsLoadedModuleList = 0xfffff800`5202a770 Debug session time: Sun Feb 4 17:59:13.346 2024 (UTC + 3:00) System Uptime: 0 days 1:18:48.021 Loading Kernel Symbols ............................................................... ................................................................ ............................................................. Loading User Symbols PEB is paged out (Peb.Ldr = 00000040`dcc84018). Type ".hh dbgerr001" for details Loading unloaded module list ........... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff800`517fd550 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffaf81`f013dda0=000000000000003d 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* INTERRUPT_EXCEPTION_NOT_HANDLED (3d) The exception handler for the kernel interrupt object interrupt management was not able to handle the generated exception. Arguments: Arg1: ffffaf81f013ed28, Exception Record (When Available) Arg2: ffffaf81f013e560, Context Record (When Available) Arg3: 0000000000000000, Not used Arg4: 0000000000000000, Not used Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : AV.Fault Value: Read Key : Analysis.CPU.mSec Value: 2984 Key : Analysis.Elapsed.mSec Value: 3539 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: 374 Key : Analysis.Init.Elapsed.mSec Value: 2582 Key : Analysis.Memory.CommitPeak.Mb Value: 95 Key : Bugcheck.Code.LegacyAPI Value: 0x3d Key : Failure.Bucket Value: 0x3D_C0000005_nt!KiCallInterruptServiceRoutine Key : Failure.Hash Value: {33679e11-230c-9496-3c04-01103275bbbc} Key : WER.OS.Branch Value: vb_release Key : WER.OS.Version Value: 10.0.19041.1 BUGCHECK_CODE: 3d BUGCHECK_P1: ffffaf81f013ed28 BUGCHECK_P2: ffffaf81f013e560 BUGCHECK_P3: 0 BUGCHECK_P4: 0 FILE_IN_CAB: 020424-7562-01.dmp EXCEPTION_RECORD: ffffaf81f013ed28 -- (.exr 0xffffaf81f013ed28) ExceptionAddress: fffff8005170098b (nt!KiCallInterruptServiceRoutine+0x000000000000020b) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: ffffffffffffffff CONTEXT: ffffaf81f013e560 -- (.cxr 0xffffaf81f013e560) rax=00000000000000a2 rbx=ffffd48a4df160e0 rcx=ffffd48a4df160e0 rdx=0000000000000000 rsi=ffffd48a4df160e0 rdi=0000000000000001 rip=fffff8005170098b rsp=ffffaf81f013ef60 rbp=fffff483547e2b80 r8=00000000003e8938 r9=0004000000000000 r10=ffffd48a59c97918 r11=0000000000000003 r12=0000000000000000 r13=0000000000000009 r14=0000000011b291f9 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010206 nt!KiCallInterruptServiceRoutine+0x20b: fffff800`5170098b 4180791000 cmp byte ptr [r9+10h],0 ds:002b:00040000`00000010=?? Resetting default scope BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: FiveM_b3095_GTAProcess.exe READ_ADDRESS: fffff800520fb390: 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_STR: 0xc0000005 STACK_TEXT: ffffaf81`f013ef60 fffff800`517ff53a : fffff483`547e2b80 ffffd48a`4df160e0 00000000`00000006 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x20b ffffaf81`f013efb0 fffff800`517ffd47 : ffffd48a`59c97080 000001f9`00000000 fffff483`00000000 ffffd48a`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa fffff483`547e2b00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37 SYMBOL_NAME: nt!KiCallInterruptServiceRoutine+20b MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.19041.3996 STACK_COMMAND: .cxr 0xffffaf81f013e560 ; kb BUCKET_ID_FUNC_OFFSET: 20b FAILURE_BUCKET_ID: 0x3D_C0000005_nt!KiCallInterruptServiceRoutine OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {33679e11-230c-9496-3c04-01103275bbbc} Followup: MachineOwner ---------
 
Son düzenleme:
Çözüm

Hocam mesajınızı yeni gördüm.

RAM'lerin XMP ayarı kapalıymış, açınca düzeldi herhangi bir hata vermedi.

Hocam mesajınızı yeni gördüm.

RAM'lerin XMP ayarı kapalıymış, açınca düzeldi herhangi bir hata vermedi.
 
Çözüm
Bu siteyi kullanmak için çerezler gereklidir. Siteyi kullanmaya devam etmek için çerezleri kabul etmelisiniz. Daha Fazlasını Öğren.…