Fixing an Unbootable Windows 11 OS


Disk 0: Windows 11 Pro 10.0.22631 installed 02/15/25


Please perform the following steps:


1) The BIOS Version/Date American Megatrends Inc. 2204, 2/08/2024

Upgrade the BIOS: 2204 > 2704




2) Move the paging file from D: > C:

Reboot



3) Free up space on C: so that there is > 30 GB free space



4) Turn off Windows fast startup




5) Run Tuneup plus > post a share link






6) Create a new restore point




7) Run diskparinfo > post a share link





8) Boot to advanced startup > type:

bootsect /nt60 all

post a share link








Code:
Event[1494]
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2025-02-22T10:19:13.2110000Z
  Event ID: 41
  Task: N/A
  Level: Critical
  Opcode: Info  a
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-1CRFSEL
  Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Code:
Event[1480]
  Log Name: System
  Source: EventLog
  Date: 2025-02-22T10:19:22.6400000Z
  Event ID: 6008
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: DESKTOP-1CRFSEL
  Description:
The previous system shutdown at 9:38:26 AM on ?2/?21/?2025 was unexpected.



Code:
------------------------
Disk & DVD/CD-ROM Drives
------------------------
      Drive: C:
 Free Space: 5.0 GB
Total Space: 61.4 GB
File System: NTFS
      Model: Samsung SSD 990 PRO 2TB

      Drive: D:
 Free Space: 311.5 GB
Total Space: 1845.5 GB
File System: NTFS
      Model: Samsung SSD 990 PRO 2TB
Thanks zbook,

Ok so I've updated the BIOS to the latest version.

Moved the paging file from D: to C: and rebooted

I adjusted the partitions to give C:\ 40Gb more space
Just a side note here, when looking at Disk Management, it lists the C:\ partition has having a "boot" property, whilst the problem D:\ partition is just listed as a "Basic Data Partition". Is this significant or just normal?
Disk Management.webp

I turned off windows fast startup by modifying the registry of the offline windows....... I'm pretty sure

I ran Tuneup plus, though does this run the commands on the online windows and not the offline problematic windows? I have run the sfc /scannow, DISM /restorehealth and chkdsk /f commands on the problem offline windows, I've got all to run successfully, except for one file that sfc /scannow cannot fix.
The tuneup log is attached to this post.

I created a restore point for both win11 partitions.

I ran diskparinfo and attached the log.

I ran bootsect /nt60 all in CMD from a windows installation USB. The results are in a .txt file attached to the post.

I'm not sure what to do with the last three "code" quotes on your post.
 

Attachments

My Computer

System One

  • OS
    Windows 11
    Computer type
    PC/Desktop
    CPU
    AMD Ryzen 7 7800X3D
    Motherboard
    ASUS X670E-E
    Memory
    Trident Z5 Neo RGB, DDR5-6000 CL30-38-38-96, 2x16GB
    Graphics Card(s)
    EVGA RTX 3060 XC
    Monitor(s) Displays
    Samsung 34" Odyssey OLED G8 & Dell U2518D
    Screen Resolution
    3440 x 1440 & 2560 x 1440
    Hard Drives
    Samsung 990 Pro 2TB & Samsung 850 Evo 1TB
    PSU
    Corsir RM1000x
    Case
    Fractal North
    Cooling
    EK-Nucleus AIO Lux CR240 D-RGB
    Internet Speed
    250Mbps/25Mbps
On the working Windows partition please run the V2 log collector > post a share link



On the problematic Windows partition please boot to window RE

Type:

bcdedit | find "osdevice"
bootsect /nt60 all

post a share link



type: notepad
type: notepad
type: notepad
(this will open three notepad windows)

click file open

search for these files > if found > save to the windows iso flash drive > move the flash drive to a working computer > post results into this thread using share links


Code:
C:\windows\minidump
C:\windows\memory.dmp
C:\windows\livekernelreports
C:\windows\logs\CBS\CBS.log
C:\windows\logs\CBS\CbsPersist
C:\windows\system32\logfiles\srt\srttrail.txt

or

Code:
%systemroot%\minidump
%systemroot%\memory.dmp
%systemroot%\livekernelreports
%windir%\logs\cbs\cbs.log
%windir%\logs\CBS\CbsPersist
%windir%\System32\LogFiles\Srt\SrtTrail.txt
Hey sorry I just realised what you were asking at the end of this post.

I searched the folders you listed but I didn't find anything from this year in windows\minidump, windows\livekernalreports and I didn't have a memory.dmp file.
Although in the logfiles\srt folder, the files bcdinfo.txt, bootfailure.txt and disklayout.txt were last modified the morning after the initial failure. DISMRepairLogFile.txt, SrtTrail.log and SrtTrail.txt were last modified a few days after. You can find them all with the link below:

The CBS log is also in there.

I had a read of the logs, but I didn't really know what to look for. I hope that they are a useful insight into what happened!
 

