new ram causing unstable OC?

[jonnylaw13]

ASRock G41C-GS R2.0

intel Core2Quad 9400 (oe 2.66-OC 2.84)

8GB 4gx2 gskill ripjaw nv ddr3-1333 previously 4GB 2x2 gskill value ddr2-800

 

today i finally got the exact specific 1333 ddr3 ram that ASRock requires for DDR3 to work in my mobo but now its being very finicky, showing all my settings in the bios but underclocking itself down to 2.64 until i reboot it twice and "restart" leaves me "sleep" black screened unless i do 2 to 3 hard resets with the power button, without playing reset cmos all night, is this an OC instability with the new ram which is running at 1074 (low OC options on mobo options are 1074 or 14xx)  or is it more likely an issue with my mobo running in DDR3 or the ram itself?

thank you in advance!

[belfouf]

check RAM voltages first.

compare current voltage to gskill ripjaw nv ddr3-1333 standard voltage

put timings AUTO

put manual 1333hz

 

if it's all good, check for BIOS update

[Nord]

If you OC something and then it suddenly stops working due to w/e reasons, you remove the OC and see if thats the issue. Thats basic overclocking knowledge.

 

Anyhow, from what I remember, you could only OC said processor by increasing the Baseclock of the system, which means it  would overclock your RAM aswell, at the same time.

 

RAMS have jedec and xmp nowerdays. (https://en.wikipedia.org/wiki/JEDEC_memory_standards)

jedec has been here pretty much always and has a high standard, its like a quality control, while xmp is a vague "its probably gona work in 80% of all cases". RAM that dont have XMP profiles basically only have jedec "verficiation" if you so will and in your case the jedec is 1333mhz.  Meaning that any alteration to said speed could result in system instability, even if its just a 10mhz difference in plus or minus.

 

Also higher bandwith obviously means more "stress" on your system when under load, making it possible the OC is just too much now in the first place.

A possible fix would be to increase the ram Voltage by a very small ingrement, like 0.5v or so (google that first, im not 100% certain on the voltage) this maybe fixes it. If it does not, down the OC down until it works or increase the CPU Voltage.

Honestly for a 200mhz I would not bother with any of that, you wont really feel that increase anyway.

[jonnylaw13]

4 hours ago, Nord said:

If you OC something and then it suddenly stops working due to w/e reasons, you remove the OC and see if thats the issue. Thats basic overclocking knowledge.

 

Anyhow, from what I remember, you could only OC said processor by increasing the Baseclock of the system, which means it  would overclock your RAM aswell, at the same time.

 

RAMS have jedec and xmp nowerdays. (https://en.wikipedia.org/wiki/JEDEC_memory_standards)

jedec has been here pretty much always and has a high standard, its like a quality control, while xmp is a vague "its probably gona work in 80% of all cases". RAM that dont have XMP profiles basically only have jedec "verficiation" if you so will and in your case the jedec is 1333mhz.  Meaning that any alteration to said speed could result in system instability, even if its just a 10mhz difference in plus or minus.

 

Also higher bandwith obviously means more "stress" on your system when under load, making it possible the OC is just too much now in the first place.

A possible fix would be to increase the ram Voltage by a very small ingrement, like 0.5v or so (google that first, im not 100% certain on the voltage) this maybe fixes it. If it does not, down the OC down until it works or increase the CPU Voltage.

Honestly for a 200mhz I would not bother with any of that, you wont really feel that increase anyway.

you are correct, any OC affects both the CPU and ram, I'm not sure that I have ram volt settings, I know I don't don't for the CPU, the mobo calls for 1333 o.c. To use 1333 ram. Should I maybe bring down my OC until 1333 is one of my ram speed options?

[Nord]

Like I said I would just remove the OC entirely and see if the issue persists and if it does not, you than can than start to OC again until it shows up again and step back.

OC = trial and error, always.

[jonnylaw13]

6 hours ago, Nord said:

Like I said I would just remove the OC entirely and see if the issue persists and if it does not, you than can than start to OC again until it shows up again and step back.

OC = trial and error, always.

back to 2.66 and ram running 1333, reboots like it should, think ill just leave it for now

[Nord]

You can always just increase the BCLK again by increments of 1  every time you turn your PC on, then use it normally for the rest of the day to "test" if its stable and if it is, do the same again next day until it does not work anymore, roll it back by one or two steps and voila.

 

FYI: if you do time consuming work, editing for example, overclocking with BCLK is never a good idea as it will in one way or another make your system  a little bit less stable.

[jonnylaw13]

10 minutes ago, Nord said:

You can always just increase the BCLK again by increments of 1  every time you turn your PC on, then use it normally for the rest of the day to "test" if its stable and if it is, do the same again next day until it does not work anymore, roll it back by one or two steps and voila.

 

FYI: if you do time consuming work, editing for example, overclocking with BCLK is never a good idea as it will in one way or another make your system  a little bit less stable.

nope, just some games and youtube basically.. odd side-affect.. now my keyboard doesnt work from a restart.. really odd i think

[Nord]

I actually had a simular issue on my pre-upgraded system where the keyboard, very rarerly, would not get detected inside windows and had to be re-plugged in.

I dont exactly remember if a new OS install fixed it or if it was the keyboard itself, but anyway USB devices not being detected are stuff that can happen from time to time, as long as it works in BIOS its ok.

 

Theoretically, even though im not exactly sure if thats even true, BCLK OC also affets the USB ports, like literally everything inside your system, so if it happend directly after you removed the OC, thats perhaps it and it just had to be re-connected because "safety". Unless it does happen again I would not worry about it.

 

[jonnylaw13]

2 minutes ago, Nord said:

I actually had a simular issue on my pre-upgraded system where the keyboard, very rarerly, would not get detected inside windows and had to be re-plugged in.

I dont exactly remember if a new OS install fixed it or if it was the keyboard itself, but anyway USB devices not being detected are stuff that can happen from time to time, as long as it works in BIOS its ok.

 

Theoretically, even though im not exactly sure if thats even true, BCLK OC also affets the USB ports, like literally everything inside your system, so if it happend directly after you removed the OC, thats perhaps it and it just had to be re-connected because "safety". Unless it does happen again I would not worry about it.

 

it happened when i moved my FSB jumper and installed the DDR3 ram, but i did just switch from win10x32 to x64 and hadnt done many restarts between then and the ram