Page MenuHomeFeedback Tracker

CTD jogging up hill - strange behavior afterwards
Closed, ResolvedPublic


I was squatting on the side of a hill and I ate two red berries. I stood and took one step (jogging) and I got a CTD with the following message:
"The instruction at 0x0067dbfc referenced memory at 0x00000000. The memory could not be read. Click on OK to terminate the program." {F31850}


Legacy ID
Unable To Reproduce
Game Crash
Steps To Reproduce

Can not attempt to reproduce unable to collect any more apples / berries. Will submit separate report.

Additional Information

Can no longer collect apples. Begin the searching animation, but it stops in the middle, with no status result. Can not get a prompt to stop current action, or to start a new search. Can go to another tree and search, but likewise, the animation stops, with no result.

Can no longer pick up boxes of ammo (.357 and .380). Was able to pick up loose .22 (but this was before the CTD).

Can pick up other objects, but there is a massive delay.

I have constant, rapid fire eating, drinking, well/water and soda can noises.

These issues may not all be related to the CTD. The server seems very unstable since the CTD and may be the cause of the CTD as well as these other issues.

Event Timeline

BleedoutBill edited Additional Information. (Show Details)
BleedoutBill set Category to Game Crash.
BleedoutBill set Reproducibility to Unable To Reproduce.
BleedoutBill set Severity to None.
BleedoutBill set Resolution to Duplicate.
BleedoutBill set Legacy ID to 1065349115.May 8 2016, 10:45 PM

I can confirm this.
But i think this should be two seperate issues.

However, i know of many others from reddit who gets memory could not be read now.

And interactions are either laggy/slow or they wont work at all. I havent waited more then 15minutes for a interaction tho. But that shouldent be nesecary right? I aint going to play if 20minutes for eating an apple is acceptable if you know what i mean hehe.

After additional play time on different servers, I no longer think that the "Strange Behavior" is related to the original CTD. Other servers randomly exhibited this same strange behavior.

Geez added a comment.Jun 16 2015, 12:18 PM

Hello BleedoutBill.
This is an issue we are aware of (#0024916) and it has been fixed. However, feel free to submit another ticket in case the issue re-appears.