Not sure if ram is faulty

2Kul4Skul

Reputable
Sep 27, 2014
7
0
4,510
I just got a new pair of sticks (2x4Gb), Kingston HyperX Beast, 1600MHz CL9 for my computer.
They run on 1.6V at 1600 opposed to the 1.5 i have been getting up till now but i thought it wouldn't be a problem since i will have to run them at 1333 (since i use i3 540 and didn't clock it) so i assumed that there wouldn't be any problems.
All the ram i got up till now was 1600 capable without OCing but my MB downclocked them to 1333 without a hitch. I even have (atm) different manufacturers sticks running together (though they were 1.5V). Also tried to find any indication on Kingstons site if their ram can safely run at 1333 1.5V but i found none, didn't think much of it since that ram is usually used OCed and some other manufacturers have listed it as safe for their products.

Now, the problem is that when i put both sticks in i can't even enter BIOS and my Mem OK light shines like a Christmas light so i tried putting only one. That worked the first time and the other time it just kept restarting after exiting BIOS. Light was flashing again but not as much.
Then i tried to manually set the voltage in BIOS while having my old ram in. Despite setting it to 1.55 or 1.6 it showed to be at 1.5 without fluctuation like it normally did when it was on auto.
My MB is P7P55D and i haven't updated my BIOS since i got it (store bought).

My question is am I doing something wrong or is the ram defective? And if it's me, how can i fix it.
(Really hope its not ram's fault since i will have to ship it back to Germany (1-1.5k km) and then back to Amazon...)
 

fkr

Splendid
try different slots.

you can download cpu-z and go to the SPD tab and see what your ram is already rated for.

it should run at 1.5v and 1333 no problem. you may even be able to tighten the timings down to 8-8-8-22
 

2Kul4Skul

Reputable
Sep 27, 2014
7
0
4,510
Think i tried them on 1&3 and 2&4 though I'm not certain about the later one. Individually I'm not sure on which slots did i use them because by then i was extremely annoyed by that time(traveled for 15 hours that day, and when i came home there was nothing to eat and i had to clean the fridge/vacuum my room/clear the dust from the PC case at 11 PM, on top of instaling OS on the new SSD i also got in Germany). Though i think i did put it once in a blue slot and the other time in the black one.


The problem is i can't get into BIOS with both on, let alone boot Windows. And i tried manually increasing Voltage to 1.55 and to 1.6 in BIOS while the old ram was in but for some reason the Voltage didn't change according to the readings in BIOS even after restarting and trying several times.

At this point i would be happy if they ran on 1066 CL12 but i cant get them to work in any configuration, so I'm wondering if there is another angle that I'm missing or something that i haven't tried.
Also i don't really have another PC on which i could try out if they work on a different machine.

These are my current ram's: http://pokit.org/get/?ddeb952e79f159f222a5c649293cf8b0.jpg
 

2Kul4Skul

Reputable
Sep 27, 2014
7
0
4,510
There is a never version of bios for my MB that says:

P7P55D 2003 BIOS
1. Improve memory compatibility
2. Improve system stability

I'll probably update it and try again when i figure out how to flash a mobo or ask a friend.
 

2Kul4Skul

Reputable
Sep 27, 2014
7
0
4,510
Ok, i backed up then flashed my BIOS and tried to boot by MemOK!
kept crashing on slot 1&3 before anything loaded, switched to 2&4 and to my surprise it got to the BIOS/EZ Flash/2 other things screen but was non responsive. Then i tried it with one stick and i managed to get into bios and raise the voltage to 1.55. Put the other stick in and turned the PC back on.
It crashed me to a blue screen saying it was done to prevent system damage and it said "IRQL NOT LESS OR EQUAL" My google skills told me that it can be one of the following: driver issues, or a bad Windows Service caused by a backup utility or antivirus scanner.
Any suggestions? It says run drive verifier but I'm not sure that drivers could be to blame here.
At this point is there any point in trying the ram on another rig?