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

Paul Black · 24 Jun 2021

I have had a thought that you may, or may NOT, find helpful.

Scrutinising the OS to find the cause of a BSOD can be a complicated and time consuming process. When a member posts their specific problem, they are asked, depending on the information given, to run anything between one or several Scripts to try to narrow down and rectify the problem.

There have been MANY Scripts and different versions of those Scripts over the last year, and depending on the members expertise level and familiarity of computers, the downloading and running of the scripts can be daunting, leading to them NOT being run correctly or the information extracted NOT being found, or the posted results are NOT as expected or wrong.

What if you were to have a Master Script in a downloaded Zipped File that was Menu Based. This way, all the possible information that will be required via the Scripts will ALL be in one place. The advantage of this is two-fold. The FIRST is for the BSOD Team, who will know that whatever they want the member to run is ALREADY available on the members computer via a Menu. The SECOND, is for the member, because they will NOT have to keep downloading extra Scripts and following extra or additional instructions. Additionally, because this Forum accommodates members from all over the World, which involves different Time Zones, it SHOULD cut down on the length of Time for responses when additional information is requested.

Just a thought.

Matthew Wai · 24 Jun 2021

zbook said:

https://www.tenforums.com/attachment...p_plus_log.bat

The URL is correct, as the attachment ID is 338471.
It would be a miracle if the download were an old version.

zbook · 24 Jun 2021

Code:

 ###########################################################################
 #                                                                         #
 #                           Tuneup_plus_log.bat                           #
 #                                                                         #
 #    A LOG file named Tuneup.log has been created on the desktop.         #
 #    Please copy the data from the file into your post (recommended)      #
 #    or upload the file as an attachment to your post.                    #
 #                                                                         #
 #    There are detailed instructions on how to properly copy the data.    #
 #    Batch files and instructions for use in BSOD debugging [Part Two]    #
 #                                                                         #
 #      Press [V] to visit TenForums for the detailed instructions.        #
 #      Press [C] to close this window.                                    #
 #                                                                         #
 ###########################################################################

