DJenser

I suspect it was mostly mod bloat, although I did make sure the [memory] ini tweaks were all in place & that ENBOOST was running (which it was, given that SPM showed my vRAM running consistently around 1400-1900, but my system RAM was sometimes peaking around 2200-2300, indicating that ENBHelper.exe was indeed doing its thing)... I removed the majority of the LOD & flora mods (I tend not to focus on far-off trees & mountains enough to care about those) along with a house mod I no longer use, started from a slightly earlier save in a smaller interior space inside Windhelm proper, and voila, no ILS... And none since. Load times were also reduced to seconds, instead of minutes. I guess I simply needed to prioritize performance over eye candy, so I kept a few nicer textures on the interior spaces, NPCs, weapons, and armor. The rest will have to wait until my cash reserves are up and my spousal aggro is down enough to upgrade my rig again. (Although, I suspect that 4GB cards will be flooding eBay in the coming months, given that the the new GTX 1080's are priced way lower than Titans were last Christmas.)

After completing my setup of S.T.E.P. Core last night, I have experienced consistent ILS's whenever I attempt to fast travel from my current location near the Windhelm stables to pretty much any other spot on the map. I know they're legit ILS's and not 2 min. LS's because each time, the SPM shows my "disk I/O:" at zero while my RAM & vRAM usage appears to cap out at around their combined 4gb maximum (2gb 750ti/8gb ddr3 system RAM.), and the CPU output locks at a minimum of 25% (Phenom II X4 3.4ghz). All of the textures I've loaded are per recommendations, with none of them higher than 2048, and I have ENBoost running with 768/256 in my Skyrim folder and the latest version of SKSE, which automatically includes Sheson's Memory Patch. I even went in and removed my map mods and deleted several map-related ini tweaks, which many people cited as the culprit in their own ILS's, before finally deleting my Skyrim.ini and SkyrimPrefs.ini (and yes, I have file extensions enabled) and running the launcher to install a fresh set. None of it had any effect. I'll try the block log to see if anything is inexplicably misconfigured, but it's looking like I'm going to have to start uninstalling some of this S.T.E.P. Core eye candy I spent the last several nights setting up, which is a shame, since I was able to run around causing trouble at the docks with a couple followers in tow with only slight frame drops and a single CTD, which is something I've never managed even without a follower. Needless to say, I'll be hanging on to the performance and stability mods, but some of the textures and effects mods may have to go... :-(

So, without those components, Windows 7 treats the VRamSizeDX9.exe as just another 32 bit application, with a max allowable allocation of 4 gigs, despite being 64 bit itself? That would explain why the DX11.exe showed my available RAM in the neighborhood of 10 gigs... I'll do that as soon as I get home. Just another item on a LONG laundry list of things I need to do to get my game running again. Well, fresh OS, fresh start. Now I can reinstall everything properly, starting with SKSE. I copied the mods folder to my desktop so I wouldn't have to hunt them all down again when I reinstall MO, which is going to be a chore in and of itself, since I don't think I have the right version of .NET or Visual C++ redists installed yet either.

Oh crap, I just realized what you meant by that... My fresh install of Win7 would have DX11, not DX9, wouldn't it?

To be honest, I didn't find S.T.E.P. until after I'd made the switch to 10. Of course, that wasn't my only issue with 10... It had an annoying tendency to BSOD occasionally after loading, when it would access my network adaptor during startup, or it would return a "kmode exception not handled" fatality. It wasn't constant, & I figured I'd eventually be able to track down the offending drivers, but when I read that 10 would never use more than 4 gigs of my RAM for Skyrim & other DX9 apps, that was the straw that broke the camel's back.

Fresh install. It was well past the 30-day window.

Hi guys. Quick question... I recently "downgraded" back to Windows 7 64 bit from 10 in order to avoid being shoehorned into 4096GB of available memory, as I have 8GB system RAM and a 4GB 750ti card, but VramSizeDX9.exe still has my available RAM at 4096GB. What gives?