Perhaps we have different definitions of physical memory. The task manager screenshot does show that I'm consuming physical memory by the task manager's definition.

1
2

Attached is the modified version of the memory stressor tool I posted above. I have made it so that this version is able to consume both virtual and physical memory at the same time. I have also changed it so that it consumes between 50%-100% of the available memory, which I think is more relevant for stress testing applications.

It is still command line based. Usage is the same as before. Use the Windows CMD window to run it.

I have tested the program on my computer with about 2GB of ram. The results are shown in the screenshots above. Note the sinusoidal-like pattern of the memory usage in the Task Manager.

Note that I'm not sure what the program will do if you have more than 2GB of ram on your system and the program itself tries to consume more than 2GB of memory. There is a limit to the amount of physical memory the program can access on a 32-bit system so the memory stressor tool itself may shutdown if it runs into this memory limitation. However, I think it is unlikely you will run into this bug on a 32-bit system. It should run fine on a 64-bit system and should be able to access all the physical memory since there is a larger memory address space in 64-bit.

I wasn't able to find a memory stressor tool that would work for application testing. There were too many memory error checking tools listed on Google that made the search results useless. Perhaps someone knows of an already built tool that can do what the attached program does?