Reboot issue after installing SSD

Bios flash didn't help. And no BSOD. It just gives a black screen and sometimes a black screen with a very large mouse cursor that can't move.

Going to try get a firmware for the drive and see if that helps. Apparently some people have had similar issues with these drives because of the Sandforce chipset of the drive.

Like I said, BIOS settings are standard settings that worked fine with a normal old HDD.
 
Soz - I've been offline for a while now, but I'm back!

Dude, I had many issues - much the same with SSD and Win7 x64 reboot and BSOD etc etc etc.

After a whole year of research and problems I eventually found something undocumented that is the actual cause of it all.

I won't bother you with the technicals as to why, but, read on:

IF YOU ARE BOOTING WIN7 OS from the SSD and you are using an INTEL chipset, the Intel SATA controller will initialize 1st before any other add-on controller, with the nature of how an SSD works etc etc blah blah, you MUST connect the SSD to the very 1st port on the Intel controller. <-- simple as that.

If you connect it to the second or any other port and you are booting Win7 OS from it, you will have random problems.

SATA0 on some motherboard vendors, but SATA1 on most others.
It MUST BE ON PORT 1 (the very 1st port), no exceptions.
 
Soz - I've been offline for a while now, but I'm back!

Dude, I had many issues - much the same with SSD and Win7 x64 reboot and BSOD etc etc etc.

After a whole year of research and problems I eventually found something undocumented that is the actual cause of it all.

I won't bother you with the technicals as to why, but, read on:

IF YOU ARE BOOTING WIN7 OS from the SSD and you are using an INTEL chipset, the Intel SATA controller will initialize 1st before any other add-on controller, with the nature of how an SSD works etc etc blah blah, you MUST connect the SSD to the very 1st port on the Intel controller. <-- simple as that.

If you connect it to the second or any other port and you are booting Win7 OS from it, you will have random problems.

SATA0 on some motherboard vendors, but SATA1 on most others.
It MUST BE ON PORT 1 (the very 1st port), no exceptions.
Except I'm using the Marvell controllers as they are SATA3 and the Intel SATA ports are only SATA2 and the drive is a SATA 3, so would kinda defeat the point of having a 6GB/s drive on SATA2?
 
Remember to underclock your RAM's frequency. I've had a lot of issues with this.

My RAM runs at 1600mhz, I have to underclock it to 1333 for my system to be stable.
 
Anybody know where I can get firmware for Adata S511 120GB MLC SATA SSD? That's all that I can still think of.
 
To wrap up this fred.

I finally seem to have it working! Updated the firmware of the actual drive and voila! A BIG thanks to Craig from Foxcomp the importers of ADATA for sourcing the files for me, because they are nowhere to be found on the interwebz!

Been up and running for 2 days solid now with no issues. Yay!
 
Remember to underclock your RAM's frequency. I've had a lot of issues with this.

My RAM runs at 1600mhz, I have to underclock it to 1333 for my system to be stable.

firstly, this ^^ blows my mind.... but anyway...

secondly, DenSweeP is your system still running stable? I suspect it will be considering you updated the firmware of the actual SSD.

Its a well documented issue regarding the SF-2281 chipset.

I dont mean to be critical here, but why dont you okes do some research before you go out and buy something? I know when you spend money you expect it to work, but these days one cant be too careful... Especially when spending a lot of money on something like a SSD.
 
Seems to be stable and running fine, but about twice now since firmware it has hanged the PC. So maybe it's not the drive. I don't know and frankly, I've given up for now. Will investigate again when I have time.
 
Back
Top