Jump to content
  • 0
Quahogs

Wondering if MEM patch is working correctly

Question

Starting to get frequent CTD's running from Whiterun to Riverwood (last test lasted 17 minutes before CTD)  and 4 out of 10 times when I exit Whiterun to Skyrim.

I have UGRIDS at 7, running Vividian High Quality version.

I have 4G vram and before I crashed it registered 3824mb per Skyrim Performance monitor.  

I have most of the SR/LE graphics mods installed along with REGS too with about 250 plugins.  

I realize I'm probably pushing things and can live with the 1 hour CTD but they're now becoming more frequent.  For starters I just want to make sure I have the MEM patch working at least. Thanks.  

 

I also ran the the speedmult 1500 test before I launched a new playthru and didn't CTD.   Game looks beautiful but I'm probably never going to get a playthru using anything greater than 10 mods and stick figures...  

 

SKSI.ini (set up under MO)



[General]

ClearInvalidRegistrations=1

 

[Memory]

DefaultHeapInitialAllocMB=768

ScrapHeapSizeMB=256

 

[Display]

iTintTextureResolution=2048



 

Memoryblocklog.txt


logging of blocks enabled

logging max values only

Timer disabled

Block1 Block2

512MB 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

85 117

85 118

85 119

85 120

85 121

85 122

85 123

85 124

85 125

85 126

85 127

85 128

85 129

85 130

85 131

85 132

85 133

85 134

85 135

85 136

85 137

85 138

85 139

85 140

85 141

85 142

85 143

85 144

85 145

85 146

85 147

85 148

85 149

85 150

85 151

85 152

85 153

85 154

102 154

102 155

102 156

102 157

102 158

102 159

102 160

102 161

102 162

102 163

102 164

102 165

102 166

102 167

102 168

102 169

102 170

102 171

118 171

118 172

118 173

118 174

118 175

118 176

118 177

118 178

125 178

125 179

126 179

127 179

128 179

132 179

134 179

134 180

141 180

145 180

146 180

151 180

163 180

163 181

164 181

175 181

175 182

175 183

176 183

177 183

178 183

183 183

189 183

199 183

199 184

199 185

199 186

199 187

199 188

199 189

199 190

199 191

200 191

201 191

201 192

202 192

203 192

204 192

204 193

205 193

206 193

206 194

207 194

208 194

209 194

210 194

211 194

212 194

213 194

214 194

215 194

216 194

217 194

219 194

220 194

221 194

222 194

223 194

224 194

225 194

226 194

227 194

228 194

229 194

230 194

231 194

232 194

233 194

234 194

235 194

236 194

237 194

238 194

239 194

240 194

241 194

242 194

243 194

244 194

245 194

246 194

247 194

248 194

249 194

250 194

251 194

252 194

253 194

254 194

255 194

255 195

256 195

259 195

265 195

266 195

267 195

267 196

271 196

272 196

273 196

274 196

290 196

291 196

307 196

307 197

308 197

309 197

309 198

309 199

309 200

309 201

309 202

330 202

330 203

330 204

330 205

330 206

330 207

330 208

330 209

330 210

330 211

330 212

330 213

330 214

330 215

330 216

330 217

340 217

347 217

351 217

351 218


Share this post


Link to post
Share on other sites

7 answers to this question

Recommended Posts

  • 0

Disagree on the advice to raise block 2.

 

The truth is that the game never accesses more than 256 for block 2, even if you set it higher. Sheson tried to figure out why this is true, but that is still unknown. Personally, I've played with block 2 fully maxed out at 256 for hours without any CTDs.

 

Back when Sheson first introduced it and many people were running tests, it was found that for many people (myself included,) block 2 only needs to be raised to 512 when block 1 (as reported in Memblock) is set to either 768 or 1024. You will know that block 2 needs to be raised if you set block 1 higher and then Skyrim crashes on start up.

 

My advice is to keep Memory Block Log going until you've had a chance to run through a number of areas known to push the block 1 heap usage quite high, such as around Solitude and/or Windhelm.

 

However, based on your Memory Block usage log, your skse.ini is fine. Which means your crashes are being caused by something else. Perhaps your enblocal.ini / ENBoost settings?

Share this post


Link to post
Share on other sites
  • 0

the mem patch is working like it should.

You are getting close to needing to raise the values for block 2 tho

Share this post


Link to post
Share on other sites
  • 0

really because I know the way it is supposed to work is that it'll just create another block 2 but I have seen multiple instances myself were it'll CTD right after hitting 255. I even compared it with the time and it was really close.

 

I have never needed to raise block 1 beyond a value of 512 MB...

 

I remember looking for info a while back on that and there was little info other than that really large thread. I just know that there were a few sets of ini setting going around.

the common 768|256

another version 1024|256

and a really heavily modded version 1024|512

 

I have found that it is best to leave it at the default values of 768|256 but I haven't come across any harm or 768|512

Share this post


Link to post
Share on other sites
  • 0

 

 

My advice is to keep Memory Block Log going until you've had a chance to run through a number of areas known to push the block 1 heap usage quite high, such as around Solitude and/or Windhelm.

 

However, based on your Memory Block usage log, your skse.ini is fine. Which means your crashes are being caused by something else. Perhaps your enblocal.ini / ENBoost settings?

Thanks.  Good to know that it's working as it should.   The fact that my RAM never goes above 1200mb means ENB (.264 and Vividian 6.03)  is working correctly too ?   Not at home-don't have my settings- but am sure they are what NEO / Vividian recommended since I don't know enough to tinker.  Oh well another start aborted, back to troubleshooting

Share this post


Link to post
Share on other sites
  • 0

I think your RAM usage looks really good considering all the mods and texture packs you are using. Just as a point of comparison, my RAM usage never exceeds 1200mb (and averages right around 1100mb) with STEP Extended and REGS, so in your case I think ENBhost is doing what it's supposed to do. If you're curious to see what ENBHost is doing, check "Combined TESV and ENBHost System RAM" in the Miscellaneous Settings tab in Skyrim Performance Monitor. With this enabled, you'll see all the RAM ENBHost is pulling out of TESV into a 64-bit process space. I doubt it's really useful other than to see ENBHost working, though.

Share this post


Link to post
Share on other sites
  • 0
Been reading up on some threads here and I'm going to give the below setting a shot.  I have 16g ram and 4g vram.  I was previously using the settings 64 and 4096 respectively.  We'll see how this goes...

 

ReservedMemorySizeMb=256

VideoMemorySizeMb=8192

Share this post


Link to post
Share on other sites
  • 0

I thought we were talking about ssme/memory patch 3.0....

Enbboost is men patch 2.0... And it doesn't mess with blocks 1 and blocks 2 inside the ram

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.