Hey guy's
Now before I go shouting against Asus, I'll better be sure what is exactly going on.
I've read that the owners of a quad-core can RMA their EVGA board because of problems with the FSB. That is a fact!
I know also there is a new revision off the Asus Striker Extreme that also affects overclocking. That's true also!
But what I don't know, if this should concurn me. I'm running a quad-core on the Asus Striker Extreme. If there really is a problem with the Striker, I want to know about it. Now getting my board replaced by Asus is wishfull thinking of course. But still, if it is the same error on those two boards, and EVGA RMA's them and Asus don't. It says a lot about Asus. And things like that should be thrown in the open, as it is the only power we have against big company's like that.
But first off, before starting to shout out. (hmm, did already a little of that). Is it the same error on the 2 boards? Can someone check it? I have no clue about things like that. It sounds the same, but is it really?
Now before I go shouting against Asus, I'll better be sure what is exactly going on.
I've read that the owners of a quad-core can RMA their EVGA board because of problems with the FSB. That is a fact!
I know also there is a new revision off the Asus Striker Extreme that also affects overclocking. That's true also!
But what I don't know, if this should concurn me. I'm running a quad-core on the Asus Striker Extreme. If there really is a problem with the Striker, I want to know about it. Now getting my board replaced by Asus is wishfull thinking of course. But still, if it is the same error on those two boards, and EVGA RMA's them and Asus don't. It says a lot about Asus. And things like that should be thrown in the open, as it is the only power we have against big company's like that.
But first off, before starting to shout out. (hmm, did already a little of that). Is it the same error on the 2 boards? Can someone check it? I have no clue about things like that. It sounds the same, but is it really?