Jump to content
  • 0

CTD after a specific amount of playing time regardless of other variables.


Question

Posted

I am getting a CTD after about 11-12 minutes of play time. The CTD occurs no matter where or what I'm doing. I have tried a lot of different scenarios to see if I could get something I could replicate on purpose but I can't find a common denominator.

 

If I had to compare what I feel like is happening, I'd say its like when I start the game a water faucet starts to drip and as the game runs it drops and drops until the sink overflows and I get a CTD. Lol.

 

Some info about what is happening and what I've tried.

 

Crash occurs indoors, outdoors, with menu up, and even if I just pause the game and wait.

 

I have transported to various regions of the map including the test hall and it still happens.

 

I have waited in-game for various amounts to see if it was like the game clock. (I read about an issue someone else had where the game would crash at a specific time in-game)

 

Running the game with Skyrim Performance Monitor to see some data, none of the numbers match up anywhere across the many CTDs. That is to say, it happens if I'm close to Max VRAM or I have a gig or more left. System memory also doesn't get near max not does CPU%.

 

GPU temp hit 78c bit I see those temps with very intensive games like th Arkham games, Bioshock Infinite, etc. I read the max temp for this card was 110c. So, these temps should be "normal" unless I've misread.

 

The CPU is liquid cooled with Corsair H80i and the case is loaded with Noctua 120mm fans.

 

I am just lost as to what to try and I am hoping somebody may have some insight.

 

 

SYSTEM SPECS:

 

CPU: AMD 8 Core FX-8350 @ 4.7GHz

Maijboard: ASUS Sabertooth 990 FX

System Memory: 8GB DD3-1600 G.Skill Ripjaws (7,8,8,24)

OS Drive: 240 GB Samsung 850 Pro SSD for OS

Gaames Drive: 480 GB Samsung 850 Pro SSD for Games

Programs Drive: 256 GB SanDisk Exxtreme Pro SSD for Programs

Storage drive: 2 x 1TB Western Digital Black HDD in RAID for storage.

GPU: EVGA GTX 780 Classified Edition 3GB VRAM

Operating System: Windows 10 x64

 

Pagefile is 3000 MB (just a note)

 

 

All help is very appreciative.

14 answers to this question

Recommended Posts

  • 0
Posted (edited)

I found the solution and the issue seems to be resolved.

 

Thank you to everyone who helped out. To quickly answer Electrocutor's last question, all the settings matched except EnableOcclusionCulling was set to false. After setting that to true the issue remained.

 

I then started timing how long it took to crash. Skyrim Performance Monitor has a timer so I used it again. After about 6 times the game would CTD at 15.44-15.50

 

Factoring in that the 44-50 seconds was start-up time I cleverly (jk) deduced that the game was crashing at 15 minutes exactly.

 

So, I Googled Skyrim crashes after 15 minutes and the first result had the answer.

 

The crash is related to Windows 10 and the Touch Keyboard and Handwriting service. I don't know if this service just auto starts with a fresh Windows 10 install or not. I definitely use the service with Splashtop Streamer and my Wacom Tablet so the service may have only been in use for me because of the way I use my PC.

 

So, simply going in to task manager, then Services tab, and I sorted by the Description column and found Touch Keyboard and Handwriting, right clicked on the service and chose stop.

 

Since doing this, I've played a few 3 hour or more sessions without an issue.

 

To double-check, I re-enabled the service and the CTD came back. So, I am 100% percent this was the issue. Or, the last remaining issue. I still had some fields wrong in my Enblocal.ini and so forth that all of you helped me iron out.

 

Again, thanks to everyone.

 

I'm marking this solved. All of your answers contributed to the solution and if I could mark them all Best Answer I would. I encourage anyone who finds this thread by searching their issue to read it from beginning to end to cover possible scenarios.

 

 

Edited by vile83r
  • 0
Posted

Your memory blocks may be completely filling up. You may need to adjust the values in skse.ini.

 

Try Memory Blocks Log...install it, and then play until you crash. The log will show your current setting (numbers at the top of the log), and you can see what the memory blocks fill to when you crash (the numbers at the very bottom). If the first block fills up, you will crash.

 

