Anyway it's too late to cancel my order but it might not be too late to send it back if anyone has bad experiences with the memory. Thanks
Wanna join the discussion?! Login to your HotHardware Forums forum account, or Register a new forum account.
Every time you said "rams" I thought STL and football. It doesn't get pluralified, it is many sticks of RAM, or I have some RAM, not RAMS. xD I don't farm mooses or gooses lol
Appearance wasn't my consideration, but I do remember someone else making the same remark, that they looked like something that would go well in a themed build, like their texture made them look stone-like.
Actually I have always wanted to submerge a build in mineral oil for quieter cooling, and most of those builds are done in aquarium tanks. Throw in some fake fish and the stone-esque appearance of the RAM would fit right in.
Heh. If I get around to that or anything else on my bucket list, I'll be sure to document it.
We'd love to have it on the forums.
The other concern is that this is the first really high speed RAM I've ever had. I've read about XMP and AMP, but have never used them, to wit, I have an AMD processor and this RAM doesn't offer AMP, just XMP. Even so, when I hopped into bios before the first boot, my ASRock motherboard detected the xmp profile and let me select to load it. It didn't look like it was going to load by default, but I suppose it might have.
Upon booting into Windows, the task manager detects RAM running at 2133, the maximum supported by my APU, and everything certainly seems fine. I need to read up and understand the XMP profiles a little more, and figure out if I need to go back into bios and manually tune the timing to whatever would be appropriate for these sticks at 2133 instead of their rated 2400, I also understand that there is a way to get 2400 running with an APU despite the lack of support, and I am at least curious about that.
I think I might run it at 1600 for a while until I learn a little more. Just to be on the safe side.
Edited by user Sunday, April 3, 2016 1:27:23 AM(UTC)
| Reason: minor correction
grammar nazzzzzi (it gets censored so i had to put more zzz) lol. idk i love calling it rams. it is more bad ass.. it has moree ooomphhh but yeah i know it is silly lol.
id check the manufacturer timings and just put it manually in the bios. i would suggest to s[censored]ze more frequency as high as you can get, apus perform better with higher ones.
Edited by user Sunday, April 3, 2016 4:52:29 AM(UTC)
| Reason: Not specified
Someday I even intend to test the performance at each frequency (1600, 1866, 2133, 2400 if I can figure out the last one) on my setup, just as I requested in the HH coverage subforum. I've seen differing results, and I wonder since my 7800 has a lower end gpu than many of the APUs I've seen tested if it might benefit less. Only one way to find out, but since it's time consuming I won't get around to it right away.
So now I get my new memory installed, and boom, a few days later just like it used to happen, BSOD with a familiar irql error. The biggest pain about this issue is I can't just trigger it. After a reboot, it won't reappear for several days, so it's very time consuming to troubleshoot. A few possibilities other than bad RAM:
Switching off dual channel is probably the easiest first move.
Have you tried googling the specific issue with the specific motherboard of yours? :P
Wierd, IDK, can't help you xD