Something strange happens yesterday when playing...
Well the game crashed, nothing strange here, after about 1-2 hours of play that's happens in my rig ... then I restarted the obselauncher but crashed at start, after two o three other tries I headed for Wrye Bash to control that all is OK and not ever WB starts... then I opened /data folder and about all the non ghosted esp/esm is missing, oblivion.esm missing (the one that crash WB).
The strange thing is I found some esm was ghosted and I'm SURE that all the esm was activated before the crash...

I copied oblivion.esm again in the data folder and restarted WB. I found that about 50 or so esm/esm was missing, some have ruined intestation and was left from the load list and I'm not sure that some other files (like textures and meshes) is missing, all the BSA is there however

I have no idea of what is happening here...

Someone had seen something like this in the past? What can cause a behaviour like this? Anyone knows?

Thanks a lot

I'm pretty sure I heard of this happening to a few people a while back. I think it was caused by a bug in WB, so make sure you're using the latest version.

Well I'm sure I downloaded latest wrye bash in TESNexus... mmm I'll erase all traces of WB and redownload the latest

Someone known if that bug is patched?

If I'm right in thinking that it was caused by a bug in WB, that bug has long since been patched. If you're using a recent version, then that can't have been the issue.

Uhuh... and then what it can be? I don't want incur another time in a "reconstruction without know exactly what pieces is amiss"

Maybe is windows that throw a firetrooper incinerating my /data files :flamethrower:

The only times I've ever heard of this happening was when Psymon had the same thing happen. As Wrinklyninja said, it was caused by an old bug in Wrye Bash that was related to opening more than one copy of the program at once. This is fixed now, so make sure you're running version 285+ and that won't be an issue again. Obviously it won't help with your existing problem, but at least it won't bite you later.

For all, I'm using WB 285 as before, then isn't the problem there obviously...

Yeah that was me alright - happened several times. although there were two others who reported similar issues as I recall.

I've had the game installed on two different drives. Happened on both but not for a long time, so I don't think it was hard drive related. I suspected as much and that was a prime motivation in reinstalling on a different drive (well also to have a dedicated drive). Imagine my frustration when it happened again soon after installing and getting the mods all built up. :brokencomputer:

I was never able to determine if this eating of mods was the result of the game crashing then you don't notice it until trying to open Wrye Bash or if opening Wrye Bash caused it.

I can't say I definitively solved anything. But I did find one pattern and after addressing this I've not had the issue. I noticed that if I double clicked the Wrye Bash icon too quickly and it was opened twice at the apparent same time - then Wrye Bash would crash and it took a while before I would notice that key esm/esp were missing.

As time went on my Habu mouse started malfunctioning more severely and many other applications started opening twice or even three times. Much later another poster (kyoma, Hamma, I forget who ... but someone more tech savy than me) even made a whole thread about the dangers of malfunctioning mice that double clicked during play.

New mouse - no problems.

But because of this I also adapted a habit of never having Wrye bash active when i play (always close before starting Oblivion) and I always check to make sure to not have two copies of Wrye Bash open. Even that - it was not that if I opened it once then again - it was when it was opened twice at the same time. Closing one caused a crash in both and the loss of mods - I saw that with my own eyes several times.

My problems were occuring back when Wrye Bash was around version 240-250 or so - I can't recall when ghosting was implemented or if it played a big part. Last year though.

that is most of the details.

My game is up and running again, with about all the mods (some more was added and one changed in the run) and working (crashing after a bit as before), in less time I hoped.

Now that I remember before the "deleting crash" I played some 10 minutes with WB open, then I remembered it, exited the game,close WB and restarted the game without apparent problems (I did that because my rig is a bit low on specifics), the next crash was the fatal one.

Is for sure that is WB is somewhat implied there because I found about all the remaing esp/esm ghosted even the ones that wasn't before and the ones missing was the one not ghosted - as if WB tried to "save the esps" ghosting it or erased all because of this.

Thanks to Psymon I'll pay attention on double clicking WB and not play with WB open.

well back to game

Another thing I started doing that may save you some headaches.

I copy and paste out all my esm/esp (without bsa or other replacers even 400 esp/esm are not that much disc space wise).

Great back up and name the folder the date of the backup. I also run boss on that folder and not the main data folder. then hand move the files (old school like).

It has been a while since those crashes have happened and others reported but I do recall one other stating that having WB open twice was an issue.

I lean toward it being about Wrye Bash because it does manage esp files while the game engine only reads from them. Thank gosh no reports of replacers being eaten.