i have taken a screen of the interesting part:
There's likely an unallocated stratum session id variable with value "deadbeef......"
Like I said in my previous reply, very strange. Hex code that form highly visible words are often used to help debugging
by making invalid data stick out in a hex dump.
Those hex tags are very useful. The specific deafbeef tag was used in a product I supported and got us into
trouble when we tried to sell to India.
I this case deadbeef is used to initialize a local variable in uint256 code only used by the non-optimized hodl code.
In other words this code does not get run on a 4770K.
The invalid session id also contains two other hex tags: cafe & babe, that are only used in hamsi code which isn't used
by hodl.
It is also interesting that a valid share was hashed with the apparently invalid session id.
These three observations are not related to each other and don't appear to be related to the crash which tells me process
was corrupt. Either the program file is corrupt or the CPU is corrupting data. Since your system is running I assume the
CPU is ok.
Try downloading a fresh copy. I've had no other complaints about the download so it should be ok.
