So, the other day by Gigabyte GA-P35-DS4's onboard gigE died. Computer just fell off the network. In fact, even if I went into the BIOS screen, there was no entry for "onboard lan".
Died, kaput, gone.
The system has been running fine for just over a year with a q6600 running at 3.2.
I tried a bunch of things, including reseting the bios to safe defaults...upgrading the bios, reverting back to the bios that I was on...nothing.
No big deal, as I was looking for an excuse to put intel gigE pci-e cards in this box and my WHS for better throughput. Purchased them on ebay, installed them, and all was good...back on the network.
Oh, in the meantime, the onboard nic shows up in bios again...but it still can't connect to my network...I think it is legitimately fried.
However, I think something is still wrong with the MB. When I went back into BIOS to restore my O/C things started getting strange. The O/C worked fine, I could boot into windows, do whatever I wanted, etc...I always place the computer in standby when I'm done with it...but now it can't wake from standby. It tries...the fans come on, the lights come on, it tries for a few moments, then stops...and then starts trying again...over and over. The only thing I can do is turn off the power supply at that point.
This works FINE without the O/C, but can't wake from standby as soon as I try to O/C it...but it worked fine forever before this problem.
Gigabyte's RMA policy absolutely sucks. I will never buy another Gigabyte board for this simple fact. I've had to RMA an ABIT board before and they happily cross-ship...You buy a new MB from them, receive it, move your parts to it, ship them yours, and when they receive it and confirm a problem, they refund the purchase price of the replacement. Wonderful. Gigabyte won't cross ship under any circumstances, and the turnaround time is measured in multiple weeks, not days.
So, here's the question.
Does this sound like a MB problem (the OC issue, not the network issue). I have an easy RMA due to the network issue. Or, do you think I'm missing something in my OC settings that could cause this behavior?
Thanks in advance.
-Kevin
Died, kaput, gone.
The system has been running fine for just over a year with a q6600 running at 3.2.
I tried a bunch of things, including reseting the bios to safe defaults...upgrading the bios, reverting back to the bios that I was on...nothing.
No big deal, as I was looking for an excuse to put intel gigE pci-e cards in this box and my WHS for better throughput. Purchased them on ebay, installed them, and all was good...back on the network.
Oh, in the meantime, the onboard nic shows up in bios again...but it still can't connect to my network...I think it is legitimately fried.
However, I think something is still wrong with the MB. When I went back into BIOS to restore my O/C things started getting strange. The O/C worked fine, I could boot into windows, do whatever I wanted, etc...I always place the computer in standby when I'm done with it...but now it can't wake from standby. It tries...the fans come on, the lights come on, it tries for a few moments, then stops...and then starts trying again...over and over. The only thing I can do is turn off the power supply at that point.
This works FINE without the O/C, but can't wake from standby as soon as I try to O/C it...but it worked fine forever before this problem.
Gigabyte's RMA policy absolutely sucks. I will never buy another Gigabyte board for this simple fact. I've had to RMA an ABIT board before and they happily cross-ship...You buy a new MB from them, receive it, move your parts to it, ship them yours, and when they receive it and confirm a problem, they refund the purchase price of the replacement. Wonderful. Gigabyte won't cross ship under any circumstances, and the turnaround time is measured in multiple weeks, not days.
So, here's the question.
Does this sound like a MB problem (the OC issue, not the network issue). I have an easy RMA due to the network issue. Or, do you think I'm missing something in my OC settings that could cause this behavior?
Thanks in advance.
-Kevin