Your PC Didnt start Properly ERORR - Bricked PC

[TutorialNeededN19]

PC HELP PLEASE!!


My computer instead of booting up goes to a blue screen and states it didn’t start properly and to try auto repair

Auto repair fails and I tried to reset the pc with the troubleshooter and that also failed

It will boot into safe mode.

Windows 10 OS

ERROR CODES:
1. 0xc0000001 - Recovery

2. File/BCD
0xc0000098 -Recovery


I got the following information from CMD:

CMD

C:\Users\Cosse>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.

Verification 35% complete.

Windows Resource Protection could not perform the requested operation.

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

C:\Users\Cosse>chkdsk/spotfix

The type of the file system is NTFS.

Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another

process. Would you like to schedule this volume to be

checked the next time the system restarts? (Y/N) y

====================================
Now the following from DSIM:
====================================

DISM

Windows PowerShell

Copyright (C) Microsoft Corporation. All rights reserved.

Try the new cross-platform PowerShell Install PowerShell on Windows, Linux, and macOS - PowerShell

PS C:\Users\Cosse> wmic diskdrive get status

Status

OK

OK

PS C:\Users\Cosse>


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


C:\Users\Cosse>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool

Version: 10.0.19041.844

Image Version: 10.0.19044.2965

[========== 17.8% ]

Error: 605

The specified buffer contains ill-formed data.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log


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

C:\Users\Cosse>dism /online /cleanup-image /checkhealth

Deployment Image Servicing and Management tool

Version: 10.0.19041.844

Image Version: 10.0.19044.2965

No component store corruption detected.


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

===========================================================
Following from ComponentsScanner Version 1.5.1.0 by sysnative.com
==========================================================

ComponentsScanner Version 1.5.1.0 by sysnative.com
Windows Version: Windows 10 21H2 x64 (10.0.19044.2965)
Start time: 2024-01-24T21:19:21
Hive scanned: %windir%\System32\config\COMPONENTS
Number of keys: 63837
Number of values: 203530

==== Critical Errors ====
None

==== Corrupt Key Names ====
None

==== Corrupt Value Names ====
None

==== Corrupt Value Data Type ====
None

==== Corrupt Value Data ====
None

==== Repair Log ====
No possible repairs

==== Warnings ====

== f! Mark Count Mismatch ==
amd64_microsoft-windows-mediaplayer-shortcut_31bf3856ad364e35_10.0.19041.1_none_64c27fc7ed12e401 has 1 f! marks, expected 0
wow64_microsoft-windows-onedrive-setup_31bf3856ad364e35_10.0.19041.1_none_e585f901f9ce93e6 has 3 f! marks, expected 2



Storing 0KB in C:\Users\Cosse\AppData\Local\Sysnative\ComponentsScanner

Finish Time: 2024-01-24T21:19:56. Corruption scan time: 11.7478891s
===========================EOF===========================

==========
Malware info - RKill.exe
==========
Rkill 2.9.1 by Lawrence Abrams (Grinler)
BleepingComputer
Copyright 2008-2024 BleepingComputer.com
More Information about Rkill can be found at this link:
RKill - What it does and What it Doesn't - A brief introduction to the program - Anti-Virus, Anti-Malware, and Privacy Software

Program started at: 01/24/2024 10:04:52 PM in x64 mode. (Safe Mode)
Windows Version: Windows 10 Home

Checking for Windows services to stop:

* No malware services found to stop.

Checking for processes to terminate:

* No malware processes found to kill.

Checking Registry for malware related settings:

* No issues found in the Registry.

Resetting .EXE, .COM, & .BAT associations in the Windows Registry.

Performing miscellaneous checks:

* Windows Defender Disabled

[HKLM\SOFTWARE\Microsoft\Windows Defender]
"DisableAntiSpyware" = dword:00000001


...............................................................................................................
I am about to hire someone to fix this as im not a windows troubleshooter and its frustrating as i dont know the cause of this other than possibly a virus. We don't need to get into why really until we fix it although. All help is appreciated, i just want to be able to game again.

 

[TutorialNeededN19]

CMD Information 2:
C:\Users\Cosse>Bootsect /nt60 all /MBR
Target volumes will be updated with BOOTMGR compatible bootcode.

C: (\\?\Volume{229ec75b-d7e8-4787-bec9-ce63099b0ff8})

Updated NTFS filesystem bootcode. The update may be unreliable since the
volume could not be locked during the update:
Access is denied.

D: (\\?\Volume{e49421d0-4ba9-4e06-95c3-c7d7d17405b7})

Updated NTFS filesystem bootcode. The update may be unreliable since the
volume could not be locked during the update:
Access is denied.

E: (\\?\Volume{7973f462-2322-11ec-b9a5-40b07640e2bb})

Updated FAT32 filesystem bootcode. The update may be unreliable since the
volume could not be locked during the update:
Access is denied.

\\?\Volume{a2935f9d-0939-4983-baff-57e8f433ad32}

Successfully updated NTFS filesystem bootcode.

\\?\Volume{11a2aacb-65ab-4af7-bed2-bb777a5de393}

Updated FAT32 filesystem bootcode. The update may be unreliable since the
volume could not be locked during the update:
Access is denied.

\Device\HarddiskVolume2

Could not open the volume root directory:
The parameter is incorrect.

\Device\HarddiskVolume4

Could not open the volume root directory:
The parameter is incorrect.

\??\PhysicalDrive0

Bootcode is only updated on MBR partitioned disks. A different
partitioning scheme is used on this disk.
\??\PhysicalDrive1

Bootcode is only updated on MBR partitioned disks. A different
partitioning scheme is used on this disk.
\??\PhysicalDrive2

Successfully updated disk bootcode.

Bootcode was successfully updated on at least one volume.

 

[TutorialNeededN19]

Boot files were damaged somehow. fixed it with a bootable usb OS windows 10

 

[x BlueRobot]

Boot files were damaged somehow.

I was going to mention that this was probably the case, what is the result of SFC and DISM now? Do they both complete successfully with no errors?