Memtest86 одна ошибка

Здравствуйте, эксперты!
Буквально час назад закончился 7 часовой тест моей оперативной памяти.
Тестировал с помощью MemTest86 V8.0 Pro (64-bit).

Программа выявила 1 ошибку в Test 7 после 4 прохода (на 5 часу тестирования):

Test — #Tests Passed — Errors
Test 7 [Moving inversions, 32-bit pattern] — 3/4 — (75%) — 1

В конце 18 года собрал новую машину

  • Ryzen 5 2600X,
  • Asus Tuf x470-plus,
  • RX580 Nitro+
  • и 32гб памяти от Kingston 4 плашки по 8 гб, 3200Mhz

Плашки брал по 2 комплекта по 16гб в разное время и у разных компаний (Xcom SPB b Юлмарт), но специально подбирал, чтобы совпадали коды производителя. К слову, плашики различаются только цветом — белые и черные.

Kingston HX432C18FW2K2/16 — белые (Xcom SPB).
Kingston HX432C18FB2K2/16 — черные (Юлмарт).

В момент замены железа, старый Windows 10 Pro 1809 (17763.292) не переустанавливал, просто переподключил SSD к новой мамке и радовался жизни. В какой-то момент начали молча вылетать игры, без предупреждения и уведомлений (BF4, FarCry, Battlerite + Manion Masters → игры на Unity 3d).

Покопавшись в Журнале событий Windows, нашел постоянно упоминающийся код ошибки 0xc0000005.

В рабочих программах, типа Photoshop, Axure RP, Word 365 и тем более обычно сёрфинге на 50+ вкладок + youtube, проблема не проявляется и работе не мешает.

Однако, я решил проверить память и вот какой результат:

Test Start Time 2019-02-01 05:23:44
Elapsed Time 7:10:58
Memory Range Tested 0x0 — 81F380000 (33267MB)
CPU Selection Mode Parallel (All CPUs)
ECC Polling Enabled
# Tests Passed 55/56 (98%)

Lowest Error Address 0x271E85104 (10014MB)
Highest Error Address 0x271E85104 (10014MB)
Bits in Error Mask 0000000080000000
Bits in Error 1
Max Contiguous Errors 1

2019-02-01 10:55:46 — [Data Error] Test: 7, CPU: 9, Address: 271E85104, Expected: 20000000, Actual: A0000000

Конфигурация ПК и спецификация памяти

EFI Specifications 2.60

BIOS
Vendor American Megatrends Inc.
Version 4207
Release Date 12/08/2018

Baseboard
Manufacturer ASUSTeK COMPUTER INC.
Product Name TUF X470-PLUS GAMING
Version Rev X.0x

CPU Type AMD Ryzen 5 2600X Six-Core
CPU Clock 3615 MHz [Turbo: 4242.9 MHz]
# Logical Processors 12
L1 Cache 12 x 96K (84153 MB/s)
L2 Cache 12 x 512K (81128 MB/s)
L3 Cache 1 x 16384K (32276 MB/s)

— — —

Memory 32713M (19622 MB/s)

DIMM Slot #0 8GB DDR4 XMP PC4-25600
Kingston / KHX3200C18D4/8G / 0F02A03A
18-21-21-39 / 3200 MHz / 1.200V

DIMM Slot #1 8GB DDR4 XMP PC4-25600
Kingston / KHX3200C18D4/8G / 543F927D
18-21-21-39 / 3200 MHz / 1.200V

DIMM Slot #2 8GB DDR4 XMP PC4-25600
Kingston / KHX3200C18D4/8G / 4F165326
18-21-21-39 / 3200 MHz / 1.200V

DIMM Slot #3 8GB DDR4 XMP PC4-25600
Kingston / KHX3200C18D4/8G / 4F165726
18-21-21-39 / 3200 MHz / 1.200V

— — —
Собственно, вопросы:

  1. Насколько критичная эта ошибка, в том плане, что она появилась единожды в последнем прогоне?
    Могла ли это быть … не знаю, случайная ошибка?
  2. Можно ли как-то локализовать проблему, есть ли шанс, что после переустановки Windows «с нуля», проблема исчезнет?
  3. Как эффективнее выявить «битую» плашку или придётся прогонять из раза в раз, вынимая плашки по очереди?

— — —

Troubleshooting Memory Errors

  • MemTest86 detected errors in my memory. Is there something wrong with my RAM?
    • Why am I only getting errors during Test 13 Hammer Test?
    • Why do I get errors only when testing RAM modules together, and not when individually tested?
  • MemTest86 reported the memory address of the failure. What does this mean?
    • How does MemTest86 report ECC errors?
    • If I know the address decoding scheme, can I configure MemTest86 to report the failing module?
  • How do I know which RAM module is failing?
  • How do I fix the memory errors?

Below is a video overview on how to troubleshoot bad RAM with MemTest86.

Download

Right-click to download, MP4 format, 9MB

MemTest86 detected errors in my memory. Is there something wrong with my
RAM?

