Please see post #20 and #22
Code:
The plan is to use windows driver verifier to cause crashes by stressing drivers.
There may be decreased performance and slow boots while using the tool.
(do not use the tool until it is communicated in the thread)
Code:
Plan to run the tool for approximately 48 hours. And then for an additional 36 hours after the last BSOD.
Start with the three customized tests in the Ten Forums link:
Enable and Disable Driver Verifier in Windows 10
Always make a new restore point before using the tool.
The testing was to be performed with only three customized tests.
Please restart testing using the customized settings in the Ten Forums link.
When the tool is used there can be immediate and delayed BSOD.
Start with the three customized tests. Test all non-Microsoft drivers simultaneously.
If there are no major performance or delayed boot problems then increase the number of customized tests by two to four per hour. If there are problems with performance or boot then remove some of the customized tests. The goal is to expose all of the non-Microsoft drivers to all of the customized tests displayed in the Microsoft link.
If you are able to identify a customized test that causes a major change in performance that test behavior may change as drivers are modified or uninstalled. Alternatively you can try running the tool wit only one customized test. Allow sufficient testing time for bot immediate and delayed BSOD.
There is a lot of flexibility wile using the tool. Over 48 hours all of the non-Microsoft should be exposed to all or almost all of the 19 customized tests. Then the tool is run for additional 36 hours of typical computer use.
After each BSOD you should use the computer's windows advanced troubleshooting menu to turn off the tool (safe mode with reset or command prompt with bootmode). When back to the desktop run V2 and post a share link for the memory dump if the file size is <1.5 GB.
If there are problems turning off the tool you may be able to use system restore. Often though system restore can lead to a loss of the dump file. If there is no dump file then there is little progress in the troubleshooting. If you have available the windows advanced troubleshooting menu on a DVD or USB they can be used following the instructions in the Ten Forums link (command prompt bootmode and system restore)
For the troubleshooting if possible uninstall software, otherwise uninstall and reinstall.
https://answers.microsoft.com/en-us/...0-8d22254aa1c1
Uninstall and reinstall: SteamStreamingMicrophone.sys
Code:
SteamStreami Steam Streaming Microp Steam Streaming Microp Kernel Manual Running OK TRUE FALSE 8,192 8,192 0 07/28/17 08:33:15 AM C:\Windows\system32\drivers\SteamStreamingMicrop 4,096
Code:
Name Steam Streaming Microphone
Manufacturer Valve Corporation Audio DDK
Status OK
PNP Device ID ROOT\STEAMSTREAMINGMICROPHONE\0000
Driver c:\windows\system32\drivers\steamstreamingmicrophone.sys (, 39.78 KB (40,736 bytes), 04/30/19 08:30)
Code:
SteamStreamingMicrophone.sys Fri Jul 28 08:33:15 2017 (597B593B)