Solving a Conflict Between Cache Manager and Memory Manager

My company recently moved several Windows NT 4.0 servers to multiprocessor machines. Now we're finding more corrupted files than usual—especially during peak usage. Any idea what the cause might be?

This problem is probably the result of a conflict between the Cache Manager and the Memory Manager. The problem worsens when you enable write-back cache in BIOS. The solution involves trial and error. First, disable write-back cache (you'll simply need to accept the performance loss). Also, be certain to use NT 4.0 Service Pack 5 (SP5) or later (I prefer SP6a). If the problem persists, try using Windows 2000 Server; Microsoft has improved thread management in that OS.