Note that MBL will always show 256MB less than what the setting is in skse.ini. (If first block is set to 768, it will show 512, etc.)

  • 0
Posted

Thanks for responding. I do have that info. Last week I struggled with the issue of getting MemoryBlockLog to recognize the settings set in SKSE.ini. With this forum's help I was able to get it solved by adding the -forcesteamloader argument to SKSE in ModOrganizer.

 

So now, MemoryBlocksLog works fine and has the headers 512/256 and the last entries in the log are 488/178

  • 0
Posted

Lol my mistake. Sorry about that. Your username did look familiar, I just failed to put two and two together.

 

MBL is my autopilot response for CTDs or ILSs if it isn't mentioned in the OP.

 

It could be something such as an incorrect ENB memory setting. It couldn't hurt to post more info such as your enblocal.ini, Skyrim.ini, and SkyrimPrefs.ini.

 

Use spoiler tags if pasting directly in your response.

[spoiler]text[/spoiler]
  • 0
Posted (edited)

No problem. I appreciate the help. Here is the enblocal.ini, skyrim.ini, skyrimprefs.ini, and loadorder as they are right now. The only settings that differ from what is suggested in the SRLE guide is enabling fullscreen borderless window in enblocal.ini. That was another attempt to fix this CTD issue. The issue existed before that change.

 

Other than that, it is as suggested. I was curious about the VRAM amount. In the enblocal.ini file prior to now, that setting was always 3072 since my card is a 3GB card. However, 4064 was the result of the DX9 VMSizeTest which I never used prior to this. Probably not the issue if everyone else is using this method to calculate that value. Just thought I would mention that.

 

I appreciate all your help. If there is another log file or anything that would help, please let me know.

 

I forgot to mention that I usually play 1920 x 1080 but I did try 1280 x 720 and got the same CTD.

 

 

ENBLocal.ini

 

 

  Reveal hidden contents

 

 

Skyrim.ini (from SRLE ModOrganizer profile)

 

  Reveal hidden contents

 

 

Skyrimprefs.ini (from SRLE ModOrganizer profile)

 

  Reveal hidden contents

 

 

Loadorder

 

 

  Reveal hidden contents

 

 

 

EDIT: I misspelled spoiler in the first tag. Embarrassing.

Edited by vile83r
  • 0
Posted

The DX9 VRamSizeTest is correct. The advantage of the ENB memory workaround is that it can utilize your system RAM as well as VRAM, so the higher number makes sense...something would be wrong if it was lower than the actual videocard VRAM amount. The value given by the test is limited to 4064MB due to the fact that you are using Windows 10. Windows 8 and up are capped at 4GB of VRAM use in DX9, due to a Microsoft bug that they don't seem in a hurry to fix.

 

However, for VideoMemorySizeMb it looks like you forgot to subtract the amount for background processes based on your OS. Try using 3714 instead. Also, for ReservedMemorySizeMb, did you try turning around 360-degrees in-game until you experienced stutter, per Neo's recommendation? If you can lower this amount without experiencing stutter, it will be beneficial, as that value is VRAM that cannot be used for anything else.

 

Besides that, I am not sure. I didn't even look at the load order, as I am not very familiar with SR:LE.

  • 0
Posted

Is this happening with a new game or when loading a save? The reason I ask is because this is known to happen when loading an autosave or a corrupted save.

  • 0
Posted

Nebulous, thanks for the suggestions. I haven't tested it yet but I will update when I do.

 

Greg,this is a new game. I did try a couple old saves. They were saves after doing a “cleaning in the Test Hall" and they loaded and played but it also CTD after the same amount of time.

 

I tell ya, SRLE is really difficult to pinpoint if its a mod causing the issue. So many of these mods rely on so many others. I can't just disable them one at a time and test.

  • 0
Posted

Try doing it the other way around. Go back to all but no mods and then add a section at a time. Start game, see if issue.

 

Rinse/repeat till you find the section that causes your issue and then drill down.

  • 0
Posted

I made the changes suggested by Nebulous and I still ended up with the same CTD. I think starting with vanilla and adding chunks at a time is a good method to try going forward.

 

