Yeah. Texture spooling is what I meant. It depends. The default seems fine and doesn't drive up the paging file. I have noticed the paging file can go up alot and not back down when this is set high especially if using high textures and working on a render for awhile. This is not conclusive tho and will depend on real ram amts. Scratch disk in the same area might also play into it. How big it is. If you are running out of room that could be a problem. The cpu will be used no matter what tho. Watching the commit charge can be of benefit to see how performance is going based on these other settings also. If you have a charge higher than the actual ram for instance that already means you are giving it a work out. In theory it should just chug on tho, but much slower. I think seamless is a better idea for tiling and interpolation may help if the scene is pushing things. If you try that and don't get anywhere I would report it because it could likely be a bug.  It's possible a seam at a particular camera angle could be causing a rendering issue. Based on what was said and the error message seems like a bug to me, but it is different if you are really pushing something...we all know how that goes. Reporting these things is how they find bugs.

No need to think outside the box....
    Just make it invisible.