I'm wondering, after this initial test, if disabling the video driver is actually required- I've read where Boris recommended it for older 'buggier' drivers (not more recent ones), but this is the lastest one and I have no idea if that's required for 'disabling' texture caching in older versions of DX. He had it set to true by default. If so, it would make that setting required if just buffering textures. It also makes me wonder if it's required to prevent FNV interaction with the graphics driver period, though going through the enb dll should do that or if he's patching something on the 'fly' which disables or NOPs code that would call the 'shadowing' functions.
For this test, I disabled ReduceSystemMemoryUsage=false. I also dropped the 'reserved' vram down to 128mb.
If you notice the ENB settings (enbconfig.txt), with just EnableUnsafeMemoryHacks=true within a very short time (game log at the bottom- game-test.txt), I start getting "out of memory" hits which eventually crashed the game. Up until that point, everything seems to be working ok for about 7+ hours of testing.
This might be because of I didn't disable the graphics memory driver also, but last time I tested that particular feature (just a few weeks ago), I picked up a slight performance hit; so I opted to use the newest video driver for my card (NVidia GTX 1060 6g- it's fairly modern so the driver should be relatively good). Using MSI Afterburner (which doesn't cause a problem for me, at least from what I've been able to tell- no crashes in countless hours using it on FNV unless caused by bad or missing assets or memory issues), the total ram usage never really goes over 2.5+ or so gb with the highest hitting around 2.9gb.
Let me switch back to ReduceSystemMemoryUsage=false and give it another quick test run. Windows just updated a day or so ago and it couldv'e caused a problem with one of the existing memory 'tweakers'.