New Build, No Display

R

ryan1180

New Member
Hi,

I just completed a computer build with:

CoolerMaster 600W Extreme Power Plus
SONY Black SATA DVD-ROM Drive Model DDU1681S-0B - OEM
Western Digital Caviar Green WD7500AARS 750GB IntelliPower SATA 3.0Gb/s 3.5" Internal Hard Drive -Bare Drive
COOLER MASTER HAF 912 RC-912-KKN1 Black SECC/ ABS Plastic ATX Mid Tower Computer Case
SAPPHIRE 100283-3L Radeon HD 5770 1GB 128-bit GDDR5 PCI Express 2.1 x16 HDCP Ready CrossFireX Support Video Card
Intel Core i3-2100 Sandy Bridge 3.1GHz LGA 1155 65W Dual-Core Desktop Processor BX80623I32100
MSI P67A-C43 (B3) LGA 1155 Intel P67 SATA 6Gb/s USB 3.0 ATX Intel Motherboard
ushkin Enhanced Essentials 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1333 (PC3 10666) Dual Channel Kit Desktop Memory Model


Originally when I started up the computer it would turn on for 5 seconds and then shut off. I then found out that my RAM was in the wrong slot, and was moved to the closest slot to the CPU. All four blue lights turn on and all of the fans work including the fan on the video card.

Now, when I turn the computer on it starts but there is no display. I am running the output from the video card which seems to be functional(fan is running). I have tried multiple monitors and none of them have changed the outcome.

Any help would be GREATLY appreciated, this is my first build and I am really lost here.
 
So most of what I have read says to try resetting the BIOS by switching CMOS jumper. When I was looking for the jumper I discovered that it was not there. Could the lack of a CMOS jumper be causing all of my problems?
 
What does your manual say concerning the jumper?

Let's try a tried and true diagnostic method that though it can be tedious at times can also be very effective.

Uninstall every piece of hardware you have from your motherboard including power cables except the following: cpu, one stick of RAM, and the main power cable to your motherboard.

Now boot-up. If it remains booted up then shut it down and add one piece of hardware and boot-up again. If it remains on then repeat as needed.

Often this can zero in on where the problem is. It worked for me and many others on a new build.
 
You must log in or register to reply here.
Back
Top