@MegaChintz, when you do this can you open Chrome Developer tools and see what it shows for that particular network request?
If you are feeling brave, can you download wireshark (https://www.wireshark.org/) and capture a packet trace at the time of the problem? To keep it simple, try to visit a unique page in CHrome (e.g. www.torn.com/?test=xxxx) so that we can trace the 'bad tab' to a particular TCP stream.
It sounds likely that for some reason our servers are returning odd things to you, or there is some sort of other network problem between you and the loadbalancer we have our side.
Once you have that data, post in here and i'll PM you somewhere to send it. Thanks!