My Computer

System One

  • OS
    Windows 11
    Computer type
    PC/Desktop
    CPU
    AMD Ryzen 7 7800X3D
    Motherboard
    ASUS X670E-E
    Memory
    Trident Z5 Neo RGB, DDR5-6000 CL30-38-38-96, 2x16GB
    Graphics Card(s)
    EVGA RTX 3060 XC
    Monitor(s) Displays
    Samsung 34" Odyssey OLED G8 & Dell U2518D
    Screen Resolution
    3440 x 1440 & 2560 x 1440
    Hard Drives
    Samsung 990 Pro 2TB & Samsung 850 Evo 1TB
    PSU
    Corsir RM1000x
    Case
    Fractal North
    Cooling
    EK-Nucleus AIO Lux CR240 D-RGB
    Internet Speed
    250Mbps/25Mbps
Disk 0 has Windows 11 on partition #4 C:.

The Windows recovery files are enabled on C:.

For the dual boot (windows 10) try Macrium boot repair or backup files as needed.

This link may be useful:






Code:
    Disk 0 : SSD. It has 5 partition(s). Model: Samsung SSD 990 PRO 2TB
    Disk 1 : USB. It has 1 partition(s). Model: Lexar USB Flash Drive

    The script has found the above 2 storage device(s) in total.
=======================================================================

Microsoft DiskPart version 10.0.22621.1

Copyright (C) Microsoft Corporation.
On computer: DESKTOP-1CRFSEL

  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online         1863 GB  1024 KB        *
  Disk 1    Online           14 GB      0 B         

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     D   Samsung 990  NTFS   Partition   1762 GB  Healthy           
  Volume 1     C                NTFS   Partition    100 GB  Healthy    Boot   
  Volume 2                      FAT32  Partition    100 MB  Healthy    System 
  Volume 3                      NTFS   Partition    707 MB  Healthy    Hidden 
  Volume 4     E   HBCD_PE_x64  NTFS   Removable     14 GB  Healthy           

Disk 0 is now the selected disk.

Samsung SSD 990 PRO 2TB
Disk ID: {24A4A67B-EBDE-4A1E-810E-632584F371F2}
Type   : NVMe
Status : Online
Path   : 0
Target : 0
LUN ID : 0
Location Path : PCIROOT(0)#PCI(0102)#PCI(0000)#NVME(P00T00L00)
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 0     D   Samsung 990  NTFS   Partition   1762 GB  Healthy           
  Volume 1     C                NTFS   Partition    100 GB  Healthy    Boot   
  Volume 2                      FAT32  Partition    100 MB  Healthy    System 
  Volume 3                      NTFS   Partition    707 MB  Healthy    Hidden 

  Partition ###  Type              Size     Offset
  -------------  ----------------  -------  -------
  Partition 1    System             100 MB  1024 KB
  Partition 2    Reserved            16 MB   101 MB
  Partition 3    Primary           1762 GB   117 MB
  Partition 4    Primary            100 GB  1762 GB
  Partition 5    Recovery           707 MB  1862 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 2                      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 0     D   Samsung 990  NTFS   Partition   1762 GB  Healthy           

Partition 4 is now the selected partition.

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

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

Partition 5 is now the selected partition.

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

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

Disk 1 is now the selected disk.

Lexar USB Flash Drive USB Device
Disk ID: 0314E5E2
Type   : USB
Status : Online
Path   : 0
Target : 0
LUN ID : 0
Location Path : UNAVAILABLE
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     E   HBCD_PE_x64  NTFS   Removable     14 GB  Healthy           

  Partition ###  Type              Size     Offset
  -------------  ----------------  -------  -------
  Partition 1    Primary             14 GB  1024 KB

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 4     E   HBCD_PE_x64  NTFS   Removable     14 GB  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: 1fd751d3-eb22-11ef-ba3a-dfc0a5dbe091
    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}
                        {2ab213ee-e80c-11ef-8058-806e6f6e6963}
timeout                 1

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            {1fd751d1-eb22-11ef-ba3a-dfc0a5dbe091}
displayorder            {current}
                        {e8c81375-e809-11ef-b30c-ae93269f02db}
toolsdisplayorder       {memdiag}
timeout                 30

Firmware Application (101fffff)
-------------------------------
identifier              {2ab213ee-e80c-11ef-8058-806e6f6e6963}
device                  partition=E:
description             UEFI: Lexar USB Flash Drive 1100, Partition 1

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \Windows\system32\winload.efi
description             Windows 11
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {1fd751d3-eb22-11ef-ba3a-dfc0a5dbe091}
displaymessageoverride  Recovery
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \Windows
resumeobject            {1fd751d1-eb22-11ef-ba3a-dfc0a5dbe091}
nx                      OptIn
bootmenupolicy          Standard

