How to fix (2013 update)
I've tried the bugged saved game file I initially posted in my question with the current latest versions of the official patch, Unofficial Skyrim Patch (USKP) and Skyrim Script Extender (SKSE), and the saved game is now Aspect of Peryite-free.
I've configured SKSE to use its ClearInvalidRegistrations
console command on every saved game load, which removes invalid scripts left running by uninstalled mods. This feature was introduced in v1.6.7 of SKSE:
add console command ClearInvalidRegistrations
to remove invalid
OnUpdate() registrations
This prevents orphaned OnUpdate() events and
the resulting bloated/broken saves when removing certain mods. When
applied to an already bloated save, it will stop growing further and
instead shrink over time as the game processes all queued events. This
may take hours depending on the amount of bloat.
To execute automatically after each reload, add this to \Data\SKSE\skse.ini
:
[General]
ClearInvalidRegistrations=1
According* to a developer of the Unofficial Skyrim Patch (USKP), the underlying cause is because DA13 ('The Only Cure' quest) is never stopped.
A possible fix* for this:
In the meantime, load an affected save, then type stopquest DA13
into the console. That ought to put an end to that. Plus it’ll free up some unnecessarily leftover alias memory.
BTW, don’t use the console command on a save not bothered by it. Even though it may appear benign, console commands can have negative consequences you don’t know about.
If this doesn't work or if you experience issues like: NPCs not responding properly to conversation (not reply to you when you choose a certain conversation path - leaving you stuck), merchants not opening the buy/sell window, horses that can't be ridden, and other interaction issues, then the save game is most likely corrupted. Try the SKSE ClearInvalidRegistrations
console command fix I've posted above, instead.
To prevent this from happening in the PC, get the latest version of the Unofficial Skyrim Patch. This has been fixed since version 1.1 of the USKP:
"The Only Cure" (DA13) was never stopped which would lead to the Aspect of Peryite randomly initiating conversation and being unable to exit.
* This info is from the old USKP bug tracker page at 16bugs.com, which is now not viewable. The new USKP bug tracker report page of this bug is at afkmods.iguanadons.net.
I did some looking and there appear to be a good variety of glitches in which dragons can die. Some of them might fit your scenario:
Dragon flies (glitches) into ground and dies. Thunder sound, death throes animation, dead. No soul absorbed but this guy was pretty far away and never engaged the dragon:
There are a few recorded accounts of dragons dying when they land. This one shows a dragon that was at full HP who lands, dies, and the soul is still absorbed:
Same case as before, but the dragon was damaged:
There are plenty of other videos in which dragons die as the result of glitches, but I think that these three best match your scenario out of all of them. Let me know if this helps!
Here is an example of a dragon simply spawning dead in front of a player; the "dead dragon glitch" you mentioned earlier. This one doesn't match your scenario too well, but appears to be fairly common:
For the sake of showing that it appears to be possible, here's a video showing two dragons going at it (uhh... fighting):
Wasn't able to find a video of Alduin attacking other dragons, though.
Best Answer
It fell through the floor or ground mesh. I don't know who said "That can't happen," because it happens all the time.
Either reload a previous save, or use console commands (if on PC) to either walk through the floor or spawn in a replacement.
tcl
will let you walk through things. Use it again to turn collision back on.additem <item ID> <count>
will give you an item. The item ID of Dawnbreaker is0004e4ee
.