if the khash documentation is correct, why not show how exactly did you obtained "0E76390E88C27932C9816D326AF12CEA2B"?
ok, it seem to be the same one...
this is just getting more weird then, why it did not work in the past?
and why did it say OK on specific scenario (was failing on others)...
there seem to be more KSS bugs