Please be aware that not all errors reported by MemTest86 are due to bad memory. The
test implicitly tests the CPU, L1 and L2 caches as well as
the motherboard. It is impossible for the test to determine what causes the failure to
occur. However, most failures will be due to a problem
with memory module. When it is not, the only option is to replace parts until the
failure is corrected.

Sometimes memory errors show up due to component incompatibility. A memory module may
work fine in one system and not in another.
This is not uncommon and is a source of confusion. In these situations the components
are not necessarily bad but have marginal
conditions that when combined with other components will cause errors.

Often the memory works in a different system or the vendor insists that it is good. In
these cases the memory is not necessarily bad
but is not able to operate reliably at full speed. Sometimes more conservative memory
timings on the motherboard will correct these errors.
In other cases the only option is to replace the memory with better quality, higher
speed memory. Don’t buy cheap memory and expect it to work
reliably. On occasion «block move» test errors will occur even with name brand memory
and a quality motherboard. These errors are legitimate and
should be corrected.

All valid memory errors should be corrected. It is possible that a particular error will
never show up in normal operation. However, operating
with marginal memory is risky and can result in data loss and even disk corruption. Even
if there is no overt indication of problems you cannot
assume that your system is unaffected. Sometimes intermittent errors can cause problems
that do not show up for a long time. You can be sure that
Murphy will get you if you know about a memory error and ignore it.

We are often asked about the reliability of errors reported by MemTest86. In the vast
majority of cases errors reported by the test are valid.
There are some systems that cause MemTest86 to be confused about the size of memory and
it will try to test non-existent memory. This will cause a
large number of consecutive addresses to be reported as bad and generally there will be
many bits in error. If you have a relatively small number
of failing addresses and only one or two bits in error you can be certain that the
errors are valid. Also intermittent errors are without exception
valid. Frequently memory vendors question if MemTest86 supports their particular memory
type or a chipset. MemTest86 is designed to work with all
memory types and all chipsets.

MemTest86 cannot diagnose many types of PC failures. For example a faulty CPU that causes
Windows to crash will most likely just cause MemTest86 to crash in the same way.

Why am I only getting errors during Test 13 Hammer Test?

The Hammer Test is designed to detect RAM modules that are susceptible to disturbance
errors caused by charge leakage. This phenomenon is characterized
in the research paper
Flipping Bits in Memory
Without Accessing Them: An Experimental Study of DRAM Disturbance Errors
by
Yoongu Kim et al.
According to the research, a significant number of RAM modules manufactured 2010 or
newer are affected by this defect. In simple terms, susceptible RAM modules can be
subjected to disturbance errors
when repeatedly accessing addresses in the same memory bank but different rows in a
short period of time. Errors occur when the repeated access causes charge loss in a
memory cell, before the cell contents
can be refreshed at the next DRAM refresh interval.

Starting from MemTest86 v6.2, the user may see a warning indicating that the RAM may be
vulnerable to high frequency row hammer bit flips.
This warning appears when errors are detected during the first pass (maximum hammer
rate) but no errors are detected during the second pass (lower hammer rate).
See MemTest86 Test Algorithms for a description of
the two passes that are performed during the Hammer Test (Test 13).
When performing the second pass, address pairs are hammered only at the rate deemed as
the maximum allowable by memory vendors (200K accesses per 64ms).
Once this rate is exceeded, the integrity of memory contents may no longer be
guaranteed. If errors are detected in both passes, errors are reported as normal.

The errors detected during Test 13, albeit exposed only in extreme memory access cases,
are most certainly real errors. During typical home PC usage (eg. web browsing, word
processing, etc.),
it is less likely that the memory usage pattern will fall into the extreme case that
make it vulnerable to disturbance errors. It may be of greater concern if you were
running highly sensitive equipment
such as medical equipment, aircraft control systems, or bank database servers. It is
impossible to predict with any accuracy if these errors will occur in real life
applications. One would need
to do a major scientific study of 1000 of computers and their usage patterns, then do a
forensic analysis of each application to study how it makes use of the RAM while it
executes. To date, we have only
seen 1-bit errors as a result of running the Hammer Test.

There are several actions that can be taken when you discover that your RAM modules are
vulnerable to disturbance errors:

  • Do nothing
  • Replace the RAM modules
  • Use RAM modules with error-checking capabilities (eg. ECC)

Depending on your willingness to live with the possibility of these errors manifesting
itself as real problems,
you may choose to do nothing and accept the risk. For home use you may be willing to
live with the errors. In our experience, we have several machines that have been stable
for home/office use despite experiencing errors in the Hammer Test.

You may also choose to replace the RAM with modules that have been known to pass the
Hammer Test. Choose RAM modules of different brand/model as it is likely that the RAM
modules with the same model would still fail the Hammer test.

For sensitive equipment requiring high availability/reliability, you would replace the
RAM without question and would probably switch to RAM with error correction such as ECC
RAM. Even a 1-bit error can result in catastrophic consequences for say,
a bank account balance. Note that not all motherboards support ECC memory, so consult
the motherboard specifications before purchasing ECC RAM.

