BSOD - RAM Speed. Is it hardware related?

Drake5 · 2 Mar 2013 at 15:23

I do have a post in the RAM section about this but thought I'd make one here aswell as I'm unsure if it's just a RAM related issue.

This is my RAM:
http://www.overclockers.co.uk/showproduct.php?prodid=MY-133-GL
This is my motherboard:
http://www.asrock.com/mb/Intel/B75 Pro3-M/?cat=Specifications

CPU-Z Reads:

It appears my RAM isn't running as fast as it should be. As I was advised, I enabled XMP in the bios and reset but when it got to the desktop I got a BSOD, so I disabled it and just manually set the multiplyer to 1600 but that also caused a BSOD.

I'm worried that something is wrong, I only built this system yesterday. I don't have much experience with RAM at all, do I need to mess around with the timings when upping the multiplyer to the speed my RAM supposed to be?

Could another issue be causing the BSOD?

Many thanks

EDIT - Mobo website says:
**DDR3 1600 with Intel® Ivy Bridge CPU, DDR3 1333 with Intel® Sandy Bridge CPU.

Drake5 · 2 Mar 2013 at 17:19

Ok I've done some Googling and from what I can see, I need to set the voltages and timings myself.

I can see all the options for this in the BIOS but I have no idea at all which voltages and timings I need to set. Can anyone please help me.

Idleman · 2 Mar 2013 at 17:29

Don`t` understand why you bought that ram when the 1600 version was specced.
You will see no real benefit from the the ones you bought.
Save your self some unnecessary hassle, take them back to OCUK and swap them them for these.

YOUR BASKET
1 x GeIL EVO Leggera 8GB (2x4GB) DDR3 PC3-12800C9 1600MHz Dual Channel Kit (GEL38GB1600C9DC) £44.99
Total : £48.90 (includes shipping : £3.26).

dacads · 2 Mar 2013 at 17:31

lol..get some 1600MHz RAM

http://www.overclockers.co.uk/showproduct.php?prodid=MY-012-AD&groupid=701&catid=8&subcat=1517

Drake5 · 2 Mar 2013 at 17:32

IGNORE.

Drake5 · 2 Mar 2013 at 17:36

Sorry guys the link in the OP is wrong.

This is the RAM:
http://www.overclockers.co.uk/showproduct.php?prodid=MY-133-GL

It is 1600MHz. It just won't work at 1600MHz when I set it in the bios. I just get BSOD.

I need to tinker with the voltages and timings I think but I'm sure as to how I set them.

dacads · 2 Mar 2013 at 17:38

You changed "DRAM FREQUENCY"?

Try manually changing the DRAM VOLTAGE to 1.5v

What CPU do you have?

Drake5 · 2 Mar 2013 at 17:41

dacads said:
You changed "DRAM FREQUENCY"?

Try manually changing the DRAM VOLTAGE to 1.5v

What CPU do you have?

Yeah, there were 4 different settings, 1600 being the highest which I set it to. I did also set DRAM Voltage to 1.5v but it still BSOD at desktop.

CPU is i3 3220.

Many thanks

Idleman · 2 Mar 2013 at 18:03

In your other thread you stated you were all up and running and was looking for ways to check for stability.
So, when you first put the system together, what exactly did you set in bios?
The system should still work, without manual or XMP, as it should run on the rams lower setting of 1333mhz.
And have you made any other changes since, prior to the BSOD?
Also, try it without the Gpu installed, just use the onboard graphics.

Drake5 · 2 Mar 2013 at 18:05

Idleman said:
In your other thread you stated you were all up and running and was llloking for ways to check for stability.
So, when you first put the system together, what exactly did you set in bios?
The system should still work, without manual or XMP, as it should run on the rams lower setting of 1333mhz.
And have you made any other changes since, prior to the BSOD?
Also, try it without the Gpu installed, just use the onboard graphics.

Yeah, I didn't realize until afterwards that the RAM wasn't running at full speed.

I didn't touch the bios at all, everything was left on default settings.

It does run on the lower setting of 1333MHz without a problem. There just may be a little element of confusion here so I will clarify. The system is absolutely fine apart from when I try and get the RAM working at full speed of 1600MHz.

Thanks.

mranderson · 2 Mar 2013 at 18:11

Give 1.6v to the ram. Your motherboard may not be delivering 1.5v but less.

Idleman · 2 Mar 2013 at 18:17

mranderson said:
Give 1.6v to the ram. Your motherboard may not be delivering 1.5v but less.

Set it to 1.6v and then if it is ok, go back into the bios and lower it slightly. Just keep doing this until you find the sweet spot.

Drake5 · 2 Mar 2013 at 18:26

Idleman said:
Set it to 1.6v and then if it is ok, go back into the bios and lower it slightly. Just keep doing this until you find the sweet spot.

I gave it 1.6 and it still BSOD. Should I just step it up from 1.5 and see how it goes?

This is what the BIOS settings look like if it's any help. In 'DRAM CONFIGURATION' there's lots more settings. Non of them make sense to me though lol.

Also if I just put it on 1400 it's fine without changing anything else. 1600 is the issue.

dacads · 2 Mar 2013 at 18:44

I thought you disabled XMP?

mranderson · 2 Mar 2013 at 18:55

I would give 1.7v. If it doesn't work with this voltage then I would suggest trying each memory on its own.

Drake5 · 2 Mar 2013 at 19:02

I tried 1.7. Still BSOD on desktop.

XMP can only either be on Auto or have the profile selected.

Do I need to try each stick on it's own now then with just 1600 and v1.5 selected?

There's definitely nothing I need to do with relation to the timings?

Cheers

mranderson · 2 Mar 2013 at 19:04

Although auto would use conservative timings that should work with every memory it is probably worth giving it a try.

Drake5 · 2 Mar 2013 at 19:19

Ok guys, so I tried each stick on its own.

The first stick I tried gave BSOD with 1600Mhz.

So I took it out, tried the other stick on its own and that one works fine at 1600MHz, no immediate BSOD.

What do I need to do in order to totally remove the motherboard from being the suspect? Try the working stick of RAM in the other RAM slot aswell just to be sure?

Cheers

Idleman · 2 Mar 2013 at 19:28

What slots are you using?

Drake5 · 2 Mar 2013 at 19:29

Slot 1 + 3 so dual channel mode works.

EDIT - Just put the one that was dodgy at first back in and left the good one out and it booted fine. I honestly have no idea what's going on or what I need to do.