Question Extremely annoying and specific 128GB Ram problem after using 64GB

gbolcer

Distinguished
Apr 23, 2012
5
0
18,510
0
Sorry for the very specific details. I am going to put a support ticket into G.skill and Asus, but I wanted to see if anyone had any advice first.

Crosshair VIII Hero, bios 3003 12/04/2020 (southbridge Rev 51)
AMD Ryzen 9 3950X Family: F.17, Model 1.71 Revision MTS-80 @ x36-41 3.5Ghz - 4.2Ghz
G.SKILL Trident Z Royal Series 128GB (4 x 32GB) 288-Pin DDR4 SDRAM DDR4 3200 (PC4 25600) F4-3200C16Q-128GTRS
1333.6Mhz 3:40 20-19-19-19-43-62 1T (set to 3200Hz)

Memtest shows 128GB perfectly. Windows 10 x64 Pro shows 128GB perfectly.

64-bit Programs like Mysql or Java(15) will run and get memory allocation errors as soon as memory goes past 64GB. It's as if everything recognizes 128GB except when you really need to use it.

Any recommended bios settings, tests, or insights would be appreciated.
 
try enabling large page support in windows, its disabled by default (in windows)
  1. From the Start menu, open Local Security Policy (under Administrative Tools).
  2. Under Local Policies\User Rights Assignment, double click the Lock Pages in Memory setting.
  3. Click Add User or Group and type your Windows user name.
  4. Either log off and then log back in or restart your computer - unfortunately it won't work without this step.
apps need to be running in administrator mode for them to use large page allocation
java: https://www.oracle.com/java/technologies/javase/largememory-pages.html
mysql: https://dev.mysql.com/doc/refman/8.0/en/large-page-support.html
 
Reactions: gbolcer

gbolcer

Distinguished
Apr 23, 2012
5
0
18,510
0
Thank you, this looks really promising!

Got a little further:
Java HotSpot(TM) 64-Bit Server VM warning: JVM cannot use large pages because of bug in Windows GDI.

Also tried setting ava.exe javaw.exe and eclipse.exe to always run using Admin permissions, but no luck.

More info:
Windows 10 Pro 20H2 Build 19042.685
 
Last edited:

gbolcer

Distinguished
Apr 23, 2012
5
0
18,510
0
You running all this bare-metal right? Not vm or with a hypervisor, correct?
Thanks, not a vm.

I did find one problem. The 64GB may have just been a coincidence with the memory page performance that triggered non-threadsafe behaviors in the program. The java program was using the threadsafe Gson library to read part of a class into a non-threadsafe HashMap. I converted it to a ConcurrentHashMap and it hasn't crashed yet. In fact, after the change, the memory hasn't gotten anywhere near the 64GB yet, so that makes me think it was just thrashing on bad data or bloating on silent exceptions.

I'll have to do a standalone Java test. Any pointers or code to memory test large memory in Java would be appreciated. I'm thinking the mysql problem might be a different problem and actually solved by kerberos_20 's suggestion above.
 

ASK THE COMMUNITY