Jump to content
Corsair Community

V64 problems?


darkage3000

Recommended Posts

hello

i have a nova 64gb for some months and the thing that starts to get boring is the following

when i first installed win7 all went ok for about 3 months, them there was a massive windows update and the installation started to have random errors so i did a secure erase

the new installation went ok, but since this second installation i have not been able to have a win7 for more then 1 month as it starts to chksd when i restart and after some days some services go down and i have to secure erase the ssd and reinstall win7

as you may understand it is getting boring to secure erase and install windows every month

the atto bench i make i think the readings are allright, so don't know what it can be, but for sure it is related to the ssd as i had in this machine win7 with a raptor and no problem

thanks for any help

sorry for the english

Link to comment
Share on other sites

  • Corsair Employee
Please check with the MB manufacturer and see if there are any BIOS and or driver updates for that MB and then try the install again, but to be sure if you can I would test the SSD in another system and you can use software like Accronis to create a image of the drive so its much easier to restore.
Link to comment
Share on other sites

hello

my mb is allways with the latest bios, and the OS also

i will try in another system the ssd, because i just give up, just after i posted here the system is again corrupted, with windows services not responding,etc

so i will not keep installing windows every month

just ordered another ssd with other controler

thanks for your time

Link to comment
Share on other sites

  • Corsair Employee

If you can test it in another system that would help to verify if you have a failing drive or some other issue.

I have no problem at all having you get an RMA and have us replace the drive, but that is not common with that drive so it may be some other cause.

But if you do find its the drive causing the error please use the link on the left and we will be happy to replace it.

Link to comment
Share on other sites

  • 2 weeks later...

hello again

the V64 just started rebooting with chkdsk in win7 again after a secure erase made in 23-12-2010 so i think its time to rma the drive

in this time the system was full stock, only intel chipset drivers and the microsoft msahci driver for the ahci drives

i have two more hdd in this system and no problems with them

do you have a rma center in europe so i can send the drive? as the uk shop where i bought this drive just told me to send it to you

thanks for any help

Link to comment
Share on other sites

I also have a very similar problem & have submitted an RMA request yesterday.

 

My V64 drive was actually sent out as a replacement for a failing R60 drive. The R60 was working OK for a week or 2, then started corrupting files... The same results would occur after many rebuilds.

 

This V64 was working fine since installation about 2 months ago, but now I came into the office after the weekend & found my PC failing to boot. After a hard poweroff & on windows would boot, but then BSOD & drive dissapears from BIOS. A hard poweroff/on repeats the process.

 

While waiting for feedback on the RMA I'm trying to recover data off the drive & think I have come across something...

-Taking a full image of the faulty drive dies pretty quickly

-Doing a Robocopy of all files works for an extended amount of time, but kept failing at the same point & caused the drive to dissapear

-Doing a Robocopy and excluding the directory that the failures occured at above, the Robocopy seems to be completing OK...

 

Originally I was thinking the failure was 'time based', e.g. after running for 2-3 minutes the drive would crash... but the above testing seems to tell me that there is a section of the SSD that is having errors & causing the SSD controller to crash...

 

I think needless to say I'm starting to loose confidence in Corsair SSD's when two seperate product lines are experiencing these issues. (and I see posts on the forum of others experiencing the same issues with the same model drives).

Link to comment
Share on other sites

Sorry, should have specified in that post...

 

The data recovery (i.e. take image & robocopy's) is being done from a WinPE boot disk based on the latest WAIK from microsoft.

 

The imaging utility I was using was ImageX from the WAIK. All this is doing is trying to read the data from the SSD & write to a WIM file on an external USB harddisk.

I suspect any other imaging utility would hit the same stumbling block when trying to read the same files/sectors.

 

The failure on copying the file using Robocopy was repeatable with copy & xcopy also.

 

I gave up on recovering all data off the drive & have instead grabbed just the important files... I'm in the process now of re-imaging my laptop on its old clunky HDD (luckily this is mostly painless due to using SCCM for OS Deployment, still alot of customisations to be done once complete though).

 

Edit: It is probably worth mentioning that performing a chkdsk on the SSD also fails very early on also (and causes the drive to dissapear from windows/bios until a power off/on).

Link to comment
Share on other sites

  • Corsair Employee

You would need to check with Microsoft to be sure but all of the information I can find on these applications are before the release of SSD technology and they are not optimized for SSD's and may be part of the problems. And again

I would suggest using something that is optimized to work with SSD's and in this case secure erase the drive with parted magic and then try a fresh install of the O.S. If you are not using Windows 7 you will want to Quick format the drive with 4096 Allocation before the install and after the secure erase.

The data recovery (i.e. take image & robocopy's) is being done from a WinPE boot disk based on the latest WAIK from microsoft.
Link to comment
Share on other sites

The latest WAIK (and included tools) are based on Windows 7, so definately 'support' SSDs.

 

If this version WinPE & ImageX doesn't support SSD's there is a major problem, since that is what the Windows 7 installation disk is using under the covers...

Link to comment
Share on other sites

Using the Parted Magic boot disk & then the 'Partition Image' software I get the same errors also.

 

Dumped about 2-3GB of the partition, then 'Can't read block 761125 from image (135151648).

 

After that, the SSD is no longer recognized by the system. Harddisk Health Inspection tool takes a long time to scan & then reports the SSD as Unknown Model.

 

I'll try doing a secure erase using Parted Magic & see what happens.

Link to comment
Share on other sites

  • 2 weeks later...

hello

i have sent my V64 to RMA, and received today a package with a RF V64, the problem is that i sent to RMA all the retail goodies and received back just the SSD, where can i complain to have back all the other things included in the retail package?

thanks for any help

and sorry for the english

Link to comment
Share on other sites

hello again

i have sent a email to the rma service and until now just received the confirmation contact email, don't know what you are going to do about the missing accessories from my V64 RMA case

i am not happy at all because it took more than a month to have the ssd back and even so corsair send me a RF ssd, when i sent a new ssd with less then 1 year, i had to buy a new ssd for my system because of this failling V64and now i can't sell this V64 as it is RF

so i need my ssd accessories as i sent to the netherlands in the rma package

thanks

sorry for the bad english

Link to comment
Share on other sites

  • 1 month later...

hello again

as told before i received the RMA RF V64, installed the drive and is just starting again with CHDSK when rebooting win 7 64 pro

do i send it to RMA again??

any test that can be done before??

the drive is not in the system it was before, no overclocking, installed intel inf. intel RST, etc etc

Link to comment
Share on other sites

  • Corsair Employee

Can you image the drive to another HDD then use this drive as a second HDD and use parted Magic and secure erase the drive then with it as second HDD quick format with 4K Allocation then run Bart Disk Burn in over night and see if it logs any errors.

 

1. Use parted Magic to secure erase the drive.

2. Boot the system with another HDD and this drive our SSD as second drive then in disk manager create and format the partition with 4k Allocation.

3. The run Bart Drive Burn in for 24 hours or over night and let me know if you get any errors.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...