Windows Boot Loader
-------------------
identifier              {1fd751d3-eb22-11ef-ba3a-dfc0a5dbe091}
device                  ramdisk=[C:]\Recovery\WindowsRE\Winre.wim,{1fd751d4-eb22-11ef-ba3a-dfc0a5dbe091}
path                    \windows\system32\winload.efi
description             Windows Recovery Environment
locale                  en-us
inherit                 {bootloadersettings}
displaymessage          Recovery
osdevice                ramdisk=[C:]\Recovery\WindowsRE\Winre.wim,{1fd751d4-eb22-11ef-ba3a-dfc0a5dbe091}
systemroot              \windows
nx                      OptIn
bootmenupolicy          Standard
winpe                   Yes

Windows Boot Loader
-------------------
identifier              {e8c81375-e809-11ef-b30c-ae93269f02db}
device                  partition=D:
path                    \windows\system32\winload.efi
description             Windows 11
locale                  en-us
inherit                 {bootloadersettings}
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=D:
systemroot              \windows
resumeobject            {e8c81374-e809-11ef-b30c-ae93269f02db}
nx                      OptIn
bootmenupolicy          Standard

Resume from Hibernate
---------------------
identifier              {1fd751d1-eb22-11ef-ba3a-dfc0a5dbe091}
device                  partition=C:
path                    \Windows\system32\winresume.efi
description             Windows Resume Application
locale                  en-US
inherit                 {resumeloadersettings}
recoverysequence        {1fd751d3-eb22-11ef-ba3a-dfc0a5dbe091}
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
filedevice              partition=C:
custom:21000026         partition=C:
filepath                \hiberfil.sys
bootmenupolicy          Standard
debugoptionenabled      No

Resume from Hibernate
---------------------
identifier              {e8c81374-e809-11ef-b30c-ae93269f02db}
device                  partition=D:
path                    \windows\system32\winresume.efi
description             Windows Resume Application
locale                  en-us
inherit                 {resumeloadersettings}
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
filedevice              partition=D:
custom:21000026         partition=D:
filepath                \hiberfil.sys
bootmenupolicy          Standard
debugoptionenabled      No
 

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
Disk 0 has Windows 11 on partition #4 C:.

The Windows recovery files are enabled on C:.

For the dual boot (windows 10) try Macrium boot repair or backup files as needed.

This link may be useful:






Code:
    Disk 0 : SSD. It has 5 partition(s). Model: Samsung SSD 990 PRO 2TB
    Disk 1 : USB. It has 1 partition(s). Model: Lexar USB Flash Drive

    The script has found the above 2 storage device(s) in total.
=======================================================================

Microsoft DiskPart version 10.0.22621.1

Copyright (C) Microsoft Corporation.
On computer: DESKTOP-1CRFSEL

  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online         1863 GB  1024 KB        *
  Disk 1    Online           14 GB      0 B        

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     D   Samsung 990  NTFS   Partition   1762 GB  Healthy          
  Volume 1     C                NTFS   Partition    100 GB  Healthy    Boot  
  Volume 2                      FAT32  Partition    100 MB  Healthy    System
  Volume 3                      NTFS   Partition    707 MB  Healthy    Hidden
  Volume 4     E   HBCD_PE_x64  NTFS   Removable     14 GB  Healthy          

Disk 0 is now the selected disk.

Samsung SSD 990 PRO 2TB
Disk ID: {24A4A67B-EBDE-4A1E-810E-632584F371F2}
Type   : NVMe
Status : Online
Path   : 0
Target : 0
LUN ID : 0
Location Path : PCIROOT(0)#PCI(0102)#PCI(0000)#NVME(P00T00L00)
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 0     D   Samsung 990  NTFS   Partition   1762 GB  Healthy          
  Volume 1     C                NTFS   Partition    100 GB  Healthy    Boot  
  Volume 2                      FAT32  Partition    100 MB  Healthy    System
  Volume 3                      NTFS   Partition    707 MB  Healthy    Hidden

  Partition ###  Type              Size     Offset
  -------------  ----------------  -------  -------
  Partition 1    System             100 MB  1024 KB
  Partition 2    Reserved            16 MB   101 MB
  Partition 3    Primary           1762 GB   117 MB
  Partition 4    Primary            100 GB  1762 GB
  Partition 5    Recovery           707 MB  1862 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 2                      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 0     D   Samsung 990  NTFS   Partition   1762 GB  Healthy          

Partition 4 is now the selected partition.

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

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

Partition 5 is now the selected partition.

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

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

Disk 1 is now the selected disk.

Lexar USB Flash Drive USB Device
Disk ID: 0314E5E2
Type   : USB
Status : Online
Path   : 0
Target : 0
LUN ID : 0
Location Path : UNAVAILABLE
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     E   HBCD_PE_x64  NTFS   Removable     14 GB  Healthy          

  Partition ###  Type              Size     Offset
  -------------  ----------------  -------  -------
  Partition 1    Primary             14 GB  1024 KB

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 4     E   HBCD_PE_x64  NTFS   Removable     14 GB  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: 1fd751d3-eb22-11ef-ba3a-dfc0a5dbe091
    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}
                        {2ab213ee-e80c-11ef-8058-806e6f6e6963}
