The name is actually the first 2-4 letters of your forum name, anything else and you're getting too picky.
Ok, lets do advanced mode troubleshooting shall we?. Do a search by date of files for stuff modified roughly at the installation of 1.5. Perhaps it modified a dll. Once you find what did it touched, through google and patience, roll it back to it's former state.
If that doesn't work try messing around with the audio codecs and exceptions and crap. Something tells me it's the audio codec pack gone awry with the geck.
Hmm, you think the FO3 reinstall I had to make cause of patch 1.5 might have something to do with it? Be an odd occurance, since numerous reports of this bug have been around since before 1.5's antics. I simply ran it to play BS and check it out to see how the story conflicts with what I had written. (which, thankfully, doesn't really. Like 2 lines had to be changed, which is why I found said problem) Other program wise, I updated FOSE to 1.5 complaint, but no other programs installed unless the wife did something. I'll have to ask when she's awake tommorow.
Dude, I told you, Try to find the source of your problem by using FOEDIT, or atleast I think thats what its called, Many people have fixed their errors using it. Dont just jump my ass because you cant read my entire message.
Again with the not following. *sigh* It's not a problem in my mod or any other mod. It's a problem in the GECK itself. Any file will cause the CTD. Every dialogue option in every esp/esm does it. FO3Edit is to find discrepancies that don't belong, like when esps change stuff they shouldn't touch, like when I had to track down what messed with the lvl cap and shouldn't of. This is a whole different beast, I know you want to be helpful, but seriously, please stop. Blank may be on to something, I'll follow the trail of codecs.