Issue: Cannot see any blocks in the world. Inventory & NEI are fine

[xBlizzDevious]

Operating System, bit type: Windows 7 Ultimate 64 Bit
Java version/update, bit type: Java Runtime Environment 7 Update 51 x64
Launcher version: 1.3.4
Completed the troubleshooting guide (y/n): Y
Console log, pastebin.com link: http://pastebin.com/udHnnG2R
Description of the problem:

Basically, I load up Minecraft and everything appears to be fine until I get into a game. This happens whether I use a texture pack or not, whatever I change the graphics options to, whatever I do; it doesn't work. This always used to work fine, but I haven't played since FTB Monster 1.0.5 a few weeks ago.

I've no idea what's causing Minecraft to do this and it's not a bug I've ever seen before anywhere, and I've seen a lot of bugs.

 

[Tristam Izumi]

I'm not really seeing anything odd in your log, though I'm curious: how much RAM does your computer have? It's also usually not a good idea to throw 16GB of RAM at Java. It's like a kid in a candy store with RAM; it won't use it in moderation and it can actually make things worse after a certain allocation. Try toning it back to 4GB and see if that makes any different.

 

[xBlizzDevious]

I'm not really seeing anything odd in your log, though I'm curious: how much RAM does your computer have? It's also usually not a good idea to throw 16GB of RAM at Java. It's like a kid in a candy store with RAM; it won't use it in moderation and it can actually make things worse after a certain allocation. Try toning it back to 4GB and see if that makes any different.

Haha. I've got 32GB of RAM. I've never had any issues with it at 16GB of RAM before. In theory, there's nothing changed with my computer since I last played FTB but I can tell you now that FTB Monster is not the only mod pack that does this. I just ran Unleashed as I wanted to check something out in an old world I used to have. Exactly the same result. Setting RAM to only 4GB changes nothing; it still looks the same. About to try running vanilla Minecraft to see if that does it.



EDIT: Fixed it. It's an issue with the Catalyst 14.1 drivers which I'd forgotten I'd installed the other day. I did some Googling and found a Reddit post that lead to this forum: http://forums.guru3d.com/showthread.php?t=386289 giving me the solution. Download those DLLs, put them in your system folders and it's sorted.