R7 7800X3D işlemcili sistemde RAM'ler nasıl CL30 6000 MHz olarak kullanılır?

Amoemo

Çalışkan
Katılım
29 Mart 2025
Mesajlar
38
Beğeniler
4
Merhaba,

Sistemimdeki CL30 6400 MHz RAM işlemcime göre biraz üst seviye bir RAM. Bu RAM'de EXPO'yu 6400 MHz'de kullandığımda Memtest'te 10 bine yakın hata alıyorum ama EXPO'yu açıp 6000 MHz'e düşürdüğümde hata sayısı sıfırlanıyor. Asıl sorun şu ki bu RAM'de EXPO'yu açıp hızı 6000 MHz'e düşürdüğümde, Auto ayarda olmasına rağmen CPU SoC voltage 1.272v, MC voltage ise 1.424v olarak kalıyor. Yani voltaj ve DRAM timing dahil her şey 6400 MHz profiline göre yapılandırılmış kalıyor. Bu da sistemimde Micro stutter yaratıyor. Benim amacım bu RAM'leri CL30 6000 MHz kitlerinin ayarına getirmek. Bu RAM'leri EXPO açıkken kullanabilir miyim? Eğer EXPO açıkken kullanamazsam bu kiti CL30 6000 MHz kitleriyle aynı ayara getirmem için yapmam gereken ayarlar nedir?

Not: Bu RAM'leri 6400 MHz'de kullanmak istemiyorum lütfen bu işten anlayanlar bana CL30 6000 MHz kitleriyle bu kiti nasıl aynı ayara getireceğime dair yol göstersin.
  • AMD Ryzen 7 7800X3D.
  • ASUS Prime RTX 5070 Ti OC.
  • ASUS B850M Plus Wi-Fi anakart.
  • Corsair RM850e 850W 80+ Gold 140mm fanlı güç kaynağı.
  • G.Skill 32 GB (2x16 GB) Trident Z5 Neo 6400 MHz CL30 EXPO.
  • Kingston Renegade 2 TB PCI-e 4.0 NVMe M.2 SSD (7300 MB okuma / 7000 MB yazma)





























 
hocam occt de hata vermedi zentiming raporumda burada
 

Dosya Ekleri

  • Ekran görüntüsü 2025-10-26 142115.webp
    97,4 KB · Görüntüleme: 57
  • Ekran görüntüsü 2025-10-26 142054.webp
    87,2 KB · Görüntüleme: 52
hocam occt de hata vermedi zentiming raporumda burada
@Haluk Albayrak Gayet iyi, bundan sonrasına sen yardımcı olabilirsin aslında bu stabilse. Testmem önerebilirsin ekstra.

@Haluk Albayrak Bu arada ayrı bir konu aç, GDM Disabled deneyelim sen de. Bir de anti-cheat ve defender kapat, bu ZenTimings son sürümünde bile sağ kısımdaki voltajlar görünmüyor, biraz forum üzerinden ilerleyelim GDM Disable için

hocam occt de hata vermedi zentiming raporumda burada
@Amoemo Son durum nedir, RGB olayı düzelti mi, restart atınca ya da kapat aç yaptıktan sonra düzelmesi gerekiyor.

hocam occt de hata vermedi zentiming raporumda burada

@Amoemo Bu kısım hatalı, tWRWRSC 1 olacak yuvarlak içine aldığım timing, onu düzelt, 1 olmak zorunda o, yoksa performans kısıyor.
 
Son düzenleme:
tamam hocam her şey icin tesekkur ederim rgbler sanki bana oncesine gore biraz yavas hareket ediyor gibi geldi onun disinda valoranttaki saglam micro stutterlar devam ediyor latencymon testime gore sizce sorunum neyden kaynakli


ONCLUSION
_________________________________________________________________________________________________________
Your system seems to be having difficulty handling real-time audio and other tasks. You may experience drop outs, clicks or pops due to buffer underruns. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates.
LatencyMon has been analyzing your system for 0:09:38 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-RFC20Q1
OS version: Windows 11, 10.0, version 2009, build: 26100 (x64)
Hardware: System Product Name, ASUS
BIOS: 1087
CPU: AuthenticAMD AMD Ryzen 7 7800X3D 8-Core Processor
Logical processors: 16
Processor groups: 1
Processor group size: 16
RAM: 32418 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed (WMI): 4201 MHz
Reported CPU speed (registry): 420 MHz

Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.


_________________________________________________________________________________________________________
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_________________________________________________________________________________________________________
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.

Highest measured interrupt to process latency (µs): 1483,50
Average measured interrupt to process latency (µs): 7,044051

Highest measured interrupt to DPC latency (µs): 1466,90
Average measured interrupt to DPC latency (µs): 1,693139


_________________________________________________________________________________________________________
REPORTED ISRs
_________________________________________________________________________________________________________
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt Signal.

Highest ISR routine execution time (µs): 82,660
Driver with highest ISR routine execution time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation

Highest reported total ISR routine time (%): 0,000977
Driver with highest ISR total time: Wdf01000.sys - Çekirdek Modu Sürücü Çatısı Çalıştırma Zamanı, Microsoft Corporation