Detection and mitigation of row hammer errors

The ability of MemTest86 to detect and report on row hammer errors depends on several
factors and what mitigations are in place. To generate errors adjacent memory
rows must be repeatedly accessed. But hardware features such as multiple channels,
interleaving, scrambling,
Channel Hashing, NUMA & XOR schemes make it nearly impossible (for an arbitrary CPU &
RAM stick) to know which memory addresses correspond to which rows in the RAM.
Various mitigations might also be in place. Different BIOS firmware might set the
refresh interval to different values (tREFI). The shorter the interval the more
resistant the RAM will be to errors.
But shorter intervals result in higher power consumption and increased processing
overhead. Some CPUs also support pseudo target row refresh (pTRR) that can be used in
combination with pTRR-compliant RAM.
This field allows the RAM stick to indicate the MAC (Maximum Active Count) level which
is the RAM can support. A typical value might be 200,000 row activations.
Some CPUs also support the Joint Electron Design Engineering Council (JEDEC) Targeted
Row Refresh (TRR) algorithm. The TRR is an improved version of the previously
implemented
pTRR algorithm and does not inflict any performance drop or additional power usage.
As a result the row hammer test implemented in MemTest86 maybe not be the worst case
possible and vulnerabilities in the underlying RAM might be undetectable due to the
mitigations in
place in the BIOS and CPU.


Why do I get errors only when testing RAM modules together, and not
when individually tested?

Most memory systems nowadays operate in multiple channel mode in order to increase the
transfer rate between the RAM modules and the memory
controller. It is recommended that modules with identical specifications (ie. «matching
modules») when running in multi-channel mode. Some motherboards
also have compatibility issues with certain brand/models of RAM when running in
multi-channel mode.

When you see errors while running MemTest86 with multiple RAM modules installed, but not
when they are tested individually, it is likely that the multi-channel
configuration is the culprit. This could be due to mismatched RAM specifications, or
simply using brands/models of RAM that is incompatible with the motherboard.
Most motherboard vendors release a list of known compatible RAM models that have been
tested to work with your motherboard. Replace the modules with a matching set of
known good ones and see if you get better results.

MemTest86 reported the memory address of the failure. What does this
mean?

When MemTest86 detects errors during the memory tests, the memory address, actual and
expected data are reported to the user. The memory address is the location in system
memory where the data contained does not match what was expected.
This is the address that is specified by the CPU to the memory controller when
requesting data from DRAM. The memory controller then decodes this memory address to
identify the specific channel, DIMM, rank, DRAM chip, bank, row and column in DRAM using
a chipset-specific address decoding scheme.

The address decoding scheme is the process used by the memory controller to generate the
appropriate address signals to the DRAM chip. Depending on the memory controller, this
process can get fairly complex as it is not simply a a direct mapping of the system
address bits to the DRAM address bits. In order to increase
the memory performance, strategies such as channel interleaving (for Dual, Tri and Quad
channel setups), rank/bank/row interleaving, and address swizzling are used to increase
the concurrency of memory accesses. For some chipsets such as AMD, the address decoding
scheme can be configured/determined via PCI registers as
described in the chipset specifications. For other chipsets (eg. Intel), however, the
address decoding scheme is proprietary and not made available to the public. This makes
identifying the DRAM address and correspondingly, the failing module, much more
difficult. For that reason, MemTest86 only has the capability to report DRAM addresses
for supported hardware configurations.

How does MemTest86 report ECC errors?

Refer to ECC Technical Information for ECC reporting in MemTest86 and other ECC technical details.


If I know the address decoding scheme, can I configure MemTest86 to
report the failing module?

For systems where the address decoding scheme is known, MemTest86 provides several configuration file parameters to aid users in
determining the faulty module that corresponds to the memory address:

  ADDR2CHBITS=12,9,7
  ADDR2SLBITS=3,4
  ADDR2CSBITS=8

For each of these 3 parameters, a list of bit positions can be used to specify which
address bits of a memory address to exclusive-or (XOR) in order to determine the
corresponding [memory channel|slot|chip select (CS)] (0 or 1) of the failing module.
This is only useful if you know that the memory controller maps a particular address to
a [memory channel|slot|chip select (CS)] using this XOR-based decoding scheme. If these
parameters are specified and MemTest86 detects a memory error, the [memory
channel|slot|chip select (CS)] will be calculated and displayed along with the faulting
address.

How do I know which RAM module is failing?

