overclocking ram causes bsod's

[GoodEnough]

if I just try overclocking my 3000mhz ram to 3200mhz my computer gets fairly unstable and tends to blue screen every now and then (like every few hours), normally i wouldnt have said anything, but this is only an extra 200mhz, and i thought that this was really weird.

 

a few examples of the bsod's I have been getting are:

 

 IRQL_NOT_GREATER_OR_EQUAL

 IRQL_NOT_LESS_OR_EQUAL

MEMORY_MANAGEMENT

KMODE_EXCEPTION_NOT_HANDLED

SYSTEM_SERVICE_EXCEPTION

PFN_LIST_CORRUPT

PAGE_FAULT_IN_NONPAGED_AREA

CRITICAL_PROCESS_DIED

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

ATTEMPTED_WRITE_TO_READONLY_MEMORY

 

 

[Guest]

You can increase the voltage of the RAM, or you can just use it at 3000MHz the 200MHz difference won't make that big of a difference.

[Origami Cactus]

Did you raise the voltage? Changed the timings?

Usually you have to raise the voltage too to keep it stable, or loosen time timings. For example if you are on 1.35, try 1.36V.

[Origami Cactus]

1 minute ago, yaboistar said:

i tend to go for looser timings first. faster speed > lower latency within the same speed. once you find something that works then you can fiddle around with it a bit but backing timings off is a pretty good way to get to a configuration that wants to work properly

I never dared to fiddle with the timings, upping the voltage seemed safer, more in the range of my abilities. I should probably do it at some point thought.

[GoodEnough]

1 minute ago, yaboistar said:

also "only an extra 200mhz" isn't really relevant because it's a "straw that broke the camel's back" scenario. say the voltage and timing setup for the 3000 profile was theoretically perfectly stable up to something like 3125mhz, that next step up to 3200 would exceed that even though it was perfectly stable at 3000. it might be completely unstable and not want to boot, or it might be slightly unstable and cause crashes, memory leaks or BSOD's.

well to be fair one of my sticks is heavily faulty and within a millisecond of memtest it detects errors, but hey, as long as it works at 3000mhz im perfectly fine with that.

 

and because of that fact, i knew that i probably wont be able to get it to cooperate at 3200mhz, and all i really wanted to know is why it was happening so i could know for future reference.

 

and yeah, i would use the computer without that stick but.. well, thats 8 less gb, and only having 8 is kinda, oof. if your using a seriously fat modpack for minecraft it can actually use over 8gb alone, leaving me with less than nothing lol.

[GoodEnough]

1 minute ago, yaboistar said:

that's a whole lot of words for not saying much

 

memory is not all created equal. you're not seeing faults, you're seeing erroring from a device that is being run outside of it's specification. that is not a fault. if the device is erroring at it's original specification that is a fault. 

you can account for this erroring by giving the device more voltage to drive itself with, or backing timings off so that it has more time in which to function properly and thus not output errors.

ram is quite similar to processors in that way, and something i already knew, but again, it was getting those errors during the test at 3000mhz and default xmp settings, so its not something i can do too much about, if it works then it works. 

[GoodEnough]

Just now, yaboistar said:

except i've quite literally told you how to do something about it.

thats not what im getting at, im saying that the ram gets those errors while its within its specifications 

[GoodEnough]

1 minute ago, yaboistar said:

cool,

 

XMP is not a guarantee nor is it a specification. JEDEC makes the specifications. Adjust your timings and/or voltage to compensate for your XMP profile, which is a "best guess" at what is stable, not being stable

re, stop being a tism patient, just because it gets errors during the memtest doesnt mean i get bluescreens at the settings i currently have it set on.

[GoodEnough]

Just now, yaboistar said:

congratulations, sherlock, you have discovered the difference between major and minor memory instability

 

I have described the process for you to solve this. your continued whining about it is little more than a waste of my time.

seriously, i just wanted to know why it was happening, so i could fix it if in the future if it became a serious problem.

 

i openly admit that not being clear on this is my fault, i should have from the beginning specified what i wanted instead of making such a huge understanding about it, and for that i am deeply sorry.