Sleep and PNP Fails on ARM
Issue Summary I'm trying to certify a https://learn.microsoft.com/en-us/windows-hardware/drivers/ifs/ driver with HLK tests where the client is ARM64. Because Microsoft's documentation states that physical hardware must be used, I purchased a https://www.microsoft.com/en-us/store/configure/surface-laptop-13-inch/8mzbmmcjzqv3. All the tests pass fine, except the https://learn.microsoft.com/en-us/windows-hardware/test/hlk/testref/6bd51c1b-3dad-4a5e-b46d-98c2fe91d1aa test. Parameters used Parameter Name Value DQ DriverBinaryNames='myDriver.sys' Wpa2skAesSsid kistestssid Wpa2PskPassword password ResumeDelay 10 WDTFREMOTESYSTEM TestCycles 4 IOPeriod 1 DriverVerifierAdditionalDrivers MSDMFilt.sys FSMFApiTest TRUE LogDriverVerifierEventsAsFailure FALSE Key Observations - This test passes fine when certifying for x86_64. - For ARM64 Virtual Machine, test passes. - For ARM64 (Physical device), the test fails every time. - When targeting another driver (not my own) `WDFILTER.sys` the test fails with the same symptoms - When targeting Microsoft's sample driver [passThrough](https://github.com/microsoft/Windows-driver-samples/tree/main/filesys/miniFilter/passThrough) the test fails with the same symptoms - The tests will pass fine with the TestCycle parameter set to `3`. It always fails when set to the default `4` cycles. Errors/Warnings - HLK Studio typically states that the test failed due to an unexpected reboot - The client device's event viewer system logs show several instances of this log: Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: TE.ProcessHost.exe (6136) consumed 63349456896 bytes, MsMpEng.exe (5332) consumed 301400064 bytes, and HLKAcmengine.exe (6944) consumed 116539392 bytes. - There are more logs regarding memory usage such as: `The Client License Service (ClipSVC) failed to start due to insufficient memory resources.` - Right before the test fails, an error appears on the client where the `TE.ProcessHost.exe` process says: breakpoint reached - The CMD prompt on the client right before the test fails will often show: `crash with exception code 0xC000027B occurred in module "TextInputHost.exe"` Question The above observations and errors/warnings seem to point to either the device or the test itself being the issue. I've factory reset the laptop already and also created a fresh .vhlk to use in Hyper-V but the outcome is the same. What is the root cause of the error? Is this a known problem? Can I workaround the problem? Is the problem the test or my device?SysVAD Virtual Audio Driver Sample updated
The Microsoft SysVAD Virtual audio Device Deriver (SYSVAD) sample code, used to demonstrate how to develop a WDM audio driver which exposes support for multiple devices, was updated on 4 December 2019. Changes include: Removal of the Phone Audio sample Addition of a WaveTest public sample Modification of the componentized audio samples to include the addComponent directive For more details and to download the sample code, please visit the SysVAD Virtual Audio Device Driver Sample page on docs.microsoft.com.Getting the November 2019 release of Windows 10 ready for release
As you are no doubt aware, Microsoft has announced that the November release of Windows 10 has reached the final stage. For complete details, please see this blog post from Brandon LeBlanc - Getting the November 2019 Update Ready for ReleaseDo YOU want to influence future Microsoft Cloud + AI Engineering products or services?
Do you want to play an early role, helping Microsoft build and test the features YOU need from Cloud + AI? Do you want to help us improve a product or service BEFORE development has begun? If you answered, YES, you should join the Customer & Partner Engineering Engagement Program. The Customer & Partner Engineering Engagement Program's goal is to deeply understand YOUR needs and intentions, allowing us to drive feedback into the creation of new services and products BEFORE development has locked the feature plans. Joining the program means you may be contacted to provide feedback in one of several methods: Complete an online survey Participate in roundtable and/or 1:1 conversations In-person meetings with an engineering team YOU decide how much, or how little, you participate. This program is entirely voluntary and you can unsubscribe at any time. We look forward to hearing YOUR comments, suggestions, and feedback! To join, go to https://aka.ms/hwpartnerengage/ today!Windows AI Platform: Windows ML APIs, DirectML APIs, Microsoft Compute Driver Model (MCDM)
As the industry continues to focus on Artificial Intelligence, the Windows 10 platform (starting with Windows 10 1803 and continuing through Windows 10 1903) is bringing the best tools for performing local, high-performance machine learning inferencing with the Windows AI Platform: Windows ML APIs - enabling machine learning inferencing DirectML APIs - providing operator-level access to ONNX 1.3 standard resources Microsoft Compute Driver Model (MCDM) - a driver model for compute and AI specific silicon for Windows This video from Build 2019 gives a great overview of the Windows AI platform.
