ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
1usmus_v3Usage: Run TM5 with 1usmus (six cycles) to diagnose and correct errors, and then run anta777 ABSOLUT (overnight) for a final confirmationERROR #7MirrorMove 2Mb [Mode0,P0]SEE ERROR #11
- If this error happens with Errors #1 and/or #11, it is most likely not enough VDIMM
2
ERROR #0RefreshStable 0Mb [Mode0,P0]Voltage cutoff choke; almost always not enough VDIMM
- can be too low SCL with wrong tWRRD (for AMD)
- can be too low VDDQ on ADL/RPL (try testing up to 1.55V)
- can sometimes happen from overheating if it occurs in a later cycle (not the first)
- can happen if tRFC is too tight, but try raising VDIMM first
- can happen if VDIMM is set wayyyy too high (best to work from bottom up)
- can be caused by BIOS corruption (but rarely)
ERROR #8Random tests 0Mb [Mode2,P358]SEE ERROR #1
- if it happens later on in a cycle, it can be due to overheating
- can be caused by low VDIMM if combined with other low voltage errors
- can be caused by CPU cache clock being raised too high
- can be caused by BIOS corruption
3
ERROR #1Variable tests 16Mb [Mode1,P0]Can be voltage related, can be too tight tRFC, tiny timeout issues (tRRD, tWTR)
- usually happens when VDIMM or VDDQ is a tiny bit too low (try raising by +0.01V)
- can happen if VCCSA is a bit too low (esp. if only a single one, or combined with other low voltage errors)
- can happen with incorrect RTT values (one or two being too low)
- can be caused by BIOS corruption
- can be a result of other errors, so check other errors
ERROR #9MirrorMove 4Mb [Mode0,P0]Suspect tWR being too slow, voltage stability issue
If you've tightened tRP, increase VDIMM a tiny bit
If you've increased tRP, you can try decreasing VDIMM a tiny bit
- usually tiny bit not enough VDIMM (esp. if only a single error and/or with Error 1)
- if this happens with Error 0 on ADL/RPL with the E-Cores enabled, try increasing L2 Voltage
- can be an unstable CPU overclock, so boost Vcore, lower CPU multipliers, reduce cache clock, etc.
4
ERROR #2Variable tests 32Mb [Mode1,P254]Timeout issue; something ends too quickly or you lack voltage and cells are not recharged in time
^ a sync issue in other words, where first culprit is voltage or resistance somewhere
- try raising VDIMM if early on, all by itself (or with Error 12), esp. if frequency was increased
- can be caused by low VDIMM if combined with other low voltage errors
- can be due to overheating if only one or two (esp. later in the test)
- can happen if tRCD is too low and there are many in a row without any other errors
ERROR #10Random tests 8Mb [Mode2,P477]- tWR not optimal value (too tight; try loosening first)
- if it happens in a later cycle, it may be due to overheating
mostly affects the primaries; noticed it can be tRCDWR or tRCDRD, can be tRP too
but it also can be the last two tRDWR & tWRRD which don't play well with your main tRCDWR/RD
- can be inaccurate VDIMM (if only one or two), so try +/- 0.01V
- can be due to low VDIMM or VDDQ (es. if combined with other low voltage errors)
- can be caused by CPU cache clock being raised too high
- can be caused by BIOS corruption
5
ERROR #3MirrorMove 0Mb [Mode0,P1]Would suspect more tRDWR/tWRRD, while for bigger datasets tRP, tRFC
tRFC is so far always in cycle
- it can error after the first cycle, if something is off by some ns and just "got lost"
- can be due to low VDIMM or VDDQ if combined with other low voltage errors
- can be overly tight tertiaries without enough voltage to run them
- can be due to too tight tRFC
ERROR #11Random tests 16Mb [Mode2,P8568]- It can be due to RAM overheating
- it will error out if if CAD_BUS is not optimal
- will error out if tRFC is too tight, mostly errors out after time
- VDIMM might be +/- 0.01 too high/low, tFAW being awkward value, or tRAS needing +1
- can be caused by low VDIMM if combined with other low voltage errors
6
ERROR #4MirrorMove128 0Mb [Mode0,P510]PCB Crash!
- will error out if tRFC is too low, mostly errors out after time
- if this happens later on with Error #3 or other low VDIMM errors, VDIMM may need an extra +0.01V
- in some cases, could actually be too high RTTs or VDIMM or too high CAD_BUS or ClkDrvStr
ERROR #12Random tests 32Mb [Mode2,P787]SEE ERROR #2
- If this error happens at the start, try raising VDIMM
7
ERROR #5MirrorMove 0Mb [Mode0,P4]SEE ERROR #3
- can be due to BIOS corruption, esp. with Error 14 or 15
ERROR #13Random tests 64Mb [Mode2,P8968]timeout while transferring big data, as memory was not able to autocorrect it
full crash, nearly always related to voltage
- can be due to too low VDIMM, esp. with Error 1 or 7
- if this happens in a later cycle (esp. just one), it can be due to low VCCSA
8
ERROR #6Random tests 1Mb [Mode2,P125]Is related to the IMC (can mean IMC voltage is not accurate),
^ procODT, CLDO_VDDP or VSOC on AMD, or ODTs, VCCSA or VCCIO on Intel
~ it translates to "I couldn't even start transferring data, I crashed"
- typically too low VDIMM or VDDQ, esp. if there are lots or accompanied with Error 0
- can be too tight tRCD, tRP, tRFC or tertiaries, esp. if increasing voltage does nothing
- could be too low SCL with wrong tWRRD (for AMD)
- can be caused by overheating if only a single one, so retest
- can be caused by BIOS corruption (esp. if accompanied with Error 12)
- can be an unstable CPU overclock, so boost Vcore, lower CPU multipliers, reduce cache clock, etc.
ERROR #14MirrorMove 0Mb [Mode0,P16384]PCB Crash!
Errors 14, 4 and 0 - relate to badly used CAD_BUS SETUP Timing
Too low CAD_BUS AddrCmdDrvStr/CsOdtDrvStren/CkeDrvStren, or overall badly timed powerdown
They will appear together because it's the DIMMs crashing on badly timed values
- can be due to low VDIMM or VDDQ esp. if combined with other low voltage errors
- can be due to BIOS corruption, esp. with Error 5 or 15
- not very conclusive on its own
9
If errors are random and playing around with voltages doesn't help, try loosening tRCD or tRP, or even boosting Vcore (in case it's the cache)
Any combination of Errors 0, 5, 6, 9, 11, 12, 13, 14, or 15 can be caused by an unstable CPU overclock, so many sure it is fully stable before testing

