CTD at 3.1GB

[viking]

Some key posts on this and related threads (experts feel free to note any errors or insights):

• Post #11
• Post #27
• Post #40 (this is where the 500/430 ratio seems to have originated.)
• Post #66
• Post#278
• Post #313
• Post #1 (adjacent thread: Caution about memory optimisers)
• Post #64 (adjacent thread: Caution about memory optimisers)
• Post #68 (adjacent thread: Caution about memory optimisers)
• Post #70 (adjacent thread: Caution about memory optimisers)

Wiki article (draft)

 

Thanks,

STEP

 

OP follows

---

First of all I wanted to thank you all for the great work you have done with STEP. Skyrim is the first game I installed on this computer and you guys have made it an AMAZING game. That being said, I have an issue that I hope you can help me solve.

 

My setup:

Vanilla Skyrim

gtx670 w/ 4GB @1080p w/ latest driver

16GB Memory

3770K at about 4GHz

Windows 8 64bit

ENB 149

Ultra settings

Highest available texture/quality

Mod Organizer

Step 2.2.1 + Skyrim Revisited + others

 

I have noticed a post here and there saying that Skyrim can't really address more than about 3.1GB of memory without issues. This seems to jive with my experience, meaning I CTD every time my memory hits that mark, but I couldn't really find anything definitive on the topic. The issue with googling the topic is the pre 1.3 skyrim that couldn't address more than 2gb of memory.

 

My mod list is mostly based on STEP which is why I came here for help, with about ten mods added onto the end (Interesting NPCs, Detailed Cities, Economics, COT, and a couple others). The reason I haven't included my mod list is that it doesn't seem to matter. As long as I keep the memory usage below 3GB I can have pretty much any combination of mods.

 

What I have tried so far (in no particular order):

• resetting ini files
• removing enb
• not using attklt
• only using a new game
• removing all mods and adding one by one until issue crops up
• running as admin
• watching the papyrus log - it seems relatively clean, no obvious errors right before CTD

Yes, I can run STEP just fine without any issues, but I also never get near 3GB of memory. I have tracked VRAM usage as well and have seen a max of 2.7GB/4GB.

 

As an example of where I might run into issues: I start a new character with Alternate Start. I start with Breezehome. Run out of Whiterun, past the Brewry, up the hill to the bandits. Enter the cave (watching memory usage with Elys MemInfo), and it dies right after I see 3GB. I have this same issue not using AS, sitting through the intro, and then running over to whiterun.

 

I'm sorry if this post is all over the place. I have spent more than a week trying to solve this issue, and the only solution I have found is to reduce memory usage. I have got to the point where I can exchange two texture packs and get into the cave without a CTD, but with both I get a CTD. I didn't even think texture packs should even affect CTDs, but I'm relatively new to Skyrim on the PC, so I could be wrong. I also found I could get a bit further with ENB turned off, but would still crash once I got above 3GB of memory. Finally, if I reload a game after a CTD, I can play just fine...until I reach 3GB of memory.

 

I really hope you guys can help. I more than willing to try anything at this point, besides just disabling all of the mods.

[exploiteddna]

Maybe for a SLI 4GB rig this enb would be a possibility...

i could test it out, but not sure my results will be any different. im currently running the 13.7.13 enb binary for personal use so it would be really easy to swap in the 192 binary. maybe tomorrow..

[WilliamImm]

I've tested it out. RAM usage is lower, yes, but VRAM usage is much higher - 2900 something with the new ENB, and 2300 without (SR:LE install). Also, it doesn't look quite right with the ENB I'm using (Unreal Cinema).

[Neovalen]

0.192 is still very beta... Boris is putting out test DLL every few hours.

[Aiyen]

Posted by DanimalTwo: I think it is too soon to tell if this is worthwhile. I know Boris is looking for people to help debug and your are a good candidate. Around these parts you seem to be the expert with regard to ENB. Of coarse I do not want to volunteer you. He seems to be doing it in real time, thus the many updates.

I contribute a small bit, but only with matters that nobody else seems to be reporting. I always found it silly to flood a thread by saying "I have the same issue", unless the case warrants more results. So far the only thing I noticed that others do not seem to have is some micro stuttering. But I guess this is to be expected with all the increase in moving stuff around memory. 

Maybe for a SLI 4GB rig this enb would be a possibility...

Not really since VRAM is not doubled by SLI. One card is the way to go for ENB. However you are right that more VRAM would help. 

[exploiteddna]

haha yeah i wish it did double vram :) Not that i could use 8gb in skyrim anyways, but still

[torminater]

Maybe for a SLI 4GB rig this enb would be a possibility...

Not really since VRAM is not doubled by SLI. One card is the way to go for ENB. However you are right that more VRAM would help. 

 

You misunderstood my point.

I get microstuttering and FPS drops using the 1.92 as well. And that is without using any of the high-end graphical enhancements enbs usually have to offer. If I implemented those as well, my framerate would probably go black hawk down. Therefore I'ld need the extra processing power of a second GPU to keep my FPS stable enough.

[Neovalen]

Using Unreal Cinema with 0.192 (latest as of 5 minutes ago) and I'm seeing noticible differences in RAM/VRAM usage. No stutter and I haven't had a CTD yet (give it time...).

[torminater]

Using Unreal Cinema with 0.192 (latest as of 5 minutes ago) and I'm seeing noticible differences in RAM/VRAM usage. No stutter and I haven't had a CTD yet (give it time...).

How exactly did you do that? Have you just replaced the dll file or also made changes to the enbseries.ini?

[exploiteddna]

would have to make changes to the ini. or else a lot of the new parameters that didnt exist in the original binary (dll) that was used for Unreal will just automatically default to 1. You could load up the original ini with the new binary, have it default all unspecified parameters to 1, which will then add those parameters to the ini for you, then exit the game and tweak the new parameters to match the preexisting ones.

[torminater]

Jeez, far too much work for me right now. Gotta prepare for a exam on monday. @ Neo: could you upload your 1.92 tweaked ini somewhere so I could compare the performance on a single gpu setup?

[exploiteddna]

Jeez far too much work for me right now. Gotta prepare for a exam on monday. @ Neo: could you upload your 1.92 tweaked ini somewhere so I could compare the performance on a single gpu setup?

yep i hear ya. no exams for me until august 1st but def have term papers due. ugh.

[Aiyen]

Just send me a PM with what you need... most likely got it laying about. :)

Edit: ENB related anyways :P

[torminater]

Well... apparently Boris got sick of coding yesterday and just deleted all files of 1.92 on his server. Let's see if a good night sleep doesn't restore his motivation to continue his work.

[EssArrBee]

I guess Boris found out what was wrong and uploaded v193. I just saw Phinix Natural in my updated files and noticed it it is using the new version, that was quick.

 

I'm going to try it out see if works.

[EssArrBee]

So after playing around a bit, I think that Boris worked out most of the issues and my VRAM is now higher than system RAM by quite a bit. 700 MB in some places. There is a performance hit, and I experienced around 10 FPS across the board while outdoors, but running around Dragonsreach seemed to be okay.

 

In SPM my chart showed something that was very good and that was the consistent drops in both RAM and VRAM when going through a load door, especially when going from a city space to the Skyrim worldspace.