Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Try starting a new game and training the same skill (without the mod all the time). Then you would be able to eliminate if the problem was mod savegame corruption or a game or event computer problem.
There is also a chance display drivers may be the culprit, so ensure they are up-to-date! Maybe one of the visual effects of the spell may be triggering the driver-level error.
https://www.youtube.com/watch?v=NGngNzxjaXc&feature=youtu.be
When running skyrim with process monitor on I get a buffer overflow read in the moment of the crash trying to get the registry key:
HKLM\System\CurrentControlSet\Hardware Profiles\UnitedVideo\CONTROL\VIDEO\{117DFA5A-FDA1-4D92-B531-18BE69CB3BB1}\0000\DefaultSettings.DriverExtra
And that's a binary key. Process monitor says length '134' on the query event, but the key seems to be longer than that, being 448 bytes long. So this may be the cause or just a coincidence due to the race condition. The problem is related to the skill hitting a target, probably this is reproducible with two different skills being launched at the same time as well, like, say, calm and courage.
Papyrus log gives at each hit an error that seems "controlled" and not the cause of the bug, but no other output.
[02/05/2017 - 01:31:10AM] error: Object reference has no 3D
stack:
[ (0001E68C)].Sound.Play() - "<native>" Line ?
[ (000B77B6)].fxDustDropRandomSCRIPT.OnLoad() - "fxDustDropRandomSCRIPT.psc" Line 25
[02/05/2017 - 01:31:15AM] error: Object reference has no 3D
stack:
[ (0001E68C)].Sound.Play() - "<native>" Line ?
[ (000B77B9)].fxDustDropRandomSCRIPT.OnLoad() - "fxDustDropRandomSCRIPT.psc" Line 36
[02/05/2017 - 01:31:16AM] error: Object reference has no 3D
stack:
[ (0001E68C)].Sound.Play() - "<native>" Line ?
[ (00037ACE)].fxDustDropRandomSCRIPT.OnLoad() - "fxDustDropRandomSCRIPT.psc" Line 33
It always gets either line 25, 33 or 36 of that fxDustDropRandomSCRIPT.psc. But again, happens every time the courage hits something, so not really related to the crash. The key access thingy seems more the issue, and that would be related to getting a display driver setting -- what leads away from it as the problem is just something happening twice at the same time. That is most definitely a race condition in the game, maybe the same script being run twice and changing/accessing the same game variable thus breaking it away.
Maybe this helps somebody else more into skyrim debugging (maybe a bethesda guy, hopefully? hehehe) to identify & fix the issue.
Probably the problem is exactly the skill updating the its experience level twice at the same time! What will, for example, allow the bug NOT to be triggered if dual releasing two different skills at the same time. :)
Two different skills leveling are probably thread-safe in skyrim but it would be very likely the same skill couldn't handle getting two raise events at the same time. :)
Sorry. Too long. Technical, yet no solution other than releasing the skills at a different moment.
If you haven't found some other kind of fix yet.
A simple work around is just to release one hand half a second after the other. It'll be a a little slower of course but still faster that just using one hand.
Alternatively, if you have two NPCs that don't move you can position yourself so that one hand will hit one NPC and the other hand will hit the other.
Both of these methods prevented any CTD for me.