timeout                 1

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            {1fd751d1-eb22-11ef-ba3a-dfc0a5dbe091}
displayorder            {current}
                        {e8c81375-e809-11ef-b30c-ae93269f02db}
toolsdisplayorder       {memdiag}
timeout                 30

Firmware Application (101fffff)
-------------------------------
identifier              {2ab213ee-e80c-11ef-8058-806e6f6e6963}
device                  partition=E:
description             UEFI: Lexar USB Flash Drive 1100, Partition 1

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \Windows\system32\winload.efi
description             Windows 11
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {1fd751d3-eb22-11ef-ba3a-dfc0a5dbe091}
displaymessageoverride  Recovery
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \Windows
resumeobject            {1fd751d1-eb22-11ef-ba3a-dfc0a5dbe091}
nx                      OptIn
bootmenupolicy          Standard

Windows Boot Loader
-------------------
identifier              {1fd751d3-eb22-11ef-ba3a-dfc0a5dbe091}
device                  ramdisk=[C:]\Recovery\WindowsRE\Winre.wim,{1fd751d4-eb22-11ef-ba3a-dfc0a5dbe091}
path                    \windows\system32\winload.efi
description             Windows Recovery Environment
locale                  en-us
inherit                 {bootloadersettings}
displaymessage          Recovery
osdevice                ramdisk=[C:]\Recovery\WindowsRE\Winre.wim,{1fd751d4-eb22-11ef-ba3a-dfc0a5dbe091}
systemroot              \windows
nx                      OptIn
bootmenupolicy          Standard
winpe                   Yes

Windows Boot Loader
-------------------
identifier              {e8c81375-e809-11ef-b30c-ae93269f02db}
device                  partition=D:
path                    \windows\system32\winload.efi
description             Windows 11
locale                  en-us
inherit                 {bootloadersettings}
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=D:
systemroot              \windows
resumeobject            {e8c81374-e809-11ef-b30c-ae93269f02db}
nx                      OptIn
bootmenupolicy          Standard

Resume from Hibernate
---------------------
identifier              {1fd751d1-eb22-11ef-ba3a-dfc0a5dbe091}
device                  partition=C:
path                    \Windows\system32\winresume.efi
description             Windows Resume Application
locale                  en-US
inherit                 {resumeloadersettings}
recoverysequence        {1fd751d3-eb22-11ef-ba3a-dfc0a5dbe091}
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
filedevice              partition=C:
custom:21000026         partition=C:
filepath                \hiberfil.sys
bootmenupolicy          Standard
debugoptionenabled      No

Resume from Hibernate
---------------------
identifier              {e8c81374-e809-11ef-b30c-ae93269f02db}
device                  partition=D:
path                    \windows\system32\winresume.efi
description             Windows Resume Application
locale                  en-us
inherit                 {resumeloadersettings}
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
filedevice              partition=D:
custom:21000026         partition=D:
filepath                \hiberfil.sys
bootmenupolicy          Standard
debugoptionenabled      No

Hey I'm still working on the above, but I was manually able to get windows to generate a minidump at the point where it hangs.

I'm still learning how to read it, but I thought I'd upload it here in case it offers you any insight into the cause.
 

Attachments

My Computer

System One

  • OS
    Windows 11
    Computer type
    PC/Desktop
    CPU
    AMD Ryzen 7 7800X3D
    Motherboard
    ASUS X670E-E
    Memory
    Trident Z5 Neo RGB, DDR5-6000 CL30-38-38-96, 2x16GB
    Graphics Card(s)
    EVGA RTX 3060 XC
    Monitor(s) Displays
    Samsung 34" Odyssey OLED G8 & Dell U2518D
    Screen Resolution
    3440 x 1440 & 2560 x 1440
    Hard Drives
    Samsung 990 Pro 2TB & Samsung 850 Evo 1TB
    PSU
    Corsir RM1000x
    Case
    Fractal North
    Cooling
    EK-Nucleus AIO Lux CR240 D-RGB
    Internet Speed
    250Mbps/25Mbps
Hey I'm still working on the above, but I was manually able to get windows to generate a minidump at the point where it hangs.

I'm still learning how to read it, but I thought I'd upload it here in case it offers you any insight into the cause.

What were each of the steps made for the manual crash?
 

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
What were each of the steps made for the manual crash?
I followed these instructions to force a system crash from the keyboard. Essentially, I added a REG DWORD entry named "CrashOnCtrlScroll" with a value of 1, in the following path of the problem windows partition: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\kbdhid\Parameters

