Shut down upon startup

Asus Rampage ii extreme motherboard
January 19, 2010 at 02:04:42
Specs: Windows 7 professional 64bit
Hey guys,

Need some help. This is my 5th system build so I thought I knew what I was doing. Anyway, this is a completely new system, Ausu Rampage 2 M/B 3 x 5870 in 3 way crossfire, Intel I7-975, 12Gb Corsair DDR3 12800/1600 (all new in a Xaser water cooled case) Thermaltake 1500W toughpower psu - My last system was water cooled so know what im doing there. The problem is that as soon as i hit the satrt button it flashes blue, fans spin and then everything stops. The M/B stays lit up and I can clear CMOS, but cannot restart the pc. Have checked the power button connectors to the psu to make sure they were right way around - still no luck. nay suggestions?

See More: Shut down upon startup

Report •

January 19, 2010 at 02:36:18
Three hd 5870?Core i7 975?Ddr3 12800/1600?Water cooling?1500w psu? Oh god!! u spend a fortune. Before buying anything u should ask here first or u have a lot of cash to waste.Single hd 5870 can play any game maximum details.Core i7 920 can outperform core i7 975 if u overclock it.And there is no need for water cooling.

Did u benchtest your hardware? If not pull out motherboard,cpu plus cooling system,ram(one stick),single hd5870,psu,keyboard & mouse.Connect all the components together including monitor and start the system. Post back the results.

Report •

January 19, 2010 at 19:45:49
I understand that I have spent a forturne, but maybe I had a reason for doing so? Granted an overclocked 920 will out perform a stock 975, but what about when the 975 is overclocked? And yes 1 5870 will play any game on max, but i wantthe max fps possible for online gaming & 3 overclocked is still faster then 1. This is why the whole system is water cooled in the first place.

In terms of stripping it down and running bench marks. How am I meant to do this if the system will not start in teh first place and considering it is all water cooled that is not as easy as it sounds.

Lastly, the problem is that the M/B is faulty and that is why the system is not running. I may well post bench marks for the complete system once a new M/B has been installed into the system.

Report •

January 19, 2010 at 19:56:57
So I guess you figured it out in the past 5 hours or so, but the response from kuwese was correct - check it with minimal HW installed.

Report •

Related Solutions

Ask Question