Total time spent in ISRs (%) 0,001599

ISR count (execution time <250 µs): 198826
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-1000 µs): 0
ISR count (execution time 1000-2000 µs): 0
ISR count (execution time 2000-4000 µs): 0
ISR count (execution time >=4000 µs): 0


_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

Highest DPC routine execution time (µs): 901,950
Driver with highest DPC routine execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation

Highest reported total DPC routine time (%): 0,046685
Driver with highest DPC total execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 581.29 , NVIDIA Corporation

Total time spent in DPCs (%) 0,076897

DPC count (execution time <250 µs): 892418
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 4
DPC count (execution time 1000-2000 µs): 0
DPC count (execution time 2000-4000 µs): 0
DPC count (execution time >=4000 µs): 0


_________________________________________________________________________________________________________
REPORTED HARD PAGEFAULTS
_________________________________________________________________________________________________________
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.

NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.

Process with highest pagefault count: steamwebhelper.exe

Total number of hard pagefaults 38586
Hard pagefault count of hardest hit process: 5170
Number of processes hit: 127


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 19,179433
CPU 0 ISR highest execution time (µs): 82,660
CPU 0 ISR total execution time (s): 0,147871
CPU 0 ISR count: 198826
CPU 0 DPC highest execution time (µs): 844,340
CPU 0 DPC total execution time (s): 6,577889
CPU 0 DPC count: 751361
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 5,406061
CPU 1 ISR highest execution time (µs): 0,0
CPU 1 ISR total execution time (s): 0,0
CPU 1 ISR count: 0
CPU 1 DPC highest execution time (µs): 163,460
CPU 1 DPC total execution time (s): 0,194912
CPU 1 DPC count: 37148
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 4,473307
CPU 2 ISR highest execution time (µs): 0,0
CPU 2 ISR total execution time (s): 0,0
CPU 2 ISR count: 0
CPU 2 DPC highest execution time (µs): 546,460
CPU 2 DPC total execution time (s): 0,146043
CPU 2 DPC count: 45949
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 3,628176
CPU 3 ISR highest execution time (µs): 0,0
CPU 3 ISR total execution time (s): 0,0
CPU 3 ISR count: 0
CPU 3 DPC highest execution time (µs): 59,560
CPU 3 DPC total execution time (s): 0,040821
CPU 3 DPC count: 12546
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 1,990761
CPU 4 ISR highest execution time (µs): 0,0
CPU 4 ISR total execution time (s): 0,0
CPU 4 ISR count: 0
CPU 4 DPC highest execution time (µs): 901,950
CPU 4 DPC total execution time (s): 0,011171
CPU 4 DPC count: 3443
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 1,954903
CPU 5 ISR highest execution time (µs): 0,0
CPU 5 ISR total execution time (s): 0,0
CPU 5 ISR count: 0
CPU 5 DPC highest execution time (µs): 50,730
CPU 5 DPC total execution time (s): 0,007458
CPU 5 DPC count: 2270
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 3,156860
CPU 6 ISR highest execution time (µs): 0,0
CPU 6 ISR total execution time (s): 0,0
CPU 6 ISR count: 0
CPU 6 DPC highest execution time (µs): 53,160
CPU 6 DPC total execution time (s): 0,020155
CPU 6 DPC count: 6454
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 3,014194
CPU 7 ISR highest execution time (µs): 0,0
CPU 7 ISR total execution time (s): 0,0
CPU 7 ISR count: 0
CPU 7 DPC highest execution time (µs): 54,490
CPU 7 DPC total execution time (s): 0,013841
CPU 7 DPC count: 4079
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 4,003453
CPU 8 ISR highest execution time (µs): 0,0
CPU 8 ISR total execution time (s): 0,0
CPU 8 ISR count: 0
CPU 8 DPC highest execution time (µs): 60,0
CPU 8 DPC total execution time (s): 0,043038
CPU 8 DPC count: 13781
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 3,731006
CPU 9 ISR highest execution time (µs): 0,0
CPU 9 ISR total execution time (s): 0,0
CPU 9 ISR count: 0
CPU 9 DPC highest execution time (µs): 59,020
CPU 9 DPC total execution time (s): 0,028464
CPU 9 DPC count: 6980
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 1,241393
CPU 10 ISR highest execution time (µs): 0,0
CPU 10 ISR total execution time (s): 0,0
CPU 10 ISR count: 0
CPU 10 DPC highest execution time (µs): 57,950
CPU 10 DPC total execution time (s): 0,006721
CPU 10 DPC count: 2005
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 1,231710
CPU 11 ISR highest execution time (µs): 0,0
CPU 11 ISR total execution time (s): 0,0
CPU 11 ISR count: 0
CPU 11 DPC highest execution time (µs): 49,790
CPU 11 DPC total execution time (s): 0,005243
CPU 11 DPC count: 1524
_________________________________________________________________________________________________________
CPU 12 Interrupt cycle time (s): 0,828002
CPU 12 ISR highest execution time (µs): 0,0
CPU 12 ISR total execution time (s): 0,0
CPU 12 ISR count: 0
CPU 12 DPC highest execution time (µs): 31,920
CPU 12 DPC total execution time (s): 0,004891
CPU 12 DPC count: 1504
_________________________________________________________________________________________________________
CPU 13 Interrupt cycle time (s): 0,834248
CPU 13 ISR highest execution time (µs): 0,0
CPU 13 ISR total execution time (s): 0,0
CPU 13 ISR count: 0
CPU 13 DPC highest execution time (µs): 34,920
CPU 13 DPC total execution time (s): 0,004354
CPU 13 DPC count: 1415
_________________________________________________________________________________________________________
CPU 14 Interrupt cycle time (s): 0,638301
CPU 14 ISR highest execution time (µs): 0,0
CPU 14 ISR total execution time (s): 0,0
CPU 14 ISR count: 0
CPU 14 DPC highest execution time (µs): 46,860
CPU 14 DPC total execution time (s): 0,004189
CPU 14 DPC count: 1126
_________________________________________________________________________________________________________
CPU 15 Interrupt cycle time (s): 0,644926
CPU 15 ISR highest execution time (µs): 0,0
CPU 15 ISR total execution time (s): 0,0
CPU 15 ISR count: 0
CPU 15 DPC highest execution time (µs): 40,950
CPU 15 DPC total execution time (s): 0,003949
CPU 15 DPC count: 837
 