I booted the problem partition, waited for it to hang for a couple of minutes at the same point it always does, then pressed Ctrl + Scroll Lock (twice) and it crashed.
 

My Computer

System One

  • OS
    Windows 11
    Computer type
    PC/Desktop
    CPU
    AMD Ryzen 7 7800X3D
    Motherboard
    ASUS X670E-E
    Memory
    Trident Z5 Neo RGB, DDR5-6000 CL30-38-38-96, 2x16GB
    Graphics Card(s)
    EVGA RTX 3060 XC
    Monitor(s) Displays
    Samsung 34" Odyssey OLED G8 & Dell U2518D
    Screen Resolution
    3440 x 1440 & 2560 x 1440
    Hard Drives
    Samsung 990 Pro 2TB & Samsung 850 Evo 1TB
    PSU
    Corsir RM1000x
    Case
    Fractal North
    Cooling
    EK-Nucleus AIO Lux CR240 D-RGB
    Internet Speed
    250Mbps/25Mbps
What's the status for each partition boot?

Is Win 11 without problems?

Can you backup files on Win 10 and recreate the dual boot?

Or save Win 11 and reset / custom install win 10?
 

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
What's the status for each partition boot?

Is Win 11 without problems?

Can you backup files on Win 10 and recreate the dual boot?

Or save Win 11 and reset / custom install win 10?
Both the windows 11 and windows 10 disks do not boot, but I have created a temporary win11 partition on the windows 11 disk which does boot. I don't know how, but initially a boot onto the win 10 disk failed, then the win11 disk displayed the same symptoms and also failed to boot.

My priority is to try and save win11, I don't really mind if I can no longer boot onto win10 so long as the files on it are still accessible.
 

My Computer

System One

  • OS
    Windows 11
    Computer type
    PC/Desktop
    CPU
    AMD Ryzen 7 7800X3D
    Motherboard
    ASUS X670E-E
    Memory
    Trident Z5 Neo RGB, DDR5-6000 CL30-38-38-96, 2x16GB
    Graphics Card(s)
    EVGA RTX 3060 XC
    Monitor(s) Displays
    Samsung 34" Odyssey OLED G8 & Dell U2518D
    Screen Resolution
    3440 x 1440 & 2560 x 1440
    Hard Drives
    Samsung 990 Pro 2TB & Samsung 850 Evo 1TB
    PSU
    Corsir RM1000x
    Case
    Fractal North
    Cooling
    EK-Nucleus AIO Lux CR240 D-RGB
    Internet Speed
    250Mbps/25Mbps
What have you been doing to boot Win 11 and run the scripts?
Tuneup plus
Disk partition information
V2
etc.

Please post images or share links for error messages and codes.

Power on an boot each Win 11 and 10.

Can you run startup repairs and post failure srttrail.txt?



Did Macrium fix boot display an error message?


Files can be backed up:
a) Windows RE notepad
b) ubuntu / Linux
c) HD enclosure
d) empty bay
etc.
 

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
What have you been doing to boot Win 11 and run the scripts?
Tuneup plus
Disk partition information
V2
etc.

Please post images or share links for error messages and codes.

Power on an boot each Win 11 and 10.

Can you run startup repairs and post failure srttrail.txt?



Did Macrium fix boot display an error message?


Files can be backed up:
a) Windows RE notepad
b) ubuntu / Linux
c) HD enclosure
d) empty bay
etc.
Hey zbook,

I've only been able to run the scrips on the working, temporary version of win11 that I installed. I commented at the time that I didn't think this would work and the scrips would instead run only on the working win11. Is there a way to direct the scrips to an offline Windows?
I also noticed that the Tuneup Plus script was written to run the sfc /scannow, DISM /restorehealth and chkdsk /f commands. I have already run these through command prompt targeting the problem windows install.

I booted both the problem win11 and problem win10 operating systems and have included images from the boot process below:

Problem win11
1st BIOS Screen
20250226_113040.webp

2nd 'Republic of Gamers Loading Screen'
20250226_113045.webp

3rd Black Screen. It never progresses beyond this point. If booting into safe mode, the 'Republic of Gamers Loading Screen' as shown in the image above will continue to be displayed.
20250226_113132.webp


Problem win10
1st Missed the photo of the BIOS screen but it's just the same.

2nd Windows loading screen
1740544299213.webp

3rd BSOD, the stop code is 0x000021a
1740544373903.webp


I ran startup repairs on the Win11 drive from a bootable USB and it failed to fix the problem, srttrail.txt is attached.


Macrium fix boot completed its repairs but did not fix the problem. It did not display any error messages.


Regarding the win10 install, I've had its drive unplugged for most of the troubleshooting process as I was focusing on the win11 drive, but after plugging it back in I was able to get some more information from it from the time of the initial crash.
I only just learnt how to access the event log of an offline Windows, and it had quite a bit of info on the two boots which I think caused all my computers problems. I've attached an event log containing the relevant logs to this post. It looks like it had a hell of a time, there were quite a few NTFS errors among others.
I'm still not sure how this would affect my win11 drive though.
 

