Taking work now — the first look is freeSSDs posted in from anywhere in the UK, or handed in at ten drop-off pointsQuicker still, give us a ring:0800 6890668
SDRSSD Data Recovery 0800 6890668 Price my job
SDR / Manufacturers / Corsair

Force · MP510 · MP600 · MP700

Corsair SSD data recovery. Phison inside nearly every one.

Corsair's MP-series NVMe drives run Phison controllers from the E12 in the MP510 to the E26 in the MP700, and the older Force GT and Force 3 SATA drives used SandForce. The MP700 was one of the first PCIe 5.0 drives, and it shut down under sustained load without a heatsink until Corsair's firmware 22.1 changed the throttle curve. That makes a Corsair drive a known quantity on the bench: the Phison E-series routines apply, and so do the E-series failures. One Corsair SSD is £300 + VAT after the free look, fixed in writing, 3–5 days at the bench.

Free first lookOne fixed figure in writingNo data, no bill on most jobsReturn postage paid

Rather talk it through? An engineer answers the bench line
0800 6890668

Models we see, family by family.

Which kind of drive is it →
Family Models Controller commonly reported
MP-series NVMeMP300, MP400 (QLC), MP510, MP600, MP600 Core, MP600 Pro, Pro XT, Pro LPX, MP700, MP700 ProSilicon Motion (MP300, MP400) · Phison E12 (MP510), E16 (MP600), E18 (MP600 Pro), E26 (MP700)
Force SATAForce 3, Force GT, Force LS, Force LE, Force MP-series precursors, Neutron GTXSandForce SF-2281 · Phison S10 · LAMD
PortableEX100UBehind a USB bridge

What tends to go wrong on a Corsair.

MP700 thermal shutdown, 2023TechPowerUp's testing found Phison E26 drives shutting down within about a minute of sustained load without cooling. Corsair's MP700 was fixed by firmware 22.1. A drive that drops out under load should be imaged, not updated.
SandForce on the old Force drivesThe Force GT and Force 3 used the SandForce SF-2281, whose 2011 firmware fault caused blue screens and disconnects until SandForce's 3.3.2 release. Legacy, and recovered as SandForce drives.
General pattern: Phison E-seriesNo other Corsair-specific fault was documented in our research. The pattern is the Phison one: firmware that will not load, a controller reporting 2MB, a drive that vanishes under load.

Corsair symptoms, and how long each gives you.

Not listed? Describe it on the form →
It is not in the BIOS at allThe controller did not finish starting. The flash behind it is almost always sound.Do not delay
It shows 2MB, 0GB, or the controller's nameFirmware fallen back to ROM: the drive is up, its map is not.Do not delay
It disappears during large copiesA controller crashing or overheating under load. Each return costs something.Do not delay
Read-only, or writes silently failSpare blocks exhausted. Usually fully readable.Everyday job
Deleted, or formattedTRIM is working through those blocks by the hour. Cut the power now.Do not delay
Packing it and posting it: a bare SSD travels in an anti-static bag inside a small padded box, with nothing able to move. Insure it for what the files are worth rather than the price of the drive, and use a tracked service. The posting address is not printed anywhere on this site; it arrives by email in reply to the form, with a booking sheet to print; the sheet inside the parcel is what matches it to your enquiry when it is opened. Or hand the sealed parcel in at the nearest of ten drop-off points, your name on the outside and the sheet inside; say where you are on the form and it comes by email. We pay the postage home either way. The whole of it is written up on the guide to packing and posting.

What the message means on a Corsair.

Describe yours to us →
What you see The usual reason Where that leaves you
Not in the BIOS, or listed at 2MBFirmware not loaded on the Phison controllerDiagnostic-state work; the flash is usually intact
Vanishes under sustained writes, back after a rebootA controller crash, or on PCIe 5.0 drives a thermal shutdownStop using it; image it before it gets worse
Read-onlySpare blocks exhausted; drive protecting itselfUsually fully readable
Dead straight after a firmware updateThe write stopped half-wayLoader in RAM; map from the service area

From the box arriving to your files going back.

Work we have closed →
01

Logged the day it lands, and the first look costs nothing Free

