Can a bad OC ruin RAM Modules?

chaosrelay

Reputable
Feb 7, 2016
28
0
4,530
Three weeks ago, a botched Overclock completely ruined my CPU, which I then replaced around two weeks ago. My PC was running perfectly until this weekend. When my PC started dying again..

I got the bluescreens UNEXPECTED_KERNEL_MODE_TRAP and IRQL_NOT_LESS_OR_EQUAL, mainly (those two were the most common), along with some other ones. I decided to try individual sticks. One stick gave me game crashes with the code C0000005 ACCESS_VIOLATION, while the other gave me a bluescreen with those two error codes. Is it possible that both modules got killed by the long-term effects of a bad over-clock and accidental over-voltage?
 
Solution
Any overclocking on any PC component can end up ruining its lifespan faster than otherwise. It's the nature of overclocking. If accidental overvolting was happening, then it's an entirely reasonable assumption that it ended up killing your RAM. This is assuming your RAM is overclocked as well though. Voltage on the CPU won't affect RAM voltage and vice-versa, just trying to get it cleared up.

If you didn't overclock your RAM, it could be some other component. Most of those errors are too broad to pinpoint one particular component however.
 


Yeah, the PC only started giving me CPU-related bluescreens after I started messing with the voltage. Keep in mind that I only did it with the CPU voltage. BUT...I did accidentally set the voltage to 1.85 instead of 1.385, which led to the PC giving me an over-voltage error. Is it possible that it fried my RAM too? Since now I'm getting bluescreens related to the RAM two weeks after the CPU related errors stopped.

Also, in your opinion, how likely is it that the motherboard has ALSO been fried?

(sorry, I started replying before you edited your post)
 

Motherboard is my second best bet, however if you're truly worried about your RAM, it would be worth putting them inside another PC to see if it happens. It sucks but that is genuinely the one way to tell if a component is functioning as properly as it should be. I'd say it's not your HDD if you reformatted, so it's stuck between your motherboard and RAM. I wouldn't be quick to place blame on RAM.

Try that set of RAM in another system if possible. It's the best way to confirm whether or not it's fried or not.
 
Solution

TRENDING THREADS