Notifications
Notification preferences
notifications_off

No unread notifications right now

You're up to date
View All

You're up to date

Skyrim Mod Sanctuary 84 : Skyrim Memory Patch (Fix freezes and crashes)

  • Comment
More articles

79 comments

Comments locked

A moderator has closed this comment topic for the time being
  1. Escvelyn
    Escvelyn
    • member
    • 1 kudos
    Video doesn't need to be 42 minutes but ok.
    1. xKuriharax
      xKuriharax
      • supporter
      • 1 kudos
      He's just being very detailed, but true the video is a bit long and adding annotations to certain parts of the video would be nice.
  2. DramaticEvilCam
    DramaticEvilCam
    • member
    • 0 kudos
    Thanks! Now my crappy system can run without crashing everytime I move, and I can actually use some foliage mods. Still not amazing, but this patch made it doable.
    Also: I play at about 5-15 FPS sometimes, so don't get too spoiled over there! Haha
  3. Odaku
    Odaku
    • member
    • 2 kudos
    I tried both. and nothing worked for me. I still have CTD at start loadingscreen. I still have CTDs while running through towns and woods and stuff, still CTDs at random loading screens ... i rly start to give up
    1. rblevins138
      rblevins138
      • member
      • 1 kudos
      i feel you there i'm currently having the same problems
    2. skannerz22
      skannerz22
      • member
      • 0 kudos
      if you crash at bethesda logo that is a broken mod you need to manually disable all and enable in small groups then start skyrim and repeat over and over till you find the broken mod
    3. Albarix
      Albarix
      • member
      • 1 kudos
      Tes5edit will tell you what is responsible for the crash at the Bethesda logo.
    4. theblackvenom
      theblackvenom
      • member
      • 0 kudos
      If u Crash at CTD Then U probably Have a Broken Mod installed.....
      This is by far the easiest Problem To solve.....
      First Check If there is any red Plugins at Nexus Mod Manager in the Plugins Sections...If there is Simply Uncheck It and the game will Run Properly.....If this Doesn't Solve The Problem....

      Then Install LOOT......Its Easy to Install just download The file from Nexus and Just Run it through Nexus Mod manager From the supported Tools Button....U may need to browse To the folder WHere loot is located.....I think u probably have loot but even If u dont U can just Optimize the load Order and after it's done U will see on the right side a lot of plugins.....Some will have yellow highlights ...u must check if any of those Yellow Highlights have a writing that says not compatible or something....if so then just Disable that plugin through Nexus Mod Manager......

      If it still doesnt Work.....

      Then U must disable all plugins.....Except for the Skyrim.esm,Update.esm,Dragonborn.esm,Dawnguard.esm and Hearthfire.esm...... Then enable Them 1 by one or like 5plugins each time u load the game.....U will most likely not crash at the start....But when u do....Just recognize the last plugin or last 5 plugins U activated before CTD and find the culprit ....

      CTDs are pretty much Easy Problems to solve....
  4. ProPsychoMan
    ProPsychoMan
    • supporter
    • 0 kudos
    I went the SSME route, it allocated more memory but it crashes way before it reaches the allocated amount. I've tried modding this game before and always end up beating my head against a wall because this crap breaks. Any help or suggestions would be great. I wish they had a system where you hired someone to install and optimize a custom mod set up. Alas, there is no such system.
  5. Comadercrazycow
    Comadercrazycow
    • member
    • 0 kudos
    Cool.
  6. rblevins138
    rblevins138
    • member
    • 1 kudos
    i still crashed i got SSME SKSE Memory Blocks uGridsToLoad but nothing worked it still crashes my memory in my memory logs.log went to 234 when i have the 512 memory any help on what might be wrong? i would be very happy enough if i had any help.
  7. gss2
    gss2
    • member
    • 0 kudos
    thanks man! now my skyrim is not crashing or freezes anymore!
  8. orb1akatsuki
    orb1akatsuki
    • supporter
    • 4 kudos
    I know this thread is 2 years old, but thanks for your hard work teaching us how to fix our Skyrim problems Gopher , for the last 3 years, I've had non-stop ctd, now I run Skyrim 100% ctd free with over 200 mods active.
  9. ZeIgnis
    ZeIgnis
    • member
    • 0 kudos
    Got the latest SKSE 1.7.3 & Using Nexus Mod Manager.

    I tried it all create the SKSE.ini then do SKSE.ini in SKSE folder then also put it in data folder while it's in SKSE folder too, didn't work.
    also tried deleting my enboost files while having the SKSE.ini files where previously said. Didn't work.

    So my final resort installing the SSME... WORKED BY THE GODS IT WORKED AND TURNED IT INTO 512MB!!! Memory log confirms it to shows 512.

    & I can spawn over 16 guards now. Tried 120 exactly where video shows and was flowing smoothly, didn't try further test limits :-D

    Got about 112 Mods including HDS SMIM monsters ai etc.

    Thank you all modders including Gopher, Queued, MongoMonk, Sheson.

    Posting this to show my experience maybe it helps someone.
  10. MotoSxorpio
    MotoSxorpio
    • premium
    • 192 kudos


     
    In response to post #23146674.


    Spoiler:  
    Show

    oddxfellow wrote:
    i just did but when i loaded skyrim and then exited out of it i checked my memoryblockslog it still says i have 256mb for both blocks


    I don't know if you've figured out your problem yet, but I was having the same issue. I however, have discovered the issue.

    You need to create an actual .ini file. You cannot merely create a text file and name it skse.ini. I don't know how to create an .ini, so I found one that no one was using (one of the meta.ini files from MO) and edited the name and contents to fit my purpose.

    I then started skyrim, spawned about 400 riften guards, crashed, and verified that I then had 768 whole megabytes for Skyrim to play with. I did. It worked. And I felt very proud of myself when I discovered my issue.


    For those who care, the way I happened upon my solution was when I tried to apply the fix through MO. I looked at the contents of the thing and saw that MO was calling my false .ini by the name of skse.ini.txt. Noticing the vestigial file extension, I realized what I had done wrong. Then i fixed it. yay.
     


    This issue is likely caused by hidden file extension or when saved, selection of file type was left at ".txt". You can save the skse.txt, then rename to skse.ini. There is no formatting differences between .ini and .txt.