RAM being overused?

[axepig]

I'm playing Minecraft with the FTB modpack of Infinity, which adds around 160 mods. I have a windows 7 64 bit OS with 8 GB RAM and MC seems to uses the whole 8GB, which sounds wrong. It also makes my game lag a lot. http://i.imgur.com/kbzoqZa.png here's my RAM usage when LOADING the game, I wasn't even loading any map or savefile, just the mods and my RAM is already being overused. Anyone how to fix that?

 

[IntelTurtleFan]

Does it lag with every graphic on low? Can you post the rest of the build?

 

[axepig]

I have most of my settings maxed out (except the antisotropic thing and Advanced OpenGGL which is off) I was running fine for 2 days with almost no lag but it started lagging a lot now. My build is an i5 3570 (not k vers), a gtx 660and 8 GB DDR3 1600hz. I had rendering distance at 14-12 blocks before and I decided to lower it to 10 and it still lags very hard when I'm exploring new lands, I have to look around and go like a radar to render everything which takes a while and is kinda annoying. I would like to add that all of my problems started when I put the antitropic setting to 16 while I have never enabled it, it made my MC launch considerably slow and I decided to put it back to Off. It worked for the most part but I still get heavy lag spikes when exploring and my RAM usage hasn't diminushed.

Edit: I highly doubt the issue is the graphics since my GPU usage is very low and my gtx 660 should be good enough for a game like Minecraft and my CPUs aren't being used that much (max about 30%) so I'm fairly certain it's only the RAM

 

[IntelTurtleFan]

What are your temperatures? I do not think this is a RAM issue.

 

[axepig]

My CPU temp is aroud 50-60C while playing but one core did peak at 66C, my GPU is around 40C, not sure which temp is useful for the Mobo but http://i.imgur.com/lRpYv8e.png here ya go. It looks pretty normal to me and I still have lag spikes. It may be internet but 1: Skype doesn't lag when I have those issues and 2: My fps counter goes crazy during the lag spikes and goes down to 0 and then back to 60 (which is the cap)