Once a memory error has been detected, determining the failing SIMM/DIMM module is not a
clear cut procedure. Different CPUs map memory addresses
to physical memory sticks in different ways. Features like dual channel RAM (with
interleaving), channel hashing and NUMA make the mapping of addresses
to modules, banks & rows very difficult. Due to the large number of CPUs and motherboard
vendors and potential combinations of memory slots we do not have a general solution, though in some cases limited decode is possible. However, there are
steps that may be taken to determine the failing module. Here are some techniques that
you may wish to use:

  1. Removing modules

    This is simplest method for isolating a failing modules, but may only be
    employed when one or more modules can be removed from the system. By
    selectively removing modules from the system and then running the test you will
    be able to find the bad modules.
    Be sure to note exactly which modules are in the system when the test passes and
    when the test fails.

  2. Rotating modules

    When none of the modules can be removed then you may wish to rotate modules to
    find the failing one. This technique can only be used if there
    are three or more modules in the system. Change the location of two modules at a
    time. For example put the module from slot 1 into slot 2
    and put the module from slot 2 in slot 1. Run the test and if either the failing
    bit or address changes then you know that the failing module
    is one of the ones just moved. By using several combinations of module movement
    you should be able to determine which module is failing.

  3. Replacing modules

    If you are unable to use either of the previous techniques then you are left to
    selective replacement of modules to find the failure.

How do I fix the memory errors?

Depending on what is causing the memory errors, you can try the following options:

  • Replace the RAM modules (most common solution)
  • Set default or conservative RAM timings
  • Increase the RAM voltage levels
  • Decrease the CPU voltage levels
  • Apply BIOS update to fix incompatibility issues
  • Flag the address ranges as ‘bad’

Once you have determined with certainty which RAM module(s) have failed, replacing them
with a new set of RAM modules usually fixes the errors. When choosing
which modules to use as a replacement, consider using one that is listed as compatible
by the motherboard vendor as it would have been verified by the vendor
itself.

Sometimes, memory errors only manifest themselves when RAM timings are set too
aggressively in the BIOS (eg. overclocking). For certain modules that support
higher performance XMP timings, consider using standard, non-XMP timings to see if you
get better results. Consult your motherboard manual on how to set or
reset your RAM timings to default settings.

For certain configurations (especially when using aggressive RAM timings), higher
voltage may be required in order to operate the RAM in stable conditions.
If you are using non-standard RAM timings, slightly increasing the voltage (eg. from
1.5V to 1.55V) may increase the stability. Increase the voltage at your
own risk as excessive voltage may damage the components of your system

A higher CPU voltage may cause overheating, resulting in memory errors that lead to system hangs/crashes.
Check with the motherboard vendor for instructions on configuring CPU voltage levels.

In certain cases, RAM incompability issues can be fixed with a BIOS update. Check the
motherboard vendor for updated BIOS with RAM compaibiliy fixes.

Several operating systems allow the user to pass in a list of ‘bad’ memory ranges to
prevent the operating system to use or allocate memory in that range.
See Blacklisting RAM Pages for more details.

Самым надежным вариантом тестирования оперативной памяти является программа MemTest86+.

 Нам необходимо записать утилиту Memtest86 на DVD диск либо флешку или создать загрузочную флешку, в состав которой входит данная программа. Читаем статью  “Как создать мультизагрузочную флешку“, следуем пошаговой инструкции. После того как создана загрузочная флешка производим загрузку с неё, обычно для этого я использую “горячие клавиши” F8, F12, F11, Esc+клавиша отвечающая за быструю загрузку, в зависимости от модели мат. платы на компьютере/ноутбуке. После загрузки видим окно:

Мультизагрузочная флешка

Заходим в дополнительные утилиты и выбираем Memtest86. Если все прошло успешно видим такую картинку:

memtest86

После запуска программа будет проверять вашу оперативную память бесконечно, пока вы её не остановите клавишей ESC. Проверять можно как все модули памяти сразу, так и по одной. Проверяя все модули памяти, программа не скажет на какой именно ошибки, так что если есть ошибки, проверяйте лучше по одному модулю. Для проверки лучше сделать несколько циклов. А для максимального эффекта, лучше поставить проверку на ночь . Поле Pass означает количество проделанных циклов. Если у вас будут ошибки в памяти (колонка Error), вы увидите следующее:

memtest_errors

Исправить оперативную память при наличии ошибок в программе невозможно. Это не как в жестком диске затереть битые сектора. Я рекомендую вот что:

Самое распространённое – это выход из строя модуля оперативной памяти. Тестируем по одному модулю. Сначала этот модуль ставим в слот под оперативную память №1.

Слот ОЗУ

Тестируем,смотрим результат. Если ошибки есть как показано на рис. выше (там где выделено красным в программе Memtest), то ставим этот модуль слот под оперативную память №2. Тестируем,смотрим результат. Если ничего не изменилось,то модуль неисправен и подлежит замене. Меняем или ставим другой модуль памяти,тестируем. Если модуль памяти исправен,по окончанию теста в видим следующее:

memtest86

Бывает что неисправен слот для оперативной памяти на мат. плате. В этом случае подключаем модуль в другой свободный слот, далее рассматриваем целесообразность работы компьютера в данной конфигурации с неисправным слотом под оперативную память, целесообразность замены материнской платы, а может вас и так всё устроит, и объёма памяти вам будет достаточно.

В программе — 9 тестов:     

Test 0 — [Address test, walking ones, no cache] – тестирования для выяснения проблем в адресе памяти.     

