Overclock.net banner

1 - 20 of 143 Posts

·
Registered
Joined
·
67 Posts
Discussion Starter #1
Hi,

I am not the creator of this program, nor do I work with the company releasing it. I've been and I am part of the community from where this software originates.

Been wanting to share this program with a larger crowd for long, but it has been in a semi-closed alpha until now.

Let me present you Ram Test, a simple memory testing utility that is both very effective and accurate (finds errors better then i.e. HCI Memtest) and also very very fast. About 15 times faster then HCI memtest.



The program is made by Karhusoftware, a one man project from Finland. The program was born after the creator, Mustanaamio, got frustrated with how long it took to bench his memory configs with his Ryzen build last summer. He got pissed of enough to actually write his own memory tester, and it has been quite popular in finnish overclocker/computer enthusiast scene since. Mustanaamio sold licenses to Ram Test at io-tech.fi forums when the program was in alpha/beta, and has now released it 'to the wild'.

There is a large community behind this project at https://bbs.io-tech.fi/.

I rate Ram Test as the best memory testing utlity at this time, bar from using linux-mint and google's memorybench. But out of standalone utilities/programs in windows this is by far the most accurate, thorough and FAST. I repeat; about 15 times faster then HCI memtest. And no need to launch multiple instaces of the program! I can push 703% coverage on 12288 megabyte memory-run in 10 minutes, when HCI memtest only does ~45% covera in same time. HUUUUUUGE! Check my video, I show you the two of them against each other
smile.gif
You can skip to 12:00 mark to see how they compare, the beginning of the video is pretty much just showing of the program, and telling some tales about it's origins.
*edit*

A friend aproaced me saying that I should have ran 12 instances of HCI memtest, one per CPU-thread available. So I did a re-test, and the result is the same as the original:
*/edit*

Get it from here, 9.99 euros / lifetime license:

https://www.karhusoftware.com/ramtest/
Quote:
RAM TEST README

RAM Test is a fast and reliable memory testing software with a graphical user
interface. It can be used to test your system memory for hardware faults or an
unstable overclock.

The software supports up to 8 TB of memory on a 64-bit machine and up to 2 GB
of memory on a 32-bit machine. The testing algorithm scales for up to 64
threads and has optimized code paths for AVX and AVX2 capable processors.

1. SYSTEM REQUIREMENTS

Your system must meet the following requirements to be able to run RAM Test:

* Microsoft Windows 7 or later (supports both 32-bit and 64-bit versions)
* Microsoft .NET Framework 4.5 or later
* A CPU with full SSE2 support
* An internet connection during activation

2. INSTALLATION

RAM Test is a portable software and does not come with an installer. To get
the software up and running, follow the steps below:

1. Unzip the files to any folder in which your user account has full
permissions
2. Run ramtest.exe
3. Activate your license with the product key
4. Start testing

It is possible to "install" the software on a USB flash drive.

3. SETTINGS

Megabytes:

The amount of memory to test in megabytes.

If you have the paging file enabled and you use too large value, the test
may progress very slowly due to the operating system having to cycle pages
through your SSD/HDD.

Threads:

The number of threads to use for testing.

Optimal performance is achieved by specifying a value equal to the
number of processor cores in your system.

Beep on error:

Play a beep sound when a memory error is detected.

Stop on error:

Automatically stop testing when a memory error is detected.

Telemetry:

Allow the collection of the following additional personal and/or
anonymized data each time a test is finished:

* RAM Test version
* RAM Test platform (x64 or x86)
* Value of the megabytes setting
* Value of the threads setting
* Motherboard make and model
* Processor make and model
* Memory make and model
* Test duration
* Test coverage
* Test error count

4. HOW TO USE

Configure the settings to your preference in the graphical user interface and
click the start button to begin testing. To stop testing, just click the same
button again.

It is recommended to run the test for at least 10 minutes before drawing any
conclusions about the stability of your system memory. To detect intermittent
memory errors you should let the test run for at least one hour.

5. CHANGELOG

1.0.0.0 (20.12.2017):
+ Initial release

6. ADDITIONAL INFORMATION

Unstable or faulty memory can cause your computer to crash or worse. DO NOT
RUN THE SOFTWARE IF YOU HAVE ANY UNSAVED WORK OPEN. YOU HAVE BEEN WARNED.
Apologies for bad grammar, I am not a native English speaker but I try to be understandable
smile.gif
 

·
Registered
Joined
·
861 Posts
Looks interesting, looking forward to more reviews.
 

·
Registered
Joined
·
1,003 Posts
Quote:
Originally Posted by chibi View Post

Looks interesting, looking forward to more reviews.
I can guarantee this is currently best ramtester there is, I've been using this software almost as long as @CptKuolio and like him, i dont have affiliations with the creator.
 

·
Registered
Joined
·
861 Posts
Does this also stress the Cache similar to how HCI Memtest does?
 

·
Overclocking Enthusiast
Joined
·
11,378 Posts
Quote:
Originally Posted by CptKuolio View Post

