Audio Driver bit depth is controlled by the device... like my RME works at 24 bit... ALL THE TIME. It never gives 16 bit data...
Now, that said, I can choose to use that 24 bit feed to write 16 bit files.
Under Preferences > File > Audio Data... you can pick the bit depth of the files you wish to write. If you write 16 bit files then you are throwing out the additional bit precision that you are getting from your interface but you get the benefit of writing less data per track to your hard drive.
I choose Record Bit Depth of 24 bits at the level and Render Bit Depth of 32 bits. Now... when I used an old laptop, I used render bit depth of 24 bits because otherwise I would have trouble reading and writing the number of tracks I required. For most of us, there is no advantage to using a
Record Bit Depth of 32 bit if your interface only works at 24 bit.
13 Milliseconds of latency -- that you report -- is a fair amount. It suggests that your Sample Buffer is pretty high which is appropriate when troubleshooting. My understanding is your still having trouble with dropouts, so sticking with high buffers until you get this worked out is a good idea.
You should be able to rule out hard drive trouble by decreasing your File Audio Data write size (described above). This should remove pressure from the drives. It's a useful step in troubleshooting. It's not sure to help, but it might.
When I use Latency Mon on my computer
http://www.resplendence.com/latencymonMy worst reported driver is tcpip.sys (I'm streaming a Craig Anderton Video) is 0.17ms. I recommend you give this tool a try and see what your worst reported is...
I hope this helps. BTW, I'm pretty sure I've typed a response very close to this one to you in the past. I'm not being redundant because I'm forgetful. I'm being redundant because I'm hopeful it will help.