add arrow-down arrow-left arrow-right arrow-up authorcheckmark clipboard combo comment delete discord dots drag-handle dropdown-arrow errorfacebook history inbox instagram issuelink lock markup-bbcode markup-html markup-pcpp markup-cyclingbuilder markup-plain-text markup-reddit menu pin radio-button save search settings share star-empty star-full star-half switch successtag twitch twitter user warningwattage weight youtube

Motherboard not lighting up, all other components reset evry 4 seconds after a click

MrTorgueXD

20 months ago

I'm not sure whats going on with my computer. Ive just finished building it and I cannot get it to boot. Here's my build:

https://pcpartpicker.com/list/fYpBvn

Link to video: https://youtu.be/7pBdm43QLi4

Make sure and watch with sound

Does anyone know why everything but the motherboard is lighting up/ how I can remedy it?

I was originally using the Silverstone - Strider Titanium 700W 80+ Titanium Certified Fully-Modular ATX Power Supply but was having even more issues with it. With this power supply only the RAM was lighting up. Also, when I first power on the system the monitor flashes on until the first click or reset happens, then it remains inactive.

Any and all help is greatly appreciated.

Comments

  • 20 months ago
  • 2 points
  • I don't think that this is the problem, but your CPU has 165W TDP and the cooler can handle up to 130 TDP, but it is unlikely that the CPU runs so hot in just the 7 seconds boot-up phase

  • The next thing I'd try is going with the minimum: 1 Stick of RAM, 1 storage drive, CPU, cooler, GPU .... no extra fans, no extra storage, no extra ram sticks

  • see if this changes anything at all

  • dumb question: Are you certain you have connected two of 2x4(1x8) ATX power plugs to the CPU? meaning full 16 pins Upper right corner 12V

  • 20 months ago
  • 1 point

Thanks for the reply! I do have both 2x4 power cables powering the CPU. The first power supply I tried using had cables that were 4 pin(x2) side by side. That didn’t work but that could’ve not been the issue. Currently using two 8 pin cables.

Should I leave the SSD M.2 drive in while testing or the HDD connected via SATA?

Thanks again

  • 20 months ago
  • 1 point

Also, where did you see a listed TDP for my CPU Cooler?

  • 20 months ago
  • 1 point

I went to the official homepage to look for the listed TDP: http://www.coolermaster.com/cooling/cpu-air-cooler/masterair-g100m/

Low Profile for Mini-ITX Builds The low profile G100M stands at 74.5mm, a great fit for slim PC cases, including mini-ITX cases. Even at these small dimensions, the heatsink has cooling capacity of 130W TDP.

  • 20 months ago
  • 1 point

Hello, I did everything you suggested. After removing some of the RAM sticks, the CPU indicator light was revealed which was flashing. I removed the CPU Cooler, cleaned off the thermal paste, and carefully reinstalled the CPU. After re installing the CPU and CPU Cooler the Red CPU Indicator light is still on. Is it possible that the CPU is not getting enough power? What are some other common CPU errors?

  • 20 months ago
  • 1 point

well, you already tested with 2 different PSUs for power delivery, so if not having enough power is the problem, then the MOBO is faulty and not passing-through the power needed.

