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

zbook said:

In the bottom tuneup there is no empty row above or below the result for the first scannow:

Code:

Beginning verification phase of system scan.
Windows Resource Protection did not find any integrity violations.
==================================================================
    [DISM /online /cleanup-image /ScanHealth]

I have a suggestion. I can replace the following line with this text Results:

Beginning verification phase of system scan.

I don't think you have to read the above line.

zbook said:

The second scannow was missing.
There should be a second scannow (after restore health).

The second ScanNow was intentionally skipped because the first one had produced the following result:

Windows Resource Protection did not find any integrity violations.

The second will be skipped only if the first has produced the above result.
If you don't like that, I can modify the script accordingly.

The scannow and restorehealth results are easier to view with the row space above or below:
=============================================================================

Please add blank rows in the other parts of the txt report so that there is a space above and below:

=============================================================================

Ztruker said:

What about changing the NET SESSION to FSUTIL DIRTY QUERY for checking Admin level in our scripts?

NET SESSION caused the same problem even in normal mode in the following case:

Using CMD script and VBScript to control Windows Update

I think FSUTIL DIRTY QUERY should be used instead.

The V2 and DM log collectors create text files for event viewer entries.

PS1 LOGS will collect the event viewer files.
These often have information not seen in the text files.

Can you create a script that will collect event viewer results similar to PS1 LOGS?

Matthew Wai said:

Available here: Gather_additional_dump_files

It worked nicely in this thread:
Occasional DRIVER_POWER_STATE_FAILURE


If Ztruker agrees, please add to:
Batch files for use in BSOD debugging

zbook said:

Please add blank rows in the other parts of the txt report so that there is a space above and below:

=============================================================================

Updated version: 👉 Tuneup_plus_log.bat ✔️

Code:

    [SFC /ScanNow] 
Beginning system scan.  This process will take some time.
Results: 
 
Windows Resource Protection found corrupt files but was unable to fix some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.
 
==================================================================
    [DISM /online /cleanup-image /ScanHealth] 
Deployment Image Servicing and Management tool
Version: 10.0.19041.746
Image Version: 10.0.19042.746 
 
No component store corruption detected.
The operation completed successfully.
 
==================================================================
    [DISM /online /cleanup-image /RestoreHealth] 
Deployment Image Servicing and Management tool
Version: 10.0.19041.746
Image Version: 10.0.19042.746 
 
The restore operation completed successfully.
The operation completed successfully.
 
==================================================================
    [SFC /ScanNow] 
Beginning system scan.  This process will take some time.
Results: 
 
Windows Resource Protection did not find any integrity violations.
 
==================================================================
    [ChkDsk /Scan]  
The type of the file system is NTFS.
Volume label is Windows 10.

Stage 1: Examining basic file system structure ...
  254720 file records processed.                                                        

File verification completed.
 Phase duration (File record verification): 47.77 seconds.
  5984 large file records processed.                                   

 Phase duration (Orphan file record recovery): 0.00 milliseconds.
  0 bad file records processed.                                     

 Phase duration (Bad file record checking): 0.07 milliseconds.

Stage 2: Examining file name linkage ...
  968 reparse records processed.                                      

  373396 index entries processed.                                                       

Index verification completed.
 Phase duration (Index verification): 1.06 minutes.
  0 unindexed files scanned.                                        

 Phase duration (Orphan reconnection): 434.21 milliseconds.
  0 unindexed files recovered to lost and found.                    

 Phase duration (Orphan recovery to lost and found): 0.59 milliseconds.
  968 reparse records processed.                                      

 Phase duration (Reparse point and Object ID verification): 12.71 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 65.71 milliseconds.
  59339 data files processed.                                           

 Phase duration (Data attribute verification): 0.11 milliseconds.
CHKDSK is verifying Usn Journal...
  39063968 USN bytes processed.                                                          
 

