Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
I have never done this shit. I install the RAM and see if it works. If I have a problem with the system, then I'll test it.How many people here still test new RAM modules with a utility like Memtest86+ when building or upgrading a new rig?
same, ive just found that as time past, parts got more reliable and i dont bother unless something seems off. building for someone else, i do a little testing.I started building my PCs in the mid 1990's, so as the other guru suggested, I may just be a Luddite.
Nope. I started in the 1990's as well. I don't test hardware outside the case unless its a water cooling build with hard tubing. I do not run memory tests, stress tests, or any of that shit on new hardware and I never have outside the context of hardware reviews. I've worked in high volume service centers repairing computers. I'm going to tell you, software based diagnostics are not 100% accurate to begin with. I've seen Memtest86 show errors and people incorrectly assume RAM was bad only for the problem to be something else, or even BIOS settings. Tests like OCCT Intel Burn in and others place unrealistic loads on CPU's and sometimes other hardware. Yet, I've seen hardware pass those tests only to crash 30 seconds into a Handbrake encode.Interesting.
I asked the question here because in came up on another computer forum. The OP was being advised that testing was unnecessary by another long time member and that made me wonder.
I have always tested RAM on every new rig I build (and stress test too) just because - well - that's what you do! I've dealt with enough DOA parts to not just go on faith.
I wonder if it is a generational thing?
I started building my PCs in the mid 1990's, so as the other guru suggested, I may just be a Luddite.
if youre cobbling together old used parts, sure test em. new out of box, issues are rare these days...Dan, you must either be lucky, or I'm unlucky, or your stability needs differ from mine. Out of 7 computers in my backroom cluster, 6 of them would crash in gcc or show other instability at least once every hour or so. All 6 demonstrated memtest errors; I replaced the memory in one and backed off the memory clocks by a notch or two in the others, and they now run all day long. That might be partly because I tend to have at least some used / older hardware in these boxes.
if youre cobbling together old used parts, sure test em. new out of box, issues are rare these days...
I think you are unlucky, and dealing with used or older hardware is probably a contributing factor. As for stability, I demand stuff be as stable as possible. I fix broken crap all day. I don't tolerate my own systems crashing.Dan, you must either be lucky, or I'm unlucky, or your stability needs differ from mine. Out of 7 computers in my backroom cluster, 6 of them would crash in gcc or show other instability at least once every hour or so. All 6 demonstrated memtest errors; I replaced the memory in one and backed off the memory clocks by a notch or two in the others, and they now run all day long. That might be partly because I tend to have at least some used / older hardware in these boxes.
no, thats when you do do thorough testing.I can certainly understand that if your trying to make money or do it for a job you would not want to waste time on an additional task that is of limited value. Carry on!
^^ that. i gave my 3400 ram about 10min on memtest when i bumped it to 3600. when i ran it stock i didnt bother.It depends. If the RAM is just going to be run at stock or XMP, then no. If it's some 3200-rated stuff that I intend to run much faster, then yeah, I'll dial it up and run some tests to make sure I know where I should draw the line.
I'm going to tell you, software based diagnostics are not 100% accurate to begin with. I've seen Memtest86 show errors and people incorrectly assume RAM was bad only for the problem to be something else, or even BIOS settings.
I've never tested RAM. I have 3200 sticks that can be overclocked to 3466 safely through software that came with my prebuilt PC. I've never tried to push it above that because I honestly don't know how to do it and I'm not sure how much above the 3466 I could go before I start having adverse effects.
If it requires adjustment of voltage, I can't do it. At least not manually. No option in the BIOS.It's like overclocking anything else. Find the limit, and then dial it back one notch.
If it requires adjustment of voltage, I can't do it. At least not manually. No option in the BIOS.
Just checked in the BIOS and I can't modify anything for the RAM there. I appreciate your suggestion though.You might be able to raise some timings instead. Start a new thread if you want some help.
HP Omen 30LJust checked in the BIOS and I can't modify anything for the RAM there. I appreciate your suggestion though.
It looks like I can with Ryzen Master, but I don't know what I'm doing. I'll have to do some research and then ask questions in a new thread later. Thanks!HP Omen 30L
this system? yeah thats why, oems lock everything down 99% of the time. ryzen master MIGHT let you control it, if they havent locked that out too...
no prob. neither do i, i did mine in bios. but if you start a thread im sure others will be able help out.It looks like I can with Ryzen Master, but I don't know what I'm doing. I'll have to do some research and then ask questions in a new thread later. Thanks!