https://gist.github.com/Dream-Master/58fa313f5fe29e9da48c#file-gistfile1-txt
and
https://gist.github.com/Dream-Master/8c3ee3cf5b5166cd24d1#file-gistfile1-txt

Binnie has a busy life. IIRC, removing the old API from Binnie's should fix it

ok i will try

But you don't have BuildCraft installed... Also, GC should kill MJ support already.

Its Binnie Mod with an old API from buildcraft

old

There's the keyword.

https://gist.github.com/Dream-Master/223811fba675efad1b90#file-gistfile1-txt

Not working:

You are still not using buildcraft... I have no problem with Binnie's mods and buildcraft 6.1.8.
For the first two crashes it seems like you are loading an existing world after removing buildcraft mod. That is not a buildcraft issue either. It has to do with how forge treats block ids.

I got the "binnie/core/triggers/BinnieAction" crash after updating EnderIO from 2.1.8 to 2.2.1

Maybe the same problems with two or more differnet api s from Buildcraft.

I never add or delete Buildcraft in my pack. i never have it in this pack.

First I thought if have something to do with Buildcraft(API) but after a lots of testing the error not gone. I only asking it is possible that different Versions for Buildcraft Api´s (one with Mj Support in Binnie's Mod and one with RF Support Forestry) can make a Error like this. I dont want somebody fixing think. maybe i have adding Buildcraft to my Pack and see what happen or i have to asking on another place ?

@Dream-Master you don't have BC in your pack, you never had it in your pack, then why are you expecting us to fix an issue that has nothing to do with BC?

Binnie's Mods did not update their API, causing crashes due to API conflicts. You have to deal with it.