that’s not normal, so you must check with your vendor if there is an history about such a problem.
when the MS is in a neighbour cell, verify that this faulty cell is in the System Information message SI5 / SI5ter. (trace layer 3 in drive test tool)
check the BCCH for that faulty cell is correctly encoded in the SI5/SI5ter.
Force the MS to camp on the faulty cell, thanks to your drive test tool (it probably provides such an option, doesn’t it ?)
do you notice anything particular ? BSIC is well decoded ? in the SI messages, do you see correct values for reselection parameters ?