New
#11
Other results were good.Code:Windows Resource Protection found corrupt files and successfully repaired them.
Other results were good.Code:Windows Resource Protection found corrupt files and successfully repaired them.
First crash overnight. Windows would not boot afterwards, automatic repair failed on first attempt, but luckily was successful on 2nd attempt. A little apprehensive about restarting verifier now.
MEMORY7.DMP - Google Drive
Windows driver verifier has multiple commands to turn off or recover from using the tool:
verifier /reset, bootmode, restore, etc.
Using the tool should be useful in creating BSOD with different bugchecks.
The tool is used with system restore when the prior two commands fail to turn off the tool.
Macrium is normally not used and was added as an extra backup option:
Backup and Restore with Macrium Reflect
The bugcheck for the latest BSOD was 133 parameter 1.
Windows driver verifier was used with 3 customized tests.
There are approximately 19 customized tests used in the Microsoft link:
https://answers.microsoft.com/en-us/...3-c48669e4c983
See if you can review the methods used to turn off and recover from using the tool:
Enable and Disable Driver Verifier in Windows 10
Ideally the tool is used with approximately 19 customized tests for 48 hours. Then the tool is used for an additional 36 hours after the last BSOD.
The computer may become sluggish or the boots may become very slow. Customized tests can be added and removed so that all non-Microsoft drivers are exposed to the different customized tests.
When you are more comfortable the number of tests can be modified by 4 - 5 per hour so that all non-Microsoft drivers are exposed to the different customized tests.
OK so I just keep going then, uploading the v2 log and the memory dump each time?
The more the memory dumps the better.
It may take time to get non bugcheck 133 parameter 1.
And it may take several non bugcheck 133 crashes to find the misbehaving driver(s).
Here's another, still a 133/1, but this time it's also generated a NDIS dump.
Please increase the windows verifier customized tests by 4 - 5 / hour so that the drivers are exposed to the 19 different tests in this link:
https://answers.microsoft.com/en-us/...3-c48669e4c983
If there are major performance or boot problems then remove some customized test while adding others.
When available please post separate share links for each:
Code:Name LastWriteTime Size (MB) ---- ------------- --------- NDIS-20190525-2011.dmp 25/05/2019 20:11:56 1344.83Code:Crash dump found at C:\WINDOWS\MEMORY.DMP Creation date: 05/25/2019 20:09:47 Size on disk: 1414 MB
OK just uploading them now. Would you mind explaining how to increase tests by the required amount? The link above appears to be truncated.
Each time windows driver verifier is restarted:
a) select all non-Microsoft drivers
b) select customized tests
In this link it displayed how to select only 3 customized tests:
Enable and Disable Driver Verifier in Windows 10
There are approximately 21 different tests or boxes that can be checked.
In this link there are 19 customized tests or boxes to check:
https://answers.microsoft.com/en-us/...3-c48669e4c983
So the end user launches the application and then selects each the drivers and the tests for each run of the tool.
Oh I see. So I leave the initial 3 checked, then check 4 or 5 more per hour in addition to those 3, is that right? And any particular order or just start at the top and work down?