A case number goes on it the day the parcel is opened, and an engineer settles what has actually failed before anything else happens. The drive is read on our own equipment, never in a computer that might send it a TRIM command. Back to you come two things together: a straight note of what is liftable and what is not, plus one figure, fixed and written down. Accept it, or decline and owe us nothing.

Nothing to pay for lookingA single figure, put in writingNo TRIM, no writes
02

Powered on our terms

Every power-on gives a failing SSD another chance to run its own housekeeping. Here the drive is brought up in the controller's diagnostic state instead, which lets the bench speak to the flash directly and keeps damaged firmware out of the conversation.

Vendor diagnostic modeNo hopeful reboots
03

Past the fault, to the map

Working code is loaded into the controller's memory rather than onto the flash, the service area is read, and the translation table is rebuilt from what is there. Where the controller itself is dead, the chips are read one by one and the controller's scrambling and error correction are undone in software.

Loader in RAM, never on the flashMapping tables put back together
04

A full image, then the volume

Nothing is worked on live. The whole drive is imaged once, weak pages retried in their own passes, and the file system is put back together on the image. Encrypted volumes are unlocked there too, with the key you supply, and never on the original.

One careful imageThe volume verified end to end
05

You see the file list before you pay

What was recovered is listed for you first, and only then does a bill exist. Approve the list and it is invoiced; turn it down and it is not — and where nothing has come back, most jobs carry no charge at all. Recovered data travels home on fresh media bought in for your job, with the postage at our end. Your case is not closed until you have opened the files on a machine of your own.

No charge until you accept the figureFresh media, supplied with the job3–5 days at the bench

From the bench

  • Corsair SSD Toolbox is for healthy drives. Do not run its firmware update on a drive that is already missing or misbehaving.
  • Phison's NVMe controllers are well understood on the bench, from the E12 and E13T of the budget drives to the E16 and E18 in the fast ones, which is good news for the badge that sits on top of them.
  • The PCIe 5.0 E26 drives had a documented thermal shutdown when run without a heatsink, since addressed in firmware by the makers who use it. A drive that shuts down under load should be imaged, not updated.
  • Do not put a failing NVMe stick in a USB enclosure. The bridge hides the messages we need and has its own ideas about power states.

One job, followed all the way through.

UK · SDR-2026-0376JOB LOGGED ✓

A Corsair MP510 whose controller had cooked itself in a small case

A compact gaming PC with no airflow over the M.2 slot, and a drive that had run hot for two years before it stopped. The Phison E12 controller was dead; the drive was not hardware-encrypted, so the four flash packages came off and were read directly. The interleave and scrambling were undone, the map reconstructed from the flash, and the game saves, the photos and the tax paperwork came back.

98% of user files recovered6 days here, and back by post
Illustrative example — replace with a genuine case

What helps, and what harms.

Do this much first

  • A full shutdown, please: neither sleep nor hibernate
  • Write the full model and part number down
  • Deleted something? Send the form the same day
  • The stick travels on its own — no caddy, no enclosure

What sets us back

  • Rebooting over and over hoping it turns up
  • Pushing new firmware at a drive already misbehaving
  • Letting Windows initialise it when it asks
  • Running recovery software on a drive that keeps dropping out

Questions answered before you commit.

My MP700 vanishes during big copies. Is it dying?

Possibly overheating, as the E26 drives did without a heatsink before firmware 22.1. Stop using it and have it imaged; a firmware update on a drive in this state is a risk.

Which controller does a Corsair SSD use?

More than one, depending on the model and the year. The free look identifies the controller family before anything is attempted, and that decides the route in: a Phison drive, a Silicon Motion drive and an in-house design are each recovered differently.

What does it cost?

£300 + VAT for one drive after the free look, fixed in writing before any chargeable work. On most jobs no data means no bill.

How long does it take?

3–5 days at the bench after the free look. Priority handling is quoted separately when you ask for it.

Begin here if yours is doing the same thing.

NVMe M.2 →Not detected →Firmware and controller failure →Sabrent, on the same silicon →

Nothing gets worse while the power is off.

Looking at it is free. Back comes a list of what opened and what did not, together with a single price to finish, set down in writing while you are still free to say no. On most jobs an invoice only follows the data. Until that list reaches you, leave the drive switched off.

0800 6890668

Price my jobPacking and posting