Bad iventory data

I crashed in act 2 sewers with sorc, no stash, no items, just killing mobs. I doubt that this issue is entirely caused by the shared stash.

One thing that angers me the most is the radio silence from the devs - guys, a single word that this is being looked at would be appreciated... (maybe they said something about it and I missed it)

There is an easy solution to this: Bring back the original PlugY! Revert whatever changes that killed original PlugY compatibility and put PlugY back in

i back up... basically everytime i exit game... till now act 5 norm seems still fine to me

I'm a new player, started playing version 2.01 a few days ago. This bug happened to me aswell.
I noticed another bug before, I could not unquip any gear. I could not switch weapon and shield. This happened after trying to finish the put socket in Item quest (Lazarus?).

1. What class?
- Sorceress
2. What level?
- 50
3. Which location you last played? (act xx town, dungeon, map etc)
- Act V-Frozen River (just saved Anya)
4. Do you remember what last item your interact with or your last action?
- No
5. Which file was corrupted (shared stash, specific character)
- I don't know. The error says bad inventory data... so stash?
6. Which OS do you play with (xp, win 8, win10 etc)
- Windows 10
7. Did you fresh install the game or update a game via launcher from previous sigma installation?
- Fresh install of game
8. Do you have any crash while playing d2?
- Have not tested

Is there something in the works for this problem? It has been 3 days, nobody from the team appearently said anything, and I lost yet another character...

ParticuLarry wrote:I appreciate your effort Iwansquall. I'm just not sure it's that easy since it seems the issues have more than 1 cause. My first corrupted character happened on my first character. I had only 1 character at this time, I played till I got the staff in act 2 normal and then took a break. I came back and suddenly my character was corrupted. There was no muling involved. But I did put things in my normal stash.

My 2nd character was corrupted by muling items to a mule, stash not involved.

My 3rd character was corrupted after I finally began sorting my inventory by creating a honorific, a couple of rune stacks and creating 2 new uniques and upgrading them. Neither muling nor stash was involved in any way.

So it happens with either stash or muling involved, both being involved or none of these things being involved.

My conclusion:

I think it has to do with saving process. Maybe the stash file doesn't get saved as it should and thus corrupts the characters. That fits in well with the items disappearing from stash that some people have experienced. If for example you put things in your stash and it doesn't save the stash, the items disappear. If however you remove things in your stash or inventory and it doesn't save the stash/inventory, it corrupts the character.

maybe when saving game see only one page of stash like ok thats normal but it freaks out when its see 2 and 3 and also shared stash and tries to put them in 1 file that turns in to mess and that mess kills characters

was farming lvl 1 blue ring for augmenting (in first location) , picked 1 up. Opened inventory but didnt see it. Reentering broke my char :/ lvl 49 sin

I got the "Bad inventory data" character brick after pulling a Pax Mystica out of my Stash and trying to weapon swap to put it in my second weapon slot.

This might just be a coincidence, but just before the character bricked, I got one of those access violation errors and had my game crash. This happened pretty shortly after starting a new game after that crash forced the client closed.

And to piggy back off my crash-before-bricking message - that is not the first time I have crashed in SP with the Access Violation error (at least I think that is what caused the crash). When I fired it up again through the Launcher, everything appears to be fine. However, if I crash again, the Launcher will not work because it says you can only have 2 instances running at a time.

It could be that when there is a client crash and you relaunch via the Launcher, the original instance is still running as a zombie in the background and it is somehow screwing up the memory or the save file if you try to run another instance on top of it.