large FFTs is also decent at finding memory errors.
I've been using a custom FFT range of 800K - 800K, though I think any FFT value inside the large FFTs range should work.
Make sure 'Run FFTs in place' is not checked.
In prime.txt, add TortureAlternateInPlace=0 under TortureWeak to prevent P95 from testing in place. Testing in place will only use a bit of RAM, which we don't want.
You can create a shortcut to prime95.exe and add -t to the 'Properties > Target' field to immediately start testing using the settings in prime.txt.
Your target field should look like: "path\to\prime95\prime95.exe" -t.
You can also change the working directory of Prime95's config files to have one config to stress test your CPU and another config to stress test your RAM.
In the folder with prime95.exe, create another folder. This example will be called 'RAM' (without the quotes).
Copy prime.txt and local.txt to the folder you just created.
Adjust the settings in prime.txt as required.
Create another shortcut to prime95.exe, and in the target field, add -t -W<folder_name>.
Your target field should look like: "path\to\prime95\prime95.exe" -t -WRAM.
You can now use the shortcut to start Prime95 with the settings provided.