Crashes on quit -- I may be an idiot, but..

[prideslayer]

I don't remember having these issues before taking my little vacation.

 

Both FONV and the GECK refuse to quit normally. Everything else works fine, however..

 

FONV: Quitting results in a crash, every time, without fail.

 

GECK: Quitting the GECK unloads all the mods, switches the title over to the active mod with a '*' after it as if it had been modified (though it's not loaded -- object window, etc, empty) and then just sits there doing nothing, with the menu greyed out, and must be shut down with 'end task'.

 

Is this just new behavior due to new NVSE or PowerUP or something, or have I forgotten to do something basic to keep this from happening?

 

I certainly don't remember it behaving like this before now.

 

Win7 x64, 16GB, GT560Ti & GT240, detonator 311.06. All windows updates applied.

[ChancellorKremlin]

FNV crashing on exit seems to have been a recent feature if similar complaints are anything to go by. We've been advising using the stutter_remover dll to fix it (you can use it, run the game once, then delete it and it seems to fix the problem) but we're not sure what's causing it. 

 

 

[prideslayer]

Well for FNV I just quit with alt-F4 now. It still pops up the crash dialog, but at least DX is unloaded and my mouse isn't hidden away behind the canvas where I can't find it Just annoying, but at least I'm not alone.

[DoctaSax]

I've been getting the geck hang for months now, and hadn't changed anything nvse or pu at the time or since. Verifying the cache didn't do anything for me either.

When that started I had the FNV on exit crash too but that went away after I set the fast exit option in the NVSR ini (which I was sure I already had before).

[KainsChylde]

I've always had the crash on exit for the game for as long as I can remember. In the stutter reducer ini, , look for "bFastExit=0" and change it to 1. As for the GECK crash, I've never had that problem so I dunno.

[ChancellorKremlin]

Huh, so the GECK thing is an issue too now apparently? I don't know, it's been months since I've opened the GECK, but if it is then the two are probably somehow related. 

[Halstrom]

I think it's something in SCR but got no idea what it is, everything checks out fine in FNVEdit, I'm wondering if I've hit some memory / record limit.

[prideslayer]

The GECK used to do exactly the same thing, and then close like any other program. It always did the funny "unloading" lag thing, then it would toggle the title bar from 'normal' to 'modified' when the windows were empty... then it would exit. Now, it just doesn't exit.

 

Loading, editing, and saving work fine -- though all this bitching from the powerup is making me consider going back a version or two. Error checking when saving a script, nice. Vomiting countless errors upon loading anything, even vanilla ESMs, not so nice. The author has responded to criticism by basically saying "well screw you guys, dealing with that would be hard."

 

To be fair, the thing is written in ASM. To be more fair, it did not have to be.. not entirely.

[Halstrom]

I think it started arount the time I started getting a BSA error coming up on opening GECK

 

---------------------------

Warning - PowerUp - REPORTS

---------------------------

Loading a user created or misnamed BSA

 

 

 

Origin: 008A3942

 

"Yes to all" will disable all warnings of this origin.

---------------------------

Yes   No   Cancel   

---------------------------

 

[prideslayer]

I think it's something in SCR but got no idea what it is, everything checks out fine in FNVEdit, I'm wondering if I've hit some memory / record limit.

Sweet jesus if this is your fault I'm going to brain you with houses cane.

 

We should talk sometime about.. putting SCR on a diet. There's a lot of bloat there that probably doesn't need to be.

[Halstrom]

I have been trimming it back a bit actually, but added more too

[prideslayer]

I think it started arount the time I started getting a BSA error coming up on opening GECK

Yes that's from the 'new' powerup. It's just passing on GECK errors that Beth had decided to suppress, but maybe there's a reason they decided to suppress them, especially when their own material is full of GECK errors like that.

[Ark of Truth]

FONV crashing on exit is nothing new, it even happens on Vanilla.

 

Does this mean Pride is now back and he is wanting second top poster back?

[prideslayer]

second top? If you're not first, you're last!

[woodenstick]

Oh your game crashes when you quit? Boo-hoo my oblivion install crashes when I start, when I'm playing, when I'm not playing, and even when I have friends over. It just pops up, displays a crash message and I have to explain to them why there's two naked 3d models having sex on my computer. Come back when you have a REAL problem  

[prideslayer]

I don't have a problem. I have a problem solver, and his name is revolver fnvedit.

 

I'm talking scorched earth, motherfucker.

 

Hulk is on vacation. Les is here to handle things today.

[TheJuice]

I've been having this issue as well.  I re-installed FONV and played with no mods to see if the problem was the game itself and I was able to quit without a crash dialogue, but when I installed Sexout the crashes started popping up again.  

[prideslayer]

I've been having this issue as well.  I re-installed FONV and played with no mods to see if the problem was the game itself and I was able to quit without a crash dialogue, but when I installed Sexout the crashes started popping up again.

Just sexout, or everything?

 

If someone has the time, it would be helpful to start adding things in one by one, from the very start, and try quitting after each step.

 

1. NVSE first.

2. NVSE Extender next.

3. Sexout.esm

4. SCR.

5. SexoutSlavery

6. Non-pregnancy mod of your choice ( e.g. sewerslave, tryouts, brutalrapers, etc).

7. Pregnancy

8. Pregnancy mod of your choice ( e.g. Breeder )

[Loogie]

My FNV has always crashed to desktop on exit since OWB was released. The GECK, though, is something I only get if I have a huge amount of information loaded.  I haven't modded Sexout in months so I couldn't tell you if SCR also causes crashiness.

[TheJuice]

well I unchecked everything, ran the game with vanilla everything (and official dlc) and I was groovy.  Not much stutter and a clean quit.  Activated Sexout.esm (recent BETA released today) and I got the crash again when quitting, along with a lot of little stutters.  I didn't re-do everything so idk if that's thorough enough but it looks like sexout is the culprit.  If things get to the point where the crashes are unbearable and the stuttering is disruptive I'll do  a(nother) completely clean installation and do install sexout requirements one by one,  but only if someone doesn't do it soon.  

 

I'd do it today but I did it yesterday and I just want to play

[prideslayer]

Sexout could be responsible for some stuttering at startup when the quest scripts all start stampeding, or if the scan frequency is cranked way up. The crash though.. it can't really cause that.

 

That's not really any help though either, for me anyway, since there are few other people here that can really dig into sexout, and fewer still that can dig into NX or NVSE if one of those is responsible.

 

OTOH, while I get the crashes constantly, I don't get stuttering at all except in places where I've always had it, like the first time the goodsprings dust devil rolls by, or the first time a casino populates via populated.. er.. casinos.

[TheJuice]

IDK if you have seen this thread yet but the guy say he may have narrowed it down to SCR.

 

http://www.loverslab.com/topic/17615-stuttering-caused-by-sexoutcommonresourcesesm/

[jaam]

I only have (had) GECk refusing to quit if I save an ESM for the second time in one session. But the latest mod I installed was month ago.

 

[Guest]

My NV always crashed on quitting, even vanilla one. Not with a fresh new installation, it just starts after some days, the more I play. For that reason I was thinking it was something in the savegame. But my GECK too, it does the same issue. It starts fine then after few days it starts this issue. I only load FalloutNV.esm and my own esps. The only difference is that sometimes in NV I must stop the process in taskmanager since the "NV had a problem, click here to quit" window is freezed as well. I always had friends with this issue as well, since day 1, so I just took it as a new NV "feature".

[Pkatt]

Hey!   I may be able to add something!

 

I've been starting a brand new install of FONV mod by mod.     I've been installing only one or two mods at a time, then running the game for a bit, just to keep from the nightmare that happened to me back when I tried to install about a hundred Oblivion mods at the same time. 

 

Anyway, I had a completely stable game going, no CTDs, and no Crashes on quit, it would quit just fine.   I had probably 20-30 mods running, basically everything I wanted, EXCEPT body mods, and Sexout.   The next step I decided on was to install the Sexout Core stuff.     I installed just the core and data,  and got a crash on startup, so I knew something was wrong.   In my troubleshooting, (following threads on here!)   I realized that I did not have the latest version of NVSE.    So I updated that, and tried it again, and the game works fine, except it immediately started crashing on quit.      I didn't think much about it, because Oblivion used to do that all the time to me.

 

But for my install, it had to be either Sexout Core, or Data (NOT SCR, because I haven't installed that yet), or NVSE, because those are the only three things that changed.

 

Hope that might help some!