Skyrim freezes after cleaning up crashing issues

[inglorious89]

Recently I went through getting ENBoost and some other stability mods for Skyrim going to fix an issue I've been having for awhile: Skyrim CTDing every 5 minutes. Luckily for me, the CTDs have (for the most part) stopped. Unforunately, a new issue has appeared: Skyrim keeps freezing. Where is freezes is usually outside cities where there are a lot of NPCs around, although exact times are random. Sometimes when I'm running away from mobs, sometimes when I'm looting, etc. It hasn't happened in any cities, nor have there been any moments where I've almost froze. The issue improved after I installed my new 980 today, but it's still freezing more frequency than I would like. I heard the issue is related to not having enough VRAM, but with a  980 I think I have plenty (I would hope so anyway).

 

If you need anymore information please let me know. I've been messing around with Skyrim for way too long and I'd like to just get it working.

 

 

loadorder.txt

Edited November 8, 2014 by inglorious89

[hishutup]

do you have the correct values in the skse.ini?

Can you share them

[inglorious89]

do you have the correct values in the skse.ini?

Can you share them

Sure

 

[Display]

iTintTextureResolution=2048

 

[General]

ClearInvalidRegistrations=1

 

[Memory]

DefaultHeapInitialAllocMB=768

ScrapHeapSizeMB=256

 

[Display]

iTintTextureResolution=256

 

[Debug] 

WriteMinidumps=1

 

[interface]

EnableContainerCategorization=1

 

[NotPlacebo]

GiveFirstBornToSheson=1

[hishutup]

well... 
 
I know to remove
 

[Display]
iTintTextureResolution=256
[NotPlacebo]
GiveFirstBornToSheson=1

edit:install Memory Blocks Log. Purposely cause the game to CTD/IIS/freeze In the overwrite\skse\plugins folder with be a log

Then copy/paste it into spoilers  

 

 

 

 

[spoiler]
Text
[/spoiler]

 

 

Edited November 8, 2014 by hishutup

[inglorious89]

well... 

 

I know to remove

 

[Display]
iTintTextureResolution=256
[NotPlacebo]
GiveFirstBornToSheson=1

edit:install Memory Blocks Log. Purposely cause the game to CTD/IIS/freeze In the overwrite\skse\plugins folder with be a log

Then copy/paste it into spoilers  

 

 

 

[spoiler]
Text
[/spoiler]

 

 

I'll get right on it. I was going to do it last night, but I was so tired I just went to bed. I'll get a papyrus log as well.

[inglorious89]

well... 

 

I know to remove

 

[Display]
iTintTextureResolution=256
[NotPlacebo]
GiveFirstBornToSheson=1

edit:install Memory Blocks Log. Purposely cause the game to CTD/IIS/freeze In the overwrite\skse\plugins folder with be a log

Then copy/paste it into spoilers  

 

 

 

[spoiler]
Text
[/spoiler]

 

 

 

I actually have bit of an update; some good news, some bad news. I've played for several hours today and haven't frozen once. No idea why it stopped, but it did. The bad news is that now I'm CTDing occasionally. Skyrim's playable, but it's still really annoying. Typically is happens in an area with a lot of NPCs, but its happened when I'm alone going through the menu, looting a corpse, etc. Only happens in the open though, never in dungeons and rarely in cities.  I know this isn't the original issue, but if you could help me further I'd really appreciate it. If you need the crash logs let me know, I'd post them now but for some reason I'm getting the message that I'm not allowed to post them. I will post the MemoryBlocklog.

 

logging of blocks enabled

logging max values only

Timer disabled

Block1 Block2

256MB 256MB

85 8

85 8

85 9

85 10

85 11

85 12

85 13

85 14

85 15

85 16

85 17

85 18

85 19

85 20

85 21

85 22

85 23

85 24

85 25

85 26

85 27

85 28

85 29

85 30

85 31

85 32

85 33

85 34

85 35

85 36

85 37

85 38

85 39

85 40

85 41

85 42

85 43

85 44

85 45

85 46

85 47

85 48

85 49

85 50

85 51

85 52

85 53

85 54

85 55

85 56

85 57

85 58

85 59

85 60

85 61

85 62

85 63

85 64

85 65

85 66

85 67

85 68

85 69

85 70

85 71

85 72