Before I start that, I was wondering if anyone could possibly make sense of a Papyrus log? I enabled Papyrus logging and upon viewing the results I see the word "error" a lot! And, a script issue may make sense since all the other testing of vram usage, cpu usage, etc all come back fine.

 

The log is difficult to read because the formatting is terrible. Using Notepad++ helps the formatting quite a bit. I happened upon a utility on Nexus called Papyrus Log Viewer that does an outstanding job of organizing the log. If interested here is the link to that utility on Nexus https://www.nexusmods.com/skyrim/mods/42815/?

 

The Papyrus.log is almost 4MB so I cant attach it here and its way too long to post in-body even with spoiler tag. So I am providing a link to the file on my google drive which is https://drive.google.com/file/d/0B-asu3UJkcUXRklfTXo0WS1pZzQ/view?usp=sharing

 

 

Here is just a quick screenshot of the log opened in Papyrus Log Viewer. I see a lot of errors, especially regarding esp files that aren't loaded even though they are activated in MO and activated in the game via MCM. In Papyrus Log Viewer when you click on the error message, more info is presented in that bottom pane.

 

Maybe something here is the key to my issue.

 

Thanks again for all of your help so far.

 

 

 

 

 

  • 0
Posted

Typically Papyrus logs aren't very useful for finding problems. They're full of data from various mods that are not usually significant errors, and anabling the writing od Papyrus logs can cause problems as these interfere with other processes in the game engine. Sometimes noticing a pattern in the last problem written in the logs can be helpful, but otherwise I haven't found them very useful.

  • 0
Posted (edited)
You have these settings now, right?
 
  Reveal hidden contents
{ enblocal.ini }
[PERFORMANCE]
EnableOcclusionCulling=true
 
[MEMORY]
VideoMemorySizeMb=3714
 
 
 
{ skse\skse.ini }

[General]

ClearInvalidRegistrations=1

 

[Display]

iTintTextureResolution=2048

 

[Memory]

DefaultHeapInitialAllocMB=768

ScrapHeapSizeMB=256

 

 

Edited by Electrocutor
  • 0
Posted
  On 2/7/2016 at 2:58 AM, vile83r said:

I found the solution and the issue seems to be resolved.

 

Thank you to everyone who helped out. To quickly answer Electrocutor's last question, all the settings matched except EnableOcclusionCulling was set to false. After setting that to true the issue remained.

 

I then started timing how long it took to crash. Skyrim Performance Monitor has a timer so I used it again. After about 6 times the game would CTD at 15.44-15.50

 

Factoring in that the 44-50 seconds was start-up time I cleverly (jk) deduced that the game was crashing at 15 minutes exactly.

 

So, I Googled Skyrim crashes after 15 minutes and the first result had the answer.

 

The crash is related to Windows 10 and the Touch Keyboard and Handwriting service. I don't know if this service just auto starts with a fresh Windows 10 install or not. I definitely use the service with Splashtop Streamer and my Wacom Tablet so the service may have only been in use for me because of the way I use my PC.

 

So, simply going in to task manager, then Services tab, and I sorted by the Description column and found Touch Keyboard and Handwriting, right clicked on the service and chose stop.

 

Since doing this, I've played a few 3 hour or more sessions without an issue.

 

To double-check, I re-enabled the service and the CTD came back. So, I am 100% percent this was the issue. Or, the last remaining issue. I still had some fields wrong in my Enblocal.ini and so forth that all of you helped me iron out.

 

Again, thanks to everyone.

 

I'm marking this solved. All of your answers contributed to the solution and if I could mark them all Best Answer I would. I encourage anyone who finds this thread by searching their issue to read it from beginning to end to cover possible scenarios.

 

attachicon.giftmp_32287-rsz_winservices-821126859.jpg

That is an excellent piece of deductive work on your part! Kudos to you.

So yet again another Windows "service" ends up being a "not of service", more of a hindrance.

  • 0
Posted

I am just so happy to get it resolved. I have no idea why that service would cause that to happen. Thankfully that service didn't seem to interfere with Fallout 4 at all. I've put a lot of hours into that game and haven't had an issue yet.

 

Happy to be playing Skyrim again tho.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.