Bsod after reinstalling windows 11 pro.

greysmouth · 05 Feb 2024

###########################################################
# 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="GREYSMOUTH-PC" get AutomaticManagedPagefile
wmic Computersystem where name="GREYSMOUTH-PC" set AutomaticManagedPagefile=True
wmic Computersystem where name="GREYSMOUTH-PC" 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.22621.2792

Image Version: 10.0.22631.3085

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

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

Stage 1: Examining basic file system structure ...
1112064 file records processed.
File verification completed.
Phase duration (File record verification): 6.80 seconds.
28689 large file records processed.
Phase duration (Orphan file record recovery): 12.08 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 0.65 milliseconds.

Stage 2: Examining file name linkage ...
244 reparse records processed.
1513390 index entries processed.
Index verification completed.
Phase duration (Index verification): 16.96 seconds.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 2.30 seconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 0.98 milliseconds.
244 reparse records processed.
Phase duration (Reparse point and Object ID verification): 3.34 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 136.01 milliseconds.
200664 data files processed.
Phase duration (Data attribute verification): 1.22 milliseconds.
CHKDSK is verifying Usn Journal...
35050232 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 88.77 milliseconds.

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

972285199 KB total disk space.
260623300 KB in 767319 files.
541836 KB in 200665 indexes.
0 KB in bad sectors.
1259511 KB in use by the system.
65536 KB occupied by the log file.
709860552 KB available on disk.

4096 bytes in each allocation unit.
243071299 total allocation units on disk.
177465138 allocation units available on disk.
Total duration: 26.32 seconds (26326 ms).

C:\WINDOWS\System32>wmic recoveros get autoreboot
AutoReboot
FALSE

C:\WINDOWS\System32>wmic recoveros set autoreboot = false
Updating property(s) of '\\GREYSMOUTH-PC\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 11 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 '\\GREYSMOUTH-PC\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 11 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=170
Description=C:\pagefile.sys
InstallDate=20240204131314.755665+060
Name=C:\pagefile.sys
PeakUsage=177
Status=
TempPageFile=FALSE

C:\WINDOWS\System32>wmic Computersystem where name="GREYSMOUTH-PC" get AutomaticManagedPagefile
AutomaticManagedPagefile
TRUE

C:\WINDOWS\System32>wmic Computersystem where name="GREYSMOUTH-PC" set AutomaticManagedPagefile=True
Updating property(s) of '\\GREYSMOUTH-PC\ROOT\CIMV2:Win32_ComputerSystem.Name="GREYSMOUTH-PC"'
Property(s) update successful.

C:\WINDOWS\System32>wmic Computersystem where name="GREYSMOUTH-PC" get AutomaticManagedPagefile
AutomaticManagedPagefile
TRUE

C:\WINDOWS\System32>bcdedit /enum {badmemory}

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

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 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="GREYSMOUTH-PC" get AutomaticManagedPagefile
wmic Computersystem where name="GREYSMOUTH-PC" set AutomaticManagedPagefile=True
wmic Computersystem where name="GREYSMOUTH-PC" 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.22621.2792

Image Version: 10.0.22631.3085

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

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

Stage 1: Examining basic file system structure ...
1112064 file records processed.
File verification completed.
Phase duration (File record verification): 6.80 seconds.
28689 large file records processed.
Phase duration (Orphan file record recovery): 12.08 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 0.65 milliseconds.

Stage 2: Examining file name linkage ...
244 reparse records processed.
1513390 index entries processed.
Index verification completed.
Phase duration (Index verification): 16.96 seconds.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 2.30 seconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 0.98 milliseconds.
244 reparse records processed.
Phase duration (Reparse point and Object ID verification): 3.34 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 136.01 milliseconds.
200664 data files processed.
Phase duration (Data attribute verification): 1.22 milliseconds.
CHKDSK is verifying Usn Journal...
35050232 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 88.77 milliseconds.

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

972285199 KB total disk space.
260623300 KB in 767319 files.
541836 KB in 200665 indexes.
0 KB in bad sectors.
1259511 KB in use by the system.
65536 KB occupied by the log file.
709860552 KB available on disk.

