Intel SSD 530 startup problems - Bug in SSD?

[ajoha7]

I just bought an Intel SSD 530 240GB to replace my Intel SSD510 for my HP Elitebook 8460p.

When i cold-start my computer everything is fine, but when I restart my computer from within a freshly installed windows-7, the drive is not found.

If i turn off the computer and start it again, the drive is found and boots up again as usual. So the drive fails after reset.

I have upgraded the firmware of the SSD to the latest version via the SSD toolbox but still no luck. also updated laptop bios to latest version.

I had no problems in the past with the Intel SSD 510 edition.

Any ideas on what to do?

Clarification:

So, when I insert my Intel 510 SSD and start windows and restart windows it works without problem. But with the Intel 530 it wails when I do restart, the BIOS does not find it after a normal reset. So that must conclude that the Intel SSD 530 has some bug? or is sensitive to some timing issue?

Should I return it? or just assume its incompatible with my laptop?

Message was edited by: andy johansson (added some clarification at the end)

[HG41]

Migel,

We are on DC12 firmware...... Did we miss something???

[LKrus1]

Stealth:

No, you are not missing anything.

Migel:

We are talking about the latest firmware (DC12). Not all problems are fixed.

[DHata]

Same issue as everyone else 530 Series SSD 180 GB and 240 GB in HP 8470P - requires a power cycle instead of a reboot. Same workaround switch to RAID. Problem traced to Intel Rapid Storage Technology which gets installed sometime during driver setup in imaging process updates IDE ATA/ATAPI Controllers driver to Intel 7 Series Chipset Family SATA AHCI Controller. Uninstall it will make the problem go away too....

Previously using 520 Series with no issues.

[PLind5]

I have installed a Intel SSD 530 in to a HP Elitebook 2540P and have experienced the same problem.

Model: SSDSC2BW120A4 Firmware DC22

[DBerr3]

I have the same problem with an HP Elitebook Folio 9470m and an Intel 530 240GB SSD running the latest firmware. Fortunately I noticed it after the initial load of the OS. I've changed to IDE/Legacy mode and am reloading Win7 now. Hopefully this will fix the issue.