Ndujaowl Posted August 18, 2013 Posted August 18, 2013 (edited) Hi to everyone. Since when I started to use the SKSE .exe to launch my Skyrim game, it crashes randomly and often, showing a Visual C++ error message. It may happen 2 minutes after I launched the game, or 20 minutes later or 2 hours later, it seems not to have any link with the game time; the same happens for places or actions, it doesn't seem to happen only when I go to certain places or only when I do something in particular (like casting spells, or arrows, or melee combat etc.), but just happens independant of anything else, it's totally casual. It's a month already I fight with this problem and I didn't find any solution on the web, nor someone who has my same issue. I ask you to help me solving it, please. My O.S. is Windows 8. Edited August 18, 2013 by Ninnananna2
Miguelr23 Posted August 24, 2013 Posted August 24, 2013 do you have dawnguard installed?people with dawnguard start to get this error mostly after entering the soul cairn
PETNOS Posted August 24, 2013 Posted August 24, 2013 I get those C++ crashes from time to time for seemingly no reason as well. I sometimes wont get one for a week, and sometimes I'll get two within 20 minutes. I can't say I know why, although I'm not using SKSE right now, so I can tell you that it might not specifically be caused by it. Although the frequency you described just might be a result of SKSE, though I'll be honest, I've never experienced much of an issue with it in particular. Maybe if you mention how many mods you have installed, and perhaps list all the major ones, somebody might have a better explanation as to the cause.
Nimboss Posted August 24, 2013 Posted August 24, 2013 1st Please Don't bump, that is considered nono here! If one will help or have a clue they will do so, no need to bump. 2nd W8 is a new thing with it's own issues, I poked at a beta and will not run that OS until I'm forced to, but to people buying a new comp there isn't much to chose about. Microsoft may changed how some things are done, but my general advice is more to next point. 3rd SKSE is developed by skilled programmers on free time, that is they can not foresee every PC setup possible but 99% close. Have you updated all visual C++ patches from MS? Runtime VC++ errors seems to me something is missing? 4th although SKSE team make all the efforts to make a bug free release, modders are not always that technical deep to use functions as intended, wrong use might get the bail out you seen. What mods are you using that depends on SKSE? To nail the culprit, if you turn of any mod that needs SKSE and you can start a new game and run that for hours, then SKSE is not the bad guy. Start to turn on mods that needs SKSE and see if CTD (with visual c++ error) starts to happen, if so then you closing in on what makes your game unstable. You do know that the SKSE team have a thread on Bethesda official site for all issues with this special mod right? A faster answer to solve your issue might be to make a post with the VC++ error code you get when the game stops there.
Ndujaowl Posted August 25, 2013 Author Posted August 25, 2013 1st Please Don't bump, that is considered nono here! If one will help or have a clue they will do so, no need to bump. 2nd W8 is a new thing with it's own issues, I poked at a beta and will not run that OS until I'm forced to, but to people buying a new comp there isn't much to chose about. Microsoft may changed how some things are done, but my general advice is more to next point. 3rd SKSE is developed by skilled programmers on free time, that is they can not foresee every PC setup possible but 99% close. Have you updated all visual C++ patches from MS? Runtime VC++ errors seems to me something is missing? 4th although SKSE team make all the efforts to make a bug free release, modders are not always that technical deep to use functions as intended, wrong use might get the bail out you seen. What mods are you using that depends on SKSE? To nail the culprit, if you turn of any mod that needs SKSE and you can start a new game and run that for hours, then SKSE is not the bad guy. Start to turn on mods that needs SKSE and see if CTD (with visual c++ error) starts to happen, if so then you closing in on what makes your game unstable. You do know that the SKSE team have a thread on Bethesda official site for all issues with this special mod right? A faster answer to solve your issue might be to make a post with the VC++ error code you get when the game stops there. Thank you very much for the reply. 1) I'm sorry, I didn't know it and I saw my topic get digged from the newer ones :D 2) That's true, unfortunately. 3) I've installed all the MS patches available, both for 32-bit and 64-bit (I've an x64 processor). 4) That's my modlist: - Skyrim.esm - Update.esm - Dawnguard.esm - HearthFires.esm - Dragonborn.esm - Unofficial Skyrim Patch ITA.esp - Unofficial Dawnguard Patch ITA.esp - Unofficial Hearthfire Patch.esp - Unofficial Dragonborn Patch ITA.esp - moonpath.esm - HighResTexturePack01.esp - HighResTexturePack02.esp - HighResTexturePack03.esp - SkyUI.esp - iHUD.esp - DeadlyDragons.esp - moonpath_questdata.esp - Brevi_MoonlightTales.esp - WerewolfPerksExpanded_1.6b.esp - Apocalypse - The Spell Package.esp - LoreFriendlySpells.esp - Warburg's 3D Paper World Map - Texture 2.esp - ASIS-Dependency.esp - IShdr1bloom0_All.esp - GrassOnSteroids_Short.esp - Druidessentials.espBut I don't think the mods are the actual problem. I've installed SKSE before any mod and the error was already on it, and this began when I started to use it.
blacksupernova Posted August 25, 2013 Posted August 25, 2013 What is your error message? Is it Runtime error R6025?
Miguelr23 Posted August 25, 2013 Posted August 25, 2013 1st Please Don't bump, that is considered nono here! If one will help or have a clue they will do so, no need to bump. 2nd W8 is a new thing with it's own issues, I poked at a beta and will not run that OS until I'm forced to, but to people buying a new comp there isn't much to chose about. Microsoft may changed how some things are done, but my general advice is more to next point. 3rd SKSE is developed by skilled programmers on free time, that is they can not foresee every PC setup possible but 99% close. Have you updated all visual C++ patches from MS? Runtime VC++ errors seems to me something is missing? 4th although SKSE team make all the efforts to make a bug free release, modders are not always that technical deep to use functions as intended, wrong use might get the bail out you seen. What mods are you using that depends on SKSE? To nail the culprit, if you turn of any mod that needs SKSE and you can start a new game and run that for hours, then SKSE is not the bad guy. Start to turn on mods that needs SKSE and see if CTD (with visual c++ error) starts to happen, if so then you closing in on what makes your game unstable. You do know that the SKSE team have a thread on Bethesda official site for all issues with this special mod right? A faster answer to solve your issue might be to make a post with the VC++ error code you get when the game stops there. Thank you very much for the reply. 1) I'm sorry, I didn't know it and I saw my topic get digged from the newer ones :D 2) That's true, unfortunately. 3) I've installed all the MS patches available, both for 32-bit and 64-bit (I've an x64 processor). 4) That's my modlist: - Skyrim.esm - Update.esm - Dawnguard.esm - HearthFires.esm - Dragonborn.esm - Unofficial Skyrim Patch ITA.esp - Unofficial Dawnguard Patch ITA.esp - Unofficial Hearthfire Patch.esp - Unofficial Dragonborn Patch ITA.esp - moonpath.esm - HighResTexturePack01.esp - HighResTexturePack02.esp - HighResTexturePack03.esp - SkyUI.esp - iHUD.esp - DeadlyDragons.esp - moonpath_questdata.esp - Brevi_MoonlightTales.esp - WerewolfPerksExpanded_1.6b.esp - Apocalypse - The Spell Package.esp - LoreFriendlySpells.esp - Warburg's 3D Paper World Map - Texture 2.esp - ASIS-Dependency.esp - IShdr1bloom0_All.esp - GrassOnSteroids_Short.esp - Druidessentials.espBut I don't think the mods are the actual problem. I've installed SKSE before any mod and the error was already on it, and this began when I started to use it. you have dawnguard so it may be the issue i belive there is a fix involving console tricks in solitude you better google it
Recommended Posts