New
#961
Code:Started on Mon 09/20/2021 at 22:22:20.20 [SFC /ScanNow] Beginning system scan. This process will take some time. Results: Windows Resource Protection found corrupt files and successfully repaired 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 Mon 09/20/2021 at 22:29:15.99 [DISM /online /cleanup-image /ScanHealth] Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.19043.928 No component store corruption detected. The operation completed successfully. ================================================================== Started on Mon 09/20/2021 at 22:31:34.27 [DISM /online /cleanup-image /RestoreHealth] Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.19043.928 The restore operation completed successfully. The operation completed successfully. ================================================================== Started on Mon 09/20/2021 at 22:32:51.59 [SFC /ScanNow] Beginning system scan. This process will take some time. Results: Windows Resource Protection did not find any integrity violations. ================================================================== A TXT file named SFC_details.txt has been created. ================================================================== Started on Mon 09/20/2021 at 22:35:14.31 [ChkDsk /Scan] The type of the file system is NTFS. Volume label is Windows. Stage 1: Examining basic file system structure ... 834560 file records processed. File verification completed. Phase duration (File record verification): 24.59 seconds. 13491 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.05 milliseconds. Stage 2: Examining file name linkage ... 936 reparse records processed. 1264820 index entries processed. Index verification completed. Phase duration (Index verification): 4.59 minutes. 0 unindexed files scanned. Phase duration (Orphan reconnection): 6.86 seconds. 0 unindexed files recovered to lost and found. Phase duration (Orphan recovery to lost and found): 0.11 milliseconds. 936 reparse records processed. Phase duration (Reparse point and Object ID verification): 6.14 milliseconds. Stage 3: Examining security descriptors ... Security descriptor verification completed. Phase duration (Security descriptor verification): 1.02 seconds. 215131 data files processed. Phase duration (Data attribute verification): 0.10 milliseconds. CHKDSK is verifying Usn Journal... 35972368 USN bytes processed. Usn Journal verification completed. Phase duration (USN journal verification): 962.48 milliseconds. Windows has scanned the file system and found no problems. No further action is required. 722633727 KB total disk space. 193144796 KB in 580521 files. 510904 KB in 215132 indexes. 0 KB in bad sectors. 966351 KB in use by the system. 65536 KB occupied by the log file. 528011676 KB available on disk. 4096 bytes in each allocation unit. 180658431 total allocation units on disk. 132002919 allocation units available on disk. Total duration: 5.15 minutes (309076 ms). ================================================================== Started on Mon 09/20/2021 at 22:40:53.88 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=29696 CurrentUsage=0 Description=C:\pagefile.sys InstallDate=20210123182308.249920-360 Name=C:\pagefile.sys PeakUsage=1 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 Mon 09/20/2021 at 22:40:54.90
In the script does findstr only run after the second scannow or can it run after the first scannow too?
Can Gather_additional_dump_files.bat ─ Click here to go to the BSOD batch repository to download and run this batch file be modified so that it creates a new file on the desktop similar to the new tuneup?
Code:######################################################################### # # # Tuneup_plus_log.bat # # # # The following ZIP file has been created on the desktop. # # # # Tuneup_log-[2021-09-20_at_22-40-54].zip # # # # Please upload it as an attachment to your post on Ten Forums. # # You may press a key to close this windows. # # # #########################################################################
Code:####################################################################################### # # # Gather_additional_dump_files.bat # # # # The following ZIP file has been created on the desktop: # # # # LiveKernel Reports 2021-09-20 (22-46-17).zip # # # # Please upload the file as an attachment to your post on TenForums. # # Press any key to close this window. # # # #######################################################################################
Code:Creation date and time Size (MB) File path ---------------------- --------- ----------------------------- 2028-01-02 8:39:49 PM 675.17 C:\WINDOWS\LiveKernelReports\WFP-20280102-2039.dmp Note: 0 dump file(s) has/have been zipped.
It looks like this computer needs a new CMOS battery: 2028-01-02 8:39:49 PM
Code:####################################################################################### # # # Upgrade_failure_info.bat # # # # The log files have been put into the following ZIP file on your desktop: # # # C:\Users\a\Desktop\Upgrade_failure_logs_2021-09-20_22-52-18.zip # # # Please upload the file as an attachment to your post on TenForums. # # Press any key to close this window. # # # #######################################################################################
Upgrade failure appeared properly on the desktop.
Code:####################################################################################### # # # Get_Powercfg_info.bat # # # # The log files have been put into the following ZIP file: # # # C:\Users\a\AppData\Local\Temp\Powercfg_info_2021-09-20_at_22-56-08.zip # # # Please upload the file as an attachment to your post on TenForums. # # Press any key to close this window. # # # #######################################################################################
Can Get_Powercfg_info.bat - Click here to go to the BSOD batch repository to download and run this batch file. be modified so that it appears on the desktop similar to the new tune up?
Code:Powershell -ComObject Microsoft.Update.Session ============================================================================== Powershell Get-Hotfix Source Description HotFixID InstalledBy InstalledOn ------ ----------- -------- ----------- ----------- DESKTOP-K2CP43S Update KB4601554 4/9/2021 12:00:00 AM DESKTOP-K2CP43S Update KB5000736 4/9/2021 12:00:00 AM DESKTOP-K2CP43S Security Update KB5001330 4/9/2021 12:00:00 AM DESKTOP-K2CP43S Security Update KB5001405 4/9/2021 12:00:00 AM
There was no pop up box after running getWindowsUpdateList.bat
The new text file was in the proper location on the desktop.
There may not have been an older file. Please check to see whether it will appear in the location similar to tune up.
Can a pop up appear indicating that it is on the desktop?
What determines whether there is a purple or black pop up box after the script completes?
This one was black whereas all of the others were purple:
Code:################################################################################### # 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] # # # # Press [V] to visit the above web page for detailed instructions. # # Press [C] to close this window. # ###################################################################################
Code:Disk 0 : SSD. It has 4 partition(s). Model: Hitachi HTS727575A9E364 The script has found the above 1 storage device(s) in total. ======================================================================= Microsoft DiskPart version 10.0.19041.610 Copyright (C) Microsoft Corporation. On computer: DESKTOP-K2CP43S Disk ### Status Size Free Dyn Gpt -------- ------------- ------- ------- --- --- Disk 0 Online 698 GB 0 B Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- Volume 0 G DVD-ROM 0 B No Media Volume 1 K System Rese NTFS Partition 499 MB Healthy System Volume 2 C Windows NTFS Partition 689 GB Healthy Boot Volume 3 D HP_TOOLS FAT32 Partition 2056 MB Healthy Volume 4 Recovery NTFS Partition 7148 MB Healthy Hidden Disk 0 is now the selected disk. Hitachi HTS727575A9E364 Disk ID: 2CE38090 Type : RAID Status : Online Path : 0 Target : 1 LUN ID : 0 Location Path : PCIROOT(0)#PCI(1F02)#RAID(P00T01L00) 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 K System Rese NTFS Partition 499 MB Healthy System Volume 2 C Windows NTFS Partition 689 GB Healthy Boot Volume 3 D HP_TOOLS FAT32 Partition 2056 MB Healthy Volume 4 Recovery NTFS Partition 7148 MB Healthy Hidden Partition ### Type Size Offset ------------- ---------------- ------- ------- Partition 1 Primary 499 MB 1024 KB Partition 2 Primary 689 GB 500 MB Partition 3 Primary 2056 MB 689 GB Partition 4 Recovery 7148 MB 691 GB Partition 1 is now the selected partition. Partition 1 Type : 07 Hidden: No Active: Yes Offset in Bytes: 1048576 Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- * Volume 1 K System Rese NTFS Partition 499 MB Healthy System Partition 2 is now the selected partition. Partition 2 Type : 07 Hidden: No Active: No Offset in Bytes: 524288000 Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- * Volume 2 C Windows NTFS Partition 689 GB Healthy Boot Partition 3 is now the selected partition. Partition 3 Type : 0C Hidden: No Active: No Offset in Bytes: 740501225472 Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- * Volume 3 D HP_TOOLS FAT32 Partition 2056 MB Healthy Partition 4 is now the selected partition. Partition 4 Type : 27 Hidden: No Active: No Offset in Bytes: 742657097728 Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- * Volume 4 Recovery NTFS Partition 7148 MB Healthy Hidden =============================================================================== 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: d1db91ed-1a87-11ec-83fa-99fc2db626b5 Recovery image location: Recovery image index: 0 Custom image location: Custom image index: 0 REAGENTC.EXE: Operation Successful. =============================================================================== Windows Boot Manager -------------------- identifier {bootmgr} device partition=K: description Windows Boot Manager locale en-US inherit {globalsettings} default {current} resumeobject {79baf053-1a87-11ec-83f8-fcf8ae13c094} displayorder {current} toolsdisplayorder {memdiag} timeout 0 Windows Boot Loader ------------------- identifier {current} device partition=C: path \WINDOWS\system32\winload.exe description Windows 10 locale en-US inherit {bootloadersettings} recoverysequence {d1db91ed-1a87-11ec-83fa-99fc2db626b5} displaymessageoverride Recovery recoveryenabled Yes allowedinmemorysettings 0x15000075 osdevice partition=C: systemroot \WINDOWS resumeobject {79baf053-1a87-11ec-83f8-fcf8ae13c094} nx OptIn bootmenupolicy Standard Windows Boot Loader ------------------- identifier {b7d9a1e1-6cf7-11eb-83b4-e165f11dfe15} device ramdisk=[\Device\HarddiskVolume4]\Recovery\WindowsRE\Winre.wim,{b7d9a1e2-6cf7-11eb-83b4-e165f11dfe15} path \windows\system32\winload.exe description Windows Recovery Environment locale en-US inherit {bootloadersettings} displaymessage Recovery osdevice ramdisk=[\Device\HarddiskVolume4]\Recovery\WindowsRE\Winre.wim,{b7d9a1e2-6cf7-11eb-83b4-e165f11dfe15} systemroot \windows nx OptIn bootmenupolicy Standard winpe Yes Windows Setup ------------- identifier {cbd971bf-b7b8-4885-951a-fa03044f5d71} device ramdisk=[C:]\$WINDOWS.~BT\Sources\SafeOS\winre.wim,{79baf055-1a87-11ec-83f8-fcf8ae13c094} bootstatdevice partition=C: custom:11000083 partition=C: path \windows\system32\winload.exe description Windows Rollback locale en-US bootstatfilepath \$WINDOWS.~BT\Sources\SafeOS\bootstat.dat inherit {bootloadersettings} restartonfailure Yes osdevice ramdisk=[C:]\$WINDOWS.~BT\Sources\SafeOS\winre.wim,{79baf055-1a87-11ec-83f8-fcf8ae13c094} custom:21000152 partition=C: systemroot \windows nx OptIn bootmenupolicy Standard winpe Yes Windows Boot Loader ------------------- identifier {d1db91ed-1a87-11ec-83fa-99fc2db626b5} device ramdisk=[\Device\HarddiskVolume4]\Recovery\WindowsRE\Winre.wim,{d1db91ee-1a87-11ec-83fa-99fc2db626b5} path \windows\system32\winload.exe description Windows Recovery Environment locale en-US inherit {bootloadersettings} displaymessage Recovery osdevice ramdisk=[\Device\HarddiskVolume4]\Recovery\WindowsRE\Winre.wim,{d1db91ee-1a87-11ec-83fa-99fc2db626b5} systemroot \windows nx OptIn bootmenupolicy Standard winpe Yes Resume from Hibernate --------------------- identifier {4aa41867-6d08-11eb-8354-d1cd98a001ed} device partition=C: path \WINDOWS\system32\winresume.exe description Windows Resume Application locale en-US inherit {resumeloadersettings} recoverysequence {b7d9a1e1-6cf7-11eb-83b4-e165f11dfe15} recoveryenabled Yes allowedinmemorysettings 0x15000075 filedevice partition=C: filepath \hiberfil.sys bootmenupolicy Standard debugoptionenabled No Resume from Hibernate --------------------- identifier {79baf053-1a87-11ec-83f8-fcf8ae13c094} device partition=C: path \WINDOWS\system32\winresume.exe description Windows Resume Application locale en-US inherit {resumeloadersettings} recoverysequence {d1db91ed-1a87-11ec-83fa-99fc2db626b5} recoveryenabled Yes allowedinmemorysettings 0x15000075 filedevice partition=C: filepath \hiberfil.sys bootmenupolicy Standard debugoptionenabled No Windows Memory Tester --------------------- identifier {memdiag} device partition=K: path \boot\memtest.exe 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 {79baf055-1a87-11ec-83f8-fcf8ae13c094} description Windows Setup ramdisksdidevice partition=C: ramdisksdipath \$WINDOWS.~BT\Sources\SafeOS\boot.sdi Device options -------------- identifier {b7d9a1e2-6cf7-11eb-83b4-e165f11dfe15} description Windows Recovery ramdisksdidevice partition=\Device\HarddiskVolume4 ramdisksdipath \Recovery\WindowsRE\boot.sdi Device options -------------- identifier {d1db91ee-1a87-11ec-83fa-99fc2db626b5} description Windows Recovery ramdisksdidevice partition=\Device\HarddiskVolume4 ramdisksdipath \Recovery\WindowsRE\boot.sdi
The above results appeared without a result on the desktop.
Last edited by zbook; 20 Sep 2021 at 23:19.
Quote