85 73

85 74

85 75

85 76

85 77

85 78

85 79

85 80

85 81

85 82

85 83

85 84

85 85

85 86

85 87

85 88

85 89

85 90

85 91

85 92

85 93

85 94

85 95

85 96

85 97

85 98

85 99

85 100

85 101

85 102

85 103

85 104

85 105

85 106

85 107

85 108

85 109

85 110

85 111

85 112

85 113

85 114

85 115

85 116

86 116

86 117

86 118

86 119

86 120

86 121

108 121

152 121

152 122

152 123

152 124

[hishutup]

well I can tell you that the memory tweaks are NOT working

 

Try adding the -forcesteamloader argument to SKSE in MO's executables list

Source

 

Start the game, load up into the world, exit then post new memory blocks log.

I still say that mod is the most helpful thing out there and should be require for step

[inglorious89]

well I can tell you that the memory tweaks are NOT working

 

Try adding the -forcesteamloader argument to SKSE in MO's executables list

Source

 

Start the game, load up into the world, exit then post new memory blocks log.

I still say that mod is the most helpful thing out there and should be require for step

Where exactly do I insert the -forcesteamloader? Sorry for the retardation, but Google isn't giving me a clear answer. I've tried at the end of skse_loader.exe, but that didn't seem to help. I also make a shortcut of skse_loader.exe and added -forcesteamloader to the end of that, but after running Skyrim for a minute the memory log wasn't going to 512.

Edited November 9, 2014 by inglorious89

[phazer11]

You append it to the end of the executable path in MO. So, go to edit executables and select SKSE. You'll see the file path to SKSE (which'll be in the same folder as your skyrim executable) and at the end of the path (which I think is in quotes I can't check right now it's storming) you'd put the -forcesteamloader outside of the last quote.

[inglorious89]

You append it to the end of the executable path in MO. So, go to edit executables and select SKSE. You'll see the file path to SKSE (which'll be in the same folder as your skyrim executable) and at the end of the path (which I think is in quotes I can't check right now it's storming) you'd put the -forcesteamloader outside of the last quote.

Can you do this without using MO? 

[GrantSP]

 

 

Can you do this without using MO? 

If you are running your game from a shortcut on the desktop rather from a mod manager then right-click on the game's icon, select "Properties" and in the edit field labeled 'Target:' append the -forcesteamloader switch to what is already displayed.

[inglorious89]

If you are running your game from a shortcut on the desktop rather from a mod manager then right-click on the game's icon, select "Properties" and in the edit field labeled 'Target:' append the -forcesteamloader switch to what is already displayed.

Seemsl ike I'm getting the message, "Couldn't read arguements". That being said, I looked at my MemoryBlocksLog, and to me it seems like the memory patch is working. I'll post the log if need be, but Block1 is showing 512MB and Block2 is showing 256MB, which (from what I've read) is correct for the memory patch, although I could easily be wrong.

[hishutup]

yes, 512 is correct but the log that you posted had block 1 set at 256

[inglorious89]

I really do appreciate the help so far guys. Any more tips on preventing crashes outside of the obvious make-sure-mods-aren't-conflicting? I do have some crash logs if you're still interested in helping.

 

I'm also being told by a friend that, in the SKSE folder in My Documents,  skse_steam_loader should have the line "overriding memory pool sizes" in order for SKSE's memory patch to work. Currently, I don't have that line in the file. Is my friend right or is he full of it?

Edited November 9, 2014 by inglorious89

[Chubrock]

Hi just wondering if your using the latest version of SKSE? Sheson memory patch is included not sure if that will make a diff?

[GrantSP]

Seemsl ike I'm getting the message, "Couldn't read arguements". That being said, I looked at my MemoryBlocksLog, and to me it seems like the memory patch is working. I'll post the log if need be, but Block1 is showing 512MB and Block2 is showing 256MB, which (from what I've read) is correct for the memory patch, although I could easily be wrong.

If you are appending these arguments to the executable in MO via the 'Binary' field you will receive this error.

Arguments such as "-forcesteamloader" need to be placed in the 'Arguments' field.

 

Having said that you haven't said which version of Windows you are on so maybe Win8 and above likewise have an 'Arguments' field now. Of course this is only if that error is from a desktop launched shortcut, not from one inside MO.