Index of Batch Scripts for BSOD debugging, and other Windows troubleshooting


Toc1

Table of Contents​


Contents

Batch files for use in BSOD debugging-bsodlogo9x1.5.jpg

information
Information
This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10.

The first post (this one) will be an index and each additional post will be a batch file with the instructions necessary to run it. This post will also have any instructions that will apply to all batch files in general.

warning
Warning
This thread IS NOT for discussion or suggestions or problem reporting. It is strictly a batch file repository. Any other posts will be deleted.



Part Zero

Download Tips for Edge, Firefox and Chrome

Batch files for use in BSOD debugging-edge.png

When you download one of our batch files with Edge you may run into security problems.

bat was blocked because it could harm your device

This is complaining about the code to auto-elevate to Administrator level to run commands. This is not a problem and is done in almost all our batch files. There is no security exposure.

Look a the following images to see what you need to do to bypass the interference and continue to run the batch file.
Click Keep
Batch files for use in BSOD debugging-download_edge-1.png


Click Keep Anyway
Batch files for use in BSOD debugging-download_edge-2.png


Click Show in Folder
Batch files for use in BSOD debugging-download_edge-3.png
Batch files for use in BSOD debugging-firefox.png

When you download one of our batch files with Firefox there are currently no known problems.
Batch files for use in BSOD debugging-chrome.png

When you download one of our batch files with Chrome you may run into security problems.

This type of file can harm your computer. Do you want to keep .........bat anyway?

Again, this is complaining about the code to auto-elevate to Administrator level to run commands. This is not a problem and is done in almost all our batch files. There is no security exposure.

Look a the following images to see what you need to do to bypass the interference and continue to run the batch file.
Click Keep
Batch files for use in BSOD debugging-download-1.png


Click Show in folder
Batch files for use in BSOD debugging-download-2.png




Part One

Verify vertical scroll buffer (Height) is large enough​



Many of the batch files here are designed to run from File Explorer so the following are not needed. Look through the Batch file specific instructions then follow these instructions only if necessary.

If you want to run the batch file in a currently open Command Prompt or Powershell window, it would be a good idea to check the properties of the window to make sure the vertical scroll buffer (Height) is large enough to hold the output so it can be collected and posted in your BSOD thread. Some batch files will handle this for you, some may not.

To check this, do the following:


1 Right click on the Powershell (or Command Prompt) title bar and select Properties.

Batch files for use in BSOD debugging-con-height1.jpg

2 The Windows Powershell or Command Prompt properties window will open. Click on the Layout tab,
check the Height setting. Set it to 3000 then click OK
Batch files for use in BSOD debugging-con-height2.jpg




Part Two

Capture output of batch file to Clipboard​


You may need to capture output from a Command Prompt window, Powershell Window, Notepad Window or upload one or more files when you complete running the batch file. Follow the steps as directed below.


1 Command Prompt or Powershell Window - follow Part Two-OneA steps 1A, 2A, 3A and Part Two-Four steps 4 through 7.

2 Notepad Window - follow Part Two-OneB steps 1B, 2B, 3B and Part Two-Four steps 4 through 7.

3 Upload files - follow Part Two-Four step 8.



Part Two-OneA

From Command Prompt or Powershell Window​


1A Right click on the Powershell (or Command Prompt) title bar and select Edit then click on Select All.
Batch files for use in BSOD debugging-win1.png


2A Right click on the Powershell (or Command Prompt) title bar and select Edit then click on Copy.

Batch files for use in BSOD debugging-win2.png


3A That will copy everything from the Powershell (or Command Prompt) window to the Clipboard.

Click here to see a short video of the steps needed to copy & paste the data in a Command Prompt or Powershell Window to your thread in Tenforums: https://1drv.ms/v/s!AiInGuVqlXiCsQyT...xZgXy?e=Cogp44

Goto Part Two-Four step 4.



Part Two-OneB

From Notepad Window​


1B Copy all data in Notepad to the clipboard
Select all data in the notepad window by clicking anywhere in it and pressing Ctrl+ A or click on Edit at the top and then Select all.
Copy the data to the clipboard by pressing Ctrl+C or click on Edit at the top then Copy.
Now paste the results you copied to the clipboard into a post on TenForums.
Go to your thread in the BSOD section, start a new post, and paste the text you copied
into your post by pressing Ctrl+V or right-click and select Paste.

