mats version 400.184. Testing GP104 with 20 MB of memory starting with 0 MB.
Read Error Count: 0
Write Error Count: 113
Unknown Error Count: 0
=== MEMORY ERRORS BY SUBPARTITION ===
SUBPART READ ERRORS WRITE ERRORS UNKNOWN ERRS
------- ----------- ------------ ------------
FBIOA0 0 49 0
FBIOA1 0 64 0
FBIOB0 0 0 0
FBIOB1 0 0 0
FBIOC0 0 0 0
FBIOC1 0 0 0
FBIOD0 0 0 0
FBIOD1 0 0 0
Failing Bits:
A000 A001 A002 A003 A004 A005 A006 A007 A008 A009 A010 A011 A012 A013 A014 A015
A016 A017 A018 A019 A020 A021 A022 A023 A024 A025 A026 A027 A028 A029 A030 A031
A032 A033 A034 A035 A036 A037 A038 A039 A040 A041 A042 A043 A044 A045 A046 A047
A048 A049 A050 A051 A052 A053 A054 A055 A056 A057 A058 A059 A060 A061 A062 A063
=== MEMORY ERRORS BY BIT ===
P : Partition (FBIO)
READ 0 READ 1 READ ?
P BIT READ ERRORS WRITE ERRORS UNKNOWN ERRS EXP. 1 EXP. 0 EXP. ?
- --- ----------- ------------ ------------ ------ ------ ------
A 000 0 13 0 2 11 0
A 001 0 10 0 2 8 0
A 002 0 6 0 1 5 0
A 003 0 6 0 3 3 0
A 004 0 5 0 1 4 0
A 005 0 17 0 0 17 0
A 006 0 12 0 0 12 0
A 007 0 4 0 4 0 0
A 008 0 21 0 0 21 0
A 009 0 21 0 0 21 0
A 010 0 21 0 0 21 0
A 011 0 4 0 4 0 0
A 012 0 4 0 4 0 0
A 013 0 4 0 4 0 0
A 014 0 4 0 4 0 0
A 015 0 4 0 4 0 0
A 016 0 4 0 2 2 0
A 017 0 7 0 2 5 0
A 018 0 8 0 3 5 0
A 019 0 8 0 3 5 0
A 020 0 7 0 2 5 0
A 021 0 16 0 1 15 0
A 022 0 11 0 2 9 0
A 023 0 4 0 4 0 0
A 024 0 20 0 0 20 0
A 025 0 20 0 0 20 0
A 026 0 20 0 0 20 0
A 027 0 4 0 4 0 0
A 028 0 4 0 4 0 0
A 029 0 4 0 4 0 0
A 030 0 4 0 4 0 0
A 031 0 4 0 4 0 0
A 032 0 8 0 8 0 0
A 033 0 8 0 8 0 0
A 034 0 8 0 8 0 0
A 035 0 8 0 8 0 0
A 036 0 8 0 8 0 0
A 037 0 24 0 0 24 0
A 038 0 8 0 8 0 0
A 039 0 8 0 8 0 0
A 040 0 24 0 0 24 0
A 041 0 24 0 0 24 0
A 042 0 24 0 0 24 0
A 043 0 8 0 8 0 0
A 044 0 8 0 8 0 0
A 045 0 8 0 8 0 0
A 046 0 8 0 8 0 0
A 047 0 8 0 8 0 0
A 048 0 8 0 8 0 0
A 049 0 8 0 8 0 0
A 050 0 8 0 8 0 0
A 051 0 8 0 8 0 0
A 052 0 8 0 8 0 0
A 053 0 24 0 0 24 0
A 054 0 8 0 8 0 0
A 055 0 8 0 8 0 0
A 056 0 24 0 0 24 0
A 057 0 24 0 0 24 0
A 058 0 24 0 0 24 0
A 059 0 8 0 8 0 0
A 060 0 8 0 8 0 0
A 061 0 8 0 8 0 0
A 062 0 8 0 8 0 0
A 063 0 8 0 8 0 0
=== MEMORY ERRORS BY ADDRESS ===
ADDRESS : Failing memory address, or buffer offset if starting with 'X+'
T : Type of memory error: W = write, R = read
P : Partition (FBIO)
S : Subpartition
B : Bank
E : Beat
U : PseudoChannel
ADDRESS EXPECTED ACTUAL REREAD1 REREAD2 FAILBITS TPSBEU ROW COL BIT(s)
------- -------- ------ ------- ------- -------- ------ --- --- ------
00000045f8 00000000 00000720 00000720 00000720 00000720 WA1040 0000 027 A037,A040,A041,A042
00000045f0 00000000 00000720 00000720 00000720 00000720 WA1000 0000 027 A037,A040,A041,A042
00000045e8 00000000 00000720 00000720 00000720 00000720 WA1040 0000 026 A037,A040,A041,A042
00000045e0 00000000 00000720 00000720 00000720 00000720 WA1000 0000 026 A037,A040,A041,A042
00000045d8 00000000 00000720 00000720 00000720 00000720 WA1041 0000 027 A053,A056,A057,A058
00000045d0 00000000 00000720 00000720 00000720 00000720 WA1001 0000 027 A053,A056,A057,A058
00000045c8 00000000 00000720 00000720 00000720 00000720 WA1041 0000 026 A053,A056,A057,A058
00000045c0 00000000 00000720 00000720 00000720 00000720 WA1001 0000 026 A053,A056,A057,A058
00000043b8 00000000 00000720 00000720 00000720 00000720 WA0041 0000 02d A021,A024,A025,A026
00000043b0 00000000 00000720 00000720 00000720 00000720 WA0001 0000 02d A021,A024,A025,A026
00000043a8 00000000 00000720 00000720 00000720 00000720 WA0041 0000 02c A021,A024,A025,A026
00000043a0 00000000 00000720 00000720 00000720 00000720 WA0001 0000 02c A021,A024,A025,A026
0000004398 00000000 00000720 00000720 00000720 00000720 WA0040 0000 02d A005,A008,A009,A010
0000004390 00000000 00000720 00000720 00000720 00000720 WA0000 0000 02d A005,A008,A009,A010
0000004388 00000000 00000720 00000720 00000720 00000720 WA0040 0000 02c A005,A008,A009,A010
0000004380 00000000 00000720 00000720 00000720 00000720 WA0000 0000 02c A005,A008,A009,A010
0000004200 00000000 00000773 00000773 00000773 00000773 WA0000 0000 038 A000,A001,A004,A005,A006,A008,A009,A010
0000004478 00000000 00000720 00000720 00000720 00000720 WA1040 0000 033 A037,A040,A041,A042
0000004470 00000000 00000720 00000720 00000720 00000720 WA1000 0000 033 A037,A040,A041,A042
0000004468 00000000 00000720 00000720 00000720 00000720 WA1040 0000 032 A037,A040,A041,A042
0000004460 00000000 00000720 00000720 00000720 00000720 WA1000 0000 032 A037,A040,A041,A042
0000004458 00000000 00000720 00000720 00000720 00000720 WA1041 0000 033 A053,A056,A057,A058
0000004450 00000000 00000720 00000720 00000720 00000720 WA1001 0000 033 A053,A056,A057,A058
0000004448 00000000 00000720 00000720 00000720 00000720 WA1041 0000 032 A053,A056,A057,A058
0000004440 00000000 00000720 00000720 00000720 00000720 WA1001 0000 032 A053,A056,A057,A058
0000004538 00000000 00000720 00000720 00000720 00000720 WA1041 0000 021 A053,A056,A057,A058
0000004530 00000000 00000720 00000720 00000720 00000720 WA1001 0000 021 A053,A056,A057,A058
0000004528 00000000 00000720 00000720 00000720 00000720 WA1041 0000 020 A053,A056,A057,A058
0000004520 00000000 00000720 00000720 00000720 00000720 WA1001 0000 020 A053,A056,A057,A058
0000004518 00000000 00000720 00000720 00000720 00000720 WA1040 0000 021 A037,A040,A041,A042
0000004510 00000000 00000720 00000720 00000720 00000720 WA1000 0000 021 A037,A040,A041,A042
0000004508 00000000 00000720 00000720 00000720 00000720 WA1040 0000 020 A037,A040,A041,A042
0000004500 00000000 00000720 00000720 00000720 00000720 WA1000 0000 020 A037,A040,A041,A042
00000044f8 00000000 00000720 00000720 00000720 00000720 WA1041 0000 037 A053,A056,A057,A058
00000044f0 00000000 00000720 00000720 00000720 00000720 WA1001 0000 037 A053,A056,A057,A058
00000044e8 00000000 00000720 00000720 00000720 00000720 WA1041 0000 036 A053,A056,A057,A058
00000044e0 00000000 00000720 00000720 00000720 00000720 WA1001 0000 036 A053,A056,A057,A058
00000044d8 00000000 00000720 00000720 00000720 00000720 WA1040 0000 037 A037,A040,A041,A042
00000044d0 00000000 00000720 00000720 00000720 00000720 WA1000 0000 037 A037,A040,A041,A042
00000044c8 00000000 00000720 00000720 00000720 00000720 WA1040 0000 036 A037,A040,A041,A042
00000044c0 00000000 00000720 00000720 00000720 00000720 WA1000 0000 036 A037,A040,A041,A042
00000041b8 00000000 00000763 00000763 00000763 00000763 WA0040 0000 025 A000,A001,A005,A006,A008,A009,A010
00000041b0 00000000 00000775 00000775 00000775 00000775 WA0000 0000 025 A000,A002,A004,A005,A006,A008,A009,A010
00000041a8 00000000 00000773 00000773 00000773 00000773 WA0040 0000 024 A000,A001,A004,A005,A006,A008,A009,A010
00000041a0 00000000 00000720 00000720 00000720 00000720 WA0000 0000 024 A005,A008,A009,A010
0000004198 00000000 0000076f 0000076f 0000076f 0000076f WA0041 0000 025 A016,A017,A018,A019,A021,A022,A024,A025,A026
0000004190 00000000 0000074e 0000074e 0000074e 0000074e WA0001 0000 025 A017,A018,A019,A022,A024,A025,A026
0000004188 00000000 00000720 00000720 00000720 00000720 WA0041 0000 024 A021,A024,A025,A026
0000004180 00000000 0000073a 0000073a 0000073a 0000073a WA0001 0000 024 A017,A019,A020,A021,A024,A025,A026
0000004578 00000000 00000720 00000720 00000720 00000720 WA1041 0000 023 A053,A056,A057,A058
0000004570 00000000 00000720 00000720 00000720 00000720 WA1001 0000 023 A053,A056,A057,A058
0000004568 00000000 00000720 00000720 00000720 00000720 WA1041 0000 022 A053,A056,A057,A058
0000004560 00000000 00000720 00000720 00000720 00000720 WA1001 0000 022 A053,A056,A057,A058
0000004558 00000000 00000720 00000720 00000720 00000720 WA1040 0000 023 A037,A040,A041,A042
0000004550 00000000 00000720 00000720 00000720 00000720 WA1000 0000 023 A037,A040,A041,A042
0000004548 00000000 00000720 00000720 00000720 00000720 WA1040 0000 022 A037,A040,A041,A042
0000004540 00000000 00000720 00000720 00000720 00000720 WA1000 0000 022 A037,A040,A041,A042
00000041f8 00000000 00000773 00000773 00000773 00000773 WA0040 0000 027 A000,A001,A004,A005,A006,A008,A009,A010
00000041f0 00000000 00000765 00000765 00000765 00000765 WA0000 0000 027 A000,A002,A005,A006,A008,A009,A010
00000041e8 00000000 00000763 00000763 00000763 00000763 WA0040 0000 026 A000,A001,A005,A006,A008,A009,A010
00000041e0 00000000 0000076f 0000076f 0000076f 0000076f WA0000 0000 026 A000,A001,A002,A003,A005,A006,A008,A009,A010
00000041d8 00000000 00000772 00000772 00000772 00000772 WA0041 0000 027 A017,A020,A021,A022,A024,A025,A026
00000041d0 00000000 00000770 00000770 00000770 00000770 WA0001 0000 027 A020,A021,A022,A024,A025,A026
00000041c8 00000000 00000720 00000720 00000720 00000720 WA0041 0000 026 A021,A024,A025,A026
00000041c0 00000000 00000768 00000768 00000768 00000768 WA0001 0000 026 A019,A021,A022,A024,A025,A026
0000004178 00000000 00000754 00000754 00000754 00000754 WA0041 0000 023 A018,A020,A022,A024,A025,A026
0000004170 00000000 00000752 00000752 00000752 00000752 WA0001 0000 023 A017,A020,A022,A024,A025,A026
0000004168 00000000 0000074c 0000074c 0000074c 0000074c WA0041 0000 022 A018,A019,A022,A024,A025,A026
0000004160 00000000 00000745 00000745 00000745 00000745 WA0001 0000 022 A016,A018,A022,A024,A025,A026
0000004158 00000000 00000744 00000744 00000744 00000744 WA0040 0000 023 A002,A006,A008,A009,A010
0000004150 00000000 00000743 00000743 00000743 00000743 WA0000 0000 023 A000,A001,A006,A008,A009,A010
0000004148 00000000 0000074f 0000074f 0000074f 0000074f WA0040 0000 022 A000,A001,A002,A003,A006,A008,A009,A010
0000004140 00000000 00000749 00000749 00000749 00000749 WA0000 0000 022 A000,A003,A006,A008,A009,A010
00000043f8 00000000 00000720 00000720 00000720 00000720 WA0041 0000 02f A021,A024,A025,A026
00000043f0 00000000 00000720 00000720 00000720 00000720 WA0001 0000 02f A021,A024,A025,A026
00000043e8 00000000 00000720 00000720 00000720 00000720 WA0041 0000 02e A021,A024,A025,A026
00000043e0 00000000 00000720 00000720 00000720 00000720 WA0001 0000 02e A021,A024,A025,A026
00000043d8 00000000 00000720 00000720 00000720 00000720 WA0040 0000 02f A005,A008,A009,A010
00000043d0 00000000 00000720 00000720 00000720 00000720 WA0000 0000 02f A005,A008,A009,A010
00000043c8 00000000 00000720 00000720 00000720 00000720 WA0040 0000 02e A005,A008,A009,A010
00000043c0 00000000 00000720 00000720 00000720 00000720 WA0000 0000 02e A005,A008,A009,A010
00000045b8 00000000 00000720 00000720 00000720 00000720 WA1040 0000 025 A037,A040,A041,A042
00000045b0 00000000 00000720 00000720 00000720 00000720 WA1000 0000 025 A037,A040,A041,A042
00000045a8 00000000 00000720 00000720 00000720 00000720 WA1040 0000 024 A037,A040,A041,A042
00000045a0 00000000 00000720 00000720 00000720 00000720 WA1000 0000 024 A037,A040,A041,A042
0000004598 00000000 00000720 00000720 00000720 00000720 WA1041 0000 025 A053,A056,A057,A058
0000004590 00000000 00000720 00000720 00000720 00000720 WA1001 0000 025 A053,A056,A057,A058
0000004588 00000000 00000720 00000720 00000720 00000720 WA1041 0000 024 A053,A056,A057,A058
0000004580 00000000 00000720 00000720 00000720 00000720 WA1001 0000 024 A053,A056,A057,A058
0000004400 ffffffff ffff0720 ffff0720 ffff0720 0000f8df WA1001 0000 030 A048,A049,A050,A051,A052,A054,A055,A059,A060,A061,A062,A063
0000004408 ffffffff ffff0720 ffff0720 ffff0720 0000f8df WA1041 0000 030 A048,A049,A050,A051,A052,A054,A055,A059,A060,A061,A062,A063
0000004410 ffffffff ffff0720 ffff0720 ffff0720 0000f8df WA1001 0000 031 A048,A049,A050,A051,A052,A054,A055,A059,A060,A061,A062,A063
0000004418 ffffffff ffff0720 ffff0720 ffff0720 0000f8df WA1041 0000 031 A048,A049,A050,A051,A052,A054,A055,A059,A060,A061,A062,A063
0000004420 ffffffff ffff0720 ffff0720 ffff0720 0000f8df WA1000 0000 030 A032,A033,A034,A035,A036,A038,A039,A043,A044,A045,A046,A047
0000004428 ffffffff ffff0720 ffff0720 ffff0720 0000f8df WA1040 0000 030 A032,A033,A034,A035,A036,A038,A039,A043,A044,A045,A046,A047
0000004430 ffffffff ffff0720 ffff0720 ffff0720 0000f8df WA1000 0000 031 A032,A033,A034,A035,A036,A038,A039,A043,A044,A045,A046,A047
0000004438 ffffffff ffff0720 ffff0720 ffff0720 0000f8df WA1040 0000 031 A032,A033,A034,A035,A036,A038,A039,A043,A044,A045,A046,A047
0000004480 ffffffff ffff0720 ffff0720 ffff0720 0000f8df WA1000 0000 034 A032,A033,A034,A035,A036,A038,A039,A043,A044,A045,A046,A047
0000004488 ffffffff ffff0720 ffff0720 ffff0720 0000f8df WA1040 0000 034 A032,A033,A034,A035,A036,A038,A039,A043,A044,A045,A046,A047
0000004490 ffffffff ffff0720 ffff0720 ffff0720 0000f8df WA1000 0000 035 A032,A033,A034,A035,A036,A038,A039,A043,A044,A045,A046,A047
0000004498 ffffffff ffff0720 ffff0720 ffff0720 0000f8df WA1040 0000 035 A032,A033,A034,A035,A036,A038,A039,A043,A044,A045,A046,A047
00000044a0 ffffffff ffff0720 ffff0720 ffff0720 0000f8df WA1001 0000 034 A048,A049,A050,A051,A052,A054,A055,A059,A060,A061,A062,A063
00000044a8 ffffffff ffff0720 ffff0720 ffff0720 0000f8df WA1041 0000 034 A048,A049,A050,A051,A052,A054,A055,A059,A060,A061,A062,A063
00000044b0 ffffffff ffff0720 ffff0720 ffff0720 0000f8df WA1001 0000 035 A048,A049,A050,A051,A052,A054,A055,A059,A060,A061,A062,A063
00000044b8 ffffffff ffff0720 ffff0720 ffff0720 0000f8df WA1041 0000 035 A048,A049,A050,A051,A052,A054,A055,A059,A060,A061,A062,A063
0000004100 ffffffff ffff0772 ffff0772 ffff0772 0000f88d WA0000 0000 020 A000,A002,A003,A007,A011,A012,A013,A014,A015
0000004108 ffffffff ffff076f ffff076f ffff076f 0000f890 WA0040 0000 020 A004,A007,A011,A012,A013,A014,A015
0000004110 ffffffff ffff0775 ffff0775 ffff0775 0000f88a WA0000 0000 021 A001,A003,A007,A011,A012,A013,A014,A015
0000004118 ffffffff ffff0774 ffff0774 ffff0774 0000f88b WA0040 0000 021 A000,A001,A003,A007,A011,A012,A013,A014,A015
0000004120 ffffffff ffff0765 ffff0765 ffff0765 0000f89a WA0001 0000 020 A017,A019,A020,A023,A027,A028,A029,A030,A031
0000004128 ffffffff ffff073a ffff073a ffff073a 0000f8c5 WA0041 0000 020 A016,A018,A022,A023,A027,A028,A029,A030,A031
0000004130 ffffffff ffff0720 ffff0720 ffff0720 0000f8df WA0001 0000 021 A016,A017,A018,A019,A020,A022,A023,A027,A028,A029,A030,A031
0000004138 ffffffff ffff0753 ffff0753 ffff0753 0000f8ac WA0041 0000 021 A018,A019,A021,A023,A027,A028,A029,A030,A031
If you are getting failure for first MB of FB then try option -no_scan_out
Error Code = 00000001
####### #### ######## ###
####### ###### ######## ###
## ## ## ## ###
## ## ## ## ###
####### ######## ## ###
####### ######## ## ###
## ## ## ## ###
## ## ## ######## ########
## ## ## ######## ########
-
#1
I’ve been testing my new system for a few days, now. I’m running the Ryzen 3600 processor on an Asus Crosshair 6 Hero (x370) mainboard, BIOS version 7106 and 32 GB RAM (Crucial Ballistix LT Sport Red, 2 x 16 GB Dual Rank, 3200 MHz XMP).
When running MemTest64, my system usually becomes unstable. Programs just dont work correctly anymore and the system does not recover. Screens might become black, too. In contrast to <this thread here>, I’ve only allocated 8 out of 12 threads and only around 80% RAM. So it can’t be the problem that Windows runs out of memory completely. Unless it’s a weird fragmentation issue with the Windows scheduler/allocator.
I first thought my RAM is defective, but ruled that out. All other stress tests and memory test tools worked without any problem so far. To be completely honest, I can’t exactly remember whether or not I had a freeze/crash/whatever at the beginning where MemTest64 was not involved. However, I’m quite confident now that I only have issues with MemTest64.
<I posted a longer version of this on Reddit>
Initially I Thought it might be a compatibility issue or simply just a BIOS bug since many issues get reported with the new Zen2 BIOS versions.
Now a friend of mine could reproduce the same behaviour with MemTest64 (also running the Asus C6H board but a Ryzen 1800X). His system has been stable for a long time now. So that settles it for me and I have to say that MemTest64 just is not stable.
One thing that I have to add: I’ve already ran MemTest64 for 8 hours straight, but was not using the computer at that time, mostly. So, MemTest64 only seems to be unstable when other programs are running. Also quite a few times the issues arised when I opened a program and a UAC request was shown to click «yes» or «no». I’d have a black background (instead of the desktop background), and I’d be able to click «yes» but then the system would be in a weird, instable state already.
-
#2
Don’t set it to allocate that much memory. That memory is effectively gone from other applications, so if you have several other apps open they will get paged out to the pagefile = run ULTRA SLOW, this includes the OS
This is expected behavior. MemTest64 doesn’t even run with administrative privileges, it has no low-level hardware access, so it can’t do anything that makes the system unstable.
Edit: you are running OCCT and MemTest64 at the same time?
-
#3
Well I only allocated like 25 GB out of 32 GB. I’d say 7 GB is plenty for Windows to operate. MemTestPro for example doesn’t show similar problems when I allocate that amount or even more.
Edit: you are running OCCT and MemTest64 at the same time?
Yes, I wanted to stress my system while testing the memory. However running OCCT is not a necessity to make the system unstable. It’s just been fast to trigger it. Sometimes even before I start the stress test, e.g. while starting the program or more specifically while the Windows UAC request asks me if I want to start the program.
In general, if I do tasks (not too heavy on either memory or CPU, considering it’s 4 threads and around 7GB of memory left), the system will usually become unstable after a while if MemTest64 is running. Even when the task manager shows 80-90% free memory. For reference, 90% means there is still 3.2GB left.
MemTest64 doesn’t even run with administrative privileges, it has no low-level hardware access, so it can’t do anything that makes the system unstable.
That’s what I thought too, so this is even stranger.
Maybe the following has to do something with it? MemTest64 usually fails to allocate the memory in its first (or second, or third, …) try, even though there is enough memory left.
Example — imaginary — run:
- Around 30 GB free memory
- MemTest64 tries to allocate 25GB, fails when it has allocated 8 GB
- MemTest64 tries to allocate 25GB, fails when it has allocated 15 GB
- MemTest64 tries to allocate 25GB, fails when it has allocated 20 GB
- …
- MemTest64 runs.
It’s not always like this and it’s not always that MemTest64 allocated increasing amounts of RAM with each try. Sometimes it works at its first or second try. I’m not sure if this behaviour is expected and why it is occurring. Maybe this hints to some underlying problem, I don’t know.
-
#4
Check page faults with Task Manager, that shows you when Windows is making use of the page file
-
#5
It’s not like every page fault automatically is a read/write to the pagefile. However, I think I’m ready to let this rest and am not really looking forward to investigating the issue further.
If you are certain that it’s expected behaviour then it might very well be. I was just not experiencing anything like it with e.g. MemTestPro and there always was free memory left for Windows to allocate. That’s what keeps me wondering if something else is going on. Maybe the way MemTest64 works is triggering an edge case in Windows — Or it is as you say and it’s simply expected behaviour 
Thanks for your replies.
-
#6
(Yes, I know this is a 2 year old thread)
I’m seeing the same trouble with MemTest64 (v1.0) myself. More specifically, I can’t get it to allocate even 60% of my memory even when I boot in safe mode, it will usually do 50% or less, though maximum mode rarely finds >10 on my 64gb machine even when otherwise idle.
Worse yet, MemTest64 can consistently crash dwm.exe with an Event 1000 problem. Typically with 20gb of memory still free at the time.
Note: I’ve run a full windows memory diagnosis, passed, and aida 64 memory stress test was able to allocate 54gb without any problems. So I’m relatively certain the memory itself isn’t the problem.
So, I’m left wondering what MemTest64 is actually doing, how it’s allocating memory, what «Memory locking failed (might be reserved by other apps/kernel)» means in technical terms (been developing sw for 35 years now..) and how the heck is it possible for a user app to crash the windows 10 desktop window manager process.
Any thoughts?
-Peter
-
#7
MemTest64 can consistently crash dwm.exe with an Event 1000 problem.
First time I’m hearing about that. Anything that makes your setup special?
So, I’m left wondering what MemTest64 is actually doing, how it’s allocating memory, what «Memory locking failed (might be reserved by other apps/kernel)» means in technical terms (been developing sw for 35 years now..)
if (VirtualLock((PBYTE)memory + locked, lockSize) == FALSE)
{
Log(_T(«Memory locking failed (might be reserved by other apps/kernel)»));
VirtualFree(memory, 0, MEM_DECOMMIT | MEM_RELEASE);
and how the heck is it possible for a user app to crash the windows 10 desktop window manager process.
This shouldn’t happen. Do you have a super high number of page faults when this happens?
Do you have a pagefile? On HDD or SSD?
-
#8
Anything that makes your setup special?
Not particularly.. 24 core AMD 3900x, 64gb ram, 2tb ssd, page file set to auto, win 10 up to date through Apr’22. Software developer, generally running: visual studio’22 x 2 or 3, chrome, a bunch of chat apps, market data, …
Thread over on LTT with the various system details… https://linustechtips.com/topic/142…ry-used-feels-like-swapping/#comment-15354309
This shouldn’t happen. Do you have a super high number of page faults when this happens?
Not entirely sure. When this happens Task Manager says I still have north of 15gb of ram free.. Then the whole screen goes blank and things freeze up for a good 5-15 seconds. When they sort of come back much of windows isn’t right at that point (lost my night shade, taskbar doesn’t refresh, most apps blank till I forcefully minimize and resize them). I did see once a large amount of activity on the page file after things came back, but it’s hard to know if that’s a before or after the blank screen given the latency in those stats.
Do you have a pagefile? On HDD or SSD?
SSD, 2tb, which is about 90% full, but still has ~190gb free. Currently about an hour after a restart, I have a 11gb page file, but I’m not sure why. Commit charge on task manager is 24gb.
if (VirtualLock((PBYTE)memory + locked, lockSize) == FALSE)
I was hoping that would have been much more fancy to explain what’s going on.. I’m assuming you’ve done the relevant SetProcessWorkingSetSize bits so it’s not hitting some sort of process limit. I don’t suppose you’re calling GetLastError by chance? That could improve the Memory Locking Failed message.
Some threads on the ether attribute dwm problems like this to video driver issues. I’ve clean installed them (RTX 2060) just in case. Really not sure how your app allocating/using memory could trigger video driver issues, let alone crash a system app.
I should add a few notes:
- I’ve been able to get MemTest64 to allocate up to but not over 32gb.
- The screen blanking bit happens more often than the dwm crashing shows up in the event viewer.
- The problems have happened with as little as 15GB utilized in the test, typically in the last step (which is the longest running time, which may be the correlation)
- I typically turn the threads down to 12, so the rest of my system doesn’t (poop) during the test.
Cheers,
Peter
-
#9
Did a quick test on a Ryzen, Windows 11, 64 GB machine. Same problem. Will investigate more over the coming days
-
#10
Did a quick test on a Ryzen, Windows 11, 64 GB machine. Same problem. Will investigate more over the coming days
I needed to ask this question for some time.
Is it possible when a fault is detected, can a alarm sound be outputted via the normal sound output or via the motherboard speaker? This goes for all program that test ram AIDA64, Prime95, ect, ect,
ie any program that test ram.
The reason am asking is, i use a external hardware ram tester & when a fault occurs it sounds a alarm via the motherboard speaker. This saves a lot of time monitoring watching the screen for faults. I can then pause the program & say the very first fault appeared at a specific location first.
-
#11
Did a quick test on a Ryzen, Windows 11, 64 GB machine. Same problem. Will investigate more over the coming days
I have a second machine that’s a Ryzen 5400G, Win 10, 32GB, with no video card.. And it’s fine. As a third data point.
Cheers,
Peter
Test Results
All tests passed!
Total built-in memory: 8 GB
This is the total amount of physical memory that the computer has installed. If this figure is not showing the correct amount of memory there may be a problem with one or more installed DIMMS.
Available memory: 6955 MB
Available memory is the amount of physical memory that is currently not in use by any other processes. All available memory will be used for testing when the «All» option is selected. To increase the amount of available memory, you can restart your computer before testing. If you are familiar with the command line (CLI), you can run memtest (the core of Rember) in single-user mode. See Rember help, or http://www.memtestosx.org for more information.
Requested amount: All MB
The total amount of memory requested for testing by the Rember application. Not all requested memory can be allocated for testing. See information on «Available memory» for more information.
Memory allocated for testing: 6760 MB
This is the total amount of memory that memtest was able to allocate for testing. See «Available memory» section for more information.
——-
Loops selected: 1
Total loops selected by user for testing. All loops should complete when testing is successful. Test failure when the «Continue on Error» preference is selected will cancel tests before this number of loops has been completed. Users can also cancel testing before this number is reached.
Loops completed: 0
Total loops completed by memtest. Note that the Rember is not always able to identify how many loops ran. If there are discrepancies between this and the loops selected, the log should be examined to determine exactly how many loops were performed.
——-
Total execution time: 159 seconds
This is the total amount of time that it took to execute the selected tests. Execution time may vary from system to system, and is provided as a guide for determining how long users can expect tests to run based on the amount of memory installed on the system.
Testing start time: 2009-01-22 16:29:53 -0700
Testing end time: 2009-01-22 17:58:59 -0700
-
- Nov 24, 2020
-
- 18
-
- 0
-
- 1,510
- 0
-
- Apr 17, 2019
-
- 3,282
-
- 1,000
-
- 10,940
- 426
-
#2
I would do what Corsair recommended and try manually setting the RAM frequency (speed) and primary timings in the BIOS and see if that works.
You could also set the XMP profile BUT then set the RAM frequency lower (try 2933) and see if that works.
If 2933 works then try 3200 and if that works you can try 3466.
Or return that Corsair RAM kit and get a G.Skill or Crucial kit that is listed on your motherboards Memory compatibility list (for Ryzen 3000 CPUs).
-
- Jan 29, 2008
-
- 3,069
-
- 1,098
-
- 23,390
-
- 185
-
#3
So are saying you are trying to load the XMP profile and it just doesn’t take on reboot? Upon POST (Power On Self Test) the memory tries a quick check at rated speed. If it fails to read/write properly it will revert to it’s safe defaults.
If you are on manual mode, you are bypassing XMP profile settings. You are saying you want to hand enter them. If you hand enter them make sure your voltage is 1.35V. I assume all your other timings also match. Also look at the memory temperatures if possible. If you knocked the heat spreader loose, it might explain why it’s getting flakey. Also anything over 3200MHz is overclocking and not guaranteed. While 3600MHz is pretty common for most, 4 slots populated is really pushing your luck with that memory. (You didn’t say how many sticks you had)
DMAN is correct however. Corsair never made the best quality memory. Back off one or two speed bumps and try again.
-
- Nov 24, 2020
-
- 18
-
- 0
-
- 1,510
- 0
-
#4
-
- Apr 17, 2019
-
- 3,282
-
- 1,000
-
- 10,940
- 426
-
- Nov 24, 2020
-
- 18
-
- 0
-
- 1,510
- 0
-
#6
0.000: Detecting usable memory (16328 MB theoretical max)…
14.953: 13952 MB Test starting on 12 CPUs…
14.969: Allocating memory…
20.422: Memory locking failed (might be reserved by other apps/kernel)
24.110: Test finished with no errors detected
(Second test)
had 0 errors
(third test)
I will do when I get more time for those.
-
- Apr 17, 2019
-
- 3,282
-
- 1,000
-
- 10,940
- 426
-
#7
If it fails to allocate the Memory again lower the amount in the drop down box to 10 or 11 GB.
-
- Nov 24, 2020
-
- 18
-
- 0
-
- 1,510
- 0
-
#8
-
- Apr 17, 2019
-
- 3,282
-
- 1,000
-
- 10,940
- 426
-
#9
For a thorough test you can let it run overnight.
-
- Nov 24, 2020
-
- 18
-
- 0
-
- 1,510
- 0
-
#10
-
- Apr 17, 2019
-
- 3,282
-
- 1,000
-
- 10,940
- 426
-
#11
That will eliminate Windows from the equation.
-
- Nov 24, 2020
-
- 18
-
- 0
-
- 1,510
- 0
-
#12
also thanks for the reply’s 
-
- Apr 17, 2019
-
- 3,282
-
- 1,000
-
- 10,940
- 426
-
#13
If it returns errors run it set at a lower speed (like 3200).
And just to be clear you are setting the XMP profile (so that the timings and voltage get properly changed) and then lowering the Memory Frequency correct ?
Last edited: Nov 25, 2020
-
- Nov 24, 2020
-
- 18
-
- 0
-
- 1,510
- 0
-
#14
First stick I tested (8gb stick)
file:///C:/Users/davyb/OneDrive/Desktop/1st%20stick%20tested%20(A_2)/MemTest86-Report-20201118-231604.html
Second stick I tested (the other 8gb stick from the kit)
file:///C:/Users/davyb/OneDrive/Desktop/2nd%20Stick%20tested%20(B_2)/MemTest86-Report-20201119-070745.html
-
- Apr 17, 2019
-
- 3,282
-
- 1,000
-
- 10,940
- 426
-
#15
That lets you know the RAM is not actually faulty.
So you just need to figure out what speed they will actually work at.
-
- Nov 24, 2020
-
- 18
-
- 0
-
- 1,510
- 0
-
#16
file:///D:/EFI/BOOT/MemTest86-Report-20201125-005246.html
And here is a picture of the settings I had for my ram.
file:///D:/201125005208.BMP
-
- Apr 17, 2019
-
- 3,282
-
- 1,000
-
- 10,940
- 426
-
#17
You need to post them somewhere (Google Drive/Imgur) they can be viewed by anyone.
They are currently just stored on your PC.
-
- Nov 24, 2020
-
- 18
-
- 0
-
- 1,510
- 0
| Thread starter | Similar threads | Forum | Replies | Date |
|---|---|---|---|---|
|
D
|
Question New 32GB ram not working | Memory | 4 | Thursday at 10:34 AM |
|
Y
|
[SOLVED] Can XMP just not work anymore? | Memory | 6 | Tuesday at 3:57 PM |
|
—
|
Question XMP3 on X670E? Will this combination work? | Memory | 3 | Jan 20, 2023 |
|
|
Question Best RAM capacity / frequency for working with i9 13900KS? | Memory | 2 | Jan 17, 2023 |
|
|
Question G skill 7800 cl36 xmp’s don’t work | Memory | 1 | Jan 16, 2023 |
|
S
|
Question G.Skill Trident Z RGB Not Working | Memory | 2 | Jan 13, 2023 |
|
D
|
Question HELP: WHY WONT BOTH OF MY DDR5 RAM STICKS WORK??? | Memory | 5 | Jan 8, 2023 |
|
E
|
Question Will this memory work in my Dell laptop | Memory | 3 | Jan 8, 2023 |
|
|
[SOLVED] 2 pieces of ram, one works, one doesnt. Both work in a seperate computer | Memory | 12 | Jan 8, 2023 |
|
K
|
Question 2 x RAMs work in red slots but not in black slots ? | Memory | 5 | Jan 7, 2023 |
- Advertising
- Cookies Policies
- Privacy
- Term & Conditions
- Topics
Looks like no one’s replied in a while. To start the conversation again, simply
ask a new question.
Hi,
I’ve just ran memtest for some new RAM on my iMac. In the logs i got this:
«ERROR: Memory lock failed — reason unknown.»
What does this mean? And Is it bad?
Thanks
iMac,
Mac OS X (10.6.4)
Posted on Sep 21, 2010 7:04 PM
2 replies
Sep 22, 2010 2:19 AM in response to freddoongo
Hi fred,
This question is asked in the rember support page at the bottom and the answer is there as well.
http://www.kelleycomputing.net/support/rember/
Whilst technical yes, bad no.
Memtest Memory lock failed
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:
-
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. -
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. -
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.