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

For any script revisions or new scripts there are currently:

a) one computer with failure to upgrade (cause known)
b) one computer with problematic scannow

Please specify what you want.

If tuneup is done then post the latest script > I'll run it on the computer with problematic scannow.

When tuneup is done please see post #750.

The latest version of Tuneup_plus_log.bat has been uploaded.

👉 Tuneup_plus_log.bat ✔️ 【Last updated on June 24, 2021】

Source: Batch files for use in BSOD debugging

Always download the latest version from the above source.

Code:

 #######################################################################################
 #                               Tuneup_plus_log.bat                                   #
 #                                                                                     #
 #  Now copy the results from Notepad and paste them into a post on TenForums.com.     #
 #  To do so, click on [Edit]-->[Select all]. Go to your thread in the BSOD section,   #
 #  start a new post, and paste the text you copied into your post.                    #
 #                (Press Ctrl + V or right-click and select [Paste].)                  #
 #                                                                                     #
 #  Select the text you just pasted into your post. Then, on the editor toolbar, click #
 #  on the hashtag icon [#] to wrap  tags around the selected text. When  #
 #  posted, the data will appear in a code box, properly formatted and easy to read.   #
 #                                                                                     #
 #  Before you post, click on the [Go Advanced] button at the bottom on the right to   #
 #  see what it looks like and, if you make additional changes, click on the           #
 #  [Preview Post] button, so that you can see what it looks like before you actually  #
 #  post it. Click on the [Submit Reply] button when you are satisfied with it.        #
 #                                                                                     #
 #  If you close the Notepad window by accident before copying the data, you can find  #
 #  the LOG file named Tuneup.log on the desktop and then open it.                     #
 #                                                                                     #
 #                       Batch files for use in BSOD debugging                         #
 #                   Batch files for use in BSOD debugging                  #
 #                                                                                     #
 #          Press [V] to visit the above web page for detailed directions.             #
 #          *** Go to post #1. Scroll down to [Part Two] and see step [1A]. ***        #
 #          Press [C] to close this window.                                            #
 #                                                                                     #
 #######################################################################################

What happened to the prior spacing adjustments?

Code:

Beginning system scan.  This process will take some time.
Beginning verification phase of system scan.
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.
==================================================================
Deployment Image Servicing and Management tool
Version: 10.0.19041.844
Image Version: 10.0.19042.1052
The component store is repairable.
The operation completed successfully.
==================================================================
Deployment Image Servicing and Management tool
Version: 10.0.19041.844
Image Version: 10.0.19042.1052
Error: 0x800f081f
The source files could not be found. 
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see https://go.microsoft.com/fwlink/?LinkId=243077.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
==================================================================
Beginning system scan.  This process will take some time.
Beginning verification phase of system scan.
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.
==================================================================
    [ChkDsk /scan] 
The type of the file system is NTFS.
Volume label is Windows.
Stage 1: Examining basic file system structure ...
765184 file records processed.                                                        
File verification completed.
Phase duration (File record verification): 1.15 minutes.
8899 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.08 milliseconds.
Stage 2: Examining file name linkage ...
997 reparse records processed.                                      
1045080 index entries processed.                                                       
Index verification completed.
Phase duration (Index verification): 6.75 minutes.
0 unindexed files scanned.                                        
Phase duration (Orphan reconnection): 6.94 seconds.
0 unindexed files recovered to lost and found.                    
Phase duration (Orphan recovery to lost and found): 1.56 milliseconds.
997 reparse records processed.                                      
Phase duration (Reparse point and Object ID verification): 9.23 milliseconds.
Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 287.57 milliseconds.
139949 data files processed.                                           
Phase duration (Data attribute verification): 0.08 milliseconds.
CHKDSK is verifying Usn Journal...
34329784 USN bytes processed.                                                           
Usn Journal verification completed.
Phase duration (USN journal verification): 623.95 milliseconds.
Windows has scanned the file system and found no problems.
No further action is required.
722633727 KB total disk space.
212704740 KB in 547025 files.
332016 KB in 139950 indexes.
0 KB in bad sectors.
892335 KB in use by the system.
65536 KB occupied by the log file.
508704636 KB available on disk.
4096 bytes in each allocation unit.
180658431 total allocation units on disk.
127176159 allocation units available on disk.
Total duration: 8.04 minutes (482818 ms).
==================================================================
AutoReboot  
FALSE       
==================================================================
    [Set AutoReboot = False] 
Updating property(s) of '\\DESKTOP-K2CP43S\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition2"'

Property(s) update successful.

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

Property(s) update successful.

==================================================================
DebugInfoType  
7              
==================================================================
    [WMIC PageFile list] 
AllocatedBaseSize=31744
CurrentUsage=928
Description=C:\pagefile.sys
InstallDate=20210123182308.249920-360
Name=C:\pagefile.sys
PeakUsage=4692
Status=
TempPageFile=FALSE
==================================================================
==================================================================
    [Set AutomaticManagedPagefile = True] 
No Instance(s) Available.

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

zbook said:

What happened to the prior spacing adjustments?

You ran an old version, which should not be available online.
I don't know why you downloaded an old version rather than the latest version.
There must be something wrong. What browser are you using?

👉 Tuneup_plus_log.bat ✔️ 【Last updated on June 24, 2021】

Right-click on the above hypertext and select "Copy link address" or "Copy Link Location" or words to that effect. Post the URL you have copied. The URL should be as below:

https://www.tenforums.com/attachments/bsod-crashes-debugging/338471-batch-files-use-bsod-debugging-tuneup_plus_log.bat

Note that "338471", the attachment ID, refers to the latest version of Tuneup_plus_log.bat.

On Edge, Firefox, and Chrome, I get the same attachment ID—​"338471".

@zbook, search for Tuneup_plus_log.bat on your PC and delete all of them.
Then, download the latest version—​"338471".

https://www.tenforums.com/misc.php?d...ments&t=162488

The repository contains only one available version of Tuneup_plus_log.bat—​the latest version.
You can't possibly download an old version from the repository.

For the computer with problematic scannow all Tuneup_plus_log.bat were deleted.
https://www.tenforums.com/attachment...p_plus_log.bat
Firefox 89.0

Code:

    Operation (1): SFC.exe is checking the system files.