2B Use CODE formatting tags so the text displays properly
Select the text you just pasted into your post. Then, on the editor toolbar
click on the hashtag icon [#] to wrap
Code:
tags around the selected
text. The data will appear in a code box, properly formatted and easy to read when it is posted.

3B IMPORTANT Before you post, click on the
Batch files for use in BSOD debugging-goadv.png
button at bottom right to see what it looks like and, if you have made any additional changes, click on the
Batch files for use in BSOD debugging-prevpost.png
button, so that you can see what it looks like before you actually post it. Click on the
Batch files for use in BSOD debugging-subrep.png
button as long as you are satisfied with it.



Part Two-Four

Post captured data to your forum thread​


4 Post in your forum thread
Go to your thread in the BSOD forum, start a new thread and paste the text you copied into your post (CTRL+V or Right click and select Paste).

5 Use CODE formatting tags so the text displays properly
Select the text you just pasted into your post then click on the Hash tag # icon to Wrap
Code:
tags around selected text. The data will appear in a Code box, properly formatted and easy to read.

6 Use DOS formatting tags so the text displays properly
Alternatively, without selecting anything, put [DOS][/DOS] tags at the beginning and the end of the data you inserted, which will make it look like it does in a Command Prompt window, properly formatted and easy to read when it is posted. I would only use this for data copied from a Command Prompt though the CODE tags are sufficient.

7 Verify formatting
Before you post, click on the
Batch files for use in BSOD debugging-goadv.png
button at bottom right to see what it looks like and if you make any additional changes, click on
Batch files for use in BSOD debugging-prevpost.png
button, again so you can see what it looks like before you actually post it. Click on
Batch files for use in BSOD debugging-subrep.png
when your satisfied.

8 Upload files
If you have files to upload and add to your thread, see this tutorial: How to Upload and Post Screenshots and Files at Ten Forums

information
Information
Read this tutorial to learn how to change the Post Editor between Source mode (shows tags used to do the actual formatting) and WYSYWIG (What You See Is What You Get) mode.

How to Change Post Editor to Source or WYSIWYG Mode
 

My Computer

System One

  • OS
    Windows 10
    Computer type
    Laptop
    Manufacturer/Model
    HP
    CPU
    Intel(R) Core(TM) i7-4800MQ CPU @ 2.70GHz
    Motherboard
    Product : 190A Version : KBC Version 94.56
    Memory
    16 GB Total: Manufacturer : Samsung MemoryType : DDR3 FormFactor : SODIMM Capacity : 8GB Speed : 1600
    Graphics Card(s)
    NVIDIA Quadro K3100M; Intel(R) HD Graphics 4600
    Sound Card
    IDT High Definition Audio CODEC; PNP Device ID HDAUDIO\FUNC_01&VEN_111D&DEV_76E0
    Hard Drives
    Model Hitachi HTS727575A9E364
    Antivirus
    Microsoft Defender
    Other Info
    Mobile Workstation

zbook

Well-known member
Guru
VIP
Local time
7:56 AM
Posts
8,651
OS
Windows 10
Part Three

Index of Batch Scripts for BSOD debugging​


1. Tuneup.batRun SFC, DISM and CHKDSK commands and use WMIC to change some settings
2. DiskParInfo.batCollect WinRE, Boot Manager and Hard Drive information
3. Create_system_information_files.batGenerate a System Information file of your computer via a menu..
4. chkdskFromEvent.batExtract all chkdsk information from Application section of Event Viewer.
5. SFCfromFile.batExtract all SFC entries from CBS.log or CBSPERSIST*.log (if necessary).
6. LOGS.batWindows Standard Log Collection w/ EventSearch (Technet)
7. Tuneup1.batRun SFC, DISM and CHKDSK commands to repair system files and folders.
8. Tuneup2.batRuns WMIC and BCDEDIT commands to set some basic startup, debug and dump settings.
9. GetMemoryConfiguration.batGet memory configuration data via Powershell
10. GenFileList.batGenerate a List of Files and Folders within a Folder from File Explorer
11. getWindowsUpdateList.batExtract a list of all Windows Updates applied to a system
12. Get_Powercfg_info.batUse Powershell Powercfg commands to extract power and sleep information for the system
13. Upgrade_failure_info.batCollect information about Windows upgrade failure.
14. RebootToBIOSSetup.batReboot computer to BIOS/UEFI Setup if allowed by User.
15. Tuneup_plus_log.batRuns SFC, DISM and CHKDSK commands to verify or restore Operating System files.
16. Gather_additional_dump_files.batCollect dump files from C:\Windows\LiveKernelReports.

List of batch files with BBCode in a .txt file: BSOD_Repository_Batch_Files.txt
 

My Computer

System One

  • OS
    Windows 10
    Computer type
    Laptop
    Manufacturer/Model
    HP
    CPU
    Intel(R) Core(TM) i7-4800MQ CPU @ 2.70GHz
    Motherboard
    Product : 190A Version : KBC Version 94.56
    Memory
    16 GB Total: Manufacturer : Samsung MemoryType : DDR3 FormFactor : SODIMM Capacity : 8GB Speed : 1600
    Graphics Card(s)
    NVIDIA Quadro K3100M; Intel(R) HD Graphics 4600
    Sound Card
    IDT High Definition Audio CODEC; PNP Device ID HDAUDIO\FUNC_01&VEN_111D&DEV_76E0
    Hard Drives
    Model Hitachi HTS727575A9E364
    Antivirus
    Microsoft Defender
    Other Info
    Mobile Workstation

My Computer

System One

  • OS
    Windows 10
    Computer type
    Laptop
    Manufacturer/Model
    HP
    CPU
    Intel(R) Core(TM) i7-4800MQ CPU @ 2.70GHz
    Motherboard
    Product : 190A Version : KBC Version 94.56
    Memory
    16 GB Total: Manufacturer : Samsung MemoryType : DDR3 FormFactor : SODIMM Capacity : 8GB Speed : 1600
    Graphics Card(s)
    NVIDIA Quadro K3100M; Intel(R) HD Graphics 4600
    Sound Card
    IDT High Definition Audio CODEC; PNP Device ID HDAUDIO\FUNC_01&VEN_111D&DEV_76E0
    Hard Drives
    Model Hitachi HTS727575A9E364
    Antivirus
    Microsoft Defender
    Other Info
    Mobile Workstation
Post the following two lines to point people to here, the BSOD Batch repository, for how to download the batch file and collect the required output data.
Tuneup.bat - Click here to go to the BSOD batch repository to download and run this batch file.
Part Two - How to capture output of batch file to Clipboard




Tuneup.bat

Runs SFC, DISM and CHKDSK commands to verify or restore Operating System files​



information
Information

Tuneup.bat - Runs System File Checker (SFC), Deployment Image Servicing and Management (DISM) and CHKDSK commands to verify or restore Operating System files and Windows Management Instrumentation Commands (WMIC) and BCDEDIT commands to set some basic startup, debug and dump settings.

Written by Ztruker 08/10.2020 Last updated 02/01/2021
Based on forum posts by Zbook
Admin elevation code by Matthew Wai 08/14/2020

Runs the following commands

sfc /scannow
dism /online /cleanup-image /scanhealth
dism /online /cleanup-image /restorehealth
sfc /scannow
chkdsk /scan
If you want to run just these commands and not the commands listed below, run the following batch script:

Tuneup1.bat
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}
If you want to run just these commands and not the commands listed above, run the following batch script:

