Honestly, you're better off taking the rig to an auto electrician to have them install the neons—otherwise, you're just asking to void your warranty. Just make sure you track down a certified pro first. 😂 Wait, do the neons even come with their own warranty?
Good grief. I feel like I have to draw you a map just to get a point across. You definitely earned yourself a 🙂 http://upload.wikimedia.org/wikipedi..._connector.jpg Just use Google—it’s actually pretty helpful if you try... And for the newbies out there http://www.google.com/search?q=...kl=070.900.141
Hey guys, so I ordered a Zalman ZM-MFC1 from that shop that handles all the Formula orders—got it delivered today, and they sent me the ZM-MFC1 along with that black one. I hopped onto their site to double-check the price and made sure it was actually what I wanted (was thinking about the standard blue version)... I told them yeah, that's the one, and went ahead and paid $58 instead of $73 ...
So I tried bumping up my RAM a bit more, but no luck there. The only thing is—I'm still scratching my head over how to actually save the settings in that software so they actually stick next time...
I gave it a shot overclocking to 2.7, but once I boot into macOS, the whole thing just freezes up—total standstill. A BIOS update actually helped though, at least that annoying error message finally stopped popping up... http://img162.imageshack.us/img162/3446/untitledle1.jpg Here are the screenshots.
Intel Core i7 or maybe stick with 2.2? I’ve been running mine at 2.7—it works most of the time, but it freezes up occasionally... though at 2.67, everything runs perfectly. I tried pushing it further using some Gigabyte tuning tools, but once I hit 2.8, it just hits thermal throttling. I think I'll just leave it at 2.67 and see if I can squeeze out just a tiny bit more...
Hey guys—would a newer BIOS version actually help me get rid of this error I get whenever I try to push my CPU past 2.5GHz? It keeps throwing this message at me: "Now system is in safe mode please re set your cpu frequency." A few people mentioned a BIOS update might fix it... any thoughts?