Asus Sabertooth Posting Problem
Hi all,
I've just built a new rig:
i7 2600k
Asus Sabertooth P67
4GB Crucial Ballistix Tracer 1600mhz 1.65v
Enermax Rev 920watts
Corsair F60 SDD System Drive
Corsair F60 SDD Steam Drive
2 x 2TB Segate Barracuda's
2 x MSI 5770 Hawk
Okay the problem is this, built system, 1 stick of ram in got into the bios and then installed windows to the SSD. Rebooted to fit the other stick and set the Ram settings, then back into windows all fine.
Rebooted to start adding in the drivers, second GPU and assorted software goodies from Asus. Instead of posting the rig jumps into life and then holds with the RED VGA LED alight. Now I know the GPU's are fine as only one was installed. Looking at the manual this implies a problem with the GPU, so swapped out and added in the other one to check. Same problem, started swapping the Ram around, same issue.
Now I don't think it's the Cards, plus the Ram did work originally and then this issue started after a reboot. I'm confused and not keen to buy a new GPU as both can't of suddenly failed. It could be RAM but I want to know if anyone else has had the same issue, plus how they fixed it??
No random suggestions of clearing the CMOS etc, I've tried it all, including swapping RAM and sockets and cards etc etc!
Thanks all :help:
Re: Asus Sabertooth Posting Problem
****ing Hell YEAH. Found someone with the same ****ing Problem.
Cant reboot. My Sabertooth p67 tells my with its onbord led, that the GPU might have a Problem.
Changed everything. Its not the GPU, not the Ram or something else. Also tryed to reset the jumper, took out the motherbordbatterie. Nothing worked.
My Build worked very well for 1 Week. Then i changes setting in the Bios to "weakup by Keybord"
It chrashed down like a fat sack of potatoes.
Is there a solution in sight?:rolleyes:
My System:
Corsair CMPSU-850TXV2
ASUS SABERTOOTH P67 R.3.0,
Intel® Core™ i7-2600
Zalman CNPS9900NT
Corsair DIMM 16 GB DDR3-1600 Quad-Kit
Crucial RealSSD C300 2,5" SSD 128 GB
Re: Asus Sabertooth Posting Problem
Dude, it was a board failure. I RMA' d it and got a different board instead. Sorry to be the bearer of bad news.
All the best,
CTH