4096 bytes in each allocation unit.
243071299 total allocation units on disk.
177465138 allocation units available on disk.
Total duration: 26.32 seconds (26326 ms).

C:\WINDOWS\System32>wmic recoveros get autoreboot
AutoReboot
FALSE

C:\WINDOWS\System32>wmic recoveros set autoreboot = false
Updating property(s) of '\\GREYSMOUTH-PC\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 11 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 '\\GREYSMOUTH-PC\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 11 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=170
Description=C:\pagefile.sys
InstallDate=20240204131314.755665+060
Name=C:\pagefile.sys
PeakUsage=177
Status=
TempPageFile=FALSE

C:\WINDOWS\System32>wmic Computersystem where name="GREYSMOUTH-PC" get AutomaticManagedPagefile
AutomaticManagedPagefile
TRUE

C:\WINDOWS\System32>wmic Computersystem where name="GREYSMOUTH-PC" set AutomaticManagedPagefile=True
Updating property(s) of '\\GREYSMOUTH-PC\ROOT\CIMV2:Win32_ComputerSystem.Name="GREYSMOUTH-PC"'
Property(s) update successful.

C:\WINDOWS\System32>wmic Computersystem where name="GREYSMOUTH-PC" get AutomaticManagedPagefile
AutomaticManagedPagefile
TRUE

C:\WINDOWS\System32>bcdedit /enum {badmemory}

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

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 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="GREYSMOUTH-PC" get AutomaticManagedPagefile
wmic Computersystem where name="GREYSMOUTH-PC" set AutomaticManagedPagefile=True
wmic Computersystem where name="GREYSMOUTH-PC" 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.22621.2792

Image Version: 10.0.22631.3085

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

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

Stage 1: Examining basic file system structure ...
1112064 file records processed.
File verification completed.
Phase duration (File record verification): 6.80 seconds.
28689 large file records processed.
Phase duration (Orphan file record recovery): 12.08 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 0.65 milliseconds.

Stage 2: Examining file name linkage ...
244 reparse records processed.
1513390 index entries processed.
Index verification completed.
Phase duration (Index verification): 16.96 seconds.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 2.30 seconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 0.98 milliseconds.
244 reparse records processed.
Phase duration (Reparse point and Object ID verification): 3.34 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 136.01 milliseconds.
200664 data files processed.
Phase duration (Data attribute verification): 1.22 milliseconds.
CHKDSK is verifying Usn Journal...
35050232 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 88.77 milliseconds.

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

972285199 KB total disk space.
260623300 KB in 767319 files.
541836 KB in 200665 indexes.
0 KB in bad sectors.
1259511 KB in use by the system.
65536 KB occupied by the log file.
709860552 KB available on disk.

4096 bytes in each allocation unit.
243071299 total allocation units on disk.
177465138 allocation units available on disk.
Total duration: 26.32 seconds (26326 ms).

C:\WINDOWS\System32>wmic recoveros get autoreboot
AutoReboot
FALSE

C:\WINDOWS\System32>wmic recoveros set autoreboot = false
Updating property(s) of '\\GREYSMOUTH-PC\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 11 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 '\\GREYSMOUTH-PC\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 11 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=170
Description=C:\pagefile.sys
InstallDate=20240204131314.755665+060
Name=C:\pagefile.sys
PeakUsage=177
Status=
TempPageFile=FALSE

C:\WINDOWS\System32>wmic Computersystem where name="GREYSMOUTH-PC" get AutomaticManagedPagefile
AutomaticManagedPagefile
TRUE

C:\WINDOWS\System32>wmic Computersystem where name="GREYSMOUTH-PC" set AutomaticManagedPagefile=True
Updating property(s) of '\\GREYSMOUTH-PC\ROOT\CIMV2:Win32_ComputerSystem.Name="GREYSMOUTH-PC"'
Property(s) update successful.

C:\WINDOWS\System32>wmic Computersystem where name="GREYSMOUTH-PC" get AutomaticManagedPagefile
AutomaticManagedPagefile
TRUE

C:\WINDOWS\System32>bcdedit /enum {badmemory}

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

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

