Solved NTFS corruption

[borate]

Win7/SP1 (64) and OCZ-Vertex2 solid state drive (C running in AHCI mode.

Random, occasional NTFS corruption that automatically invokes CHKDSK at next boot, but takes only a minute to repair. Dozens of fixes scroll by, and a comparison of CHKDSK logs confirms that each run makes unique repairs.

This is not the problem that has been mentioned in many forums where an"NTFS corrupt/run CHKDSK" balloon appears in the notification area, but there is no actual corruption. That allegedly was patched in SP1.

Anyone else experiencing this?

 

[DustSailor]

no, try sfc /scannow in cmd prompt?

Try a repair install (last resort option)?

Try to check it for errors, and give it time to check (check BOTH options):


Failing EVERYTHING anyone could suggest, could always reinstall o.0

Failing that buy a new HDD/SDD cause yours is bad 0_0

 

[Corazon]

Is the firmware for your OCZ up to date?

OCZ Technology

 

[borate]

no, try sfc /scannow in cmd prompt?

Verifies "no errors."

Try a repair install (last resort option)?

Total W7/SP1/all updates over-install just last week.

Try to check it for errors, and give it time to check (check BOTH options):
View attachment 182162

Done. None found, except when the problem occurs.

Failing that buy a new HDD/SDD cause yours is bad 0_0

New SSD drive, latest firmware, but that option is in the offing.
If anyone is aware of W7 caching or other specific settings applicable to SDD, please share.

Thanks to DustSailor and Corazon

 

[DustSailor]

I recall there being something wrong with some previous vertex, might google to see if others have the same issue

 

[borate]

I followed your suggestion, DustSailor, and happened upon a forum where other Vertex2 users listed similar complaints.

As the fault crops up ONLY during restarts, there was speculation that it may be caused by 'timing issues' during boot up on some, but not all systems.

With little more to test here, the SSD will be swapped out shortly for another brand.

 

[Sub Styler]

I dont have an SSD but did you "align" it's partitions before use?

 

[DustSailor]

I followed your suggestion, DustSailor, and happened upon a forum where other Vertex2 users listed similar complaints.

As the fault crops up ONLY during restarts, there was speculation that it may be caused by 'timing issues' during boot up on some, but not all systems.

With little more to test here, the SSD will be swapped out shortly for another brand.

I just bought an ocz vertex 3, and it is highly recommended, so don't give up just because of a single fluk

Got some links for you before installing that SSD: http://www.sevenforums.com/tutorials/149969-ssd-install-transfer-operating-system.html

http://www.sevenforums.com/tutorials/113967-ssd-alignment.html

http://www.sevenforums.com/tutorials/70822-ssd-tweaks-optimizations-windows-7-a.html

http://www.sevenforums.com/tutorials/91339-ssd-hdd-optimize-windows-reinstallation.html

 

[borate]

I dont have an SSD but did you "align" it's partitions before use?

It is aligned, likely by W7 at install.

Later findings revealed that the corruption occurs not only at boot, but at random times as well - one being at 3 in the morning while in SLEEP mode.

Current tests involve new 8G RAM - different manufacturer, different configuration.
If that does nothing, the SSD will be swapped out for another brand.

 

[DustSailor]

You could attempt a clean install and see if that fixes anything. at least then you would know what to blame (if this drive doesn't work after the reinstall, and the new one does).

Sorry couldn't figure this thing out for ya

 

[HammerHead]

Vertex III

I just filled out RMA for this disk
Corsair Performance 3 Series CSSD-P3128GB2-BRKT 2.5" 128GB SATA III MLC Internal Solid
State Drive (SSD)


It went totally dead. Caused a BSOD, machine hung up trying to write the dump file. After reset Bios spent a long time trying to communicate with the disk and ultimately wouldn't boot. It was five months old.

 

[borate]

You could attempt a clean install and see if that fixes anything. at least then you would know what to blame (if this drive doesn't work after the reinstall, and the new one does).

Sorry couldn't figure this thing out for ya

Thanks for the effort. Hopefully solved by virtue of a firmware update to the SSD drive.