Attachments

My Computer

System One

  • OS
    Windows 11
    Computer type
    PC/Desktop
    CPU
    AMD Ryzen 7 7800X3D
    Motherboard
    ASUS X670E-E
    Memory
    Trident Z5 Neo RGB, DDR5-6000 CL30-38-38-96, 2x16GB
    Graphics Card(s)
    EVGA RTX 3060 XC
    Monitor(s) Displays
    Samsung 34" Odyssey OLED G8 & Dell U2518D
    Screen Resolution
    3440 x 1440 & 2560 x 1440
    Hard Drives
    Samsung 990 Pro 2TB & Samsung 850 Evo 1TB
    PSU
    Corsir RM1000x
    Case
    Fractal North
    Cooling
    EK-Nucleus AIO Lux CR240 D-RGB
    Internet Speed
    250Mbps/25Mbps
Unspecified changes to system configuration might have caused the problem.

Boot manager generic failure 0xc0000225



In this video, you will learn how to scan and repair Windows operating system files by using the System File Checker (SFC.exe) tool, if Windows cannot start.
To troubleshoot Windows 10 or Windows 11 boot problem, just follow the instructions in this guide, and hopefully you will fix the not booting problem in no time.
 

My Computer

System One

  • OS
    Windows 11
    Computer type
    PC/Desktop
    Manufacturer/Model
    HP Pavilion
    CPU
    AMD Ryzen 7 5700G
    Motherboard
    Erica6
    Memory
    Micron Technology DDR4-3200 16GB
    Graphics Card(s)
    NVIDIA GeForce RTX 3060
    Sound Card
    Realtek ALC671
    Monitor(s) Displays
    Samsung SyncMaster U28E590
    Screen Resolution
    3840 x 2160
    Hard Drives
    SAMSUNG MZVLQ1T0HALB-000H1
Scannow can fix OS corruption.
Restorehealth can fix component store corruption.
Chkdsk can fix drive file system corruption.
No quick command available to fix registry corruption.

Regback used to be an option.




The event viewer was dated 02/03 and 02/04.
There were drive file system problems C: and F:



Code:
The file system structure on volume C: cannot be corrected.
Please run the chkdsk utility on the volume C:.


Code:
25008: Start repair on 02/04/2025 at 10:10:14:206 25013: Processing repair verb BadFrs: 0x6c000000001f0d Flags: 0x32, 0x2100 25010: Marked file record 6c000000001f0d as in use in MFT bitmap. 25012: Marked 4c clusters in attribute of type code 0x80 and instance tag 0x3 as in use by file 0x0 in the volume bitmap. 27295: The parent 0x459000000000b4d of file name attribute IMG_5030.JPG in file 0x6c000000001f0d cannot be found. 27293: File record 0x6c000000001f0d maps to "\ProgramData\Microsoft\Windows\WER\Temp\WERC448.tmp". 25009: End repair on 02/04/2025 at 10:10:14:206


Code:
25008: Start repair on 02/04/2025 at 10:06:45:075 25013: Processing repair verb BadFrs: 0xfd0000000018bb Flags: 0x32, 0x2100 25010: Marked file record fd0000000018bb as in use in MFT bitmap. 25012: Marked 656 clusters in attribute of type code 0x80 and instance tag 0x3 as in use by file 0x0 in the volume bitmap. 27295: The parent 0x459000000000b4d of file name attribute IMG_4981.JPG in file 0xfd0000000018bb cannot be found. 27293: File record 0xfd0000000018bb maps to "\Windows\System32\config\systemprofile\AppData\Local\CrashDumps\gamingservices.exe.5760.dmp". 25009: End repair on 02/04/2025 at 10:06:45:075



Code:
A corruption was discovered in the file system structure on volume F:.
The exact nature of the corruption is unknown.  The file system structures need to be scanned online.



Code:
A corruption was discovered in the file system structure on volume Samsung 850 Evo 1TB.
The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x2000000014293.  The name of the file is "<unable to determine file name>".



Code:
A corruption was found in a file system index structure. The file reference number is 0x2d700000000a532. The name of the file is "\Program Files\WindowsApps\Microsoft.LanguageExperiencePacken-GB_22621.84.366.0_neutral__8wekyb3d8bbwe". The corrupted index attribute is ":$I30:$INDEX_ALLOCATION".



Root cause found:
---------------------------
Unspecified changes to system configuration might have caused the problem.
 

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
In this video, you will learn how to scan and repair Windows operating system files by using the System File Checker (SFC.exe) tool, if Windows cannot start.
To troubleshoot Windows 10 or Windows 11 boot problem, just follow the instructions in this guide, and hopefully you will fix the not booting problem in no time.
Hi FreeBooter thanks for getting back to me, unfortunately I have tried both those methods without success.