Usn Journal verification completed.
 Phase duration (USN journal verification): 594.90 milliseconds.

Windows has scanned the file system and found no problems.
No further action is required.

  84304867 KB total disk space.
  20046324 KB in 173704 files.
    128016 KB in 59340 indexes.
         0 KB in bad sectors.
    365595 KB in use by the system.
     65536 KB occupied by the log file.
  63764932 KB available on disk.

      4096 bytes in each allocation unit.
  21076216 total allocation units on disk.
  15941233 allocation units available on disk.
Total duration: 1.88 minutes (113030 ms).
 
==================================================================

AutoReboot  
FALSE       
 
==================================================================
    [Set AutoReboot = False] 
Updating property(s) of 
'\\DESKTOP\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 
Home|C:\\Windows|\\Device\\Harddisk0\\Partition3"'

Property(s) update successful.

==================================================================
 
AutoReboot  
FALSE       
 
==================================================================
 
DebugInfoType  
7              
 
==================================================================
    [Set DebugInfoType = 7] 
Updating property(s) of 
'\\DESKTOP\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 
Home|C:\\Windows|\\Device\\Harddisk0\\Partition3"'

Property(s) update successful.

==================================================================
 
DebugInfoType  
7              
 
==================================================================
    [WMIC PageFile list] 
AllocatedBaseSize=960
CurrentUsage=33
Description=C:\pagefile.sys
InstallDate=20201219141201.390506+480
Name=C:\pagefile.sys
PeakUsage=80
Status=
TempPageFile=FALSE
 
==================================================================
 
AutomaticManagedPagefile  
TRUE                      
 
==================================================================
    [Set AutomaticManagedPagefile = True] 
Updating property(s) of '\\DESKTOP\ROOT\CIMV2:Win32_ComputerSystem.Name="DESKTOP"'

Property(s) update successful.

==================================================================
 
AutomaticManagedPagefile  
TRUE                      
 
==================================================================
    [BcdEdit /enum {badmemory}] 
RAM Defects
-----------
identifier              {badmemory}
 
==================================================================

zbook said:

Can you create a script that will collect event viewer results similar to PS1 LOGS?

I will think about it later. I am still trying to improve Tuneup.log.

zbook said:

It worked nicely in this thread:
Occasional DRIVER_POWER_STATE_FAILURE

Code:

Creation date and time  Size (MB)          File path
----------------------  ---------    -----------------------------
2020-12-13 10:21:33 PM   0.63      C:\Windows\LiveKernelReports\ResourceTimeout\ResourceTimeout-20201128-2337.dmp
2021-01-22 8:48:34 PM   0.62      C:\Windows\LiveKernelReports\ResourceTimeout\ResourceTimeout-20210122-2041.dmp
2021-03-12 10:35:50 PM   0.61      C:\Windows\LiveKernelReports\ResourceTimeout\ResourceTimeout-20210211-2145.dmp
2021-03-31 1:39:09 PM   0.61      C:\Windows\LiveKernelReports\ResourceTimeout\ResourceTimeout-20210331-1150.dmp
2020-12-05 6:16:11 PM   0.28      C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20201205-1816.dmp
2020-12-13 10:05:37 PM   0.32      C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20201213-2205.dmp
2021-03-31 1:39:05 PM   0.49      C:\Windows\LiveKernelReports\WFP\WFP-20210316-2353.dmp

Note: 3 dump file(s) has/have been zipped.

The numbers in three file names do not agree with the creation dates.

These were the three dump files collected:

Tue Mar 16 10:53:45.815 2021 (UTC - 5:00)
Tue Mar 30 22:50:32.465 2021 (UTC - 5:00)
Thu Feb 11 08:45:38.356 2021 (UTC - 5:00)

I was happy that it collected the logs and had not checked the dates.
As you commented the dates were incorrect.

The script will check the creation dates found by PowerShell.
The creation date is the one shown in "Properties" rather than the name of a file.