If a dead NVMe drive holds data you need, stop applying power to it. Each retry pushes current through whatever is shorted on the board, so a single failed rail can spread to neighboring components. If the controller is partly alive, repeated power-ups also risk it completing queued TRIM or UNMAP (Deallocate) commands, after which garbage collection erases the NAND cells. Pull the drive & call (512) 212-9111 for a free evaluation.
Why Is My NVMe Not Detected in BIOS?
There is a line worth drawing first. A drive that shows in BIOS but not in Windows is a logical problem, a dropped partition or a file system the operating system won't mount, and consumer software can sometimes reach it. A drive absent from BIOS is physical: the controller never came up, so there is no block device for any tool to scan.
That distinction decides the whole job. Recovery software like R-Studio or DMDE works on a healthy drive the operating system can see. It has no path to a controller that never powered its PCIe link, which is why an electrically dead NVMe drive is a bench job, not a software job.
Why a Dead NVMe Can Stop Your PC From Booting
The difference is the data path. SATA drives reach the system through a host bus adapter that speaks AHCI, an electrical buffer between the drive & the rest of the board. NVMe removes that layer for speed, wiring the controller's PCIe lanes straight to the CPU.
That direct link is why a dead NVMe drive can take the whole boot down with it, & why the recovery access point is different. The fix is to reach the controller over a controlled PCIe link, not over a SATA channel.
| Electrical behavior | NVMe (PCIe) | SATA SSD |
|---|---|---|
| Host connection | Direct to the CPU over PCIe lanes, no intermediating bridge | Through a SATA host bus adapter that speaks AHCI |
| When the drive shorts | Can pull down the PCIe bus & hang host POST | Isolated behind the bridge; the PC still boots |
| Becoming visible to BIOS | Controller must train the PCIe link before BIOS enumerates it | Negotiation handled by the host adapter |
| Lab access point | Stabilize a controlled PCIe link with a PC-3000 Portable III | Reach the controller over the SATA channel |
How Much Does Dead NVMe Recovery Cost?
The tier follows the fault. Most electrically dead drives are a board repair: we revive the power tree or rebuild a broken differential pair, then image through the original controller, which is the tier that preserves the encryption key. When the link trains but the controller never finishes its NVMe handshake, the work moves to firmware-side system-area reconstruction with PC-3000 SSD.
NAND transplant is the last resort, used only when the original PCB is too damaged to repair. It requires a 50% deposit because donor parts are consumed in the attempt, and the donor cost is additional. A donor drive is a matching SSD used for its circuit board. Typical donor cost: $40–$100 for common models, $150–$300 for discontinued or rare controllers. No data recovered means no charge. +$100 rush fee to move to the front of the queue.
Low complexity
Simple Copy
Your NVMe drive works, you just need the data moved off it
Functional drive; data transfer to new media
Rush available: +$100
$200
3-5 business days
Low complexity
File System Recovery
Your NVMe drive isn't showing up, but it's not physically damaged
File system corruption. Visible to recovery software but not to OS
Starting price; final depends on complexity
From $250
2-4 weeks
Medium complexity
Circuit Board Repair
Your NVMe drive won't power on or has shorted components
PCB issues: failed voltage regulators, dead PMICs, shorted capacitors
May require a donor drive (additional cost)
$600–$900
3-6 weeks
Medium complexity
Most Common
Firmware Recovery
Your NVMe drive is detected but shows the wrong name, wrong size, or no data
Firmware corruption: ROM, modules, or system files corrupted
Price depends on extent of bad areas in NAND
$900–$1,200
3-6 weeks
High complexity
PCB / NAND Swap
Your NVMe drive's circuit board is severely damaged and requires NAND chip transplant to a donor PCB
NAND swap onto donor PCB. Precision microsoldering and BGA rework required
50% deposit required; donor drive cost additional
50% deposit required
$1,200–$2,500
4-8 weeks
Hardware Repair vs. Software Locks
Our "no data, no fee" policy applies to hardware recovery. We do not bill for unsuccessful physical repairs. If we replace a hard drive read/write head assembly or repair a liquid-damaged logic board to a bootable state, the hardware repair is complete and standard rates apply. If data remains inaccessible due to user-configured software locks, a forgotten passcode, or a remote wipe command, the physical repair is still billable. We cannot bypass user encryption or activation locks.
No data, no fee. Free evaluation and firm quote before any paid work. Full guarantee details. NAND swap requires a 50% deposit because donor parts are consumed in the attempt.
- Rush fee
- +$100 rush fee to move to the front of the queue
- Donor drives
- A donor drive is a matching SSD used for its circuit board. Typical donor cost: $40–$100 for common models, $150–$300 for discontinued or rare controllers.
- Target drive
- The destination drive we copy recovered data onto. You can supply your own or we provide one at cost plus a small markup. All prices are plus applicable tax.
The full failure-class breakdown & the M.2 and U.2 form factors we work on live on the NVMe recovery overview. Published pricing, free diagnostics, & 4.9 stars across 1,837+ Google reviews back the work, all of it done in-house at a single Austin lab since 2008.
PMIC & Power-Tree Failures: 3.3V to Secondary Rails
The power tree is the first thing that dies in a surge or a hard power loss. The controller is a complex chip with several core domains, & none of them come up without their rail. A single shorted ceramic capacitor can drag a rail to ground, & from the outside the drive looks completely dead.
- PMIC (Power Management IC)
- The chip that converts the M.2 slot's 3.3V into the lower secondary rails the controller & NAND need. A shorted PMIC pulls excess current & runs hot, which is exactly what a thermal camera catches.
- Secondary rail short
- A failed ceramic capacitor on a 1.2V or 1.8V rail drags that rail to ground. The controller domain it feeds never powers, so link training never starts.
- Dead-short signature
- A drive that draws zero or pulls a hard short on first power is a power-tree fault, not a NAND fault. The fix is on the board, not in the data.
The bench sequence localizes the fault before anything gets desoldered:
- Current-limited power-up. Apply 3.3V through a bench supply with a current limit so a dead short can't spread, & read the draw. A hard short shows immediately.
- Thermal localization. With injection current on the shorted rail, a FLIR thermal camera shows the failed part as a hot spot, the PMIC or a specific capacitor.
- Component replacement. Replace the shorted PMIC or capacitor with a Hakko FM-2032 on its FM-203 base, with an Atten 862 hot air station for the surrounding parts.
- Rail verification. Confirm each secondary rail reads its target voltage, then retry the link. A revived controller trains & enumerates with its keys intact.
None of this is platter work, so none of it needs a cleanroom. NVMe recovery is electronics on an ESD-safe bench: microsoldering, BGA rework with a Zhuo Mao station, & thermal fault-finding. Board repair on an encrypted NVMe drive is the recovery, because only the original controller can decrypt its own NAND.
PCIe Differential-Pair Damage From ESD & PCB Flex
The PCIe link rides on differential pairs: matched trace pairs that carry the high-speed TX & RX signals between the controller & the host. They are tuned to tight tolerances, & they are fragile. Bend an M.2 board over a misplaced standoff, or hit it with static during a careless install, & you can sever a pair.
When a pair opens, link training fails at the physical layer. The controller can be perfectly healthy, the power tree intact, & the drive still vanishes from BIOS because one signal path is broken. This is an electrical break, not a logic fault, so no firmware tool will see it.
The repair is microscope work: trace the broken pair, rebuild the open conductor, & restore the matched geometry as closely as the board allows. Then retry the link. Where the break is a partially severed pair, forcing a single lane often gets a usable link even before a full trace repair.
Reading exactly where the link stalls, in Detect, Polling, or a Recovery loop, is a separate diagnostic discipline. The state-machine analysis & the forced-x1 link-training method are covered in depth on our NVMe PCIe lane diagnostics page. This page stays on the hardware fault that causes those stalls.
How the PC-3000 Portable III Images a Degraded Controller
Once the board is repaired, the drive still has to be imaged without re-stressing a controller that just came back from the dead. A motherboard slot is the wrong tool for that: it forces the fastest link the drive advertises & gives a fixed power feed.
The PC-3000 Portable III acts as its own PCIe Root Complex, separate from the motherboard, & takes control of the electrical relationship with the drive. It caps the negotiation at x1 lane width, steps the link speed down toward Gen1, & controls power delivery so a degraded controller holds a stable connection it could never sustain in a normal slot. A slow link that holds beats a fast link that collapses.
From that controlled link, the lab reads the controller's identity, confirms the NAND geometry, & images sector by sector through the original silicon. Because the original controller is doing the reading, it decrypts & descrambles its own NAND on the way out. Imaging coverage on NVMe spans the Silicon Motion, Phison, & Marvell controller families that PC-3000 SSD supports, with examples including the Silicon Motion SM2262EN. Coverage varies by exact controller, so we confirm it during the free evaluation.
The full LTSSM stall analysis behind that forced-x1 link, in Detect, Polling, or a Recovery loop, is detailed on the PCIe lane diagnostics page.
Can a Dead NVMe Controller Be Replaced to Recover Data?
Controller failure & NAND failure are different problems. A dead controller, killed by a shorted rail or a fried core, is a board-repair job: bring the original silicon back so it can read its own NAND. NAND failure, where the cells themselves degrade past the error-correction threshold, is a different path entirely.
Not every consumer NVMe drive runs hardware AES. Many budget DRAM-less drives don't encrypt at all. Even on those, reading the raw NAND off-chip means undoing the controller's XOR data scrambling & its LDPC error correction, which is its own wall. Either way, the original controller is the key, & reviving it beats chip-off.
When the controller die really is destroyed & the part is old enough to be unencrypted, chip-off onto a donor PCB is the last resort. That deeper treatment is on the chip-off NAND recovery page, & the broader physical-damage failure classes are on the SSD physical damage page.
Why You Must Stop Powering a Dead NVMe Drive
TRIM is a logical deallocate, not an instant physical erase. The operating system tells the controller which blocks are no longer needed; the controller unmaps them from its translation table & returns deterministic zeros (DZAT) when those addresses are read, then garbage collection erases the physical cells afterward. On a drive failing on the host link, those queued operations can still run when power returns, which is how a recoverable drive becomes an unrecoverable one.
The electrical risk compounds it. A board with a shorted rail draws fault current every time it powers, & that current can carry a single failure into nearby components. The safe move is to stop, pull the drive, & let the first power applied at the bench be current-limited, with the link coaxed up by a PC-3000 Portable III rather than a motherboard chasing the fastest negotiation.
The Lab Sequence for an Electrically Dead NVMe Drive
The sequence runs electrical-first, cheapest test before anything irreversible. Every step happens on an ESD-safe bench with the drive off any production host.
- Power-tree triage. Apply 3.3V through a current-limited supply & read the draw. Zero draw or a hard short points at a dead PMIC or a shorted rail before any link attempt.
- Thermal fault localization. Inject current on the shorted rail & find the hot component with a FLIR thermal camera, the PMIC or a specific capacitor.
- Differential-pair inspection. Where the rails are healthy, inspect the PCIe TX & RX pairs under a microscope for a sever from PCB flex or ESD.
- Board repair. Replace the shorted PMIC or capacitor & rebuild any broken pair with a Hakko FM-2032, Atten 862 hot air, & Zhuo Mao BGA rework, then verify the rails.
- Controlled-link imaging. Connect a PC-3000 Portable III, step the link down to a stable state, read the controller identity, & image through the original silicon so it decrypts its own NAND.
- Firmware path if the handshake fails. If the link trains but the controller never asserts ready, reconstruct the system area with PC-3000 SSD before imaging.
Data Recovery Standards & Verification
Our Austin lab operates on a transparency-first model. We use industry-standard recovery tools, including PC-3000 and DeepSpar, combined with strict environmental controls to maintain drive integrity. This approach allows us to serve clients nationwide with consistent technical standards.
Open-drive work is performed in a ULPA-filtered laminar-flow bench, validated to 0.02 µm particle count, verified using TSI P-Trak instrumentation.
Transparent History
Serving clients nationwide via mail-in service since 2008. Our lead engineer holds PC-3000 and HEX Akademia certifications for hard drive firmware repair and mechanical recovery.
Media Coverage
Our repair work has been covered by The Wall Street Journal and Business Insider, with CBC News reporting on our pricing transparency. Louis Rossmann has testified in Right to Repair hearings in multiple states and founded the Repair Preservation Group.
Aligned Incentives
Our "No Data, No Charge" policy means we assume the risk of the recovery attempt, not the client.
Technical Oversight
Louis Rossmann
Our engineers review all lab protocols to maintain technical accuracy and honest service. Since 2008, his focus has been on clear technical communication and accurate diagnostics rather than sales-driven explanations.
We believe in proving standards rather than just stating them. We use TSI P-Trak instrumentation to verify that clean-air benchmarks are met before any drive is opened.
See our clean bench validation data and particle test videoFrequently Asked Questions
Why is my M.2 NVMe not detected in BIOS after a power outage?
Does a shorted NVMe drive stop the whole PC from booting?
Can I recover data from an NVMe drive with a cracked or bent PCB?
Can a dead NVMe controller be replaced to recover the data?
How much does dead NVMe board-level recovery cost?
What is the PC-3000 Portable III and how does it differ from a motherboard slot?
Can chip-off read the NAND and skip a dead NVMe controller?
What does the free NVMe evaluation cover?
NVMe drive dead or missing from BIOS?
Free evaluation. We localize the shorted PMIC or severed lane with a FLIR camera, repair the board, then image through the original controller with a PC-3000 Portable III. Board-level recovery from $600–$900. No data, no fee.