Scannow can fix OS corruption.
Restorehealth can fix component store corruption.
Chkdsk can fix drive file system corruption.
No quick command available to fix registry corruption.

Regback used to be an option.




The event viewer was dated 02/03 and 02/04.
There were drive file system problems C: and F:



Code:
The file system structure on volume C: cannot be corrected.
Please run the chkdsk utility on the volume C:.


Code:
25008: Start repair on 02/04/2025 at 10:10:14:206 25013: Processing repair verb BadFrs: 0x6c000000001f0d Flags: 0x32, 0x2100 25010: Marked file record 6c000000001f0d as in use in MFT bitmap. 25012: Marked 4c clusters in attribute of type code 0x80 and instance tag 0x3 as in use by file 0x0 in the volume bitmap. 27295: The parent 0x459000000000b4d of file name attribute IMG_5030.JPG in file 0x6c000000001f0d cannot be found. 27293: File record 0x6c000000001f0d maps to "\ProgramData\Microsoft\Windows\WER\Temp\WERC448.tmp". 25009: End repair on 02/04/2025 at 10:10:14:206


Code:
25008: Start repair on 02/04/2025 at 10:06:45:075 25013: Processing repair verb BadFrs: 0xfd0000000018bb Flags: 0x32, 0x2100 25010: Marked file record fd0000000018bb as in use in MFT bitmap. 25012: Marked 656 clusters in attribute of type code 0x80 and instance tag 0x3 as in use by file 0x0 in the volume bitmap. 27295: The parent 0x459000000000b4d of file name attribute IMG_4981.JPG in file 0xfd0000000018bb cannot be found. 27293: File record 0xfd0000000018bb maps to "\Windows\System32\config\systemprofile\AppData\Local\CrashDumps\gamingservices.exe.5760.dmp". 25009: End repair on 02/04/2025 at 10:06:45:075



Code:
A corruption was discovered in the file system structure on volume F:.
The exact nature of the corruption is unknown.  The file system structures need to be scanned online.



Code:
A corruption was discovered in the file system structure on volume Samsung 850 Evo 1TB.
The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x2000000014293.  The name of the file is "<unable to determine file name>".



Code:
A corruption was found in a file system index structure. The file reference number is 0x2d700000000a532. The name of the file is "\Program Files\WindowsApps\Microsoft.LanguageExperiencePacken-GB_22621.84.366.0_neutral__8wekyb3d8bbwe". The corrupted index attribute is ":$I30:$INDEX_ALLOCATION".



Root cause found:
---------------------------
Unspecified changes to system configuration might have caused the problem.
Hi zbook,

Do you think that it is registry corruption? Unfortunately as far as I know Win11 was not set up to do registry backups at the time, as the System32\config\ RegBack folder is empty. Is there another way to repair the registry?

Yeah the 4th of Feb was the day it went down.

I didn't notice that it had found drive system problems on both C: and F:. I'm not sure what drive F: is though, is there a way to find out what letter was assigned to which drive at the time?
 

My Computer

System One

  • OS
    Windows 11
    Computer type
    PC/Desktop
    CPU
    AMD Ryzen 7 7800X3D
    Motherboard
    ASUS X670E-E
    Memory
    Trident Z5 Neo RGB, DDR5-6000 CL30-38-38-96, 2x16GB
    Graphics Card(s)
    EVGA RTX 3060 XC
    Monitor(s) Displays
    Samsung 34" Odyssey OLED G8 & Dell U2518D
    Screen Resolution
    3440 x 1440 & 2560 x 1440
    Hard Drives
    Samsung 990 Pro 2TB & Samsung 850 Evo 1TB
    PSU
    Corsir RM1000x
    Case
    Fractal North
    Cooling
    EK-Nucleus AIO Lux CR240 D-RGB
    Internet Speed
    250Mbps/25Mbps
Corruption of the drive file system can cause corruption of any file.

Possible repair options are:

custom install

clean install




 

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
I'm still persisting in trying to solve my problem and haven't resorted to rebuilding Windows just yet.

I have a bit of an update as I have bought a USB debugging cable and are now able to access the kernel. With it attached to windbg on my laptop, at the point during the startup process where the screen goes black, I get the message:
"DriverEntry failed 0xc0020035 for driver \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\INTCCoSvc".
This can also be seen in the screenshot below.

I'm still learning how to interrogate the kernel further, but do you think that this could be a cause of my problem? I've been attempting to fix this message but have not been successful so far.

Windbg Screenshot.webp
 

My Computer

