[SOLVED] Possible M.2 Failure [Win 10]

Nov 8, 2020
3
0
10
Windows run chkdsk on startup every time I boot my PC. I've let it scan and repair multiple times but it still does it

I've used "wmic diskdrive get status" as well as "wmic /namespace:\\root\wmi path MSStorageDriver_FailurePredictStatus" in Command Prompt which gave me an OK status and "Predict Failure - False". Also checked the failurepredictstatus in PowerShell with the same results.

Now when running a system diagnostic in Performance Monitor I get these results:

Symptom:The VolumeDirty flag is set on the disk
Cause:A logical disk has the dirty bit set.
Details:This disk has been marked as dirty, it may be experiencing errors or might have not been shut down correctly
Resolution:1. Run chkdsk on the drive and document any errors identified.
2. If chkdsk determines that there are errors on the drive run chkdsk /f to repair the errors.
Related:Disk Diagnosis
Basic System Checks
TestsResultDescription
OS ChecksPassedChecks for attributes of the operating system
Test GroupsTestsFailedDescription
OS Version Check10Passed
Disk ChecksFailedChecks for disk status
Test GroupsTestsFailedDescription
SMART Predict Failure Check10Passed
Logical Disk Dirty Bit Check11Failed


What does a failed test for Logical Disk Dirty bit check mean? I then ran chkdsk manually and it found no problems. This issue started about a week ago and would like to avoid having to get a new M.2 as my motherboard only has one slot and it would me a nuisance to have to clone the drives. M.2 is a Crucial P.1 500gb (maybe 512 I forget exactly) and I've had it for almost a year now so it seems like a failure shouldn't already be occurring, any help appreciated.
 
Solution
download the Crucial OEM version of Acronis.
you can image the SSD to a hard drive and create a USB recovery drive.
may help if you need to restore to a new NVMe.

if you're highly OC'ed - Windows may no commit all writes to SSD before shutdown which may cause your issue.
Windows run chkdsk on startup every time I boot my PC. I've let it scan and repair multiple times but it still does it

I've used "wmic diskdrive get status" as well as "wmic /namespace:\\root\wmi path MSStorageDriver_FailurePredictStatus" in Command Prompt which gave me an OK status and "Predict Failure - False". Also checked the failurepredictstatus in PowerShell with the same results.

Now when running a system diagnostic in Performance Monitor I get these...
Logical Disk Dirty bit - means your system previously was not shut down properly.

Check the drive with Crucial Storage Executive.
didn't know about that program thank you, it says that the drive has good health. Why would performance monitor flag it having a dirty bit and also check disk on start up then?
 
Posted this thread yesterday:

was told that Logical Disk Dirty bit means my system wasn't shut down correctly which I've also read several times as well as to to download crucial storage executive to check the disk which I did and it says the drive is healthy. So now I would like to know why windows still runs chkdsk on startup and why performance monitor still flags the drive as having a dirty bit and if there's a way to fix this. Any help appreciated!
 
download the Crucial OEM version of Acronis.
you can image the SSD to a hard drive and create a USB recovery drive.
may help if you need to restore to a new NVMe.

if you're highly OC'ed - Windows may no commit all writes to SSD before shutdown which may cause your issue.
Windows run chkdsk on startup every time I boot my PC. I've let it scan and repair multiple times but it still does it

I've used "wmic diskdrive get status" as well as "wmic /namespace:\\root\wmi path MSStorageDriver_FailurePredictStatus" in Command Prompt which gave me an OK status and "Predict Failure - False". Also checked the failurepredictstatus in PowerShell with the same results.

Now when running a system diagnostic in Performance Monitor I get these results:

Symptom:The VolumeDirty flag is set on the disk
Cause:A logical disk has the dirty bit set.
Details:This disk has been marked as dirty, it may be experiencing errors or might have not been shut down correctly
Resolution:1. Run chkdsk on the drive and document any errors identified.
2. If chkdsk determines that there are errors on the drive run chkdsk /f to repair the errors.
Related:Disk Diagnosis

Basic System Checks
TestsResultDescription
OS ChecksPassedChecks for attributes of the operating system
Test GroupsTestsFailedDescription
OS Version Check10Passed
Disk ChecksFailedChecks for disk status
Test GroupsTestsFailedDescription
SMART Predict Failure Check10Passed
Logical Disk Dirty Bit Check11Failed


What does a failed test for Logical Disk Dirty bit check mean? I then ran chkdsk manually and it found no problems. This issue started about a week ago and would like to avoid having to get a new M.2 as my motherboard only has one slot and it would me a nuisance to have to clone the drives. M.2 is a Crucial P.1 500gb (maybe 512 I forget exactly) and I've had it for almost a year now so it seems like a failure shouldn't already be occurring, any help appreciated.
 
Solution