Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
How can I determine how much memory each device driver is consuming? I’m assuming this can be done with some Win32 or .NET API, but I just haven’t been able to determine which.
I know this is non-trivial. Here are some starting points for closely related questions:
You can get a (likely unsatisfactory) start by using VirtualQueryEx to determine the memory used by PE files, heaps, etc. Here is one program that provides a Virtual memory map view. This should answer the image size of the device driver.
The larger difficulty is in determining how to tag memory that is allocated dynamically by the code that is allocating it. The best shot there is to use something like detours to track the dynamic memory allocations as they are made and walk the stack to determine the orginator. Finally the fact that you wish to do this for device drivers takes it one step further. I doubt detours can be used for device drivers (though I don’t know definitely). I do know walking the stack from a device driver is highly non-trivial.
You may also be able to get the data you want from ProcExp in the SysInternals suite. Run it Go to ‘System’, go to View/show lower pane, enable Dll’s. Then right click on the column headers and add the ones for working set e.g. ‘WS Total’. I’m not sure what this does to properly label them memory. On my box it gives them mapped image size of device drivers, but simply has 0K in the Working set columns. I take the lack of an answer from procexp as reasonable evidence that solving this problem won’t be snap.
Good luck.