2Gb @ 3.15 or 4Gb @ 2.66?

Nick1881 · 12 Dec 2007 at 11:44

As thread title, what will give me more performance?

Im running Vista ultimate 32bit so only using 3.3Gb anyway.

I have an E6300 at 2.66Ghz, had to downclock it from 3.15Ghz as I started getting BSOD.

Right now on idle vista is using 1Gb of my ram, whats it doing with it?

My system is

E6300
Gigabyte 965 DS3
8800GTS 512mb
2Gb 6400 G.Skill PK
2Gb 6400 Crucial

Thanks

Nick

DavidB · 12 Dec 2007 at 11:56

When i put 4gb of RAM in my 32bit computer i actually found a loss of performance, so id say 2gb and 3.15.

To be honest though you should be able tog et closer your overclock anyway, have you tried slackening the timings on the RAM at all ? Adding voltage mb ?

waso_dude · 12 Dec 2007 at 12:29

Welcome to 4x1gb overclocking.

I had massive problems with it. had a stable clock of 3.6ghz on a 6600 then with 4th struggled to get 3.2ghz.

So went back to 2gb and XP.

Nick1881 · 12 Dec 2007 at 12:32

Yea I just dropped to 2Gb and gained 1000 marks in 3d06.

Thanks for the help guys, i'll stick with 2Gb

Shads · 12 Dec 2007 at 12:51

what volts where you using for 4gb ? as it will always need more than 2gb

Nick1881 · 12 Dec 2007 at 12:58

2.2 as thats what the G.skill needed at 3.15, I dont want to go any higher.

CPU hardly has any more than standard, dont worry about it, Vista is now only using 850mb on idle, its using less because I have less? lol

The crucial is doing 3.15Ghz at 2.0v.

For some reason I never managed to make my system stable at anything higher than 3.15.

bimmerboii · 12 Dec 2007 at 22:03

good thing I read your post. I was planning on getting another set of 2x1gb ocz's but based on your performance, i will just stick with my 2gb

sablabra · 12 Dec 2007 at 22:35

The 965 chipset probably isn't optimal with 4x1 GB. My P35 mobo has no problems at all dealing with 4x1 GB (running at 460x8=3680 MHz). If you want to use 4x1 GB, I suggest you either look over your bios settings and see if you might be able to solve the problem, or change mobo to something with a newer chipset. If the problem persists, it's probably some sort of compatibility problem...