New
#1
After a few hours, my new PC build decides to stop coming on
So here's the deal... I'm relatively new to PC building and this is the first PC I've built from the ground up. I spent a very long time researching which parts I was going to get, so I feel awful that it's no longer working. I have a few guesses as to what's causing the problem, but I'd love to hear some helpful ideas prior to trying anything on my own.
So, let's start with my build:
Case: Cooler Master HAF 922
Motherboard: ASUS P8Z77-V LGA 1155 Intel Z77
CPU: Intel Core i5-3570K Ivy Bridge 3.4GHz
Video Card: EVGA SuperClocked Geforce GTX 770 2GB
Memory: Crucial Ballistix Sport 8GB 240-Pin DDR3 SDRAM 1600
CPU Fan: Cooler Master Hyper 212 EVO
Hard Drive: Seagate Constellation 1TB
SSD: Samsung 840 Series 120GB
PSU: Corsair HX Series 850W
Now, I spent a great deal of time ensuring that everything was plugged in correctly... and after a grueling and exhausting night, I got it to work on my first try. Everything seemed to go well - I installed Windows 7 64 bit, updated as many drivers as I could find, installed all of my favorite programs, added all of my personal stuff to the hard drives... and then, immediately after finishing a game of Slender: The Arrival, the PC just shuts down on me. I turned it back on and received no error messages or anything, so I assumed it was a fluke... till about a minute later it happens again while I'm making a Skype call. At that point, it wouldn't turn back on at all. When power is plugged in, one green LED glows on the MB... yet it won't POST or anything.
So... I'm assuming the problem is either with my motherboard or PSU, and I plan to test that theory with a second PSU I have laying around. That said, I'd really appreciate some ideas as to what's causing this. I gotta admit, it really brought me down tonight... so I'm really hoping for some clarity.
I should note however that one odd thing happened while the PC was still working. I kept trying to do the Windows Experience Index thing to see how it was rated, and it kept failing for some reason. I don't remember exactly how the error was worded, though it mentioned that it might have to do with a malfunctioning driver, OS or device.