[SOLVED] Chkdsk skips after countdown

[voidwr]

Hello, I have a problem with a fresh system that was built maybe three months ago. Since yesterday drive C: says that has an error and restarting starts checking the disk as it should. After the countdown ends, the process is being skipped and I go straight to the login screen, the error still remains. I tried sfc /scannow, it found some problems and repaired them but still had no luck, chkdsk c: /f /r both completed their scans and error still remains, chkntfs c: says that C: is dirty . I also run Dism /Online /Cleanup-Image /RestoreHealth, cleaned all my system files and I retried chkdsk but still no luck. Event viewer everytime there is a disk check logs the same error "Volume C: (\Device\HarddiskVolume5) needs to be taken offline to perform a Full Chkdsk. Please run "CHKDSK /F" locally via the command line, or run 'REPAIR-VOLUME <drive:>' locally or remotely via PowerShell". I tried running chkdsk from windows safe boot, after it finished I got the error "failed to transfer logged messages to the event log with status 6".

System Specs:
CPU: Intel i5-10400f 2.90Ghz
Motherboard: Msi z490 Gaming Plus
SSD/HDD: Samsung M2 250gb 970 EVO (Windows OS drive C: ) / HDD: Barracuda 1TB
GPU: AMD RX 6600XT Asus
PSU: Corsair 650W
Chassis: Kolink White
OS: Windows 10 Update 21H2 KB5011543
Monitor: LG 1ms 144hz i can't rember the model.

Event Viewer Error:

Spoiler

Log Name: System
Source: Microsoft-Windows-Ntfs
Date: 4/7/2022 3:56:34 PM
Event ID: 98
Task Category: None
Level: Error
Keywords: (2)
User: SYSTEM
Computer: DESKTOP-J2JULKT
Description:
Volume C: (\Device\HarddiskVolume5) needs to be taken offline to perform a Full Chkdsk. Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Ntfs" Guid="{3ff37a1c-a68d-4d6e-8c9b-f79e8b16c482}" />
<EventID>98</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000002</Keywords>
<TimeCreated SystemTime="2022-04-07T12:56:34.9372721Z" />
<EventRecordID>22520</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="256" />
<Channel>System</Channel>
<Computer>DESKTOP-J2JULKT</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="DriveName">C:</Data>
<Data Name="DeviceName">\Device\HarddiskVolume5</Data>
<Data Name="CorruptionActionState">3</Data>
</EventData>
</Event>

 

[Lutfij]

You system specs are incomplete. Please list them like so:
CPU:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:
Monitor:

Samsung make a number of M.2 SSD's, which one do you have? Corsair have a number of Vengeance ram kits on their portfolio, might want to narrow it down for us. BIOS version for your motherboard at the time of writing? If you're able to get into OS GUI without complications, and you're on Windows 10, see what version(not edition) you're on. Lastly, where did you source the installer for your OS?

 

[voidwr]

Hello thanks for the reply, I edited the system specs and now I'm gonna restart to see the BIOS version and edit again, I can't understand what you mean with

If you're able to get into OS GUI without complications, and you're on Windows 10, see what version(not edition) you're on. Lastly, where did you source the installer for your OS?

.

Edit: Bios Version is:

Spoiler

E7C75IMS.A70

 

[MrLitschel]

If you booted to the recovery environment and ran chkdsk from there, that message is normal as it can't write the chkdsk results to the Windows event log.

The bad system config can happen when the OS boot gets corrupted. You can try running:

• try the "last known good" boot option
• a startup repair
• a boot to recovery command prompt and check/repair the boot/system partition

If none of those fix the problem, you may end up having to do a clean install.