[Last Call] Learn how to a build a cloud-first strategyRegister Now


Using Consume.exe stress testing tool.

Posted on 2011-10-11
Medium Priority
Last Modified: 2012-05-12
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.

Debugging Details:



PROCESS_NAME:  svchost.exe


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.

Question by:deek22
LVL 43

Accepted Solution

Eugene Z earned 2000 total points
ID: 37067589
it means test was done as requested
physical-memory - Consumes physical memory so that applications are forced to operate on lowered amounts.

-time Seconds - Used in conjunction with the above, this switch specifies the amount of time to consume the specified resource.
looks like all the same as for win2003


Author Closing Comment

ID: 37089340
Thanks EugenZ.  Your answer is close enough.  

Here is the official answer from the consume.exe developer at Microsoft.

There were some design changes in consume.exe after W2k3.  
In W2k8 and R2, it is always recommended to run consume.exe through Loadgen tool as Loadgen would dynamically monitor and adjust system load level as needed.
Also in W2k8 and R2 the switches other than cpu and memory have been disabled for released versions of consume.exe

It could be an issue if there’s a driver that’s leaking memory
In this case the exception was not a driver bug because the system memory resource was intentionally depleted by consume.exe
So please go ahead and ignore that message.

Featured Post

Veeam Disaster Recovery in Microsoft Azure

Veeam PN for Microsoft Azure is a FREE solution designed to simplify and automate the setup of a DR site in Microsoft Azure using lightweight software-defined networking. It reduces the complexity of VPN deployments and is designed for businesses of ALL sizes.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
What if you have to shut down the entire Citrix infrastructure for hardware maintenance, software upgrades or "the unknown"? I developed this plan for "the unknown" and hope that it helps you as well. This article explains how to properly shut down …
Via a live example, show how to shrink a transaction log file down to a reasonable size.
This tutorial will show how to configure a single USB drive with a separate folder for each day of the week. This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten. The USB drive must be s…

829 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question