Adalgar

  You can always remove sound files from the package. However if they have corresponding Sound Descriptors those will then point to non existing files. When these Sound Descriptors overwrite SexLab sounds then there will be no sounds at all. So the corresponding Sound Descriptors should then be also deleted with TES5Edit or CK.

  Could be the card, but I doubt it somewhat. 120 FPS indoors (see page 2) does not really point at a faulty card.   Wrong settings or not needed settings, applying antialiasing etc. globally, could make a card doing more and unneeded work which results in lower FPS and could also explain the higher temps.   I would advise setting all things changed at some point in time in the Nvidia Control Panel back to default, unless one exactly understands its meaning and is sure it benefits and isn't conflicting with values that may be set elsewhere. Use the Skyrim Launcher for settings. If Vsync for whatever reason is not working (FPS goes way over 60 FPS on a 60 Hz monitor for instance), then force it in Nvidia Control Panel for Skyrim (easiest way). For reference the performance of a GTX 660, unmodded Skyrim, Ultra Preset:     But of course one could always buy a newer and stronger card and the GTX 660 is aging. It would be just a pity if such a card couldn't also reach its full potential.

  Disabling Vsync for Skyrim is about the worst advice you can follow. Without Vsync the game physics can go crazy. Objects in interiors flying around, graphical artifacts, game glitches and what not. If there's is one game that desperately needs Vsync, it's Skyrim. Let the game handle it, there's good reason Vsync is on by default.  

  When you set values for antialiasing, texture filtering etc. in Globale Einstellungen they become system wide and limit your graphics card's performance in games. Because basically you let the graphics card do twice the work: for your whole system and for the game.   Undo the changes in Globale Einstellungen and only make changes if necessary in Programmeinstellungen, but if antialiasing for instance is already set through the Skyrim launcher there's no need to do this also in Programmeinstellungen - and if you have used the Skyrim launcher for your settings anyway you can leave the settings in Programmeinstellungen alone altogether. Elder Scrolls V: Skyrim should be in the drop down menu of Programmeinstellungen.   Programmeinstellungen is used for games. Better never use Globale Einstellungen for tuning game settings because of performance hindering conflicts.   So restore Gobale Einstellungen back to default: just click on Wiederherstellen and then Übernehmen. Then test your game. Your framerates should be much better.  

  Sorting the load order with Loot https://loot.github.io/ would be a good start.   Also try using a save cleaner: http://www.nexusmods.com/skyrim/mods/53045/? or http://www.nexusmods.com/skyrim/mods/52363/?

Maybe you have Automatic Free Camera checked, if that's so then unchecking it might help.

Have you maybe changed settings in Nvidia Control Panel -> Manage 3D settings -> Global Settings? Settings like Antialising and such? If so, restore to default.

  This version isn't outdated at all. It's using a cloaking mechanism whereas Redux a scanning mechanism. That's the main difference.   Personally I prefer the cloaking mechanism, I find it more stable.

Reset Voice Registry in SexLab menu?   Uncheck VoiceSlots in SexLab menu that have no voices but beeps?   (The mod is working fine in my game with 1.60.2.)

Are you sure about Extra Voices?   I've 5 slots filled and the voices appear to be working.

  Because of errors mentioning zbfSexLab.psc in logs with 1.60 installed, I now added Zaz Animation Pack to the uninstall/install process.   Et voilà, looks like my problem is solved.    

Logs ended with lines about resetting actors, sometimes it managed to write slainternalscr updating actor data after resetting. I played a bit further with 1.60.2/PapyrusUtil 3.1 and did not CTD but got several unrecoverable freezes just before or right after animation and every time with message C++ Runtime Error R6025. Repairing Visual C++ Redistributable Packages didn't help. Now I'm playing with 1.59c again, with PapyrusUtil 3.1, and no freezes whatsoever. Today I read a post - http://www.loverslab.com/topic/29971-sexlab-amorous-adventures-v205-20150726/page-177#entry1299343 - and this player has the same papyrus-log ending I had just before CTD. Also this might be of use: http://www.loverslab.com/topic/50483-sexlab-eager-npcs/page-43#entry1306529 I've attached a papyrus log and PapyrusUtilDev.log with freeze/Error R6025 happening just before animation start. zbfSexLab.psc from Zaz shows up for no apparant reason. It does so everytime with 1.60.2 animating and then game crashing, but is absent in 1.59c logs. SexLab isn't registered in Zaz btw. Papyrus.0.log PapyrusUtilDev.log

  1.59c should be first uninstalled. It contains 45 scripts for instance, whereas 1.60.2 contains 41 script files. Installing over top of 1.59c without deleting files would result in 4 scripts that should not be there.

  Okay, tested oral again with Amorous Adventures and v1.60.2 to see which animations are flagged as oral while they most probably should not be. Animation Registry is reset, all anims active.   4uDIK Cowgirl 4uDIK Doggystyle 4uDIK Leg Up 4uDIK Missionary Zyn Rough Standing Arrok Foreplay

v160.2 doesn't seem very stable in my game. Actor resetting after animation resulted in a CTD a few times.   And are the oral tags really functioning as they should? They worked alright with a little mod I made with line sslBaseAnimation[] anims =  SexLab.GetAnimationsByTags(2, "Oral,Blowjob"), however with Amorous Adventures anims with oral ónly as a first stage were also counted as 'independent' oral animations.   E.g. I got a missionary animation that only has oral in the first stage while selecting an oral animation through dialogue. And there were one or two more animations counted as oral where they shouldn't. Tested this only once.   I didn't test very thorough, so I cannot rule out mistakes I may have made. I had just spent some time adjusting AnimationProfile_1.json from 1.59c to fit the different AnimationProfile layout of 1.60 and then when 1.60 didn't seem to be as reliable as 1.59c I rather quickly called it a day and returned to 1.59c.