I rate Ram Test as the best memory testing utlity at this time, bar from using linux-mint and google's memorybench. But out of standalone utilities/programs in windows this is by far the most accurate, thorough and FAST. I repeat; about 15 times faster then HCI memtest. And no need to launch multiple instaces of the program! I can push 703% coverage on 12288 megabyte memory-run in 10 minutes, when HCI memtest only does ~45% covera in same time. HUUUUUUGE! Check my video, I show you the two of them against each other
smile.gif
You can skip to 12:00 mark to see how they compare, the beginning of the video is pretty much just showing of the program, and telling some tales about it's origins.
It's possible to run Stress App via BASH. So are you saying this is better than running Stress App under Windows? Also no limited freeware version to test, we're meant to take your word for it?
 

·
Overclocking Enthusiast
Joined
·
11,378 Posts
I've just bought the tool and testing with known conditional settings that I use regularly with Stress App test. The tool is picking up errors in under 5 minutes where Stress App under BASH terminal normally takes 20 to 30 minutes. Obviously, more time is needed to see how well this isolates the memory but this tool is definitely worth a try.
thumb.gif
 

·
Premium Member
Joined
·
5,240 Posts
Quote:
Originally Posted by Silent Scone View Post

I've just bought the tool and testing with known conditional settings that I use regularly with Stress App test. The tool is picking up errors in under 5 minutes where Stress App under BASH terminal normally takes 20 to 30 minutes. Obviously, more time is needed to see how well this isolates the memory but this tool is definitely worth a try.
thumb.gif
You're a trusted source of vital info on overclock.net, Scone, I'll give it s try.
smile.gif
 

·
Registered
Joined
·
67 Posts
Discussion Starter #9
Quote:
Originally Posted by chibi View Post

Does this also stress the Cache similar to how HCI Memtest does?
I'm not familiar with how HCI stresses cache. RAM Test is built to test memory stability. Will ask Mustanaamio about this, though he is now aware of this thread. I dont know if he has account here.

Quote:
Originally Posted by Silent Scone View Post

It's possible to run Stress App via BASH. So are you saying this is better than running Stress App under Windows? Also no limited freeware version to test, we're meant to take your word for it?
No, can't run it on bash. Not sure what you are referring to with Stress App under Windows. This is Tool for memory stresstesting, nothing else. Better then HCI memtest, memtest 86 etc. for sure.

Yes unfortunately you do need to take my word for it. No demo or shareware available at the moment. If 10€/$ is too much of an gamble then dont buy it yet, wait for someone you know better than me to recommend it.
 

·
Overclocking Enthusiast
Joined
·
11,378 Posts
Quote:
Originally Posted by CptKuolio View Post

I'm not familiar with how HCI stresses cache. RAM Test is built to test memory stability. Will ask Mustanaamio about this, though he is now aware of this thread. I dont know if he has account here.
No, can't run it on bash. Not sure what you are referring to with Stress App under Windows. This is Tool for memory stresstesting, nothing else. Better then HCI memtest, memtest 86 etc. for sure.

Yes unfortunately you do need to take my word for it. No demo or shareware available at the moment. If 10€/$ is too much of an gamble then dont buy it yet, wait for someone you know better than me to recommend it.
I'm referring to Google Stress App Test ran through BASH terminal.
 

·
OC...D
Joined
·
27,888 Posts
Quote:
Originally Posted by Silent Scone View Post

I've just bought the tool and testing with known conditional settings that I use regularly with Stress App test. The tool is picking up errors in under 5 minutes where Stress App under BASH terminal normally takes 20 to 30 minutes. Obviously, more time is needed to see how well this isolates the memory but this tool is definitely worth a try.
thumb.gif
I did also, known good config ran 1H clean. Will test some more. But yeah, worth adding to the box of ram tools. (was $12 US - a bit pricey IMO)
Quote:
Originally Posted by Silent Scone View Post

I'm referring to Google Stress App Test ran through BASH terminal.
^^ which works very well in isolating the ram subsystem for stability testing. I still use a puppy linux USB to run it on various rigs.
thumb.gif
 

·
Iconoclast
Joined
·
30,430 Posts
Need to find some settings that are borderline stable to get a feel for error detection rates.
Quote:
Originally Posted by Silent Scone View Post

I've just bought the tool and testing with known conditional settings that I use regularly with Stress App test. The tool is picking up errors in under 5 minutes where Stress App under BASH terminal normally takes 20 to 30 minutes. Obviously, more time is needed to see how well this isolates the memory but this tool is definitely worth a try.
thumb.gif
What settings do you use with stressapptest?

On most of my systems, the default settings are not the fastest at finding memory errors.
 

·
OC...D
Joined
·
27,888 Posts
Quote:
Originally Posted by Blameless View Post

Need to find some settings that are borderline stab
What settings do you use with stressapptest?

