blitzen

You might want to get to an interior cell and wait for 31 days to let all of the cells reset, then see if the same thing happens. Sometimes waiting clears problems like that. Sometimes it doesn't. Have you visited those cells previously with the same character?

I hope that the memory patches being released are built using Visual Studio with the same C++ version.

Which version of the C++ Runtime does Skyrim use? 2008? 2010? And which version was used to build SSME? I saw someone else posted about this same issue on another forum. He started seeing this error after using a version of the memory patch, I believe the original Sheson patch. I've see the error occur for a couple of different memory patch versions. It seems random to me. I haven't had it happen for a couple of hours, after reinstalling the Runtimes for 2008 and 2010 and rebooting. But I'm on a different character. And it could be coincidence, since this character is visiting locations for Dawnguard, and the other one wasn't.

There is very little perceived difference in the 1k and 2k textures for terrain unless staring straight down and studying the ground. The overall impression of the visual quality is essentially the same as the character is walking through the world. Other factors have a greater impact on the visual quality. If you have a lot of VRAM to spare, then 2k may not be a concern, so it may be worth using. I generally use 1k if it's available. Even SFO uses primarily 1k textures, and even 512. Only very specific textures are 2k.

There isn't much visual difference between 1k and 2k for most textures, unless you are looking at it from very close up. I have no idea why people even bother with 4k, except for the screen archers, who also tend to use performance-killing ENBs. 1k should be fine for normal play. I see a bigger difference in-game with different levels of anisotropic filtering than I do with 1k vs. 2k.

I've been seeing a Skyrim error for the first time during the past week. There is an boing sound, and a small window pops up with the following information: C++ Runtime Library Error "This application has requested the Runtime to terminate in an unusual way." The game has essentially crashed, but it doesn't close because the error was caught and this window appears instead. I only started to see this with the last week, around the time I started using the new memory patches. Whether I use the modified SKSE or the SSME version makes no difference. A factor that might come into play here are updates to the Microsoft Visual C++ Redistributable at the beginning of January (4th and 8th) which added versions for both 2012 and 2010. I believe one or both were added when I installed Bioshock Infinite, because I did not added them manually. That still leaves a couple of weeks before any problems manifested. Has anyone see this error? Does anyone have any ideas about how to fix it? Is there a specific version of the Runtime that works best with Skyrim? Thanks for any help.

Are you using ENBoost? If not, you might want to try it and see if you have different results. If you already use ENBoost, can you try it again using 768/512 for memory block sizes? That seems to eliminate crashing for some people that still crashed at 512/256.

Back on topic. I've logged about 8 hours with ENBoost and the memory patch. Not a single CTD, ILS or graphics freeze. Unprecedented stability and performance. I am using 512/256, ugrids=5, and have many textures upgrades and about 250 active plugins. There are a lot of extra creatures and NPCs added, and I'm running with Enhanced Blood Textures now, which has caused problems for me in the past. I've seen 40 v 40 battles with no indication of strain/slowdown except for the visible popin of NPC's as the PC entered the cell. Prior to using this fix, I was having regular freezes and CTD's. Safety Load was preventing the ILSs I would normally get in exterior cells. I have not followed the STEP guidelines, but randomly selected mods that seemed interesting. I regularly install and uninstall mods, and some of them have scripts. This does not appear to have caused problems so far, as long as I am running this fix. I start new characters each month, so my saves aren't completely hopeless at this point. I clean mods with TES5Edit. I make a Bashed Patch with Wrye Bash when new mods are added. I use NMM to manage mods. System specs: CPU: i5-2500k RAM: 8 GB Video Card: GTX 570 VRAM: 2.5 GB Video drivers: 314.22 OS: Windows 7 Home Premium The OS has its own SSD. Skyrim has its own SSD. Are you serious? Did you not just read my post about putting an end to this line of discussion? If you aren't contributing the discussion about this mod directly then do not post about this any more. We aren't going to solve anything by bickering with keyboards. I'd hate to have to freeze this forum until the morning because we can't get back on topic. My apologies. I started typing that before you posted, and did not see your post. Very sorry.

Nobody has to prove anything. It's not a product someone is trying to sell. The community is collectively testing it, but anyone is free to not use it if they aren't seeing a benefit. The rest of us don't care if other people aren't using it. There is no burden of proof. There are people with very stable games that aren't using ENBoost or the memory patch. They don't need either one of them. I don't think anyone is trying to claim that any given fix/patch will provide universal benefit. That's not actually true with anything in life. What WOULD be important information is that if someone had evidence that it caused long-term problems with savegames, or something like that. Otherwise, you have to expect that some percentage will fail to realize a benefit. This is expected. As for your comments about 1.9, that's common knowledge. Lips don't move, there's a dialog bug that requires saving, exiting and restarting, the list goes on and on. Skyrim has been "broken", to at least some degree, since the day it was released. The only question relevant to this thread is does this patch improve the memory management such that the most prevalent, common memory-related issues are resolved. That's all it's attempting to do. It's lifting some unreasonable constraints that are present in the basic Skyrim game that cause severe issues when Skyrim is heavily modded.

There is a significant body of evidence which indicates that the memory patch and ENBoost together eliminate virtually all typical/reasonable problems that are related to poor memory management and memory limitations in the Skyrim engine. There are, of course, other reasons for crashes, and they won't help at all with those. I don't know the full story, but if MG is having crashes after installing these two patches and has verified that they are both active, then it's likely that there is some other category of problem causing them. I don't think this topic can help, or should. He should consider starting a new technical support thread to debug these problems. There should be a systematic way to identify what type of issue it is, but I think it goes beyond the scope of this thread once it has been verified that the fixes are installed and behaving properly.

There will be an alpha SKSE release in the next day or two that will include the memory patch, unless their testing and analysis finds something suspicious-looking.

Which version of the memory patch are you using? Did you check the log to see the new line that indicates it's working? If the line doesn't appear, it's not working. What did you add to SKSE.ini?