Any info on the AData S599? Firmware upgrades on the way?

[dlai]

Thanks to the post by ClockerXP, I got my laptop to see the drive in Vista mode. However, the upgrade never completes. I select the drive, the firmware file is loaded and upon running the program, the drive does its thing but then either locks up, bluescreens, or reboots. The firmware never gets upgraded to 3.4.6. Anyone have any ideas?

 

[ClockerXP]

dlai-

Did you run the program again to check the firmware level now on the drive?

Also, just FYI, my system never BSOD'd. It just locked up so I had to hit reset. Also, I had the update file on a separate HDD when I ran it.

Good Luck,
CxP

 

[Hxx]

Thanks to the post by ClockerXP, I got my laptop to see the drive in Vista mode. However, the upgrade never completes. I select the drive, the firmware file is loaded and upon running the program, the drive does its thing but then either locks up, bluescreens, or reboots. The firmware never gets upgraded to 3.4.6. Anyone have any ideas?

Is your drive the boot drive? Mine BSODed every time i ran the firmware upgrade. I ended up pulling it out of my laptop and using my desktop to update the firmware on it. Only when i did that the process completed without a BSOD. I don't think the firmware works fine if the ssd is the actual boot drive, but i'm not sure of that. Either way i got the same result....that is the firmware got upgraded. Im also running W7 if that matters.

 

[dlai]

ClockerXp: Yep, checked the bios and it's still 3.1.0. I run the program in Vista mode off an external usb drive, it does its thing and the hangs up. After about 30 seconds of doing nothing, I get a real quick bluescreen and the system reboots.

Hxx: The drive is the boot drive but I'm running the update program from an external usb drive. I can't even get the program to see the drive if I run it in Win7. It's somewhat frustrating since it seems like it's so close to completing the update. I did get it once to say firmware update failed on the lower right before it did the BSOD.

So as near as I can tell, I'm running it similar to both of you but it's not happy for some reason. Any further ideas? I'm willing to try whatever ideas you folks might have. Thanks!

 

[Six]

Try disconnecting everything, but the SSD you're trying to flash. Make sure the SSD in connected to SATA connector 1. Run it in safe mode? Just tossing ideas out.

Speccy shows my drive is 46 degree Celsius (115 F), but the exterior of the drive is 76 degree Fahrenheit, 10 degrees above room temperature. Dunno what it was before.

 

[dlai]

Ok, tried to run it in safe mode, still failed. Ran it again in XP mode off the usb and got an error: Temp file allocation error. Not sure what that means. Maybe it's unable to create a needed temp file for some reason?

 

[Emulex]

you do realize the ssdupdate is the same software for all sandforce oem's - the only difference is the .pkg which is why my callisto deluxe shows up on the list too so you have to check the box on which to flash. i bet you could hot swap drives and flash another vendors firmware onto the drive lol.

so if you can't update with this software you won't be able to update any sandforce drive

 

[ClockerXP]

Ok, tried to run it in safe mode, still failed. Ran it again in XP mode off the usb and got an error: Temp file allocation error. Not sure what that means. Maybe it's unable to create a needed temp file for some reason?

Maybe your downloaded file is corrupt. Try re-downloading...

CxP

 

[posternutbag]

I was preparing to do the flash, and realized my BIOS was still set to IDE instead of AHCI. So, I went to the registry and I already had a "0" in the start key. Rebooted, changed to AHCI in bios, and when I got back to w7 there was no found new hardware action going on. So as I was going to check out devmgmt I noticed that my "WE" needed to be refreshed. When I let it run, my hard disk transfer rate went from 7.7 to 5.9! Do you think I am missing some kind of drivers?
In the process, I hooked up another sata 500gb hitachi to run the firmware update off of, which is quite older. It even has a legacy molex power connector. Is it ok to have AHCI turned on with this older drive connected?

And I need to thank you all-
I was having random crashes while playing flash videos, which I though I fixed by turning hardware acceleration off. It came back; I was still getting crashes. This process caused me to look at my CPU temp in BIOS- my i3 was getting to 95 C! I removed the stock cooler and put a hyper tx 212 plus on I had waiting for an i5 and it is nice and cool now :thumbsup:

 

[Emulex]

if you move the ssd you have to do a reboot cycle for win to load the driver before updating.

 

[demogorgon]

I have two of these drives i did the firmware updates on. On my pc it found the drive and updated ok except seeing the high heat readings. The other at first would not find the drive at all come to find out the nvidia controller drivers where the cause.

On my pc i had already changed them back to the microsoft drivers. As soon as i changed them from the nvidia to the MS ones the other pc found the drive and updated fine except the same high temps show which seem to be false.

 

[sxr7171]

I think it's kind of sad that the update program runs in Windows. Should be running straight off DOS. This is going to be a PITA for me. I might have to install Windows on 3 drives before I RAID them again. This is assuming the program can only flash the boot drive.

 

[God Mode]

Does this update require AHCI? My friend has a system without AHCI and I'm having a hell of a time trying to help him update his drive.

 

[Ataristic]

Does this update require AHCI? My friend has a system without AHCI and I'm having a hell of a time trying to help him update his drive.