Code:

    Started on Thu 06/24/2021 at  7:34:20.89 

        [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.
 
==================================================================

    Started on Thu 06/24/2021 at  7:41:11.51 

        [DISM /online /cleanup-image /ScanHealth] 

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. 
 
==================================================================

    Started on Thu 06/24/2021 at  7:48:31.00 

        [DISM /online /cleanup-image /RestoreHealth] 

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
 
==================================================================

    Started on Thu 06/24/2021 at  7:59:22.81 

        [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.
 
==================================================================

A TXT file named SFC_details.txt has been created on the desktop.

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

    Started on Thu 06/24/2021 at  8:02:28.21 

        [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): 17.63 seconds.
8900 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.13 milliseconds.
 
Stage 2: Examining file name linkage ... 
997 reparse records processed.                                      
1045090 index entries processed.                                                       
Index verification completed.
Phase duration (Index verification): 1.40 minutes.
0 unindexed files scanned.                                        
Phase duration (Orphan reconnection): 6.23 seconds.
0 unindexed files recovered to lost and found.                    
Phase duration (Orphan recovery to lost and found): 3.60 milliseconds.
997 reparse records processed.                                      
Phase duration (Reparse point and Object ID verification): 7.14 milliseconds.
 
Stage 3: Examining security descriptors ... 
Security descriptor verification completed.
Phase duration (Security descriptor verification): 117.95 milliseconds.
139954 data files processed.                                           
Phase duration (Data attribute verification): 0.06 milliseconds.
CHKDSK is verifying Usn Journal...
40374776 USN bytes processed.                                                          
Usn Journal verification completed.
Phase duration (USN journal verification): 1.19 seconds.

Windows has scanned the file system and found no problems.

No further action is required.
 
722633727 KB total disk space. 
203819336 KB in 548603 files.
332032 KB in 139955 indexes.
0 KB in bad sectors.
898479 KB in use by the system.
65536 KB occupied by the log file.
517583880 KB available on disk.
 
4096 bytes in each allocation unit. 
180658431 total allocation units on disk.
129395970 allocation units available on disk.
Total duration: 1.82 minutes (109494 ms).
 
==================================================================
 
    Started on Thu 06/24/2021 at  8:04:38.55 
 
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=950
Description=C:\pagefile.sys
InstallDate=20210123182308.249920-360
Name=C:\pagefile.sys
PeakUsage=4692
Status=
TempPageFile=FALSE
 
==================================================================
 
AutomaticManagedPagefile   
 
TRUE                      
 
==================================================================

        [Set AutomaticManagedPagefile = True]

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

Property(s) update successful.

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

        [BcdEdit /enum {badmemory}]

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

    Finished on Thu 06/24/2021 at  8:04:39.63

jbcarreon123 · 24 Jun 2021

Paul Black said:

I have had a thought that you may, or may NOT, find helpful.

Scrutinising the OS to find the cause of a BSOD can be a complicated and time consuming process. When a member posts their specific problem, they are asked, depending on the information given, to run anything between one or several Scripts to try to narrow down and rectify the problem.

There have been MANY Scripts and different versions of those Scripts over the last year, and depending on the members expertise level and familiarity of computers, the downloading and running of the scripts can be daunting, leading to them NOT being run correctly or the information extracted NOT being found, or the posted results are NOT as expected or wrong.

What if you were to have a Master Script in a downloaded Zipped File that was Menu Based. This way, all the possible information that will be required via the Scripts will ALL be in one place. The advantage of this is two-fold. The FIRST is for the BSOD Team, who will know that whatever they want the member to run is ALREADY available on the members computer via a Menu. The SECOND, is for the member, because they will NOT have to keep downloading extra Scripts and following extra or additional instructions. Additionally, because this Forum accommodates members from all over the World, which involves different Time Zones, it SHOULD cut down on the length of Time for responses when additional information is requested.

Just a thought.

That's why I am developing BSODScriptCollection as a choice.

zbook · 25 Jun 2021

For V2 which commands are running that display each of these results:

os-details.txt

Safe Mode : Normal boot
FastStartup : Enabled
FirmwareType : UEFI
SecureBoot : Not Enabled

Can something similar to this be added to display TPM data in LOGS PS1 for Windows 11 troubleshooting:

wmic /namespace:\\root\CIMV2\Security\MicrosoftTpm path Win32_Tpm get /value

IsActivated_InitialValue=TRUE
IsEnabled_InitialValue=TRUE
IsOwned_InitialValue=TRUE
ManufacturerId=1229346816
ManufacturerIdTxt=IFX
ManufacturerVersion=4.40
ManufacturerVersionFull20=Not Supported
ManufacturerVersionInfo=042800770074706d3631ffffff
PhysicalPresenceVersionInfo=1.2
SpecVersion=1.2, 2, 3

Matthew Wai · 25 Jun 2021

The data can be written into a LOG file. What file name and location do you want?

Matthew Wai · 25 Jun 2021

zbook said:

Safe Mode : Normal boot
FastStartup : Enabled
FirmwareType : UEFI
SecureBoot : Not Enabled

Get-CimInstance -ClassName Win32_ComputerSystem|Select -ExpandProperty BootupState

Code:

Get-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager\Power\" -Name "HiberbootEnabled"|Select -ExpandProperty HiberbootEnabled

Get-ComputerInfo|Select BiosFirmwareType

Confirm-SecureBootUEFI

zbook · 26 Jun 2021

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Code:

PS C:\WINDOWS\system32> get-tpm


TpmPresent                : True
TpmReady                  : True
ManufacturerId            : 1229346816
ManufacturerIdTxt         : IFX
ManufacturerVersion       : 4.40
ManufacturerVersionFull20 : Not Supported for TPM 1.2
ManagedAuthLevel          : Full
OwnerAuth                 :
OwnerClearDisabled        : True
AutoProvisioning          : Enabled
LockedOut                 : False
LockoutHealTime           : Not Supported for TPM 1.2
LockoutCount              : Not Supported for TPM 1.2
LockoutMax                : Not Supported for TPM 1.2
SelfTest                  : {128, 0, 1, 255}

Code:

PS C:\WINDOWS\system32> wmic /namespace:\\root\CIMV2\Security\MicrosoftTpm path Win32_Tpm get /value


IsActivated_InitialValue=TRUE
IsEnabled_InitialValue=TRUE
IsOwned_InitialValue=TRUE
ManufacturerId=1229346816
ManufacturerIdTxt=IFX
ManufacturerVersion=4.40
ManufacturerVersionFull20=Not Supported
ManufacturerVersionInfo=042800770074706d3631ffffff
PhysicalPresenceVersionInfo=1.2
SpecVersion=1.2, 2, 3

Some of the commands did not produce the same results as V2.
What happened?

Code:

PS C:\WINDOWS\system32> Get-CimInstance -ClassName Win32_ComputerSystem|Select -ExpandProperty BootupState
Normal boot

Code:

PS C:\WINDOWS\system32> Get-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager\Power" -Name "HiberbootEnabled"|Select -ExpandProperty HiberbootEnabled
1

Code:

PS C:\WINDOWS\system32> Get-ComputerInfo|Select BiosFirmwareType

BiosFirmwareType
----------------

Code:

PS C:\WINDOWS\system32> Confirm-SecureBootUEFI
False

Code:

Safe Mode    : Normal boot
FastStartup  : Enabled
FirmwareType : UEFI
SecureBoot   : Not Enabled

Matthew Wai · 26 Jun 2021

zbook said:

Code:

PS C:\WINDOWS\system32> Get-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager\Power" -Name "HiberbootEnabled"|Select -ExpandProperty HiberbootEnabled
1

The output "1" denotes "Enabled" as per "V2 log collector".
I have disabled hibernation and Fast Startup, but the output is "1". I don't know why.

zbook · 26 Jun 2021

How can this command display a result?
(same as V2)

Code:

PS C:\WINDOWS\system32> Get-ComputerInfo|Select BiosFirmwareType

BiosFirmwareType
----------------

What determines whether this displays not enabled or false?
(same as V2)

Code:

PS C:\WINDOWS\system32> Confirm-SecureBootUEFI
False