System One

  • OS
    Windows 11
    Computer type
    PC/Desktop
    CPU
    AMD Ryzen 7 7800X3D
    Motherboard
    ASUS X670E-E
    Memory
    Trident Z5 Neo RGB, DDR5-6000 CL30-38-38-96, 2x16GB
    Graphics Card(s)
    EVGA RTX 3060 XC
    Monitor(s) Displays
    Samsung 34" Odyssey OLED G8 & Dell U2518D
    Screen Resolution
    3440 x 1440 & 2560 x 1440
    Hard Drives
    Samsung 990 Pro 2TB & Samsung 850 Evo 1TB
    PSU
    Corsir RM1000x
    Case
    Fractal North
    Cooling
    EK-Nucleus AIO Lux CR240 D-RGB
    Internet Speed
    250Mbps/25Mbps
I'm still persisting in trying to solve my problem and haven't resorted to rebuilding Windows just yet.

I have a bit of an update as I have bought a USB debugging cable and are now able to access the kernel. With it attached to windbg on my laptop, at the point during the startup process where the screen goes black, I get the message:
"DriverEntry failed 0xc0020035 for driver \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\INTCCoSvc".
This can also be seen in the screenshot below.

I'm still learning how to interrogate the kernel further, but do you think that this could be a cause of my problem? I've been attempting to fix this message but have not been successful so far.

View attachment 127739

I'm out of ideas except post #34.

Other members may comment.
 

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
That last WinDbg trace points to the NVIDIA card. Since your motherboard has onboard graphics, you might want to try taking out the RTX and seeing if you can successfully boot without it. If that's the case, then it's either a bad GPU or NVIDIA driver issue.
 

My Computer

System One

  • OS
    Windows 7
That last WinDbg trace points to the NVIDIA card. Since your motherboard has onboard graphics, you might want to try taking out the RTX and seeing if you can successfully boot without it. If that's the case, then it's either a bad GPU or NVIDIA driver issue.
Hey Garlin, are you talking about the reference to the INTCCoSvc driver? I thought it was to do with the Intel wifi device on the motherboard, so I tried to reinstall icpsextension.inf and icpscomponent.inf with DISM.

I have already removed the GPU, but the system still doesn't boot unfortunately. Do you think that its driver could still be causing the problem?
 

My Computer

System One

  • OS
    Windows 11
    Computer type
    PC/Desktop
    CPU
    AMD Ryzen 7 7800X3D
    Motherboard
    ASUS X670E-E
    Memory
    Trident Z5 Neo RGB, DDR5-6000 CL30-38-38-96, 2x16GB
    Graphics Card(s)
    EVGA RTX 3060 XC
    Monitor(s) Displays
    Samsung 34" Odyssey OLED G8 & Dell U2518D
    Screen Resolution
    3440 x 1440 & 2560 x 1440
    Hard Drives
    Samsung 990 Pro 2TB & Samsung 850 Evo 1TB
    PSU
    Corsir RM1000x
    Case
    Fractal North
    Cooling
    EK-Nucleus AIO Lux CR240 D-RGB
    Internet Speed
    250Mbps/25Mbps
The INTCCoSvc driver is some form of network optimization, it doesn't appear to be required by the base driver. So you can try removing it.

WinDbg screen is showing the crash dump's stack. Since NVIDIA and the Intel driver are listed, one of the two are the nearest culprits. Error code 0xc0220035 is STATUS_FWP_INVALID_PARAMETER. Either the Intel driver's bad, or you have a corrupted Windows kernel.

If you have a corrupted Windows, then a repair install from an UUP dump ISO might be helpful. More specifically because UUP dump can create an image with the most recent patches already integrated.
 

My Computer

System One

  • OS
    Windows 7
I removed the driver with the below commands but I'm not completely sure that this is all that is required to remove the driver. After running the commands, the drivers no longer appear in the list when the /Get-Drivers command is run, but the INTCCoSvc DriverEntry failed 0xc0020035 error still appears in windbg.

Dism /image:d:\ /Remove-Driver /driver: oem81.inf (icpscomponent.inf)
Dism /image:d:\ /Remove-Driver /driver: oem82.inf (icpsextension.inf)

Do you know if there are further actions that need to be undertaken to remove a driver from an offline image?
 

My Computer

System One

  • OS
    Windows 11
    Computer type
    PC/Desktop
    CPU
    AMD Ryzen 7 7800X3D
    Motherboard
    ASUS X670E-E
    Memory
    Trident Z5 Neo RGB, DDR5-6000 CL30-38-38-96, 2x16GB
    Graphics Card(s)
    EVGA RTX 3060 XC
    Monitor(s) Displays
    Samsung 34" Odyssey OLED G8 & Dell U2518D
    Screen Resolution
    3440 x 1440 & 2560 x 1440
    Hard Drives
    Samsung 990 Pro 2TB & Samsung 850 Evo 1TB
    PSU
    Corsir RM1000x
    Case
    Fractal North
    Cooling
    EK-Nucleus AIO Lux CR240 D-RGB
    Internet Speed
    250Mbps/25Mbps

Latest Support Threads

Back
Top Bottom