Jump to content

Skyrim crashes to desktop, no error


tang347

Recommended Posts

I have 170 hours on Skyrim. Played flawlessly until now. Ever since I got the quest "Totems of Hircine" I havnt been able to go into Movarth's Lair. When I try to go in, It just crashes to the desktop with no error. I would just skip the quest, but i want to know why it crashes if possible. My drivers are all up to date.

PC Specs:

Windows 7 64bit

AMD Athlon 64 X2 Dual Core Processor 4200+ 2.42GHz

Nvidia GeForce GT 250

2 GB of RAM

Link to comment
Share on other sites

I have 170 hours on Skyrim. Played flawlessly until now. Ever since I got the quest "Totems of Hircine" I havnt been able to go into Movarth's Lair. When I try to go in, It just crashes to the desktop with no error. I would just skip the quest, but i want to know why it crashes if possible. My drivers are all up to date.

PC Specs:

Windows 7 64bit

AMD Athlon 64 X2 Dual Core Processor 4200+ 2.42GHz

Nvidia GeForce GT 250

2 GB of RAM

 

I have tried every fix so far with no solution to this. The only way I play it without it crashing is using the 4GB patch with 1.1 but with 1.1 my buttons don't work properly, I have to steal books cant just read them. Also certain keyboard commands dont work, menu commands especially. 1.3 It crashes to desktop every hour or so outside only, doesn't in the large cities even. I have been trying to play it with 1.1 but the issues with 1.1 I can barley play properly too. I think we have to wait, 1.3 actually crashes worse I found. I've looked everywhere 4 days after the game was released all over since I'm bored of most games and have found no fix to date. Welp back to Saints Rows the Third lol. I think it has to do with rendering outside or audio, but I cant be certain and the Windows logs only stated crashed for unknown reason it seems an erratic error but it does only outside for mine. I'm actually going to stop trying now, this has been since it came out trying to get it to work with trying all the solutions and my own trouble shooting. Wonder why yours just started though wish it gave some sort of error it's like it was designed to do it, conspiracy maybe for sabotaging PC, boogedy boogedy... I think it's just completely fudged on PC man maybe something in that new quest is just activating the crap causing the CTDs to others and me.

Edited by dark27
Link to comment
Share on other sites

I have tried every fix so far with no solution to this. The only way I play it without it crashing is using the 4GB patch with 1.1 but with 1.1 my buttons don't work properly, I have to steal books cant just read them. Also certain keyboard commands dont work, menu commands especially. 1.3 It crashes to desktop every hour or so outside only, doesn't in the large cities even. I have been trying to play it with 1.1 but the issues with 1.1 I can barley play properly too. I think we have to wait, 1.3 actually crashes worse I found. I've looked everywhere 4 days after the game was released all over since I'm bored of most games and have found no fix to date. Welp back to Saints Rows the Third lol. I think it has to do with rendering outside or audio, but I cant be certain and the Windows logs only stated crashed for unknown reason it seems an erratic error but it does only outside for mine. I'm actually going to stop trying now, this has been since it came out trying to get it to work with trying all the solutions and my own trouble shooting. Wonder why yours just started though wish it gave some sort of error it's like it was designed to do it, conspiracy maybe for sabotaging PC, boogedy boogedy... I think it's just completely fudged on PC man maybe something in that new quest is just activating the crap causing the CTDs to others and me.

My situation may have something to do with that save file because i loaded one that i had saved 50 hours or so before that one and went to Movarth's Lair and it worked fine.. :/

 

EDIT: I went ahead and skipped that quest, turned it in, and picked up a new one from the companions. I went back to Movark's Lair and it still does it.

Edited by tang347
Link to comment
Share on other sites

  • 2 weeks later...

I have 170 hours on Skyrim. Played flawlessly until now. Ever since I got the quest "Totems of Hircine" I havnt been able to go into Movarth's Lair. When I try to go in, It just crashes to the desktop with no error. I would just skip the quest, but i want to know why it crashes if possible. My drivers are all up to date.

 

Yeah I'm having problems with it crashing to desktop upon entering the Animonculory within Alftand. Unfortunately this is part of the main Dragonborn quest, so I can't even complete the game. Needless to say I'm pretty furious about that :mad:

 

As with yourself, the game went fine without a hitch until the 160-hour mark. Since then it started to crash to desktop at least once every hour, so I'd say it's a memory leak / restriction that's causing it as a reload of a previous saved-game file worked fine when I entered the same area. Changing the graphic settings made no impact.

 

I'm going to try out the 4GB thing. Makes sense that if crashing is memory-related increasing the buffer by 2GB will certainly help.

Link to comment
Share on other sites

I have 170 hours on Skyrim. Played flawlessly until now. Ever since I got the quest "Totems of Hircine" I havnt been able to go into Movarth's Lair. When I try to go in, It just crashes to the desktop with no error. I would just skip the quest, but i want to know why it crashes if possible. My drivers are all up to date.

 

Yeah I'm having problems with it crashing to desktop upon entering the Animonculory within Alftand. Unfortunately this is part of the main Dragonborn quest, so I can't even complete the game. Needless to say I'm pretty furious about that :mad:

 

As with yourself, the game went fine without a hitch until the 160-hour mark. Since then it started to crash to desktop at least once every hour, so I'd say it's a memory leak / restriction that's causing it as a reload of a previous saved-game file worked fine when I entered the same area. Changing the graphic settings made no impact.

 

I'm going to try out the 4GB thing. Makes sense that if crashing is memory-related increasing the buffer by 2GB will certainly help.

 

In the new version the game supposedly plays with 4GB of RAM... The perforamnce in this 1.3.10 patch or whatever is horrible it took a playable game on decent settings to unplayable on my computer. I hear the next patch (which may or may not fix my problem) will not be out until the end of January. If this is how Bethesda makes games this will be the last game I play of thiers. Sad thing is i cannot even go back to the vanilla version becuase steam forces us to use the 1.3.10 patch everytime it is reinstalled.

Link to comment
Share on other sites

I *had* a similar problem - repeatable despite (as I thought) removing all mods and tweaks. 1.3.10 crashed instantly on any action which triggered a save (e.g. fast travel or entering a new area). Previously it crashed at that point only after triggering a quest stage advance, but it was completely repeatable. 1.2.10 was rock steady (I might have the version number wrong - the one BEFORE the backwards dragons, anyway).

 

My solution: a clean reinstall of Skyrim, removing ALL mods (yes, including the ones I forgot I'd installed) and adding back only 'trusted' mods, and then only via NMM.

 

Everything was then rock steady where previously there were instant CTDs. I suspect the problem lay with a texture mod I'd installed early on (or an FXAAA injector thingamajig) which were installed manually;y and I'd forgotten. If you'd asked me if I'd deleted all mods - I'd have said yes: I'd have been wrong. Either that or there was a rogue file lurking somewhere from a deleted mod that was incompatible with 1.2.10.

 

My recommendation: reinstall Skyrim and mod carefully. It is a PITA but if you structure things properly, "just" a couple of hours work, depending on your mods and tweaks. I took the opportunity to re-tweak my nVidia card according to the recommendations on the tweakgide.

 

Personally I blame texture mods: I had a similar problem with FO3. Obviously not all texture mods are a problem (I assume) but some are. Oh - and then there's that ugridstoload problem: don't go messing with that unless you know what you're doing (full instructions to recover are on geforce.com in the tweakguide).

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...