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

While debugging some update install problems, I deleted the large existing logs for all types of windows events, including CBS and DISM. After doing this it is necessary to reboot (creating a new set of log files) before running tuneup_plus_log.bat or it will hang.

@Spectrum

If you're available?

The V2 partition report displayed: (see size column)

Code:

DriveLetter DevicePath              VolumeGUID                                        Size
                                                                                          
                                                                                      (GB)
----------- ----------              ----------                                        ----
            \Device\HarddiskVolume1 \\?\Volume{28b2b066-1c02-4d7f-9eda-4e8b1c8fe1c6}\ 0.25
C:\         \Device\HarddiskVolume3 \\?\Volume{49a314db-e107-442f-9c53-4845fd60a57f}\ ...9
            \Device\HarddiskVolume4 \\?\Volume{d62d90e1-86c7-400e-bc61-7978f601999c}\ 0.93
D:\         \Device\HarddiskVolume5 \\?\Volume{18137230-9577-478b-9d5f-8ac802720b2f}\ ...3

I don't think he is available. His last activity was done three and a half years ago.

The OP in this thread ran Tuneup plus twice but it did not report results after chkdsk:

UNEXPECTED_STORE_EXCEPTION when playing world of warcraft/ watching docus | Windows 11 Forum

Code:

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

 975949823 KB total disk space.
 626180768 KB in 527449 files.
    399736 KB in 140138 indexes.
         0 KB in bad sectors.
    839011 KB in use by the system.
     65536 KB occupied by the log file.
 348530308 KB available on disk.

      4096 bytes in each allocation unit.
 243987455 total allocation units on disk.
  87132577 allocation units available on disk.
Total duration: 22.15 seconds (22153 ms).

C:\Windows\System32>Echo off
   ###################################################################################
   #    How to capture batch file data and post in your thread in the BSOD forum     #
   #                                                                                 #
   #      Batch files and instructions for use in BSOD debugging[Part Two-Four]      #
   #                                                                                 #
   #        Press [V] to visit the above web page for detailed instructions.         #
   #        Press [C] to close this window.                                          #
   ###################################################################################

I found no "Tuneup.log" there.

Post #8 had results inside code:

Code:

###########################################################
# The following commands will be run in sequence.         #
# They can take quite a while to run, be patient.         #
###########################################################

sfc /scannow
dism /online /cleanup-image /scanhealth
dism /online /cleanup-image /restorehealth
sfc /scannow

chkdsk /scan


C:\Windows\System32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\System32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.22621.2792

Image Version: 10.0.22631.3672

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

C:\Windows\System32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.22621.2792

Image Version: 10.0.22631.3672

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\Windows\System32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\System32>chkdsk /scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
  695808 file records processed.
File verification completed.
 Phase duration (File record verification): 6.21 seconds.
  32232 large file records processed.
 Phase duration (Orphan file record recovery): 14.26 milliseconds.
  0 bad file records processed.
 Phase duration (Bad file record checking): 0.18 milliseconds.

Stage 2: Examining file name linkage ...
  67650 reparse records processed.
  976080 index entries processed.
Index verification completed.
 Phase duration (Index verification): 14.94 seconds.
  0 unindexed files scanned.
 Phase duration (Orphan reconnection): 796.83 milliseconds.
  0 unindexed files recovered to lost and found.
 Phase duration (Orphan recovery to lost and found): 0.50 milliseconds.
  67650 reparse records processed.
 Phase duration (Reparse point and Object ID verification): 112.37 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 17.54 milliseconds.
  140137 data files processed.
 Phase duration (Data attribute verification): 0.21 milliseconds.
CHKDSK is verifying Usn Journal...
  41967256 USN bytes processed.
Usn Journal verification completed.
 Phase duration (USN journal verification): 51.92 milliseconds.

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

 975949823 KB total disk space.
 626180768 KB in 527449 files.
    399736 KB in 140138 indexes.
         0 KB in bad sectors.
    839011 KB in use by the system.
     65536 KB occupied by the log file.
 348530308 KB available on disk.

      4096 bytes in each allocation unit.
 243987455 total allocation units on disk.
  87132577 allocation units available on disk.
Total duration: 22.15 seconds (22153 ms).

C:\Windows\System32>Echo off
   ###################################################################################
   #    How to capture batch file data and post in your thread in the BSOD forum     #
   #                                                                                 #
   #      Batch files and instructions for use in BSOD debugging[Part Two-Four]      #
   #                                                                                 #
   #        Press [V] to visit the above web page for detailed instructions.         #
   #        Press [C] to close this window.                                          #
   ###################################################################################

The last displayed command was: Echo off






These commands and / or results were not seen

Code:

wmic recoveros get autoreboot
wmic recoveros set autoreboot = false
wmic recoveros get autoreboot

wmic recoveros get DebugInfoType
wmic recoveros set DebugInfoType = 7
wmic recoveros get DebugInfoType

wmic pagefile list /format:list

wmic Computersystem where name="%computername%" get AutomaticManagedPagefile
wmic Computersystem where name="%computername%" set AutomaticManagedPagefile=True
wmic Computersystem where name="%computername%" get AutomaticManagedPagefile

bcdedit /enum {badmemory}

The results in post #8 were the output of a script written by Ztruker, not by me.

The links for the scripts that you created were posted twice in the thread.

The OP never commented on the use of another script.



Thx.

The OP never ran my script although the link had been posted twice in the thread.