Driver Memory Test
Driver non-paged memory usage constitutes a fixed cost in memory utilization for the overall lifetime of a system. Most drivers exist in memory at all times and this usage significantly contributes to the total operating system memory footprint. By optimizing driver memory, you can provide an improved user experience and better overall system responsiveness because of the greater availability of memory for user applications.
Any reduction in non-pageable driver footprint directly improves the baseline memory consumption of the operating system, and this increases system scalability. Current Windows Hardware Certification Kit (Windows HCK) tests cover driver locked allocations (MDL/Contiguous memory allocations), non-paged driver code, and non paged pool.
Test details
|
Associated requirements |
Device.DevFund.Memory.DriverFootprint |
|
Platforms |
Windows RT (ARM-based)
|
|
Expected run time |
~30 minutes |
|
Categories |
Certification |
|
Type |
Automated |
Running the test
Troubleshooting
| Error | Description | Workaround |
|---|---|---|
|
Test failed for events lost during ETW tracing. |
Driver memory test gets driver memory details from ETW trace. Events lost can happen during ETW tracing. Data for failed tests might be unreliable. |
This issue is usually caused by insufficient disk bandwidth or buffer for ETW logging. Increase the amount of installed RAM to resolve this error. |
|
Couldn’t stop kernel logger (0x00000070) Couldn’t stop user-mode logger (0x000070) |
There is not enough space on the disk. |
Free up disk space. |
More information
Command syntax
| Command option | Description |
|---|---|
|
TE /inproc /enablewttlogging /appendwttlogging devfund.memorytest.dll /p:DQ=[DQ] /p:WDKDeviceID=[WDKDeviceID] /p:WPTPath=[WPTPath] |
Runs the test. |
 Note |
|---|
| For command line help for this test binary, type /h. |
File list
| File | Location |
|---|---|
|
Devfund.memorytest.dll |
<testbinroot>\OSBinRoot]\ |
|
TE,exe |
<testbinroot>\OSBinRoot]\ |