It's better to work your way up with VDIMM rather than down, as too much of it at the start could confuse results if your RAM is overheating
You may get a combination of "low voltage" errors, when in reality there may be a sweet spot for your RAM that you skipped over completely

If TM5 freezes the PC at random times without any errors, the BIOS might be corrupted and need a reflash, and sometimes a Vcore/VDIMM increase
BIOS/OS corruption can prevent booting or cause errors that usually shouldn't happen, so reflash/run SFC if a previously stable config no longer works

tRCD, tRP, tWR, tFAW, tRFC, and tREFI are temperature-sensitive timings. Overheating and too tight tRFC can freeze the PC/corrupt the BIOS
anta777 configs are extremely heat sensitive and need a much looser tRFC to pass compared to 1usmus
ERROR #15MirrorMove128 0Mb [Mode0,P2]Crashed after #15 = End of one Cycle
Timing accuracy related, could be anything such as:
tCWL≠tCL, tight tRFC, lacking VDIMM, tFAW smaller than tRRD_L x 4, too tight tRRD_
- if it starts happening after a timing change, undo it or try raising VDIMM or VDDQ a little
- can be caused by low VDIMM if combined with other low voltage errors
- can be due to BIOS corruption, esp. with Error 5 or 14
- not very conclusive on its own, so try retesting
10
11
TM5 1usmus
https://www.overclock.net/threads/memory-testing-with-testmem5-tm5-with-custom-configs.1751608/#post-28541652
12
TM5 anta777 ABSOLUT
https://www.overclock.net/threads/official-intel-ddr4-24-7-memory-stability-thread.1569364/page-930#post-28877388
13
BSOD Error Code Diagnosis
https://www.reddit.com/r/overclocking/comments/kq69ay/psa_bsod_error_code_diagnosis_possible_solutions/
14
15
anta777 ABSOLUTERROR #3, #4, or #15: RAM is most likely overheating
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100