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

@zbook, you can deliberately cause "integrity violations" simply by using the following:

Using CMD script and VBScript to control Windows Update

Will wait for new threads.

From another computer:

Code:

    Started on Tue 11/30/2021 at  0:36:47.26 

        [SFC /ScanNow] 

Beginning system scan.  This process will take some time.

Results: 
 
Windows Resource Protection did not find any integrity violations.
 
==================================================================

    Started on Tue 11/30/2021 at  0:43:38.07 

        [DISM /online /cleanup-image /ScanHealth] 

Deployment Image Servicing and Management tool
Version: 10.0.17763.1518

Image Version: 10.0.17763.1577 
 
No component store corruption detected.

The operation completed successfully. 
 
==================================================================

    Started on Tue 11/30/2021 at  0:45:23.41 

        [DISM /online /cleanup-image /RestoreHealth] 

Deployment Image Servicing and Management tool
Version: 10.0.17763.1518

Image Version: 10.0.17763.1577 
 
The restore operation completed successfully.

The operation completed successfully. 
 
==================================================================

The second "SFC /ScanNow" was skipped, as the first output the following:

Windows Resource Protection did not find any integrity violations.
 
==================================================================

    Started on Tue 11/30/2021 at  0:46:56.52 

        [ChkDsk /Scan]  
 
The type of the file system is NTFS.
 
Stage 1: Examining basic file system structure ... 
881920 file records processed.                                                        
File verification completed.
26342 large file records processed.                                   
0 bad file records processed.                                     
 
Stage 2: Examining file name linkage ... 
1373 reparse records processed.                                      
1140166 index entries processed.                                                       
Index verification completed.
0 unindexed files scanned.                                        
0 unindexed files recovered to lost and found.                    
1373 reparse records processed.                                      
 
Stage 3: Examining security descriptors ... 
Security descriptor verification completed.
129124 data files processed.                                           
CHKDSK is verifying Usn Journal...
36108432 USN bytes processed.                                                           
Usn Journal verification completed.

Windows has scanned the file system and found no problems.

No further action is required.
 
248570090 KB total disk space. 
212861152 KB in 407341 files.
383772 KB in 129125 indexes.
0 KB in bad sectors.
1002398 KB in use by the system.
65536 KB occupied by the log file.
34322768 KB available on disk.
 
4096 bytes in each allocation unit. 
62142522 total allocation units on disk.
8580692 allocation units available on disk.
 
==================================================================
 
    Started on Tue 11/30/2021 at  0:47:46.06 
 
AutoReboot   
 
FALSE       
 
==================================================================
 
        [Set AutoReboot = False] 
 
Updating property(s) of '\\DESKTOP-9HEBUKS\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition4"'

Property(s) update successful.

==================================================================
 
AutoReboot   
 
FALSE       
 
==================================================================
 
DebugInfoType   
 
7              
 
==================================================================

        [Set DebugInfoType = 7]

Updating property(s) of '\\DESKTOP-9HEBUKS\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition4"'

Property(s) update successful.

==================================================================
 
DebugInfoType   
 
7              
 
==================================================================

        [WMIC PageFile list]

AllocatedBaseSize=15872
CurrentUsage=269
Description=C:\pagefile.sys
InstallDate=20180430231751.753916-300
Name=C:\pagefile.sys
PeakUsage=270
Status=
TempPageFile=FALSE
 
==================================================================
 
AutomaticManagedPagefile   
 
TRUE                      
 
==================================================================

        [Set AutomaticManagedPagefile = True]

Updating property(s) of '\\DESKTOP-9HEBUKS\ROOT\CIMV2:Win32_ComputerSystem.Name="DESKTOP-9HEBUKS"'

Property(s) update successful.

==================================================================
 
AutomaticManagedPagefile   
 
TRUE                      
 
==================================================================

        [BcdEdit /enum {badmemory}]

RAM Defects
-----------
identifier              {badmemory}
 
==================================================================

    Finished on Tue 11/30/2021 at  0:47:47.23
    It took 11 minutes and 0 seconds to complete the operations.

No UEFI BIOS Access in Windows 10 Pro

In the above case, the first "SFC /ScanNow" output "Windows Resource Protection found corrupt files and successfully repaired them". I wonder whether the second "SFC /ScanNow" should be skipped when the first one has successfully repaired the files.

The second scannow is performed to confirm that there are no integrity violations.

The confirmation does not have to be performed.

On most computers with SSD it takes 11 minutes or less to run all of the above commands.
The HD which has some bad sectors took 41 minutes to run all of the above commands.

In this link it is suggested to run scannow 3 times.

Run SFC Command in Windows 10

I've not yet seen a third scannow fix problems that 2 could not fix.

For now let's leave the script as is.
If users complain about a long run time then lets modify it.
With the script running in the background the run time should be ok.
The exception could be any computer that has numerous applications in use with high percentages displayed on task manager.

Code:

If SFC could not fix something, then run the command again to see if it may be able to the next time. Sometimes it may take running the sfc /scannow command up to 3 times with Fast Startup turned off and restarting the computer after each time to completely fix everything that it's able to.

If not, then run the Dism /Online /Cleanup-Image /RestoreHealth (requires Internet connection) command to repair any component store corruption, restart the PC afterwards, and try the sfc /scannow command again.

If still not, then you could refresh Windows 10, or do a system restore using a restore point dated before the bad system file occured to fix it. You may need to repeat doing a system restore until you find a older restore point that may work.

When running SFC offline (at boot), SFC logging in the CBS.log file is not supported to be able to create a sfcdetails.txt file in OPTION FIVE below.

There have been multiple threads in which V2 was unable to collect files / folders.
Once the installed antivirus was removed the missing files were collected.

For Windows upgrades these non-Microsoft software are routinely uninstalled:
a) antivirus
b) firewall
c) drive encryption


If possible please create commands to identify the above so that a separate script can run.
If the script works then the commands may be able to be added to V2 for testing purposes.
If the commands are not blocked during the V2 run then they may be able to be added to V2.

Perhaps you should contact Spectrum via the following thread:

Improving the Log Collection Script

There were multiple posts in that thread during the past year.

Had you seen him post?

He is the only one who has the right to improve "V2 Log collector". The administrator would not allow anyone else to modify it.