Reported by: Maravizzo
can anyone else reproduce this?
First of all, I've found out that you don't need to build a patch to cause the CTD!
I know it sounds odd, but just opening and closing Wrye Bash, without doing anything else, kills a clean and working Oblivion install.
Then I created a bashed patch anyway, unistalled and reinstalled Oblivion, then launched it from OBMM without opening Wrye Bash: Oblivion played correctly with its bashed patch.
So it is not the patch, load order, mods etc: it is the application itself what cause CTD.
Downgrading Wrye Bash to 2.9.0 everything worked perfectly again.
Forum post [T:69, P:128]:
http://forums.bethsoft.com/index.php?/topic/1202320-relz-wrye-bash-thread-69/page__view__findpost__p__17952883
see thread: Oblivion, Wrye Base 2.92, and Win7: a CTD on Startup Tale
http://forums.bethsoft.com/index.php?/topic/1202510-oblivion-wrye-base-292-and-win7-a-ctd-on-startup-tale/page__view__findpost__p__17972931__fromsearch__1
View and moderate all "bugs Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Bugs"
have similar problem
http://www.thenexusforums.com/index.php?/topic/400869-wrye-bash-oblivion-corruption-problem/
Both testers who were affected by this problem can no longer reproduce the crash with 294.2 or 295. We'll have to go forward for now with this bug unsolved. The test driver that will find the bug once we find someone who can reproduce it is checked into scripts/test
Any news on this bug? Any reports of it happening in the newer releases?
Ha! Great minds and all that.
Hello, I'm experiencing this bug with Wrye Bash 2.95 standalone. Deleting Documets/MyGames/Oblivion folder does nothing.
Had one user on Nexus report that he no longer gets this bug. Calling it closed.