You will also get an error like this even when both ports of the two port RAM are set to the same address and you are writing to only one of them.
The output of the second port will change to the data that you have written on the first port within a clock or two of the write. You have to ensure, by design, that if you are reading the output data within a few clocks of the write on the other port, that you are getting the data you want.
To use your case as an example, at time 3080, you are writing into one port (say port A) of your memory. The address of the other port (port B) is probably the same as the address on port A. Thus if you sample port B at this time, you'll get the old value. A clock or two later, if you sample port B, you'll get the new value. Since there is no read enable on the ports, the simulator doesn't know when you're sampling the data on port B, so it sends out a generic error to make you go look and check out the situation for yourself.
Its your job to coordinate reads and writes between the two ports so you are always getting the data you want.