OS Name Microsoft Windows 11 Pro
OS Name Microsoft Windows 11 Pro
Version 10.0.22631 Build 22631
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name GREYSMOUTH-PC
System Manufacturer HP
System Model OMEN by HP Laptop 17-ck1xxx
System Type x64-based PC
System SKU 6R404EA#ABZ
Processor 12th Gen Intel(R) Core(TM) i7-12700H, 2300 Mhz, 14 Core(s), 20 Logical Processor(s)
BIOS Version/Date AMI F.17, 11/15/2023
SMBIOS Version 3.4
Embedded Controller Version 32.25
BIOS Mode UEFI
BaseBoard Manufacturer HP
BaseBoard Product 8A17
BaseBoard Version 32.25
Platform Role Mobile
Secure Boot State On
PCR7 Configuration Elevation Required to View
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "10.0.22621.2506"
User Name GREYSMOUTH-PC\greys
Time Zone W. Europe Standard Time
Installed Physical Memory (RAM) 16.0 GB
Total Physical Memory 15.7 GB
Available Physical Memory 6.78 GB
Total Virtual Memory 18.0 GB
Available Virtual Memory 4.46 GB
Page File Space 2.38 GB
Page File C:\pagefile.sys
Kernel DMA Protection On
Virtualization-based security Running
Virtualization-based security Required Security Properties
Virtualization-based security Available Security Properties Base Virtualization Support, Secure Boot, DMA Protection, UEFI Code Readonly, SMM Security Mitigations 1.0, Mode Based Execution Control, APIC Virtualization
Virtualization-based security Services Configured Hypervisor enforced Code Integrity
Virtualization-based security Services Running Hypervisor enforced Code Integrity
Windows Defender Application Control policy Enforced
Windows Defender Application Control user mode policy Audit
Device Encryption Support Elevation Required to View
A hypervisor has been detected. Features required for Hyper-V will not be displayed.

FreeBooter · 05 Feb 2024

SetupDiag is a free diagnostic tool by Microsoft that is designed to find and parse Windows 10 setup log files to determine why an upgrade or update failed to install on a computer system.

SetupDiag works only on devices running Windows 10. The second requirement is that it depends on the Microsoft .NET Framework 4.6 which needs to be installed on the device it is run on.

If you run SetupDiag without parameters, it attempts to locate log files that Windows 10 creates during the upgrade process in the default folders on the device.

The program creates a results.log file in its directory when it completes the scan which includes upgrade issues that it detected in the log files during parsing.

SetupDiag creates a zip archive of all log files that it processed on top of that which it saves as Logs.zip in the same directory as well.

A rollback occurred due to a driver configuration issue.

Check supplemental rollback logs for a setupmem.dmp file, or event logs for any unexpected reboots or errors.
Review the rollback log and determine the stop code.
The rollback log is located in the $Windows.~BT\Sources\Rollback folder. An example analysis is shown below. This example isn't representative of all cases:

Info SP Crash 0x0000007E detected
Info SP Module name :
Info SP Bugcheck parameter 1: 0xFFFFFFFFC0000005
Info SP Bugcheck parameter 2: 0xFFFFF8015BC0036A
Info SP Bugcheck parameter 3: 0xFFFFD000E5D23728
Info SP Bugcheck parameter 4: 0xFFFFD000E5D22F40
Info SP Can't recover the system.
Info SP Rollback: Showing splash window with restoring text: Restoring your previous version of Windows.

Typically, there's a dump file for the crash to analyze. If you aren't equipped to debug the dump, then attempt the following basic troubleshooting procedures:

1. Make sure you have enough disk space.
2. If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.
3. Try changing video adapters.
4. Check with your hardware vendor for any BIOS updates.
5. Disable BIOS memory options such as caching or shadowing.

https://learn.microsoft.com/en-us/wi...upgrade-errors

zbook · 05 Feb 2024

When posting results please use: one drive, drop box, or google drive

Share OneDrive files and folders - Microsoft Support
How to use Google Drive - Computer - Google Drive Help

dalchina · 05 Feb 2024

Please be aware that this is tenforums - for... yes.. Win 10.

For Win 11, please register on elevenforum.com for the most appropriate volunteer support. Thanks.