Test 1 — [Addresstest, ownaddress] – глубокий тест для выявления ошибок в адресационной прописки памяти     

Test 2 — [Movinginversions, ones&zeros] – проверка на трудноуловимые и аппаратные ошибки.    

Test 3 — [Movinginversions, 8 bitpat] – как и предыдущий тест, только в нем используется алгоритм в 8ми битном подходе от 0 до 1. Тестируется 20 различных методов.     

Test 4 — [Moving inversions, random pattern] – Выявление ошибок связанных с data sensitive. В этом тесте 60 различных методов.     

Test 5 — [Block move, 64 moves] – Поиск проблем в схемах оперативной памяти.

Test 6 — [Moving inversions, 32 bit pat] – Самый долгий тест для выявления  data sensitive errors.     

Test 7 — [Randomnumbersequence] – Проверка ошибок в записи памяти.     

Test 8 — [Modulo 20, ones&zeros] –  Выявление скрытых ошибок в оперативной памяти с помощью буферизации и кеша.     

Test 9 — [Bit fade test, 90 min, 2 patterns] – Тест может быть включен вручную. Он записывает адреса в памяти, после чего уходит в сон на 1.5 часа. После выхода из сна, сверяет биты в адресах, на схожесть. Клавишей C для ручного запуска. Тест требует около 3х часов времени.

Теперь вы увидели как проводится тестирование оперативной памяти, как восстановить её работоспособность самостоятельно и проверить с помощью программы  Memtest86 с приведенной инструкцией.

Bought a new computer back in August with 4×4 GB RAM. Had problems with the RAM. They sent me four new sticks, which also generated errors. Singled out four sticks (from the eight I now had) that didn’t generate any errors. Discovered by coincident a new RAM error last week (this time no BSOD). Contacted the company. According to them there have been issues with a bad stock from last summer so I got two tested 8 GB sticks sent to me. Been running Memtest86+ over the weekend. After 20 hours I got an error (see attached photo). The test has now been running for 37 hours but so far only this one error. I contacted the company where I bought the computer. They wrote back:

I wouldn’t worry about hat one fail.

We have had similar situations here whereby it passes numerous times
but then fails once. We think it’s an issue with memtest, after all
memory is faulty or it isn’t so you can’t really have it pass a few
times, fail the next time around and then pass again!

Please trust me on this and continue with the memory we sent you and
if your problems continue we’ll look at getting it replaced again.

I gather from other forum posts that many people do not accept a single error. What could this single error signify, faulty RAM or a glitch in the MEMTEST program (or other)?

Update: From the helpful comments below I conclude that an occasional (and rare) «random» error could occur and be acceptable, but repeated errors at the same address would indicate malfunction. Memtest has now run for 45 hours and I still have only one error. For everyone’s information, I will keep running the test. In less than two days I am going away for a month. I will most likely leave Memtest running. As I do not have a UPS there is a risk that a power outage will ruin the experiment. The computer is a desktop so I cannot bring it with me (which would curiously have exposed it to more cosmic rays as I will be flying ;)).

Memtest

You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.



Mar 6, 2022


5


0


10


  • #1

Hello, I’ve finally decided to write in this forum because I’ve become quite desperate. A couple of months ago I started having some BSOD’s with the stop code «Memory_Management», «Page_fault_in_non_paged_area», and «IRQL_not_less_or_equal». At first, I dismissed it as random crashes, but they began to be a bit more frequent. I formatted my PC just in case it had something to do with bad software or any third party applications, but the errors continued. Now I get error codes in Google chrome like «Status_access_violation» and «Not enough memory», and now I’m more concerned than ever.

My specs are:

Processor AMD Ryzen 5 3400G with Radeon Vega Graphics 3.70 GHz (Stock CPU cooler)
RAM 32.0 GB (G Skill Trident Z Neo C16 3600Mhz)
Mobo ASUS B550-f Gaming Wifi
GPU Nvidia 3070
Storage Corsair Mp600

I decided to give memtest86 a go, and I got a lot of errors. I tested each RAM individually and got errors on both of my modules. It is worth noting that when I was building the PC around December 2020, one of the pins of the CPU got bent and I had to straighten it (I don’t know if this could be an issue for long term usage so I thought it was worth mentioning). Also, the CPU and the Mobo aren’t technically compatible, but it was the only CPU I had since acquiring a new one was hard and I ran out of money.

Here’s the results from my memtest86 test (I stopped it at test 9 because I thought it was useless to leave it running completely):
Summary

Report Date 2022-03-06 19:25:12
Generated by MemTest86 V9.4 Free (64-bit)
Visit MemTest86.com to Upgrade to Pro
Result FAIL

System Information

