Post problem reports here for Batch files for use in BSOD debugging

Ztruker said:

Is LOGS.bat important enough to merit all this effort?

In the spirit of being a team player I thought it was worth my time making sure that batch files are safe and GDPR compliant if they are going to be used. I probably will not use it unless there is no other way of getting the information needed. zbook has shown that in some cases it can reveal useful data that is not found in the standard log collector tool.

Also at some point in the future Microsoft is going to remove the wmic function from W10 and so all batch files that rely on wmic functions will stop working. PowerShell becomes the new way and the syntax of the commands will be slightly different. No one seems to know when this will happen but it might be worth getting ready for it.

The Tuneup scripts use WMIC

Hopefully, WMIC will not be removed, and users are free to choose between WMIC and PowerShell.

The command to collect the memory dump to the desktop displayed an error message:
Win10 BSOD driver power state failure
(post #20)

Please update the progress with LOGS PS1.

zbook said:

The command to collect the memory dump to the desktop displayed an error message:

The command should be run via PowerShell rather than Command Prompt.

zbook said:

Please update the progress with LOGS PS1.

Are you satisfied with the following version?

https://www.tenforums.com/attachment...gging-logs.bat

Do you want the collected files to be put into a ZIP file on the desktop?

zbook said:

There is an early flash....can this be eliminated / modified?

If you want to kill the flash, right-click on the file and select "Run as administrator".

zbook said:

Can you add commands from other scripts?

Any commands can be added if need be.

Please indicate whether logs ps1 is not collecting all of these:

Code:

C:\Windows\Panther\UnattendGC
C:\Windows\Panther\NewOS
C:\Windows\Panther\setupact.log
C:\Windows\Panther\setuperr.log
C:\Windows\Logs\MoSetup
C:\Windows\inf\setupapi.dev.log
C:\Windows\setupapi.log
C:\$Windows.~BT\Sources\Rollback
C:\$Windows.~BT\Sources\Panther
C:\$Windows.~WS\Sources\Panther\setupact.log
C:\$Windows.~WS\Sources\Panther\setuperr.log

This one I've identified:
C:\Windows\inf\setupapi.dev.log

Please add C:\Windows\inf\setupapi.dev.log and any others identified.

Tuneup_plus_log.bat has an algorithm where it does not run the second scannow.
I'm wondering about an algorithm that triggers a run of SFCfromFile.bat.