USB SanDisk 3.2 Gen1 drive reports “USB memory doesn’t exist” and fails low-level format due to permanent hardware failure.

I have a SanDisk 3.2 Gen1 USB drive (57 GB) that has suddenly become unusable. Windows DiskPart and other tools report “Data error (cyclic redundancy check)” when attempting to clean or create partitions. Low-level formatting tools fail immediately with Device I/O errors at offset 0.

Using a USB identification tool, I confirmed the controller is recognized (VID 0781 PID 5597), but the controller part number is unknown, indicating it cannot detect the internal NAND flash memory. The drive now reports “USB memory doesn’t exist,” which is a clear sign of permanent hardware failure.

I’ve tried all standard recovery steps including clearing read-only attributes, repartitioning, formatting, and low-level format tools, but the USB remains inaccessible.

Is there any firmware update or recovery method available? Or is this drive permanently damaged and requires replacement?

The Information:

Description: [D:]USB Mass Storage Device(USB SanDisk 3.2Gen1)
Device Type: Mass Storage Device

Protocal Version: USB 2.10 ← Hint: This device can run faster when plugged to a USB3.0 port
Current Speed: High Speed
Max Current: 224mA

USB Device ID: VID = 0781 PID = 5597
Serial Number: 0401AD7E7030246299F784F850B6600432614425BAAF662FD23B66C3339012434957000000000000000000003B2A6AB7FF0406189755810721B2FB50

Device Vendor: USB
Device Name: SanDisk 3.2Gen1
Device Revision: 0100

Manufacturer: USB
Product Model: SanDisk 3.2Gen1
Product Revision: 1.00

Controller Part-Number: Unknown

@PlaterMan

Have you checked our knowledge base articles?
( Get Support for Your SSDs and Flash Products | Sandisk )

Try these.

Yeah, checked the website—nothing works. Also heard that they don’t release official firmware to consumers. So yeah, it needs a fix, but only by the officials.

About:

Cruzer Glide 3.0 64GB SDCZ600-064G BN2501002391W Made in Malaysia

Honestly, the drive is dead. All software tricks on my part: Removing read-only attributes, repartitioning, and a low-level format have failed. Where the hardware itself won’t even allow a low-level format, we know the internal controller is shot, or the memory has simply reached its physical maximum. There is no correcting software for a hardware death, and into the trash it goes. Hope you didn’t lose anything ?

Did you figure it out? The CRC error that you saw usually indicates that a storage device contains corrupted or unreadable sectors, which prevents the system from accessing data properly.

If the USB drive can still be accessed, it’s best to recover your important files first using data recovery software before attempting any repairs. This step is important because some repair utilities may modify the file system or overwrite existing data, which could make data recovery much harder or even impossible.

After successfully recovering your data, you can run CHKDSK (Check Disk) in Windows to scan the drive for logical file system errors. CHKDSK may try to retrieve information from damaged sectors and then mark those sectors as bad so the system will avoid using them in the future. However, keep in mind that this process cannot fix the underlying physical damage on the drive—it only helps reduce future read errors. Read also: How to fix data error cyclic redundancy check and recover lost data?

No, fortunately I did not lose anything important. The device was only a bootable USB drive containing a Linux distribution. I have already purchased another USB drive, so it is not a significant issue. However, I believe the original USB drive may be permanently bricked.