@Ayhan Dönmez hocam cihazı teknik servise bıraktığımda bu ayarlar yüzünden işlemci ve ram garanti dışı kaldı dediler bu ayarlar güvenli değil miydi?
 
@Ayhan Dönmez hocam cihazı teknik servise bıraktığımda bu ayarlar yüzünden işlemci ve ram garanti dışı kaldı dediler bu ayarlar güvenli değil miydi?
Güvenli, ayarlarda problem yok, EXPO direkt garanti dışı bırakıyor, AMD yönergesi bu şekilde, sendeki sıkıntının bununla alakası yok ama EXPO ya da manuel OC yaptığını teknik ekiple paylaştıysan, kendileri bir sorun bulamadıysa bunu öne sürerler, aradan sıyrılırlar. Bu işlerden anlayan kalifiye eleman sayısı TR'de çok az var.

@Amoemo Senin kitten birisi arızalıdır, modüllerden birisi yani, en başından beri sorun odur muhtemelen. En başta da zaten hata var diye konu açmıştın, bu durumda G.Skill garantisi Vektron bakıyordu, oraya göndereceksin, iade/değişim yapacaklar, sen dersen ki ben OC falan yaptım, adamlar tabii ki garanti dışı kalmış diyecek, sorun onunla alakalı değil, en başından beri 1 tane stick, modül faulty, arızalı sende yani. Ona bir şey yapamazsın, içindeki IC'lerden çiplerden bir tanesi patlak yani. RAM'de tamir olmuyor, yenisiyle değişim olacak.
 
Son düzenleme:
Hocam ben garantiye şu latencymondaki gecikmeden dolayı komple sistemi vermiştim de sorunu bulamayınca oradaki 1,45V’a takılıp işlemci ve ramde oc tespit edilmiştir yazmışlar ama onlar ürünü Resmi distribütöre göndermemişler senin dediğin gibi büyük ihtimalle bilgisizler. Hocam senin dediğin ayarlarda ve ram 6000mhzdeyken memtestte hata vermedi ramde fiziksel sorun buna rağmen var mıdır ki? Bir de hocam teknik servis anlamıyor oradaki 1,45V a bakıp garanti dışıdır diyorlar senden ricam bana cl30 6000mhz kitin expo 1’deki default ayarlarını neyse bu kiti o ayarlara getirmeme yardımcı olman
 
1.45v EXPO profili olan kitler var, bilgisizler dediğim gibi, sendeki işlemlerle alakası yok ama BIOS default alıp göndermen lazımdı. Sende oyunlarda drop sorunu mevcut muydu, neden göndermiştin?
 
1.45v EXPO profili olan kitler var, bilgisizler dediğim gibi, sendeki işlemlerle alakası yok ama BIOS default alıp göndermen lazımdı. Sende oyunlarda drop sorunu mevcut muydu, neden göndermiştin?
Hocam bu latencymondaki gecikmeden dolayı vermiştimde bu kit expo ayarlardayken cl30 6400 mhz e göre ayarlı sizden ricam bunu cl30 6000 mhz kitlerin ayarına getirmeme yardımcı olmanız
 
Hocam bu latencymondaki gecikmeden dolayı vermiştimde bu kit expo ayarlardayken cl30 6400 mhz e göre ayarlı sizden ricam bunu cl30 6000 mhz kitlerin ayarına getirmeme yardımcı olmanız


@Amoemo BIOS güncelse bu şekilde ayarla EXPO1 aç, DRAM Timings içerisinden karşılıklarına böyle yaz. Nitro kısmı yine 1-2-1 olsun, öncesinde yaptırdığım gibi, lokasyon vermiştim. 1.4v yeterli 6000 CL28
 
Bu siteyi kullanmak için çerezler gereklidir. Siteyi kullanmaya devam etmek için çerezleri kabul etmelisiniz. Daha Fazlasını Öğren.…