On most of my systems, the default settings are not the fastest at finding memory errors.
that's not a problem.
wink.gif
Also want to be sure there's no false positives (errors in this case).
for bash GSAT, I use: stressapptest -W -M 28672 -s 7200 --pause_delay 14400
 

·
Iconoclast
Joined
·
30,430 Posts
Quote:
Originally Posted by Jpmboy View Post

that's not a problem.
wink.gif
Also want to be sure there's no false positives (errors in this case).
for bash GSAT, I use: stressapptest -W -M 28672 -s 7200 --pause_delay 14400
Have you tried adjusting the thread counts and or omitting the -W? Sometimes 1.5 threads per logical CPU, or the less CPU intensive memory copy tests in combination with the inversion tests can prompt errors faster.
 

·
Registered
Joined
·
67 Posts
Discussion Starter #16
Quote:
Originally Posted by Silent Scone View Post

I'm referring to Google Stress App Test ran through BASH terminal.
I have 'limited' amount of experience with that, then! I began my memory OC tries and "getting into memory beyond XMP profile" stuff by reading guides on this forums, like the 'Official Intel Memory stability thread' and the 'Comprehensive Memory Overclocking Guide'. Those threads were pretty much my starting point for me about 8-9 months ago, little after Ryzen launch and little after The Stilt was hyping memory speeds on Ryzen at io-tech forums. Afterwards I closely followed ryzen overclocking and ryzen memory threads here.

I followed the procedures given in those threads, and so I also tried the Google Stress App, with linux mint on USB drive. Also used the same drive to run /kill ryzen and determined that mine was one of those that segfault, but that is another story. But also that was something I learned from this forum. Nevertheless I found it 'cumbersome' to say the least to boot into Linux and run stress-test while having all other OC-tools on windows (ryzen timing checker, at that time ryzen master because nothing else showed some values correct, hwinfo etc.) so I gave up on that and started lookin at HCI memtest. But with HCI-Memtest the whole process of testing memory was so slow and felt so 'inaccurate', that it was a total pain to hunt for the correct settings with Ryzen.

This all changed after Mustanaamio released the first iteration of this software and stilt was raving over it, because it made his workflow a lot faster with the ryzen timing things he was doing back then. RAM Tests first iteration was fast, a lot faster then other windows utilities. Mustanaamio has been updating RAM Test over the past months, and it has been getting even more faster all the time. I used to run a lot of HCI memtest after running RAM test, to verify that the RAM is 'hci-stable', and from that I noticed that many times RAM Tester showed up errors that HCI did not.

So I avoid comparing RAM Test to Google's Stress App, because I have too limited experience with it. I've only ran it a handful of times. I see that people here are testing RAM Tester and comparing it to Stress App, and it is very interesting to follow! Thanks guys
thumb.gif
But I also think that perhaps Stress App is not the 'main competitor' here, but the windows platform programs are. Nevertheless, this was what I was expecting, to see OC guys and gals to get arms deep to testing RAM Test
thumb.gif


My motivation to bringing this RAM Test software to this forum is simple; I've learned so much from threads here that I feel like it's only fair to give back. RAM Test revolutionized how I feel about memory overclocking. Prior to to RAM Test it was a big and slow process to OC memory, mainly because it took so long to stress test between steps. Now I can literally run RAM Test for ten minutes, get to 700% coverage, and that gives me enough info if I'm in between steps and want to go further, or finetune and continue benching with current values. With other tools it takes much longer, every step you bench between different settings, even when changing one value by 1, takes hours. With ram-test it's a lot more like OC'ing your CPU in a way, where you hit prime running for 20 minutes between steps and see if it is "stable enough", and boot to bios to up the frequency even more
biggrin.gif
 

·
Overclocking Enthusiast
Joined
·
11,378 Posts
Quote:
Originally Posted by Blameless View Post

Need to find some settings that are borderline stable to get a feel for error detection rates.
What settings do you use with stressapptest?

On most of my systems, the default settings are not the fastest at finding memory errors.
What settings are you using? There are arguments that work better with cache, I've not used any that find memory errors quicker.
Quote:
Originally Posted by Jpmboy View Post

I did also, known good config ran 1H clean. Will test some more. But yeah, worth adding to the box of ram tools. (was $12 US - a bit pricey IMO)
^^ which works very well in isolating the ram subsystem for stability testing. I still use a puppy linux USB to run it on various rigs.
thumb.gif
It's simple here, as I know that simply dropping tRCD one clock is enough to throw 2 or 3 errors in GSAT.
 

·
Iconoclast
Joined
·
30,430 Posts
Quote:
Originally Posted by Silent Scone View Post

What settings are you using? There are arguments that work better with cache, I've not used any that find memory errors quicker.
Depends on the platform.

My LGA-2011v3 parts seem to crap out fastest simply by mixing some inversion threads in to the test, while my Vishera parts seem to fail faster with the less intensive copy test (probably a bottleneck somewhere using -W on them).
 
1 - 20 of 143 Posts
Top