EFI Specifications 2.70
System
Manufacturer ASUS
Product Name System Product Name
Version System Version
Serial Number System Serial Number
BIOS
Vendor American Megatrends Inc.
Version 2423
Release Date 08/10/2021
Baseboard
Manufacturer ASUSTeK COMPUTER INC.
Product Name ROG STRIX B550-F GAMING (WI-FI)
Version Rev X.0x
Serial Number 200670412004727
CPU Type AMD Ryzen 5 3400G with Radeon Vega Graphics
CPU Clock 3693 MHz [Turbo: 4055.5 MHz]
# Logical Processors 8 (4 enabled for testing)
L1 Cache 8 x 96K (70065 MB/s)
L2 Cache 8 x 512K (53759 MB/s)
L3 Cache 1 x 4096K (21244 MB/s)
Memory 32698M (14878 MB/s)
Number of RAM SPDs detected 2
SPD #0 16GB DDR4 XMP PC4-28800
G Skill Intl / F4-3600C16-16GTZNC
16-19-19-39 / 3602 MHz / 1.350V
SPD #1 16GB DDR4 XMP PC4-28800
G Skill Intl / F4-3600C16-16GTZNC
16-19-19-39 / 3602 MHz / 1.350V
Number of RAM slots 4
Number of RAM modules 2
DIMM Slot #0 Empty slot
DIMM Slot #1 16GB DDR4 PC4-17000
G-Skill / F4-3600C16-16GTZNC / 00000000
2133 MHz
DIMM Slot #2 Empty slot
DIMM Slot #3 16GB DDR4 PC4-17000
G-Skill / F4-3600C16-16GTZNC / 00000000
2133 MHz

Result summary

Test Start Time 2022-03-06 18:58:39
Elapsed Time 0:26:15
Memory Range Tested 0x0 — 830000000 (33536MB)
CPU Selection Mode Parallel (All CPUs)
CPU Temperature Min/Max/Ave 40C/61C/54C
RAM Temperature Min/Max/Ave 33C/40C/38C
# Tests Passed 1/9 (11%)
Lowest Error Address 0x230A0198C (8970MB)
Highest Error Address 0x72E67F428 (29414MB)
Bits in Error Mask 00004100008A4110
Bits in Error 8
Max Contiguous Errors 2
CPUs that detected memory errors { 0, 2, 4 }

Bits in Error

. . . . . . . . . . . . . . . . . x . . . . . x . . . . . . . . . . . . . . . . x . . . x . x . . x . . . . . x . . . x . . . .
63 0
Test # Tests Passed Errors
Test 0 [Address test, walking ones, 1 CPU] 1/1 (100%) 0
Test 1 [Address test, own address, 1 CPU] 0/1 (0%) 23
Test 2 [Address test, own address] 0/1 (0%) 19
Test 3 [Moving inversions, ones & zeroes] 0/1 (0%) 140
Test 4 [Moving inversions, 8-bit pattern] 0/1 (0%) 497
Test 5 [Moving inversions, random pattern] 0/1 (0%) 538
Test 6 [Block move, 64-byte blocks] 0/1 (0%) 691
Test 7 [Moving inversions, 32-bit pattern] 0/1 (0%) 1551
Test 8 [Random number sequence] 0/1 (0%) 132
Test 9 [Modulo 20, ones & zeros] 0/0 (0%) 2
Test 10 [Bit fade test, 2 patterns, 1 CPU] 0/0 (0%) 0
Test 13 [Hammer test] 0/0 (0%) 0
Last 10 Errors
2022-03-06 19:23:50 — [Data Error] Test: 9, CPU: 2, Address: 230A0198C, Expected: EC85E515, Actual: EC8DE515
2022-03-06 19:23:50 — [Data Error] Test: 9, CPU: 2, Address: 230A3F9DC, Expected: EC85E515, Actual: EC87E515
2022-03-06 19:22:03 — [Data Error] Test: 8, CPU: 0, Address: 72C67F074, Expected: 535EF48E, Actual: 535EF58E
2022-03-06 19:22:03 — [Data Error] Test: 8, CPU: 0, Address: 72C67D0BC, Expected: C9BC563C, Actual: C9BC573C
2022-03-06 19:22:03 — [Data Error] Test: 8, CPU: 0, Address: 72C6790AC, Expected: B0348FB0, Actual: B0348EB0
2022-03-06 19:22:03 — [Data Error] Test: 8, CPU: 0, Address: 72C67F0EC, Expected: E03FD79F, Actual: E03FD69F
2022-03-06 19:22:03 — [Data Error] Test: 8, CPU: 0, Address: 72C6690E4, Expected: 813DCF3D, Actual: 813DCE3D
2022-03-06 19:22:03 — [Data Error] Test: 8, CPU: 0, Address: 72C6610AC, Expected: 333B904F, Actual: 333B914F
2022-03-06 19:22:03 — [Data Error] Test: 8, CPU: 0, Address: 72C655074, Expected: A5C10371, Actual: A5C14371
2022-03-06 19:22:03 — [Data Error] Test: 8, CPU: 0, Address: 72C6530EC, Expected: ADE1679F, Actual: ADE1279F

Thank you for help, and Kind regards.

Koekieezz


  • Koekieezz

    Koekieezz

