If you're absolutely sure it's not related to load order or compatibility between mods, you may be hitting your VRAM's limit. There, you'll start seeing floating grass in the wilderness, interior spaces and generally in places where it shouldn't be. Shortly after, the game will either freeze, or outright quit.

If your game is heavy on texture replacements/mods, this is where ENB comes in. It cooperates quite nicely with Sheson's/SKSE's memory tweaks. If you don't want to use the graphics enhancement part, open enblocal.ini, find UsePatchSpeedhackWithoutGraphics=false, change it to true and save it.

Now: Because Skyrim doesn't really like getting pushed beyond it's limits, you may still get the odd silent crash, every 4-6 (maybe even more) hours of gameplay.

Hope it helps

Holy crap... Nothing in this entire thread has anything to do with what I asked.

I specifically wanted to know (and apparently nobody does know) if not hitting the block limits meant that the crash wasn't due to texture mods.

This thread was supposed to be about the memory patch and the kinds of crashes it was meant to fix, and what kinds of things can be deduced from the memoryblockslog.log file. Not uGrids or load orders or any of that stuff. There are hundreds of threads about the common causes of crashes; this is not meant to be one of them.

The memory patch increases the buffers the game uses to load up objects, npcs etc. How much VRAM is used to display them, is system related. Also, the game is x86 (32bit) and even though it is large address aware, it will crash when it reaches 3.2GB of RAM usage. When the game crashes and memory blocks log doesn't indicate capped buffers, it can be due to the RAM cap (heavy texture mods), a bad load order, or incompatible mods.

A good read about the memory patch, is http://enbseries.enbdev.com/forum/viewtopic.php?f=13&t=2729 from the author himself, before it was added to SKSE.