Falcon II OS Drive Corruptions

[EzDingo]

Anyone else randomly and repetatively getting Windows OS corruptions using this drive and having to reimage or reinstall windows? I am getting more and more frustrated with this drive and regret ever buying it now. Any comment or help appreciated.

- Bought the new drive to use as OS (P6X58D i7)
- Tried running as IDE ACHI with no difference to problem
- While it stable everything is good
- Over few months randomly windows corrupts (avg 1-2 per month)
---- cckdisk will show errors and run through fixing but this is always a sign of worse trouble to come and time to reinstall or reimage. Seems to happen more when turning on/off the PC than if left on permanently. Sometimes chkdisk can not fix at all.

- Tried to install new firmware and the drive ended up locked. RMA'd and received new drive with new firmware.

- New New drive does the same thing... randomly windows will corrupt and the end result is a reinstall to fix it.
- Just lately BIOS 'sometimes' does not show the drive at all after a corruption despite trying different SAT prots and lead and power cables.

NOTE: I have tried and tested the system. With a std sata drive in place for the OS windows never corrupts and life is good... albeit a bit slower.


I am starting to think this G.Skill product is just rubbish and unreliable. 2 drives doing the same thing. Backing up and reimaging is not a huge issue unless you have to do it every other day (which is the case lately).

[vaca]

Dear Customer,
If your replacement is defective, you can RMA it again and you could choose pay on delivery that we will pay the freight.
Could you tell me the specific model name of your falcon II?
I believe the issue would be generally for those SSDs that use indilinx controller with intel 34nm NAND flash on the market.
I think the indilinx controller is still improving their firmware to controll the intel 34nm NAND flash better. We will push them to release new firmware for making our Falcon series product more stable.

[whiteze]

Same here, Windows lasts week, max two weeks, than it needs to be reinstalled, random files are being lost/corrupted. Even tried to use it as non-os drive to have games on it, games got corrupted too.
Got back to raid0 setup on hard drives, had no problem since...

Precious SSD is getting dusty on the shelf.

Yet before i was waiting two months to get it back to life when it died after hard reset of my system, as there was no way to restore firmware on it because firmware wasn't released!

Cheers

[wenis]

Same here.

Store I bought from told me I was the 3rd RMA'er in 3 days.

[ffm76600]

Falcon I problem

Strange.

I have the same problem with a ssd falcon I. 2 weeks later, i have a corrupt Windows

I have to reinstall Windows image and my computer works again for ~ 2 weeks maybe more

[vaca]

We are working on the new firmware 2030 update which would make SSD more stable.
We would release it soon.

[ffm76600]

Vaca.

When do you think to release the new firmware for Falcon 1st gen ? (1 week, one month or more ?)

[vaca]

No more than one month, We are trying to release ASAP.

[omniman]

No more than one month, We are trying to release ASAP.

Hi,and what is with Falcon II SSD?s , when comes here a new Firmware?

[ffm76600]

Thanks for your answer.

This morning, I reinstalled the firmware 1571. I think the version 1916 is buggy. My problem was beginning when i install this version

I wait the new firmware maybe there will no problem

[ffm76600]

I found my problem.

I have Windows 7 Pro x64, a gskill falcon 1 128gb, ahci mode. firmware 1571

My problem comes only when I execute the wiper command. The command prompt moves very quickly. If I reboot my computer after that my system is corrupt.

The firmware 1916 change nothing.

[vaca]

Firmware 2030 has released, you could try it

[ffm76600]

Same problem with the newest firmware 2030.

Do you have a solution ?

[EzDingo]

Will 2030 stop corruptions (if it updates correctly this time)

Well I am about try and install the new firmware 2030 over 1916 to see if this helps stop those repetative OS drive corruptions....

Thats if the firmware installs correctly without bricking my drive again like 1916 did requiring an RMA...

And thats if I can 'guess' what the correct procedure is to actually install firmware 2030!

GSKILL... your firmware update instructions are the worst in the world for any company... if you can actually call them instructions at all...

Your firmware post for Falcon II simply shows the procedure of running 128GB_1.exe and thats it... oh sorry I forgot it also shows it failing perhaps and if so try another version... and if that still doesn't work try another version again... How about 1 version that intelligently works out which NAND the drive uses and executing to correct code accordingly instead of the user randomly trying each .exe? Too hard? Too simple?

Ok... so now i know how to run the .exe but thats it... nothing about that the drive should or should not be set to disk 0 (physically connected on sata port 1 on the Motherboard)... nothing about can this be done from boot disk or if you still need to pull the drive out of your machine - install it in another machine as disk 0 - and then update via windows OS - and then piece back together both machines... nothing about the jumper pin... REALLY - ARE THESE ACTUAL INSTRUCTIONS THAT A PROFESSIONAL COMPANY RELEASES?

So... all of the above snippets come from various other threads and are so jumbled its not funny for different firmware updates. the process for 1916 has chnaged with 2030 but no step by step detailed instructions.

So can anybody confirm with Falcon II 2030:

- Will a dos boot disk suffice?
- Does the SSD need to be on Disk 0 (motherboard connection)
- Is the jumper required
- Does bios IDE mode need to be set to compatible
- Methods?: 1 have 2 OS drives in your PC (dual boot) or 2: put the SSD in another computer
- Anything else we need to know before pressing go to have the best chance of success and not brick another drive?

[EzDingo]

Firmware Update 2030 Success with Errors

128GB_1 confirmed successful update at end of process to 2030

BUT...

During update the following 4 messages came up in yellow text:

ERROR: erase failure-high low\
ERROR: erase failure|low
ERROR: erase failure-high low\
ERROR: erase failure|high low\

Should I be concerned about the above?



Crystal Disk Info shows the following of which I have no idea if its bad or normal:

ID 01: Error read rate = 6
ID B8: Initaial bad Block Count = 1543
ID C4: Erase Failure Block Count = 27
ID CA: Total Count of Error Bits From Flash = 14875
ID CB: Total Count of Read Sector with Correctable Bit Errors = 12528

Can anyone comment on these values?