Tuneup2.bat



Part One

Download the batch file​


Download the batch file to your Desktop or Downloads folder.

Download Tuneup.bat




Part Two

Run the batch file​


To run the batch file, open File Explorer, navigate to where you downloaded the batch file then double click on it or right click and select Open.

DO NOT run directly from a Download as your anti-virus may object and prevent it from running.
Always download to your hard drive then run it from there.



When you launch Tuneup.bat, you may see this:

Batch files for use in BSOD debugging-securitywarning.jpg


If you do, click the Run button or uncheck Always ask before opening this file then click on the Run button.

A typical run with no errors will look similar to the following:

Code:
###########################################################
# The following commands will be run in sequence. #
# The first 5 will take quite a while to run, be patient. #
###########################################################

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

chkdsk
/scan

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="DESKTOP" get AutomaticManagedPagefile
wmic
Computersystem where name="DESKTOP" set AutomaticManagedPagefile=True
wmic
Computersystem where name="DESKTOP" get AutomaticManagedPagefile

bcdedit
/enum {badmemory}


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

Image Version: 10.0.19041.508

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

Image Version: 10.0.19041.508

[==========================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.
Volume label is Lenovo_C.

Stage 1: Examining basic file system structure ...
337152 file records processed.
File verification completed.
Phase duration (File record verification): 3.82 seconds.
7830 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.63 milliseconds.

Stage 2: Examining file name linkage ...
855 reparse records processed.
468834 index entries processed.
Index verification completed.
Phase duration (Index verification): 14.43 seconds.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 340.37 milliseconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 1.11 milliseconds.
855 reparse records processed.
Phase duration (Reparse point and Object ID verification): 5.53 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 34.11 milliseconds.
65842 data files processed.
Phase duration (Data attribute verification): 0.46 milliseconds.
CHKDSK
is verifying Usn Journal...
38587264 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 510.83 milliseconds.

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

976122921 KB total disk space.
67772720 KB in 249519 files.
162484 KB in 65843 indexes.
0 KB in bad sectors.
474933 KB in use by the system.
65536 KB occupied by the log file.
907712784 KB available on disk.

4096 bytes in each allocation unit.
244030730 total allocation units on disk.
226928196 allocation units available on disk.
Total duration: 19.16 seconds (19160 ms).

C
:\Windows\system32>wmic recoveros get autoreboot
AutoReboot
FALSE


C
:\Windows\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\DESKTOP\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk0\\Partition3"'
Property(s) update successful.

C
:\Windows\system32>wmic recoveros get autoreboot
AutoReboot
FALSE


C
:\Windows\system32>wmic recoveros get DebugInfoType
DebugInfoType
7


C
:\Windows\system32>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\DESKTOP\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk0\\Partition3"'
Property(s) update successful.

C
:\Windows\system32>wmic recoveros get DebugInfoType
DebugInfoType
7


C
:\Windows\system32>wmic pagefile list /format:list


AllocatedBaseSize=2432
CurrentUsage=92
Description=C:\pagefile.sys
InstallDate=20200731210746.123361-240
Name=C:\pagefile.sys
PeakUsage=142
Status=
TempPageFile=FALSE




C
:\Windows\system32>wmic Computersystem where name="DESKTOP" get AutomaticManagedPagefile
AutomaticManagedPagefile
TRUE


C
:\Windows\system32>wmic Computersystem where name="DESKTOP" set AutomaticManagedPagefile=True
Updating property(s) of '\\DESKTOP\ROOT\CIMV2:Win32_ComputerSystem.Name="DESKTOP"'
Property(s) update successful.

C
:\Windows\system32>wmic Computersystem where name="DESKTOP" get AutomaticManagedPagefile
AutomaticManagedPagefile
TRUE


C
:\Windows\system32>bcdedit /enum {badmemory}

RAM
Defects
-----------
identifier
{badmemory}
Press any key to continue . . .


When done, you will see the following instructions on how to open your Browser in the BSOD Batch Repository for detailed instructions on how to copy data from the Command Prompt or Powershell Window to the Clipboard so you can paste it into your BSOD thread at Tenforums.com.

Batch files for use in BSOD debugging-helpmenu.png




Part Three

Capture output of batch file to Clipboard​


Follow the directions in Part Two of the Index (first post at the top) to capture the output of the batch file in the Command Prompt or Powershell Window for posting in your BSOD thread at tenforums.com.

If you accidentally close the Command Prompt/Powershell window before you captured the data, you can still collect the SFC data by downloading and running:


SFCfromFile.bat to extract all SFC entries from CBS.log or CBSPERSIST*.log (if necessary).

All other output is lost. If needed you will have to run
Tuneup.bat again.
 

My Computer

System One

  • OS
    Windows 10
    Computer type
    Laptop
    Manufacturer/Model
    HP
    CPU
    Intel(R) Core(TM) i7-4800MQ CPU @ 2.70GHz
    Motherboard
    Product : 190A Version : KBC Version 94.56
    Memory
    16 GB Total: Manufacturer : Samsung MemoryType : DDR3 FormFactor : SODIMM Capacity : 8GB Speed : 1600
    Graphics Card(s)
    NVIDIA Quadro K3100M; Intel(R) HD Graphics 4600
    Sound Card
    IDT High Definition Audio CODEC; PNP Device ID HDAUDIO\FUNC_01&VEN_111D&DEV_76E0
    Hard Drives
    Model Hitachi HTS727575A9E364
    Antivirus
    Microsoft Defender
    Other Info
    Mobile Workstation
Post the following two lines to point people to here, the BSOD Batch repository, for how to download the batch file and collect the required output data.
DiskParInfo.bat - Click here to go to the BSOD batch repository to download and run this batch file.
Part Two - How to capture output of batch file to Clipboard



DiskParInfo.bat

Generates the right number of diskpart commands to run based on the number of hard drives (HDD and SSD) and partitions on each hard drive.​



information
Information

DiskParInfo.bat - Generates the right number of diskpart commands to run based on the number of hard drives (HDD and SSD) and partitions on each hard drive. Runs reagentc to collect recovery environment data, bcdedit to collect boot manager and loader info.
All output is written to a DiskParInfo.LOG file in the users temp folder (%temp%\DiskpParInfo.LOG).

Written by Matthew Wai 09/02/2020 Last update 12/27/2021
Modified by Ztruker 09/02/2020 Last update 02/01/2021
Based on forum posts by Zbook

Runs the following commands to collect Reagent, Boot Manager and Hard Drive information.
list disk
list vol
select disk nThere will be a diskpart command group for each detected disk on your computer
detail disk
list partitionIt will have diskpart partition commands for each detected partition on each disk
select partition 1
detail partition
select partition 2
detail partition
--- --- --- --- --- --- ---
echo select partition n
echo detail partition
reagentc /info
bcdedit /enum all



Part One

Download the batch file​

Download the batch file to your Desktop or Downloads folder.

Download DiskParInfo.bat



Part Two

Run the batch file​


To run the batch file, open File Explorer, navigate to where you downloaded the batch file then double click on it or right click and select Open.

DO NOT run directly from a Download as your anti-virus may object and prevent it from running.
Always download to your hard drive then run it from there.



When you launch DiskParInfo.bat, you may see this:

Batch files for use in BSOD debugging-securitywarning.jpg


If you do, click the Run button or uncheck Always ask before opening this file then click on the Run button.

The first window you will see if this:

Batch files for use in BSOD debugging-diskparinfo1.jpg


When DiskParInfo completes, notepad will open DiskParInfo.LOG from the %temp% folder. The log file will look similar to the following:

Code:
Disk 0 is an SSD. Model: Samsung SSD 860 QVO
Disk 1 is an HDD. Model: ST2000NM0011
Disk 2 is an HDD. Model: ST2000DM006-2DM164
======================================================================
Disk 0 has 4 partition(s).
Disk 1 has 3 partition(s).
Disk 2 has 3 partition(s).

This computer has the above 3 HDD(s) or SSD(s) in total.
======================================================================

Microsoft DiskPart version 10.0.19041.1

Copyright (C) Microsoft Corporation.
On computer: DESKTOP

Disk ### Status Size Free Dyn Gpt
-------- ------------- ------- ------- --- ---
Disk 0 Online 931 GB 1024 KB *
Disk 1 Online 1863 GB 2048 KB *
Disk 2 Online 1863 GB 16 MB
Disk 3 No Media 0 B 0 B
Disk 4 No Media 0 B 0 B

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 0 M DVD-ROM 0 B No Media
Volume 1 C Lenovo_C NTFS Partition 930 GB Healthy Boot
Volume 2 NTFS Partition 505 MB Healthy
Volume 3 FAT32 Partition 100 MB Healthy System
Volume 4 D Lenovo_D NTFS Partition 732 GB Healthy
Volume 5 E Lenovo_E NTFS Partition 722 GB Healthy
Volume 6 F Lenovo_F NTFS Partition 408 GB Healthy
Volume 7 G Lenovo_G NTFS Partition 929 GB Healthy
Volume 8 H Lenovo_H NTFS Partition 931 GB Healthy
Volume 9 X WIN10XPE FAT32 Partition 2048 MB Healthy
Volume 10 K Removable 0 B No Media
Volume 11 L Removable 0 B No Media

Disk 0 is now the selected disk.

Samsung SSD 860 QVO 1TB
Disk ID: {BBAD39C8-C88B-4704-843C-888B6720D956}
Type : SATA
Status : Online
Path : 0
Target : 0
LUN ID
: 0
Location Path : PCIROOT(0)#PCI(1F02)#ATA(C00T00L00)
Current Read-only State : No
Read-only : No
Boot Disk : Yes
Pagefile Disk : Yes
Hibernation File Disk : No
Crashdump Disk : Yes
Clustered Disk : No

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 1 C Lenovo_C NTFS Partition 930 GB Healthy Boot
Volume 2 NTFS Partition 505 MB Healthy
Volume 3 FAT32 Partition 100 MB Healthy System

Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 System 100 MB 1024 KB
Partition 2 Reserved 16 MB 101 MB
Partition 3 Primary 930 GB 117 MB
Partition 4 Recovery 505 MB 931 GB

Partition 1 is now the selected partition.

Partition 1
Type : c12a7328-f81f-11d2-ba4b-00a0c93ec93b
Hidden : Yes
Required: No
Attrib : 0X8000000000000000
Offset in Bytes: 1048576

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
* Volume 3 FAT32 Partition 100 MB Healthy System

Partition 2 is now the selected partition.

Partition 2
Type : e3c9e316-0b5c-4db8-817d-f92df00215ae
Hidden : Yes
Required: No
Attrib : 0X8000000000000000
Offset in Bytes: 105906176

There is no volume associated with this partition.

Partition 3 is now the selected partition.

Partition 3
Type : ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
Hidden : No
Required: No
Attrib : 0000000000000000
Offset in Bytes: 122683392

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
* Volume 1 C Lenovo_C NTFS Partition 930 GB Healthy Boot

Partition 4 is now the selected partition.

Partition 4
Type : de94bba4-06d1-4d40-a16a-bfd50179d6ac
Hidden : No
Required: Yes
Attrib : 0X8000000000000001
Offset in Bytes: 999673561088

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
* Volume 12 NTFS Partition 505 MB Healthy Hidden

Disk 1 is now the selected disk.

ST2000NM0011
Disk ID: {10800FF6-5858-9090-8081-828310111213}
Type : SATA
Status : Online
Path : 1
Target : 0
LUN ID
: 0
Location Path : PCIROOT(0)#PCI(1F02)#ATA(C01T00L00)
Current Read-only State : No
Read-only : No
Boot Disk : No
Pagefile Disk : No
Hibernation File Disk : No
Crashdump Disk : No
Clustered Disk : No

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 4 D Lenovo_D NTFS Partition 732 GB Healthy
Volume 5 E Lenovo_E NTFS Partition 722 GB Healthy
Volume 6 F Lenovo_F NTFS Partition 408 GB Healthy

Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 Primary 732 GB 20 KB
Partition 2 Primary 722 GB 732 GB
Partition 3 Primary 408 GB 1454 GB

Partition 1 is now the selected partition.

Partition 1
Type : ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
Hidden : No
Required: No
Attrib : 0000000000000000
Offset in Bytes: 20480

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
* Volume 4 D Lenovo_D NTFS Partition 732 GB Healthy

Partition 2 is now the selected partition.

Partition 2
Type : ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
Hidden : No
Required: No
Attrib : 0000000000000000
Offset in Bytes: 786567266304

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
* Volume 5 E Lenovo_E NTFS Partition 722 GB Healthy

Partition 3 is now the selected partition.

Partition 3
Type : ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
Hidden : No
Required: No
Attrib : 0000000000000000
Offset in Bytes: 1562261848064

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
* Volume 6 F Lenovo_F NTFS Partition 408 GB Healthy

Disk 2 is now the selected disk.

ST2000DM006
-2DM164
Disk ID: 5641B4B0
Type : SATA
Status : Online
Path : 2
Target : 0
LUN ID
: 0
Location Path : PCIROOT(0)#PCI(1F02)#ATA(C02T00L00)
Current Read-only State : No
Read-only : No
Boot Disk : No
Pagefile Disk : No
Hibernation File Disk : No
Crashdump Disk : No
Clustered Disk : No

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 7 G Lenovo_G NTFS Partition 929 GB Healthy
Volume 8 H Lenovo_H NTFS Partition 931 GB Healthy
Volume 9 X WIN10XPE FAT32 Partition 2048 MB Healthy

Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 Primary 929 GB 16 MB
Partition 2 Primary 931 GB 929 GB
Partition 3 Primary 2048 MB 1861 GB

Partition 1 is now the selected partition.

Partition 1
Type : 07
Hidden: No
Active: No
Offset in Bytes: 16777216

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
* Volume 7 G Lenovo_G NTFS Partition 929 GB Healthy

Partition 2 is now the selected partition.

Partition 2
Type : 07
Hidden: No
Active: No
Offset in Bytes: 997619400704

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
* Volume 8 H Lenovo_H NTFS Partition 931 GB Healthy

Partition 3 is now the selected partition.

Partition 3
Type : 0C
Hidden: No
Active: No
Offset in Bytes: 1998249263104

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
* Volume 9 X WIN10XPE FAT32 Partition 2048 MB Healthy

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

Windows Recovery Environment (Windows RE) and system reset configuration
Information:

Windows RE status: Enabled
Windows RE location: \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE
Boot Configuration Data (BCD) identifier: 8d90a8b3-d39b-11ea-982c-97b4c3117002
Recovery image location:
Recovery image index: 0
Custom image location:
Custom image index: 0

REAGENTC
.EXE: Operation Successful.

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

Firmware Boot Manager
---------------------
identifier
{fwbootmgr}
displayorder
{bootmgr}
{8d90a8af-d39b-11ea-982c-97b4c3117002}
{8d90a8ad-d39b-11ea-982c-97b4c3117002}
{8d90a8ae-d39b-11ea-982c-97b4c3117002}
{8d90a8ac-d39b-11ea-982c-97b4c3117002}
timeout
2

Windows Boot Manager
--------------------
identifier
{bootmgr}
device partition
=\Device\HarddiskVolume1
path \EFI\Microsoft\Boot\bootmgfw
.efi
description
Windows Boot Manager
locale en
-US
inherit
{globalsettings}
default {current}
resumeobject
{8d90a8b1-d39b-11ea-982c-97b4c3117002}
displayorder
{current}
toolsdisplayorder
{memdiag}
timeout
10

Firmware Application (101fffff)
-------------------------------
identifier
{8d90a8ac-d39b-11ea-982c-97b4c3117002}
description
Generic Usb Device

Firmware Application (101fffff)
-------------------------------
identifier
{8d90a8ad-d39b-11ea-982c-97b4c3117002}
description CD
/DVD Device

Firmware Application (101fffff)
-------------------------------
identifier
{8d90a8ae-d39b-11ea-982c-97b4c3117002}
description
Windows Boot Manager

Firmware Application (101fffff)
-------------------------------
identifier
{8d90a8af-d39b-11ea-982c-97b4c3117002}
device partition
=X:
path \EFI\Microsoft\Boot\bootmgfw
.efi
description
Windows Boot Manager

Windows Boot Loader
-------------------
identifier
{current}
device partition
=C:
path \Windows\system32\winload
.efi
description
Windows 10
locale en
-US
inherit
{bootloadersettings}
recoverysequence
{8d90a8b3-d39b-11ea-982c-97b4c3117002}
displaymessageoverride
Recovery
recoveryenabled
Yes
isolatedcontext
Yes
allowedinmemorysettings
0x15000075
osdevice partition
=C:
systemroot \Windows
resumeobject
{8d90a8b1-d39b-11ea-982c-97b4c3117002}
nx
OptIn
bootmenupolicy
Standard
hypervisorlaunchtype
Auto

Windows Boot Loader
-------------------
identifier
{8d90a8b3-d39b-11ea-982c-97b4c3117002}
device ramdisk
=[\Device\HarddiskVolume4]\Recovery\WindowsRE\Winre.wim,{8d90a8b4-d39b-11ea-982c-97b4c3117002}
path \windows\system32\winload
.efi
description
Windows Recovery Environment
locale en
-us
inherit
{bootloadersettings}
displaymessage
Recovery
osdevice ramdisk
=[\Device\HarddiskVolume4]\Recovery\WindowsRE\Winre.wim,{8d90a8b4-d39b-11ea-982c-97b4c3117002}
systemroot \windows
nx
OptIn
bootmenupolicy
Standard
winpe
Yes

Resume from Hibernate
---------------------
identifier
{8d90a8b1-d39b-11ea-982c-97b4c3117002}
device partition
=C:
path \Windows\system32\winresume
.efi
description
Windows Resume Application
locale en
-US
inherit
{resumeloadersettings}
recoverysequence
{8d90a8b3-d39b-11ea-982c-97b4c3117002}
recoveryenabled
Yes
isolatedcontext
Yes
allowedinmemorysettings
0x15000075
filedevice partition
=C:
filepath \hiberfil
.sys
bootmenupolicy
Standard
debugoptionenabled
No

Windows Memory Tester
---------------------
identifier
{memdiag}
device partition
=\Device\HarddiskVolume1
path \EFI\Microsoft\Boot\memtest
.efi
description
Windows Memory Diagnostic
locale en
-US
inherit
{globalsettings}
badmemoryaccess
Yes

EMS
Settings
------------
identifier
{emssettings}
bootems
No

Debugger Settings
-----------------
identifier
{dbgsettings}
debugtype
Local

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

Global Settings
---------------
identifier
{globalsettings}
inherit
{dbgsettings}
{emssettings}
{badmemory}

Boot Loader Settings
--------------------
identifier
{bootloadersettings}
inherit
{globalsettings}
{hypervisorsettings}

Hypervisor Settings
-------------------
identifier
{hypervisorsettings}
hypervisordebugtype
Serial
hypervisordebugport
1
hypervisorbaudrate
115200

Resume Loader Settings
----------------------
identifier
{resumeloadersettings}
inherit
{globalsettings}

Device options
--------------
identifier
{8d90a8b4-d39b-11ea-982c-97b4c3117002}
description
Windows Recovery
ramdisksdidevice partition
=\Device\HarddiskVolume4
ramdisksdipath \Recovery\WindowsRE\boot
.sdi

Device options
--------------
identifier
{8d90a8b6-d39b-11ea-982c-97b4c3117002}
description
Kyhi Rescue
ramdisksdidevice partition
=X:
ramdisksdipath \NST\boot
.sdi

Device options
--------------
identifier
{8d90a8b8-d39b-11ea-982c-97b4c3117002}
description
Kyhi Rescue
ramdisksdidevice partition
=X:
ramdisksdipath \NST\boot
.sdi

Device options
--------------
identifier
{8d90a8ba-d39b-11ea-982c-97b4c3117002}
description
Kyhi Rescue
ramdisksdidevice partition
=X:
ramdisksdipath \boot\boot
.sdi

Device options
--------------
identifier
{8d90a8bc-d39b-11ea-982c-97b4c3117002}
description
Kyhi Rescue
ramdisksdidevice partition
=X:
ramdisksdipath \boot\boot
.sdi

Setup Ramdisk Options
---------------------
identifier
{ramdiskoptions}
description
RamdiskOptions
ramdisksdidevice partition
=X:
ramdisksdipath \NST\boot
.sdi


When done, you will see the following instructions on how to open your Browser to the BSOD Batch Repository for detailed instructions on how to copy data from the Command Prompt or Powershell Window to the Clipboard so you can paste it into your BSOD thread at Tenforums.com.

Review the instructions in Part Two of the Index (the first post in this thread) by pressing the [V] key which will open your default web browser to that page and close the window, or press C to just close the window.

Batch files for use in BSOD debugging-helpmenu.png





Part Three

Capture output of batch file to Clipboard​


Follow the directions in Part Two of the Index (first post at the top) to capture the output of the batch file displayed in notepad for posting in your BSOD thread at tenforums.com.

Note
Note

You can review the DiskParInfo.LOG file at any time (as long as it hasn't been deleted):
Press Window key + X, type notepad %temp%\DiskParInfo.LOG and press Enter

You can also review the commands input to diskpart at any time (as long as it hasn't been deleted):
Press Window key + R, type notepad %temp%\DiskParInfo.INP and press Enter



Part Four

Error during Powershell processing​


If an error occurs during Powershell processing, specifically for a Powershell Get-Partition command, you will see the following window:

Batch files for use in BSOD debugging-diskparinfo2.jpg


Pressing D will download the Tuneup1.bat file (and close the window) so you can run it. Tuneup1.bat runs SFC and DISM commands to correct any corrupted system files which is one of the causes of failure for the Powershell Get-Partition command.

Pressing C will exit the window and you can then manually download Tuneup.bat and run it.
Last edited by Ztruker; 28 Dec 2021 at 11:13.
 

My Computer

System One

  • OS
    Windows 10
    Computer type
    Laptop
    Manufacturer/Model
    HP
    CPU
    Intel(R) Core(TM) i7-4800MQ CPU @ 2.70GHz
    Motherboard
    Product : 190A Version : KBC Version 94.56
    Memory
    16 GB Total: Manufacturer : Samsung MemoryType : DDR3 FormFactor : SODIMM Capacity : 8GB Speed : 1600
    Graphics Card(s)
    NVIDIA Quadro K3100M; Intel(R) HD Graphics 4600
    Sound Card
    IDT High Definition Audio CODEC; PNP Device ID HDAUDIO\FUNC_01&VEN_111D&DEV_76E0
    Hard Drives
    Model Hitachi HTS727575A9E364
    Antivirus
    Microsoft Defender
    Other Info
    Mobile Workstation
Post the following two lines to point people here to the Batch repository for how to download the batch file and collect the required output data.

Create_system_information_files.bat - Click here to go to the BSOD batch repository to download and run this batch file.
Part Two - How to capture output of batch file to Clipboard



Create_system_information_files.bat

Generate 3 types of System Information Reports individually or all together​


information
Information
Create_system_information_files.bat - Generate 3 types of System Information Reports individually or all together, that can be uploaded and posted in a forum thread at tenforums.com.

Written by Matthew Wai 09/02/2020 Last update 02/01/2021



Part One

Menu choices and processes​

Batch files for use in BSOD debugging-cresysinf1.jpg


1 = Create a system information file via System Information (in full details).
This choice calls msinfo32.exe to generate a full System Information report and saves it as System Information.nfo on your Desktop.
2 = Create a system information file via Systeminfo.exe.
This choice calls Systeminfo.exe to generate a shorter System Information report and saves it as Systeminfo.txt on your Desktop.
3 = Create a system information file via PowerShell.exe.
This choice calls Powershell cmdlets to generate a different, shorter, System Information report and saves it as Get-Computerinfo.txt on your Desktop.
4 = All of the above.
This choice runs all the above to generate each report shown on your Desktop.

If you enter ? you will get this menu:

Batch files for use in BSOD debugging-cresysinf2.jpg




Part Two

Download the batch file​

Download the batch file to a location on your hard drive. Your Downloads folder or Desktop is a good place but it can be anywhere you want.

Download Create_system_information_files.bat



Part Three

Run the batch file​

To run the batch file, open File Explorer, navigate to where you downloaded the batch file then double click on it or right click and select Open.

DO NOT run directly from a Download as your anti-virus may object and prevent it from running.
Always download to your hard drive then run it from there.



When you launch Create_system_information_files.bat, you may see this:

Batch files for use in BSOD debugging-securitywarning.jpg


If you do, click the Run button or uncheck Always ask before opening this file then click on the Run button.



Part Four

Upload Systeminfo.txt​

Upload 1. System Information.nfo, 2. Systeminfo.txt and/or 3. Get-Computerinfo.txt from your Desktop to a post in your thread in the BSOD Forum at tenforums.com.

See Part Two-Four 7 of the Index (1st post at the top) for a Tutorial link on how to do this.

Last edited by Ztruker; 01 Feb 2021 at 14:09.



Post the following two lines to point people to here, the BSOD Batch repository, for how to download the batch file and collect the required output data.

chkdskFromEvent.bat
- Click here to go to the BSOD batch repository to download and run this batch file.
Part Two - How to capture output of batch file to Clipboard



chkdskFromEvent.bat

Extract all chkdsk output from the Application section of Event Viewer using Powershell commands​


information
Information
chkdskFromEvent.bat - Extract all chkdsk output from the Application section of Event Viewer using Powershell commands and write the output to chkdskFromEvent.log in the %temp%directory.

Written by Ztruker 09/07.2020 Last update 02/01/2021
Based on code by Matthew Wai and Paul Black



Part One

Download the batch file​

Download the batch file to your Desktop or Downloads folder.

Download chkdskFromEvent.bat



Part Two

Run the batch file​

This batch file is designed to be run from File Explore by double clicking on it or right clicking and selecting Open.

DO NOT run directly from a Download as your anti-virus may object and prevent it from running.
Always download to your hard drive then run it from there.



When you launch chkdskFromEvent.bat, you may see this:

Batch files for use in BSOD debugging-securitywarning.jpg


If you do, click the Run button or uncheck Always ask before opening this file then click on the Run button.

When you run the batch file and Powershell starts processing, the first window you will see is this:

Batch files for use in BSOD debugging-chkdskfromevent-1.jpg


When Powershell completes, you will then see the Notepad window which should look something like this:

Code:
TimeCreated : 9/2/2020 11:18:16 PM
Message : Chkdsk was executed in read-only mode on a volume snapshot.

Checking file system on C:
The type of the file system is NTFS.
Volume label is Lenovo_C.

WARNING! /F parameter not specified.
Running CHKDSK in read-only mode.

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

File verification completed.
Phase duration (File record verification): 3.42 seconds.
5625 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.46 milliseconds.

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

425498 index entries processed.

Index verification completed.
Phase duration (Index verification): 13.51 seconds.
0 unindexed files scanned.

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

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

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

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

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

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

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

976122921 KB total disk space.
65893048 KB in 233434 files.
147608 KB in 61839 indexes.
0 KB in bad sectors.
435633 KB in use by the system.
65536 KB occupied by the log file.
909646632 KB available on disk.

4096 bytes in each allocation unit.
244030730 total allocation units on disk.
227411658 allocation units available on disk.
Total duration: 18.00 seconds (18009 ms).


TimeCreated : 8/22/2020 1:25:05 PM
Message : Chkdsk was executed in scan mode on a volume snapshot.

Checking file system on C:
The type of the file system is NTFS.
Volume label is Lenovo_C.

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

File verification completed.
Phase duration (File record verification): 3.08 seconds.
4899 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.60 milliseconds.

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

419868 index entries processed.

Index verification completed.
Phase duration (Index verification): 12.62 seconds.
0 unindexed files scanned.

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

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

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

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

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

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

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

976122921 KB total disk space.
71639024 KB in 229908 files.
144372 KB in 60432 indexes.
0 KB in bad sectors.
438233 KB in use by the system.
65536 KB occupied by the log file.
903901292 KB available on disk.

4096 bytes in each allocation unit.
244030730 total allocation units on disk.
225975323 allocation units available on disk.
Total duration: 16.58 seconds (16584 ms).

-------------------------------------------------------------------
---


Stage 1: Examining basic file system structure ...

Stage 2: Examining file name linkage ...

Stage 3: Examining security descriptors ...


TimeCreated : 8/13/2020 2:40:42 PM
Message : Chkdsk was executed in scan mode on a volume snapshot.

Checking file system on D:
The type of the file system is NTFS.
Volume label is Lenovo_D.

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

File verification completed.
Phase duration (File record verification): 11.98 seconds.
2077 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.04 milliseconds.

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

1706794 index entries processed.

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

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

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

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

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

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

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

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

768131071 KB total disk space.
526905200 KB in 187839 files.
117052 KB in 99847 indexes.
0 KB in bad sectors.
1638663 KB in use by the system.
65536 KB occupied by the log file.
239470156 KB available on disk.

4096 bytes in each allocation unit.
192032767 total allocation units on disk.
59867539 allocation units available on disk.
Total duration: 1.37 minutes (82258 ms).

-------------------------------------------------------------------
---


Stage 1: Examining basic file system structure ...

Stage 2: Examining file name linkage ...

Stage 3: Examining security descriptors ...


TimeCreated : 8/13/2020 2:07:41 PM
Message : Chkdsk was executed in scan mode on a volume snapshot.

Checking file system on D:
The type of the file system is NTFS.
Volume label is Lenovo_D.

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

File verification completed.
Phase duration (File record verification): 11.96 seconds.
2077 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.27 milliseconds.

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

1706792 index entries processed.

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

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

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

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

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

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

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

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

768131071 KB total disk space.
526905200 KB in 187839 files.
117048 KB in 99846 indexes.
0 KB in bad sectors.
1638663 KB in use by the system.
65536 KB occupied by the log file.
239470160 KB available on disk.

4096 bytes in each allocation unit.
192032767 total allocation units on disk.
59867540 allocation units available on disk.
Total duration: 1.40 minutes (84218 ms).

-------------------------------------------------------------------
---


Stage 1: Examining basic file system structure ...

Stage 2: Examining file name linkage ...

Stage 3: Examining security descriptors ...






TimeCreated : 9/3/2020 3:26:44 PM
Message :

Checking file system on C:
The type of the file system is NTFS.
Volume label is Lenovo_C.


A disk check has been scheduled.
Windows will now check the disk.

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


File verification completed.
Phase duration (File record verification): 3.32 seconds.
5626 large file records processed.


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


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

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


425550 index entries processed.


Index verification completed.
Phase duration (Index verification): 14.20 seconds.
0 unindexed files scanned.


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


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


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

Stage 3: Examining security descriptors ...
Cleaning up 1156 unused index entries from index $SII of file 0x9.
Cleaning up 1156 unused index entries from index $SDH of file 0x9.
Cleaning up 1156 unused security descriptors.
Security descriptor verification completed.
Phase duration (Security descriptor verification): 36.15
milliseconds.
61864 data files processed.


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


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

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

976122921 KB total disk space.
66153096 KB in 227383 files.
147688 KB in 61865 indexes.
0 KB in bad sectors.
440249 KB in use by the system.
65536 KB occupied by the log file.
909381888 KB available on disk.

4096 bytes in each allocation unit.
244030730 total allocation units on disk.
227345472 allocation units available on disk.
Total duration: 18.63 seconds (18630 ms).

Internal Info:
00 9b 04 00 ea 69 04 00 fa 46 08 00 00 00 00 00 .....i...F......
a8 01 00 00 52 01 00 00 00 00 00 00 00 00 00 00 ....R...........

Windows has finished checking your disk.
Please wait while your computer restarts.
When done, you will see the following instructions on how to open your Browser to the BSOD Batch Repository for detailed instructions on how to copy data from the Command Prompt or Powershell Window to the Clipboard so you can paste it into your BSOD thread at Tenforums.com.

Review the instructions in Part Two of the Index (the first post in this thread) by pressing the [V] key which will open your default web browser to that page and close the window, or press C to just close the window.

Batch files for use in BSOD debugging-helpmenu.png


The Notepad window will remain open.



Part Three

Capture output of batch file to Clipboard​

Follow the directions in Part Two of the Index (first post at the top) to capture the output of the batch file displayed in notepad for posting in your BSOD thread at tenforums.com.

Last edited by Ztruker; 01 Feb 2021 at 14:17.
 
Last edited:

My Computer

System One

  • OS
    Windows 10
    Computer type
    Laptop
    Manufacturer/Model
    HP
    CPU
    Intel(R) Core(TM) i7-4800MQ CPU @ 2.70GHz
    Motherboard
    Product : 190A Version : KBC Version 94.56
    Memory
    16 GB Total: Manufacturer : Samsung MemoryType : DDR3 FormFactor : SODIMM Capacity : 8GB Speed : 1600
    Graphics Card(s)
    NVIDIA Quadro K3100M; Intel(R) HD Graphics 4600
    Sound Card
    IDT High Definition Audio CODEC; PNP Device ID HDAUDIO\FUNC_01&VEN_111D&DEV_76E0
    Hard Drives
    Model Hitachi HTS727575A9E364
    Antivirus
    Microsoft Defender
    Other Info
    Mobile Workstation
Back
Top Bottom