SD Card Write Exception A1

Las SD son de corta vida y dan problemas si escribes y borras constantemente, solo te durarán menos de 6 meses.

Las SD hay que escribir y leer, no borrar, llenarlas hasta el máximo de su capacidad antes de borrarlo todo o casi todo y repetir el ciclo.

Saludos.

I am also having the same issue. Sandisk SD card that I have used since day 5 of owning this printer. The issue has only been occurring since I updated to the newest release of Bambu Studio ver 2.1.1.52. I have power cycled the printer to no avail. I still have the crappy SD card that came with the printer and can use that in the meantime but it looks like I may have to roll back to an earlier version of Bambu Studio.

Hello.

You need to find out how to use SD and micro SD cards.

These SD cards are for reading and writing, not erasing.
Write to them until they’re completely full and only then erase everything you don’t need at once. Don’t write and erase daily, because repeated erasures damage the card.

Also, always use “eject card” before removing it from the PC and printer. The printer also has an “eject card” command.
If you don’t do this, SD cards will last less than 3 months.

If you have problems, format the SD card from the printer’s control panel, not from the PC.

Best regards.

I am not a novice at using SD cards and my card was far from full.

I find your response to be slightly belittling.

Not sure if this is still causing any issues for others, but I had the same problem this morning - started randomly getting the MicroSD Read/Write Exception error and couldnt get rid of it.

For me - I ended up using the printer to Format the SD Card, then I shut down Bambu Labs completely and started it up fresh. After that, I sent a quick print through and it seems to be working again for me now.

This is still an issue which can occur. My A1 has approx 1100 hours printing time on it and two weeks ago it started throwing this same error at me. I thought nothing of it since it was still the OG microSD that came with the printer and ordered a Sandisk High Endurance microSD card to get rid of this nuisance once and for all. Here we are … two weeks later .. the error is back!

I never bothered to check the OG microSD until now - it still works fine when inserted into my PC. Throwing a testing tool at it to find bad sectors and stuff - so far not a thing wrong with it.

Afterwards will test the Sandisk too, but my gut feeling is that this is not a SD card issue.

Just got this error today on my A1M. Formatting the card, reinserting the card, power-cycling all accomplished nothing.

Just a small followup on the board replacement…

I haven’t had any issues since, all is good.

Hi,

I have the same feeling. I replaced the original with a SanDisk Ultra, and it gave me this error. About a month later, I had the same error with another new SanDisk. It seems like the card is not the problem. BUT once I got those errors, both cards became useless.

Started getting this i/o error on my 3 day old A1 combo with factory sd card (32gb). Some notes on what i observed so far:

  1. printer is running latest fw 1.08.01.00. Newly installed bambu studio.

  2. I had several good prints, slicing makerworld with bambu studio (using send option). ranging from 1 to 10 hrs. total print time is now 28 hours.

3) The first i/o error occurred almost immediately after I naively hit the back arrow on the print status screen while printing 5 hours into a 10 hour print (did not pause first). I was just curious what the arrow was going to show, hoping for some deeper stats or something. Back arrow was enabled, so I was confident it was not a bad thing to do. An even more brain-dead screen appeared with minimal info about the job, THEN THE CRASH.

  1. I resliced the model, after changing the infill patter to lines (cut print time by an hour), but send to printer kept failing with useless error message.

5) I pulled the card and put it in Win 11 PC. Was surprised to see it nearly 75 percent full.

  1. I ran a disk check and it found errors and corrected them.

  2. I then deleted the useless low quality recordings from recording and camera folders, and deleted a few print files that I no longer needed. I also deleted the CHK files created by the disk check repair. (many of them)

  3. I put the card back in the printer, and resliced the job, and resent. (send now worked)

  4. I disabled all camera recording options, hoping to reduce the write i/o load.

  5. I restarted the resliced 9 hour print. Got i/o error after a few layers.

  6. I pulled card and put back in pc. Ran H2testw.exe to do deeper analysis. Got: Error writing file ‘J:\9.h2w’, offset 0x9d00000.
    Writing speed: 8.64 MByte/s
    H2testw v1.4

  7. I decided to reformat the card in the PC, since it would no longer mount at all (until formatted), so i just went ahead with an exFAT format (With Quick Format UNCHECKED-I wanted full sector testing and bad sector repair), knowing I would need to reformat again in the printer back to FAT32.

  8. Interestingly, the 32GB card shows up with capacity of 64GB in the format USB drive window!!! Most likely a totally corrupt partition table using 64GB as a default. Copilot AI says this might be a sign that the card was actually SMALLER that 32GB and actually DID FILL UP due to the massive camera recordings. (a counter-fit card shipped in a new Bambu printer???)

  9. format failed. card is toast.

  10. Using a 8gb card i had. formatted in printer. so far so good.

y A1 regularly kills microSD cards in just a few days of normal operation.

The original microSD card that came with the printer worked fine for less than a week, and then suddenly stopped being recognized. After that, neither the printer nor the computer could see it.

After that, I tried several other cards—4 GB, 8 GB, and finally a not-so-cheap 64 GB Kingston Canvas Select Plus microSDXC—and it failed in just 2 days.

Important point: initially, each card worked normally. I successfully printed from each of them for a certain period, and then the card became completely unreadable. The failed cards are no longer recognized by either the A1 or any computer/card reader.

I understand these are not High Endurance / Max Endurance class cards. However, I do not think it is normal for a regular microSD card to physically fail after only 2–7 days of normal operation with the printer. I have already had four cards fail in this exact printer.

It is hardly a firmware issue, because right next to it sits a slightly smaller A1 mini, which has been working brilliantly almost 24/7 on its original flash drive for over a year.

I suspect the problem might be in the A1’s microSD slot itself, the SD interface, the controller, or the card power supply. There are no power issues with the printer; it is connected through a good voltage stabilizer. Data is transmitted via the cloud by default. Video recording is always disabled. Yes, I have very complex high-poly models, I design them myself. That is exactly why I bought the Bambu as a supplement to my wonderful Elegoo Neptunes—for small, complex models. But still, this is no reason to ruin flash drives!

I don’t know what to do. I don’t want to buy another expensive microSD card and risk destroying it before the root cause is found. Are there any diagnostic methods? I have ruined a lot of filament and lost a lot of time. I am having issues with a client, and I might lose an order because of this. I am desperate…

Turn off power recovery, the early recording thing and the full timelapse recording (sounds like you already have the full timelapse turned off).

Video recording is always disabled. However, I would like to keep “Turn off power loss recovery” enabled. I live in Ukraine, we are facing Russian aggression and a full-scale war, and power outages happen frequently due to enemy bombings. Do you think this feature (Power Loss Recovery) could be the reason why the printer is killing the cards by constantly writing recovery states to the flash drive?

Yes.

But Power Loss Recovery is a standard factory feature enabled by default, not some exotic setting. And the A1 mini right next to it works brilliantly with the exact same settings…