Microsoft Visual C++ Runtime Library error constantly

[Sarcasm]

After a few minutes of gameplay, I am met with this error:

Microsoft Visual C++ Runtime Library

 

...\common\Skyrim\TESV.exe

 

Runtime Error!

 

The application requested the runtime to terminate in an unusual way.

 

 

 

This is starting to drive me just crazy, there is no end to this message. I've tried everything I can come up with through Google and nothing stops it. I even just reformatted both my hard drives yesterday, completely reinstalling Windows on my SSD and wiping my hard drive with a reformat. And the error still appears!

 

This isn't the Dawnguard Impatience of a Saint \ Arvak quest Runtime error as far as I can tell; I completed both and the error still hit. Plus, people getting that error report an "R6025" error code on their crash and I do not have this, just a generic message. I played for 6 and a half hours on my save just fine with no errors, almost all of that time spent around Falkreath. The first time I saw this error was when I stepped into the walled yard exterior of Fort Greymoor, west of Whiterun. After completing the two Dawnguard quests, I returned to the Fort Greymoor exterior and almost instantly, Runtime error. Is there something diseased about this area? So far, it has only happened in that area and never in an interior, but I haven't continued playing to find it if it happens elsewhere now. The error just hits whenever it feels like it, I can't reliably reproduce it, except that it always happens within a matter of minutes.

 

After 5-15 minutes of gameplay it hits, thus far always outdoors. I followed STEP, but skipped many plugins because some were problematic for me in the past and my computer could never handle a full STEP. I would post a load order but I don't think this problem is connected to the mods at all. I kept my Mod Organizer install and some other random stuff through the reformat, but I can't imagine any of it would be causing this. Besides MO, I kept save games from other games and images.

 

I posted this question on the Nexus and got a lengthy response, but I didn't really understand most of it since it wasn't written in English all that well. I can't imagine it could be anything on my hard drive, because I just reformatted and I've installed hardly anything. My motherboard ethernet drivers, my Nvidia 344.60 drivers, Steam, WinRAR, 7z, Java, IrfanView, and one other game besides Skyrim. I've had this computer for almost 3 years now and I've been playing Skyrim on it since release, even as recently as a few months ago, and I have never seen this error. Now it's just ominpresent in Skyrim, but everything else on my system runs fine. What could be interfering with Skyrim? The only thing that's different with Skyrim this time around is my using Mod Organizer for the first time, could it be causing this somehow?

 

Can ANYONE offer a solution on this? I would be so, so forever thankful to you for an end to this madness!

 

I'm using:

Windows 7 64-bit

Nvidia GTX 750 Ti 2GB

ENB w/ VideoMemorySizeMb=4096

Edited November 10, 2014 by Sarcasm

[DoubleYou]

Inside your Skyrim folder is a VCRedist folder with vcredist_x86.exe application in it. Run that and repair and hopefully that should fix it.

[Sarcasm]

I have done that as well, unfortunately.

[z929669]

Try disabling ENB and SKSE to see if that resolves the error (just checking for source)

[Freyrgjurd]

Make sure you have the various versions of VC installed.

 

There are:

 

2005

2008

2010

2012

2013

 

If I record correctly, the Skyrim is 2010. I install all of them in order of oldest to latest just to cover all ground.

Another note, if you use a x64 system (as you are), install both x86 and x64 versions.

 

I hope it helps ya.

[Sarcasm]

Before I reformatted, I installed both 2013 redistributables, x64 and x86. I couldn't install the 2012 or 2010 versions however because it said I had a newer version already, even after I had uninstalled both of the 2013 versions. The 2010 version in Skyrim's VDRedist folder repairs and installs though. Still, it made no difference in stopping or delaying the crashes. The only thing that seemed to delay the errors was removing several script-heavy mods, which moved the error from appearing instantly-5 seconds of loading, to 5-10 minutes after loading. Using a lot of hotkeys to switch weapons and spell seemed to make the error appear faster.

 

Could the SKSE memory patch be causing this? I deleted my SKSE.ini from my SKSE Scripts mod in Mod Organizer, and my game has been running for two hours now with no error. This is the only change I've made. I have a new character sitting idle at Fort Greymoor in the very spot where it crashed the most, and it's still going two hours later now. The only odd thing is that now my load screens take much longer and seem to "hang" a bit, in that the game goes Not Responding for 10 seconds or so on each loading screen before it recovers and finishes loading. Not sure why this is or if its relevant.

 

Now this isn't to say the error won't happen in the future, but two hours is far, far longer than I've managed to keep the game up for so far.

