.
.
ok, so I've spent the past 3 hours of my (well deserved) weekend reading disturbing and confusing threads about the 680i frying RAM. or poorly built RAM whose silicon can't handle sustained 2.Xv for extended periods, blah...blah...blah...still not sure if the problem is RAM or mobos....hehe.
I don't OC (don't even know how), but thought it might be interesting to try OC'ing out some day. That said, I was intending to buy a top-o-the-line 680i board in-case I ever wanted too. (was leaning towards the EVGA 680i - NF68-A1)
I'm a simply gamer and REALLY desire a stable system...but I have to admit this RAM frying thing has really made my anal pucker and left me questioning any current mobo purchases. (Do I still get a 680i...650i...or go Intel?)
I have yet to purchase a mobo for my current build...alas, I did find and purchase some (good, high quality??) RAM on the cheap. I HAVE ALREADY purchased 4GB...here it is:
Crucial Ballistix
BL2KIT12864AA804
800MHz DDR2-800/PC2-6400
4-4-4-12 2.2V
(also have purchased the Antec900 case and Corsair HX620 psu)
So please...will any of you tech-studs please take me under your wing and answer a few Q's for me? (I was considering getting a E6600 and OC'ing at least to E6700 levels at some point in my new build's lifetime, obviously I need to learn how to first.)
1) Since I don't know OC'ing, I don't know what to expect when I put in my RAM and start up my box. Will the RAM/mobo default settings to 2.2v or is this label just a spec stating what the max warrantied conditions for the RAM actually are?
2) Is the RAM frying issue ONLY a problem if you overclock? (since, if I'm not mistaken, you OC both chip and RAM concurrently??) appears most users in those threads are bad-ass overclockers pushing things to the limit...that won't be me.
3) To be safe, should I consider a different mobo chipset?
4) Is the RAM I purchased in danger since it is 2.2v (again, I think that might just be a "rating")?? How can I prevent it from being damaged and run stable? Should I "underclock"..or try to underclock?
.
ok, so I've spent the past 3 hours of my (well deserved) weekend reading disturbing and confusing threads about the 680i frying RAM. or poorly built RAM whose silicon can't handle sustained 2.Xv for extended periods, blah...blah...blah...still not sure if the problem is RAM or mobos....hehe.
I don't OC (don't even know how), but thought it might be interesting to try OC'ing out some day. That said, I was intending to buy a top-o-the-line 680i board in-case I ever wanted too. (was leaning towards the EVGA 680i - NF68-A1)
I'm a simply gamer and REALLY desire a stable system...but I have to admit this RAM frying thing has really made my anal pucker and left me questioning any current mobo purchases. (Do I still get a 680i...650i...or go Intel?)
I have yet to purchase a mobo for my current build...alas, I did find and purchase some (good, high quality??) RAM on the cheap. I HAVE ALREADY purchased 4GB...here it is:
Crucial Ballistix
BL2KIT12864AA804
800MHz DDR2-800/PC2-6400
4-4-4-12 2.2V
(also have purchased the Antec900 case and Corsair HX620 psu)
So please...will any of you tech-studs please take me under your wing and answer a few Q's for me? (I was considering getting a E6600 and OC'ing at least to E6700 levels at some point in my new build's lifetime, obviously I need to learn how to first.)
1) Since I don't know OC'ing, I don't know what to expect when I put in my RAM and start up my box. Will the RAM/mobo default settings to 2.2v or is this label just a spec stating what the max warrantied conditions for the RAM actually are?
2) Is the RAM frying issue ONLY a problem if you overclock? (since, if I'm not mistaken, you OC both chip and RAM concurrently??) appears most users in those threads are bad-ass overclockers pushing things to the limit...that won't be me.
3) To be safe, should I consider a different mobo chipset?
4) Is the RAM I purchased in danger since it is 2.2v (again, I think that might just be a "rating")?? How can I prevent it from being damaged and run stable? Should I "underclock"..or try to underclock?
