Augentim

Here I am again to say: if you have 32bit upgrade to 64bit.

No? And guess what in .60 and so on it wont get fixed....

I know I had this glitch myself. End of the story i now have 6gb ram and 64bit. cant wait for the devs to do stuff that isnt affecting the majority - heck they wont optimize until the game hits beta so roughly in 2018

You can BUT no dont do it. get more ram and install 64bit or play dayz with the glitch

Frankly you have to completely reinstall your system with a 64bit ISO(downloadable just search for it on google). Ram usage is slightly higher so you might want to get more than 4gb Ram(cant use more with 32bit). I am not quite sure but you cant activate a 64bit system with your old key; so eitjer get a new one or you know what.

I am not quite sure why it only happens to some people with 32-bit, but all of the guys who have upgraded to 64-bit never complained about this glitch happening again.

Problem: 32bit Solution:64Bit

Not quite sufe if your second pic shows the blocky graphics which I am going to be referring to but if you run 32-bit go upgrade to 64-bit.

Yes 64 bit fixes this!

At least that solved it for me and various others..these kind of threads tend to occur once every month but there is no devside fix.. only solution is to upgrade to 64bit Edit: No clue can just vaguely guess it has something to do with the 32bit system receiving too much data/ or too long data therefore crashing/getting blocky

Do you have 32-Bit system? If yes go upgrade to 64

Do your graphics turn blocky/n64 like?

Wrong, there are/were actually 2 bugs leading to this graphic glitch. Many experienced it during 0.54 where deleting the startup parameters helped. But some people, like myself, always had to deal with the blocky graphics. Nevertheless I updated my system to 64-bit, as somebody on devtracker mentioned something along those lines, and bam never had this problem ever again.

Did you actually try to get 64bit?

Like I said install 64bit. Patch 0.54 added this bug for most of the people who use launch parameters. But before that patch even came out the problem was solved by upgrading to 64bit.