In general such corruption happens when the driver is interupted saving changes to the file system.
That can happen, for example, when a high priority thread consumes all cpu times. It may also happen, when the device is hard reset, for example by taking the battery out during thed river is writing to the file system.
A low battery normally cannot result in that corruption: a) as the device shuts down itslef with critcal battery power and b) the file system is in flash RAM (in contrast to Windows Mobile 2003 and before) and does not need battery power to hold data.
It is also possible that there is a bad behaving process doing these corruptions.
As you say you see this only in one city: What is the main difference with the devices there? Are others also using the same device? Maybe the device series itslef or there firmware is faulty (contact symbol/motorola for new firmware or patches to the 'disk' driver) Are the users in that area doing special things to the devices that others do not? For example remove the battery when they mean the device does not react? Is the MC75A used in other areas and there it does not show the corruption?
You see, you have some more items to examine a rule for the corruption?