Using Consume.exe stress testing tool.
Posted on 2011-10-11
We are using Consume.exe utilitiy fromthe Windows 2008 SDK test memory consumption effects on one of our servers. The command we use to launch the utility is: "consume.exe -physical-memory". The test runs for about 15 minutes then reboots the server with a BSOD. Debug tools interpret the BSOD as follows:
No free pages available to continue operations.
If kernel debugger available, type "!vm 3 and !memusage 1".
This bugcheck usually occurs because the component owning the
modified nowrite pages failed to write out these pages after
marking the relevant files as dont-write to memory management.
This indicates a driver bug.
Arg1: 0000000000000006, Total number of dirty pages
Arg2: 0000000000000043, Number of nowrite dirty pages.
Arg3: 0000000000000009, Internal flags.
Arg4: ffffffffc0000054, Most recent modified write error status.
LAST_CONTROL_TRANSFER: from fffff8000174469f to fffff8000167ec40
Has anyone used this tool before and had this problem? Is a time limit required to keep your machine from crashing? (ex. consume.exe -physical-memory -time 30)? The system is running W2k8R2 with 16Gigs RAM. All hardware test passed according to HP. We are stress testing for MS SQL 2008 install.