Using Consume.exe stress testing tool.

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.

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Eugene ZCommented:
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


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
deek22Author Commented:
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.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.