As always , I get the visual c++ ctd whenever loading Dawnguard. That's working as intended, as we all know by now. So, I usually decide to load DG after playing my char up to after finishing the main quest. But apparantly, there's a fix for that according to a YouTube video I found*. Not the useless technical one (the steam backup one), but one where you simply finish the painfully tedious quest for Jiub's lost pages, because apparantly that's what's tripping up the whole thing or something. So far, that seems to have helped, but that's where my question comes in:

*video is titled "visual c++ runtime library error FIXED 100% "

Assuming the tip I heard is actually useful, or for that matter if I used a tip that actually was:

Does the C++ CTD Dawnguard bug require one to redo *whatever technique one needs to use* every time one re-loads Dawnguard*?

*---1A: I never load Dawnguard untill after my character has hit at least lvl 40+, and has finished the main quest. So, whenever I make a new character I de-select Dawnguard from the Data Files (or whatever it's called in the openeing screen) loading list, and then select it again as soon as I'm ready to do Dawnguard with him/her.

In other words, do I need to re-do the Jiub quest in Soul Cairn, or whatever really helps fix the game every time after re-loading DG?

NVM: Question answered elsewhere.

yes, because then the quest comes back when you reload and it is as if you never did it.

I don't care about the quest, I only care about it's supposed ability to stop the c++ visual error crash that Dawnguard introduced to my game. What I'm asking is wether de-selecting Dawnguard will also make the c++ visual error crash come back once I select Dawnguard again.

Nvm... should have looked more closely at the video comments.