I have the same video card as you, Ghidorah but a newer Intel CPU, which makes a big difference along with 8 GB Ram.
My system specs: Intel i3570k, Radeon HD6850 1 GB VRAM, 8 GB System RAM, Windows 7/64 bit, SanDisk 120 GB SSD, 1 TB Standard HDD
As for mods to run on such a system, to be honest the RAM is the most worrisome followed by the CPU. All things being equal, the video card would be fine if it was the weakest link. I use a lot of 2k textures, but my CPU and RAM has more room and power to jugle it around with the help of ENBoost and SSME. What you need to do is just reduce overhead wherever you can.
Higher than 1k+ texture mods are just going to slow your system down even with ENBoost because the slower CPU data transfer coupled with 4 GB and only 1 GB VRAM are going to get bogged down.
I would keep the list of mods you use to be very selective and short.
TESV Reduced Texture Pack by alex30001
Vanilla Reduced Textures by alt3rn1ty
Consider overwriting any textures (if any from above) with textures by Gamwich:
Bethesda Performance Textures - Animals and Creatures by Gamwich
Also Script heavy mods are going to tax the CPU as well.
Keep away from mods that rely on scripts like Forstfall, Immersive Armors, Footprints, etc.)
ERSO has many mods that are scriptless but add to the game:
Erkeil Team – SKYRIM MODS Erkeil, RS (relliosavini), Ramarda
Obviously, you can't avoid scripts entirely, but keeping a close watch on mods will keep the performance issues down. Script lag can ruin a game just as easy as stutters, CTD's and low FPS can. Some scripted mods are very well made and do not overwhelm your game. But this has to taken in a "straw that broke the camel's back" approach.
Ideally, you should be running:
-ENBoost (UsePatchSpeedhackWithoutGraphics=true)
-SSME
-Reduced Vanilla Textures
-A few select Non-Scripted Mods
If you ever did a incremental upgrade, I'd recommend RAM first, then CPU followed by a video card upgrade. (To be honest, RAM & CPU are a close match to replace first)
No reason I can think of...does disable still work on other things just not this same dragon corpse?
It could be a save corruption that has things fouled perhaps...
...markfordelete is safe to use if you are sure the specific object is something you no longer need in the current game, in this case an empty dragon corpse which is assigned a specific id:
- https://www.uesp.net/wiki/Skyrim:Form_ID
The dragon corpse is FF...
Also markfordelete is better then disable because it doesn't bloat your save file whereas disable will simply make an object "invisible" the data for it will still be loaded and retained in your save.
I have started using markfordelete because the next time I load the cell the dragon will be gone without me "magically" making it go poof. But you can also mfd and then disable the object which should have a (d) signifying it has been mfd flagged.
Only had one stalking dragon corpse this play through (level 39)...Whiterun.