Yes, the sata mode must be set to AHCI for the update to be succesfull, read my post on the detailed process of enabling AHCI without having to reinstall the OS.

 

[God Mode]

Too bad for him then. A lot of systems still lack AHCI namely ICH7 based chipset computers and laptops.

 

[Emulex]

dude the same program is used by ALL sandforce drives. if you go download OCZ,MUSHKIN/etc the same program. only thing different is the .PKG file.

So if you can't figure it out, rma the drive and get an intel or indilinx

 

[demogorgon]

I did the two i have without AHCI and worked.

 

[ClockerXP]

BTW, CrystalDiskInfo says my Microcenter 64GB SSD is running at 55C now too. Oh well....

CxP

 

[sxr7171]

Will it only flash the O/S drive? Or will it flash any drive.

 

[ultimaus]

Hey Thread!

I don't really browse through Anand forums but I flip through the reviews quite often but since I saw this thread was active I decided to make an account to post as I'm also quite confused about this particular pkg

Now I just purchased this drive Adata S599 128gb SSD... straight from the get go... I put it in my M17x Laptop... I loaded the OS Windows 7 64bit Ultimate, deleting the partition and creating the default size with the system reserved partition too

To my surprise after the installation completed I'm getting this BSoD (with restart disabled) the error is just random with letters and numbers like ACXX1242CCXA11... with no particular file at fault... it happens also if you try booting to the safe mode... I was delighted to find that ADATA's promised firmware upgrade has arrived... hence I google'd for one after this started happening...

unfortunately I'm having problems detecting the SSD using the launcher right now... after much dabbling I decided to delete the system reserved partition... and I no longer BSoD... I've yet to run any tests but after multiple successful restarts I'm happy enough...

Although I have UAC disabled... I've hated such security functions since time... and of course it's run using administrative rights and the ahci for sata is enabled by default on my computer...

I don't have access to someone's computer to try to flash on... but can anyone help me out by giving me a clue as to why the firmware launcher isn't detecting the drive?

Do you guys think if I just hook it up to some x58 computer the software would be more keen to detect it's existance?

As I'm limited to this 1 computer to try things out on I'd really appreciate feedback from anyone who has had similar problems this sort of problem but has solved the problem through other resources

 

[trulore]

I have 3 different computers ranging from 6 months old to 3 years old, and all of them have SATA, but none of them have "ACHI" mentioned anywhere in the BIOS settings. In fact, my newest computer only has 1 BIOS screen that lets you change boot order and set a BIOS password, and that's it. (I guess this is to protect against dumb users changing BIOS settings).

So, am I just out of luck? I guess I'll have to return the drive then, because I really need this firmware update, but it won't seem to apply. I tried several times under Windows 7, and the update never did anything but reboot the computer and leave me at firmware 3.1.0

 

[God Mode]

I have 3 different computers ranging from 6 months old to 3 years old, and all of them have SATA, but none of them have "ACHI" mentioned anywhere in the BIOS settings. In fact, my newest computer only has 1 BIOS screen that lets you change boot order and set a BIOS password, and that's it. (I guess this is to protect against dumb users changing BIOS settings).

So, am I just out of luck? I guess I'll have to return the drive then, because I really need this firmware update, but it won't seem to apply. I tried several times under Windows 7, and the update never did anything but reboot the computer and leave me at firmware 3.1.0

If you really need the drive to work correctly and you dont want to bother with accessing a pc with ahci, return it. A lot of people should consider paying a slight premium to go with a brand with better support and documentation.

 

[scrubman]

I had the problem of the firmware update program not detecting my Microcenter rebadged 64GB Adata SSD. I am running Win 7 Pro 64-bit. I was running the program as Admin. I solved the detection issue by running it Windows Vista SP2 compatibility mode.

Note: the update program causes the system to hard lock but upon a reboot (reset button) and then the system prompting to restart after rebooting all seems to be normal and the firmware update was successful.

You are da man!!! Same deal here but it was XP mode that I used and problem solved! Update complete. Thank you and everyone else posting on this!

 

[Double Trouble]

I have this micro center rebadge drive as well, and I'm having a heck of a time trying to update the firmware. I've tried on a few systems with no luck. On one system it would just freeze up the system, on another it would not find the drive, on a third it would start the flash process but then fail to "download" it to the drive etc.

For those of you who successfully upgraded the firmware, after the upgrade, what does the adata app show as the firmware after the upgrade? What OS / mobo did you use to do the flash?

 

[xsoulbrothax]

I have this micro center rebadge drive as well, and I'm having a heck of a time trying to update the firmware. I've tried on a few systems with no luck. On one system it would just freeze up the system, on another it would not find the drive, on a third it would start the flash process but then fail to "download" it to the drive etc.

For those of you who successfully upgraded the firmware, after the upgrade, what does the adata app show as the firmware after the upgrade? What OS / mobo did you use to do the flash?

Mine would hang on block 855 indefinitely (running it in Vista SP2 or XP SP3 both 'detected' the drive and hung at the same place), but after a reboot showed 3.4.6 and seemed to work fine - but it still did the sleep bug, even after a Win7 reformat. Going to probably test it on a different chipset to try flashing again.

edit: wow, never posted on this login apparently!