SD cards are notorious for this, but the contributing factors could be: bad batteries being used, bad habits of depowering, bad programming (see below) or programming in SAN DIEGO with the A/D patch problem could contribute to firmware chip being filled with read/writes, until full reset is necessary (which was originally noticed in the BCD396t P25 decode threshold auto-adjusting until memory chip was full from read and writes).
Or there could be some character you are using the scanner has trouble interpreting, check programming for characters improperly displayed ~, |, [,{,},] or not displayed at all thats corrupting the memory.
Under powering/improper grounding could also cause memory corruption problems, too.
Besides, every time this has popped up, here on the forum, 1 of the previously mentioned 5 things were the contributing factor and all are at least, partially mentioned in the user manual, so you have heard from Uniden on the issue.
FAT32 for cards larger than 2gb, with a 32 kilobytes as the sector size