Hello, I’ve finally decided to write in this forum because I’ve become quite desperate. A couple of months ago I started having some BSOD’s with the stop code «Memory_Management», «Page_fault_in_non_paged_area», and «IRQL_not_less_or_equal». At first, I dismissed it as random crashes, but they began to be a bit more frequent. I formatted my PC just in case it had something to do with bad software or any third party applications, but the errors continued. Now I get error codes in Google chrome like «Status_access_violation» and «Not enough memory», and now I’m more concerned than ever.

My specs are:

Processor AMD Ryzen 5 3400G with Radeon Vega Graphics 3.70 GHz (Stock CPU cooler)
RAM 32.0 GB (G Skill Trident Z Neo C16…

Koekieezz



Apr 30, 2020


3,639


531


25,690


  • #2

Hello, I’ve finally decided to write in this forum because I’ve become quite desperate. A couple of months ago I started having some BSOD’s with the stop code «Memory_Management», «Page_fault_in_non_paged_area», and «IRQL_not_less_or_equal». At first, I dismissed it as random crashes, but they began to be a bit more frequent. I formatted my PC just in case it had something to do with bad software or any third party applications, but the errors continued. Now I get error codes in Google chrome like «Status_access_violation» and «Not enough memory», and now I’m more concerned than ever.

My specs are:

Processor AMD Ryzen 5 3400G with Radeon Vega Graphics 3.70 GHz (Stock CPU cooler)
RAM 32.0 GB (G Skill Trident Z Neo C16 3600Mhz)
Mobo ASUS B550-f Gaming Wifi
GPU Nvidia 3070
Storage Corsair Mp600

I decided to give memtest86 a go, and I got a lot of errors. I tested each RAM individually and got errors on both of my modules. It is worth noting that when I was building the PC around December 2020, one of the pins of the CPU got bent and I had to straighten it (I don’t know if this could be an issue for long term usage so I thought it was worth mentioning). Also, the CPU and the Mobo aren’t technically compatible, but it was the only CPU I had since acquiring a new one was hard and I ran out of money.

Thank you for help, and Kind regards.

this step by step in order (read till end):

  • Make sure ram is on slot 2 and 4
  • Disconnect from internet
  • Uninstall gpu driver DDU (clean and do not restart).
  • Uninstall all the processors (is a must, should be 8 on yours, also when it asks for restart, click on no and keep uninstalling all processors) on device manager like this:
    unknown.png

    and the chipset driver/software in control panel (if there is none just skip)

  • restart the pc to bios, re flash the bios (Bios ver 2423, your current bios), then after updating bios go to bios again, then load default or optimized settings, find AMD SVM and IOMMU options, enable them (if the option is only auto and disable, just leave it auto), set your XMP/Manual OC and PBO/XFR back then save and exit.
  • boot up to windows and install the latest Chipset driver on the mobo web page (should be 3.10.22), reboot, and make sure in power plan, amd ryzen balanced is used, and then connect to internet.
  • Install the latest gpu driver.

    *do this all offline until reboot after installing chipset driver, also you may reboot to bios after all of this to set the XMP (and previous settings you did). Download needed files (highlighted word) before doing step 1, do the step by orders.

  • Run cmd as admin, then do chkdsk /x /f /r, after that do sfc /scannow
  • And check windows update (and optional updates) if there is any and install them (except chipset in optional update).
  • Make sure the psu connected to the gpu is 1 pcie cable per 1 slot (use main cable, not the branches/split) like this:
    unknown.png

For ram you could try to use the fastest xmp profile, then drop it to 3466 or 3533, then set this timing manually:

SOC Voltage: 1.15v (you could try lower this later)
CPU VDDG CCD and IOD: 0.955v or 1.050v
CLDO VDDP: 0.910v
Dram Voltage: 1.36~1.41v (you could try lower this later)

then go to advanced timings, and change these (try to use the bigger number first):
Command Rate: 2T
tCL: 16
tRCDWR and RD: 19
tRP: 19
tRAS: 36 or 38
tRP: 55 or 57 or 64
tWR: 22 ~ 16
tRFC: 630
tRRD_L: 8 or 6 or 4
tRRD_S: 4
tWTR_L: 14 or 12 or 10
tWTR_S: 4 or 5
tFAW: 24 or 16
tRFC: 630
tCWL: 16
tRDWR: 8
tWRRD: 3 or 2

ProcODT: 40 or 43.6
ClkDrvStr: 24
AddrCmdDrvStr: 24
CsOdtCmdDrvStr: 24
CkeDrvStr: 24

Power Down Mode: Disabled
Gear Down Mode: Disabled

And for ram stability test, you could try to use TM5 with absolut config, you could google it.



Mar 6, 2022


5


0


10


  • #3

this step by step in order (read till end):

  • Make sure ram is on slot 2 and 4
  • Disconnect from internet
  • Uninstall gpu driver DDU (clean and do not restart).
  • Uninstall all the processors (is a must, should be 8 on yours, also when it asks for restart, click on no and keep uninstalling all processors) on device manager like this:
    unknown.png

    and the chipset driver/software in control panel (if there is none just skip)

  • restart the pc to bios, re flash the bios (Bios ver 2423, your current bios), then after updating bios go to bios again, then load default or optimized settings, find AMD SVM and IOMMU options, enable them (if the option is only auto and disable, just leave it auto), set your XMP/Manual OC and PBO/XFR back then save and exit.
  • boot up to windows and install the latest Chipset driver on the mobo web page (should be 3.10.22), reboot, and make sure in power plan, amd ryzen balanced is used, and then connect to internet.
  • Install the latest gpu driver.

    *do this all offline until reboot after installing chipset driver, also you may reboot to bios after all of this to set the XMP (and previous settings you did). Download needed files (highlighted word) before doing step 1, do the step by orders.

  • Run cmd as admin, then do chkdsk /x /f /r, after that do sfc /scannow
  • And check windows update (and optional updates) if there is any and install them (except chipset in optional update).
  • Make sure the psu connected to the gpu is 1 pcie cable per 1 slot (use main cable, not the branches/split) like this:
    unknown.png

For ram you could try to use the fastest xmp profile, then drop it to 3466 or 3533, then set this timing manually:

SOC Voltage: 1.15v (you could try lower this later)
CPU VDDG CCD and IOD: 0.955v or 1.050v
CLDO VDDP: 0.910v
Dram Voltage: 1.36~1.41v (you could try lower this later)

then go to advanced timings, and change these (try to use the bigger number first):
Command Rate: 2T
tCL: 16
tRCDWR and RD: 19
tRP: 19
tRAS: 36 or 38
tRP: 55 or 57 or 64
tWR: 22 ~ 16
tRFC: 630
tRRD_L: 8 or 6 or 4
tRRD_S: 4
tWTR_L: 14 or 12 or 10
tWTR_S: 4 or 5
tFAW: 24 or 16
tRFC: 630
tCWL: 16
tRDWR: 8
tWRRD: 3 or 2

ProcODT: 40 or 43.6
ClkDrvStr: 24
AddrCmdDrvStr: 24
CsOdtCmdDrvStr: 24
CkeDrvStr: 24

Power Down Mode: Disabled
Gear Down Mode: Disabled

And for ram stability test, you could try to use TM5 with absolut config, you could google it.

The only thing I find troubling is the part where I have to set to xmp to the fastest profile, my CPU doesn’t support frequencies above 3200MHz, what should I do then?

Koekieezz



Apr 30, 2020


3,639


531


25,690


  • #4

The only thing I find troubling is the part where I have to set to xmp to the fastest profile, my CPU doesn’t support frequencies above 3200MHz, what should I do then?

well then with the fastest xmp profile set and used, set back to 3200mhz, and use the timings i listed. Zen+ should be able to do 3466, but i think you lost the lottery XD

or else, the ram got faulty.



Mar 6, 2022


5


0


10


  • #5

well then with the fastest xmp profile set and used, set back to 3200mhz, and use the timings i listed. Zen+ should be able to do 3466, but i think you lost the lottery XD

or else, the ram got faulty.

Alright I did everything step by step, ran TM5 at the end and still wound up with a lot of errors… I suppose I can narrow it down to just faulty RAM now?



Mar 6, 2022


5


0


10


  • #6

Alright I did everything step by step, ran TM5 at the end and still wound up with a lot of errors… I suppose I can narrow it down to just faulty RAM now?

Also when I ran chkskd I got a BSOD with the stop code «Page_fault_in_non_paged_area NTFS.Sys»

Koekieezz



Apr 30, 2020


3,639


531


25,690


  • #7

Alright I did everything step by step, ran TM5 at the end and still wound up with a lot of errors… I suppose I can narrow it down to just faulty RAM now?

even at 3200 there is errors? with fastest XMP + low freq and timings? its either a ram faulty, or the cpu imc itself..



Mar 6, 2022


5


0


10


  • #8

even at 3200 there is errors? with fastest XMP + low freq and timings? its either a ram faulty, or the cpu imc itself..

Sorry for the late reply, it was already pretty late where I live. I wanted to ask if there’s a way to isolate the culprit? If it’s the CPU or the RAM, to know which part to replace because I don’t really have enough to buy both things.

Koekieezz



Apr 30, 2020


3,639


531


25,690


  • #9

Sorry for the late reply, it was already pretty late where I live. I wanted to ask if there’s a way to isolate the culprit? If it’s the CPU or the RAM, to know which part to replace because I don’t really have enough to buy both things.

either you test another ram kit, if your friend have some might want to swap it for a test.



Mar 17, 2022


3


0


10


  • #10

I would say its better if you let the BIOS stay in default and just reinstall the windows again.
It should be OS problem. I once had the same problem. Clean installation of windows removed that problem.

Similar threads

  • Advertising
  • Cookies Policies
  • Privacy
  • Term & Conditions

Понравилась статья? Поделить с друзьями:
  • Mediaget ошибка установки
  • Mediaget ошибка при запуске
  • Mediaget ошибка загрузки перепроверить данные
  • Mediaget ошибка 1114
  • Mediaerror 3 fired by video element ошибка wink