Edited November 10, 2014 by Sarcasm

[Redferne]

I had the problem once. The only way I found to get rid of it, was to delete the saves until I found one without the problem.

In the end it was such a setback that I started a new character.

I still don't know where it came from and I'm still not sure if what I did was right.

You might also want to allocate more space to your swap file or update your drivers. I was also toying with those when the problem disappeared.

One thing I'm sure of is, on a new character with the same mods, I did not encounter the crash anymore on a place I had it 100% of time with the other character.

[Sarcasm]

It sounds like you're referring to the R6025 error from Dawnguard, which is connected to a broken script in the Jiub and/or Arvak quests in that DLC. If the script is running in your save, then your save is screwed no matter what. My error is different though; just a generic error with no code. I'm getting the error even in new games on brand new characters not 10 minutes old.

 

I still haven't gotten a crash though in another 30 minutes since deleting SKSE.ini. It could very well be the SKSE memory patch that's causing it. I saw a bit of talk about the memory patch possibly causing a resurgence in these errors on the Bethesda forums, but only one or two posts. Is there any more info on this? If it is the memory patch, does anyone have some suggestions on what to do about it? Modded Skyrim is basically unplayable without that patch.

[z929669]

I mentioned disabling the previous for suspicions that SKSE mem patch 3.0 and/or enbhost.exe causing some issue with TESV.exe. My guess is that's it and maybe try changing the mempatch settings (assuming default now?) in SKSE (with and without ENB memory fixes running). How much RAM do you have?

[Sarcasm]

I have 16 GB of RAM, what would you recommend I change them to?

 

It is almost certainly the memory patch though. I put SKSE.ini back into the game and within a few minutes the screen checkerboarded and froze up the computer. Very different this time, no runtime error that I could see. I left it on while I was out and came back to checkerboard screen, not exactly sure what happened but I saw no error. Had to restart the computer. Previously I had the game running for three hours straight just fine without SKSE.ini.

[phazer11]

Have you updated the redistributables using Windows Update?

[Redferne]

It sounds like you're referring to the R6025 error from Dawnguard, which is connected to a broken script in the Jiub and/or Arvak quests in that DLC. If the script is running in your save, then your save is screwed no matter what. My error is different though; just a generic error with no code. I'm getting the error even in new games on brand new characters not 10 minutes old.

Not at all, it was near Riverwood just after the bridge to Whiterun on a character that has never been to Dawnguard.

[z929669]

you have plenty of RAM then, and the default SKSE settings should be fine. The checkerboard thing makes me wonder if you don't have some GPU (or other hardware) compatibility issue. Very hard to say. Definitely something to Google or go onto the ENB forums to investigate.

[hishutup]

checkerboard thing is a method of multigpu and/or 3d method

[Sarcasm]

Have you updated the redistributables using Windows Update?

 

No sure how to do that exactly, I installed all the available updates. Is there a way to get it from Updater when there are no more updates?

 

Not at all, it was near Riverwood just after the bridge to Whiterun on a character that has never been to Dawnguard.

 

Huh, interesting. It was a generic error with no error code? Regardless though I still get it on brand new characters.

 

you have plenty of RAM then, and the default SKSE settings should be fine. The checkerboard thing makes me wonder if you don't have some GPU (or other hardware) compatibility issue. Very hard to say. Definitely something to Google or go onto the ENB forums to investigate.

 

Oh yes that is a good idea, I'll make a thread over there too then.

checkerboard thing is a method of multigpu and/or 3d method

What does that mean exactly, method of what ?

[keithinhanoi]

I've had a series of the Microsoft Visual C++ Runtime Library error in my game before, and it was also not associated with the Dawnguard Impatience of a Saint \ Arvak quest, because I was getting it on a brand new character.

 

I investigated into it, and it was not at all related to MS Visual C++ being installed in the wrong way. It's just a memory exception error, and the MS VisC++ Runtime Library tries to "catch" the error, but it can't. It's pretty much the same as getting CTDs, really.

 

That all happened to me before Sheson's memory patch fix. I was at my wits end, pulling my hair out.

 

Still, even with the memory patch active, you can make Skyrim go belly up. It depends on what you have set for the memory fix values in the SKSE .ini, and also what your other ENBoost settings are in enblocal.ini. From everything you've described, it sounds as though either Skyrim's allotted RAM or your VRAM is getting gobbled up.

 

If you post any contents of your .ini files, please kindly use the spoiler tags to avoid mega-long forum posts - thanks!