What does it say on the debug LEDs ?

  • Code Description
  • 10 PEI Core is started.
  • 11 Pre-memory CPU initialization is started.
  • 12~14 Reserved.
  • 15 Pre-memory North-Bridge initialization is started.
  • 16~18 Reserved.
  • 19 Pre-memory South-Bridge initialization is started.
  • 1A~2A Reserved.
  • 2B~2F Memory initialization.
  • 31 Memory installed.
  • 32~36 CPU PEI initialization.
  • 37~3A IOH PEI initialization.
  • 3B~3E PCH PEI initialization.
  • 3F~4F Reserved.
  • 60 DXE Core is started.
  • 61 NVRAM initialization.
  • 62 Installation of the PCH runtime services.
  • 63~67 CPU DXE initialization is started.
  • 68 PCI host bridge initialization is started.
  • 69 IOH DXE initialization.
  • 6A IOH SMM initialization.
  • 6B~6F Reserved.
  • 70 PCH DXE initialization.
  • 71 PCH SMM initialization.
  • 72 PCH devices initialization.
  • 73~77 PCH DXE initialization (PCH module specific).
  • 78 ACPI Core initialization.
  • 79 CSM initialization is started.
  • 7A~7F Reserved for AMI use.
  • 80~8F Reserved for OEM use (OEM DXE initialization codes).
  • 90 Phase transfer to BDS (Boot Device Selection) from DXE.
  • 91 Issue event to connect drivers.
  • 92 PCI Bus initialization is started.
  • 93 PCI Bus hot plug initialization.
  • 94 PCI Bus enumeration for detecting how many resources are requested.
  • 95 Check PCI device requested resources.
  • 96 Assign PCI device resources.
  • 97 Console Output devices connect (ex. Monitor is lighted).
  • 98 Console input devices connect (ex. PS2/USB keyboard/mouse are activated).
  • 99 Super IO initialization.
  • 9A USB initialization is started.
  • 9B Issue reset during USB initialization process.
  • 9C Detect and install all currently connected USB devices.
  • 9D Activated all currently connected USB devices.
  • 9E~9F Reserved.
  • A0 IDE initialization is started.
  • A1 Issue reset during IDE initialization process.
  • A2 Detect and install all currently connected IDE devices.
  • A3 Activated all currently connected IDE devices.
  • A4 SCSI initialization is started.
  • A5 Issue reset during SCSI initialization process.
  • A6 Detect and install all currently connected SCSI devices.
  • A7 Activated all currently connected SCSI devices.
  • A8 Verify password if needed.
  • A9 BIOS Setup is started.
  • AA Reserved.
  • AB Wait user command in BIOS Setup.
  • AC Reserved.
  • AD Issue Ready To Boot event for OS Boot.
  • AE Boot to Legacy OS.
  • AF Exit Boot Services.
  • B0 Runtime AP installation begins.
  • B1 Runtime AP installation ends.
  • B2 Legacy Option ROM initialization.
  • B3 System reset if needed.
  • B4 USB device hot plug-in.
  • B5 PCI device hot plug.
  • B6 Clean-up of NVRAM.
  • B7 Reconfigure NVRAM settings.
  • B8~BF Reserved.
  • C0~CF Reserved.
  • E0 S3 Resume is started (called from DXE IPL).
  • E1 Fill boot script data for S3 resume.
  • E2 Initializes VGA for S3 resume.
  • E3 OS S3 wake vector call.
  • S3 Resume
  • F0 Recovery mode will be triggered due to invalid firmware volume detection.
  • F1 Recovery mode will be triggered by user decision.
  • F2 Recovery is started.
  • F3 Recovery firmware image is found.
  • F4 Recovery firmware image is loaded.
  • F5~F7 Reserved for future AMI progress codes.
  • 50~55 Memory initialization error occurs.
  • 56 Invalid CPU type or speed.
  • 57 CPU mismatch.
  • 58 CPU self test failed or possible CPU cache error.
  • 59 CPU micro-code is not found or micro-code update is failed.
  • 5A Internal CPU error.
  • 5B Reset PPI is failed.
  • 5C~5F Reserved.
  • D0 CPU initialization error.
  • D1 IOH initialization error.
  • D2 PCH initialization error.
  • D3 Some of the Architectural Protocols are not available.
  • D4 PCI resource allocation error. Out of Resources.
  • D5 No Space for Legacy Option ROM initialization.
  • D6 No Console Output Devices are found.
  • D7 No Console Input Devices are found.
  • D8 It is an invalid password.
  • D9~DA Can't load Boot Option.
  • DB Flash update is failed.
  • DC Reset protocol is failed.
  • DE~DF Reserved.
  • E8 S3 resume is failed.
  • E9 S3 Resume PPI is not found.
  • EA S3 Resume Boot Script is invalid.
  • EB S3 OS Wake call is failed.
  • EC~EF Reserved.
  • F8 Recovery PPI is invalid.
  • F9 Recovery capsule is not found.
  • FA Invalid recovery capsule.
  • FB~FF Reserved.

You can try starting the MOBO with only the CPU (+cooler), no RAM, no storage whatsoever and see if you can any Error codes like "RAM missing"

  • 20 months ago
  • 1 point

Thanks for the thorough reply! The LED indicators don't even come on - and the red flickering light is the same when no RAM is connected. I carefully reinstalled the processor so I know its not just set wrong. I also double checked the compatibility of the Chip and Chipset and they match. Either the motherboard is fualty or the Processor is, but I have no way of knowing which without having a working version of either.

  • 20 months ago
  • 1 point

that sucks hard

RMA the MOBO, they either send you a new one or tell you, that yours is fine. either way, you should get a functioning MOBO back. IF the problem is still there, RMA the CPU.

Sort

add arrow-down arrow-left arrow-right arrow-up authorcheckmark clipboard combo comment delete discord dots drag-handle dropdown-arrow errorfacebook history inbox instagram issuelink lock markup-bbcode markup-html markup-pcpp markup-cyclingbuilder markup-plain-text markup-reddit menu pin radio-button save search settings share star-empty star-full star-half switch successtag twitch twitter user warningwattage weight youtube