Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
@alexbrooklyn maybe I should go back to sleep. Are you running them in spec then?
-
RAM has three main parameters: capacity, frequency and timings. Capacity is of course fixed, frequency and timings are tweakable to some extent (higher frequency = better, lower timings = better, trading timings for frequency = sometimes better on AMD platform).
-
@alexbrooklyn when memtest fails it has nothing to do with frequencies.
Memtest writes memory, reads memory and check's if written == read.
When this fails, it usually means that the RAM is fucked up. Many possible reasons - missing quality assurance, damage sustained during transport / warehousing and so on.
But sad that the assembler who Sold the PC didn't run a memtest and load test. :(
Hope ya PC get's fixed immediately, as this is just a no go imho... (I know some stores who offer an load test / stress test for cash, it's usually money wise spent....) -
Yup it's fixed now, I even got myself some nice rainbow RGB to go along with it. RAM was indeed defective
-
@IntrusionCM running memory out of spec can cause instability which causes memtest to fail
-
@electrineer lemme explain: normal frequency and / or frequencies set by profiles of the RAM vendor (eg XMP), shouldn't be possible.
When you OC manually: possible.
Most likely not the frequency itself, but rather an insufficient VDIMM / voltage, hence the RAM itself is oky, but due to power loss memtest will go awry.
But I'd expect everyone who OC's manually to read the myriad of warnings that instability and damage of hardware is "your own idiocracy".
And that rant sounded nothing like that... At all.
Lately programs have been crashing a lot on my pc, I've tried different things like disabling SWAP for a sec, BIOS changes, remove firefox and use Google Chrome, try different commands, it kept happening.
Obviously along the way I started investigating what was causing these crashes, looking through bug reports and my syslog. There was no consistency, except for 1 thing: SIGENV. Everything that crashed had a segmentation fault, now I'm not an expect and I don't know what this means or how to fix it, so I went to Google to ask for answers.
Then I downloaded memtest and ran a memory test, error palooza. Then I went to Windows and ran memory check, error palooza.
This is week 3 of this high-end gaming pc which was a huge investment AND IT HAS BEEN FUCKING WITH ME BECAUSE OF BAD MEMORY HOW THE FUCK DOES THIS HAPPEN I ALMOST STARTED TO DOUBT UBUNTU BUT IT WAS A FUCKING FAULT IN BRAND NEW MEMORY MODULES WHAT THE FUCK.
Obviously I'm pissed off. Today I'm gonna call the store that assembled it to voice my complaints.
Thank you for listening to my TedTalk.
rant