Please complete the steps that Matthew Wai posted above (#21).
Then make a new restore point.
If you understand how to boot into safe mode to turn off the WDV tool then start WDV with the 3 customized tests in the TF link.
For any BSOD you must be able to return to the desktop running the applicable commands.
Then run V2 as it will collect any new files.
This was displayed in file:@Coach81
Please right-click on the Start button--> Windows PowerShell
Run the following command to open a text file:
CMD /C "%Temp%\#Dump_log.txt"
If the file is opened, upload it as an attachment or simply copy and paste the displayed text into your post.
Creation date and time Size (MB) File path
---------------------- --------- -----------------------------
2021-11-05 18:46:21 0,25 C:\Windows\LiveKernelReports\USBHUB3\USBHUB3-20211105-1846.dmp
Please right-click on the Start button
Run the following command to put the DMP file into a ZIP file:
Code:Compress-Archive -Path "C:\Windows\LiveKernelReports\USBHUB3\USBHUB3-20211105-1846.dmp" -Update -DestinationPath "C:\ZIP"
Post the output and see whether the file "C:\ZIP" has been created.
Zip file was created, had to run Powershell elevated as got an error message when done normally.Please right-click on the Start button
Run the following command to put the DMP file into a ZIP file:
Code:Compress-Archive -Path "C:\Windows\LiveKernelReports\USBHUB3\USBHUB3-20211105-1846.dmp" -Update -DestinationPath "C:\ZIP"
Post the output and see whether the file "C:\ZIP" has been created.
No file output just placed the single file into zip file.
The file in question is indeed 0.25MB
The script ran perfectly and will be uploaded.
- - - Updated - - -
When i start the process, should i just do the 3 customized tests for the duration or add additional testing as i go?
i think you mentioned adding 3-5 per hour so i just wanted to confirm.
Is this initial test for 48 hours or when there is a BSOD - whichever happens first?
Start with the 3 customized tests in the TF link.
If there are no BSOD and no major performance problems including very slow boot then add customized tests as per the earlier post.
See the image in the Microsoft link displaying 19 customized tests.
Run administrative command prompt: verifier /querysettings
if there is no immediate BSOD after each customization.
Post an image or share link of the command with results.
I'll be available for the next 4 - 5 hours.
Once in rhythm you'll be more comfortable using the tool.
After the next 4 - 5 hours I'll be unavailable for 5 - 6 or more hours.
Run the tool for 48 hours.
And run the tool for 36 additional hours after the last BSOD.
If there are no more BSOD then that will complete the use of the tool.
Read the prior post summary section again.
Misbehaving drivers can be uninstalled and the tool restarted.
Or replacement drivers can be immediately installed.
The results should be the same as long as you follow the 48 + 36 hour testing.
Quote