I recently built a new PC (my third or fourth one) and after some minor mishaps during the Windows installation, I finally got everything up and running.
EVGA Z68 FTW mobo
EVGA GTX 570 HD video
Intel i7 2600K CPU
16GB (4x4GB) G. Skill Ripjaws DDR3 2133
Intel 520 SSD
The system ran like a champ, absolutely no problems, for three weeks. Then I came home from work one day and saw a blue screen of death stating "Physical Memory Dump". When I restarted the system, the motherboard stalled at the first logo and wouldn't POST. I couldn't get into the BIOS, nothing. Just that stinkin' logo!
I called EVGA and they had me run several tests...disconnecting all drives/USB/peripheral devices; resetting the CMOS, etc. and each time it still stalled on the first logo, no POST. They told me to remove all RAM sticks and try starting with only one at a time, no go. They asked me to check the CPU for any bent pins and the board itself for any visible problems; CPU & Board looked absolutely pristine.
SO. They said it could be a faulty board so I set up an RMA and returned it. They haven't shipped a replacement yet, but HOPEFULLY a new board will cure the problem, but I do have a few questions:
If it was a defective board, why would it work right away, then just die after three weeks? You'd think a lemon would be DOA, but this thing ran fine.
If - and let's hope this ISN'T the case - the problem is NOT with the board and I get the same issue when I install the replacement, what else could be causing this?
If the CPU was fried, the board wouldn't even power up to the logo, would it? And if it was the memory, I find it hard to believe that all 4 sticks would be defective, especially since everything worked for a few weeks.
I've searched the net and people who've received a Physical Memory Dump error have been advised to run some diagnostics tests through Windows...the problem is that I can't even enter BIOS, let alone boot to Windows.
I'm probably just being paranoid, but this is the first time I've had any serious issues with a custom build, and I'm hoping someone can give me some insight as to what might be going on if the problem isn't with the board.
Thanks.
EVGA Z68 FTW mobo
EVGA GTX 570 HD video
Intel i7 2600K CPU
16GB (4x4GB) G. Skill Ripjaws DDR3 2133
Intel 520 SSD
The system ran like a champ, absolutely no problems, for three weeks. Then I came home from work one day and saw a blue screen of death stating "Physical Memory Dump". When I restarted the system, the motherboard stalled at the first logo and wouldn't POST. I couldn't get into the BIOS, nothing. Just that stinkin' logo!
I called EVGA and they had me run several tests...disconnecting all drives/USB/peripheral devices; resetting the CMOS, etc. and each time it still stalled on the first logo, no POST. They told me to remove all RAM sticks and try starting with only one at a time, no go. They asked me to check the CPU for any bent pins and the board itself for any visible problems; CPU & Board looked absolutely pristine.
SO. They said it could be a faulty board so I set up an RMA and returned it. They haven't shipped a replacement yet, but HOPEFULLY a new board will cure the problem, but I do have a few questions:
If it was a defective board, why would it work right away, then just die after three weeks? You'd think a lemon would be DOA, but this thing ran fine.
If - and let's hope this ISN'T the case - the problem is NOT with the board and I get the same issue when I install the replacement, what else could be causing this?
If the CPU was fried, the board wouldn't even power up to the logo, would it? And if it was the memory, I find it hard to believe that all 4 sticks would be defective, especially since everything worked for a few weeks.
I've searched the net and people who've received a Physical Memory Dump error have been advised to run some diagnostics tests through Windows...the problem is that I can't even enter BIOS, let alone boot to Windows.
I'm probably just being paranoid, but this is the first time I've had any serious issues with a custom build, and I'm hoping someone can give me some insight as to what might be going on if the problem isn't with the board.
Thanks.