Find the cause before replacing parts
Record what changed, make one supported change at a time, and keep a way back.
Work through a specific symptom
A source-backed path for no display, persistent debug lights, memory and missing storage.
Turn off the PC and disconnect its power. Follow the exact model manuals. Keep cooling installed for boot tests. Never open a PSU or substitute undocumented modular cables. Stop when a procedure or data-loss risk is unclear.
Start with what you can observe.
What can you observe?
Choose the symptom you can reproduce. This guide narrows the next check; it cannot identify a failed component remotely.
The checks and their outcomes
Read a single check or follow its linked next options. A persistent light narrows an investigation; it does not prove that a part is defective.
Check the display path first
Check the display path first
Select the monitor input and check the cable. Use the graphics card output when relying on a discrete card; a motherboard output requires CPU graphics support.
Look for the firmware screen or a change in the monitor’s signal indication.
Return the monitor input or external cable to its previous position if this check changes nothing.
The display path changed the result
The display path changed the result
Record which input, output or cable restored the picture. This observation does not establish that every other component is healthy.
Check that firmware recognizes the installed CPU, memory and storage.
Observation recorded; further checks may remain.
Continue the first-boot checklistRead the printed label, not only its color
Read the printed label, not only its color
During startup, LEDs may change in sequence. Use the exact board manual to interpret a light that remains on; labels and behavior vary.
Identify the persistent label after the board’s documented initialization procedure.
ASUS: motherboard Q-LED troubleshooting · MSI: motherboard boot and display checks
Verify CPU support and power connections
Verify CPU support and power connections
With power disconnected before internal work, compare the exact CPU with the board’s CPU-support list and required BIOS. Check the CPU power plugs against the board and PSU manuals.
A confirmed processor/BIOS match and documented required connections.
Keep the original cables. Do not flash guessed firmware, mix modular PSU cables or remove the CPU as a first step.
Test one documented memory configuration
Test one documented memory configuration
Disconnect power before reseating. Use one module in the manual’s recommended single-module slot. Give initialization the time documented for this board.
A firmware screen, changed LED indication or the same failure. Record the module and slot used.
Restore the recorded module/slot configuration with power disconnected. Stop if you cannot verify the seating or slot procedure.
ASUS: no power, no boot or no display · ASUS: motherboard Q-LED troubleshooting
Check card seating, power and output
Check card seating, power and output
Disconnect power before checking card seating and required power plugs. Follow the exact GPU, board and PSU instructions. Confirm that the monitor cable uses the intended output.
A firmware picture or a changed diagnostic indication after one documented check.
Restore the original connection after a check that changes nothing. Never substitute a modular cable based on appearance.
ASUS: no power, no boot or no display · ASUS: motherboard Q-LED troubleshooting
Use the board’s minimal-POST procedure
Use the board’s minimal-POST procedure
Follow the manufacturer’s documented minimal configuration. Keep CPU cooling installed; retain a graphics card if the CPU has no usable integrated graphics. Disconnect power before removing internal parts.
Observe whether the failure persists with only the documented required components.
Reconnect removed devices one at a time, with power disconnected. Record which change alters the result.
Reconnect one item at a time
Reconnect one item at a time
A successful minimal setup narrows the investigation. Restore one recorded device or connection, then repeat the same boot check.
Identify a repeatable change in behavior. A correlation is not proof that the last part is defective.
Return to the last working documented configuration. Preserve your observations before seeking model-specific support.
Observation recorded; further checks may remain.
Check the exact parts and unresolved compatibilityWhich memory issue do you have?
Which memory issue do you have?
Record module part numbers, installed count, reported capacity and operating data rate before changing anything.
Compare the operating setting with the profile
Compare the operating setting with the profile
Check the actual firmware data rate and exact kit profile. DDR data rate in MT/s is twice its clock frequency in MHz. Profile operation depends on the CPU, board, BIOS and module configuration.
Distinguish a units mismatch or default setting from an unsupported configuration.
Record current settings before changing them. Do not raise voltage or enable a profile without exact support instructions.
Return to a documented baseline
Return to a documented baseline
Use the board’s instructions to disable the optional memory profile or restore supported defaults. Record changed settings first; defaults can also affect boot and security settings.
Repeat the same failing workload at the documented baseline.
Keep the previous values and recovery instructions. Do not blindly clear CMOS or change unrelated settings.
Kingston: CAS latency and memory timings · ASUS: no power, no boot or no display
Record the rate in the correct units
Record the rate in the correct units
For DDR, a 3,000 MHz memory clock corresponds to 6,000 MT/s. This unit conversion does not prove stability, capacity or a particular application result.
Observation recorded; further checks may remain.
Compare timing specificationsThe optional profile is part of the investigation
The optional profile is part of the investigation
Keep the working baseline. Consult the exact board/CPU/kit support and BIOS notes before trying another configuration. Stability at defaults does not prove that the advertised profile is guaranteed on this system.
Observation recorded; further checks may remain.
Review memory compatibility checksRecord the working module and slot
Record the working module and slot
One working arrangement is useful evidence. It does not establish that another module is faulty. Reintroduce the remaining modules using the documented slot order and record each result.
Observation recorded; further checks may remain.
Check the full memory configurationWhere is the drive missing?
Where is the drive missing?
Identify the drive by exact model and capacity. Firmware detection, a boot entry and a Windows drive letter are separate observations.
Check the interface and documented slot rules
Check the interface and documented slot rules
Disconnect power before checking the connection. Verify the exact drive interface, supported slot and shared-port restrictions in the board manual; M.2 alone does not identify the interface.
A supported connection and a repeatable firmware detection result.
Restore the recorded slot/cable arrangement if a check changes nothing. Do not format a drive to solve firmware detection.
Does the drive contain data you need?
Does the drive contain data you need?
Open Windows Disk Management to inspect the exact disk, without initializing, formatting or deleting anything yet.
Confirm the disk identity and whether it has existing partitions or valuable data.
Preserve the data before repair
Preserve the data before repair
Stop before initialization, formatting or deletion. A missing letter or an uninitialized status does not make an existing disk safe to erase. Use documented troubleshooting or qualified recovery support.
A backup or recovery plan before any destructive action.
Next step: model-specific support.
Read Microsoft’s disk troubleshootingFollow the new-disk setup instructions
Follow the new-disk setup instructions
For a confirmed new empty drive, use Microsoft’s initialization and volume-creation instructions. Reconfirm the exact disk before applying any write operation.
A configured volume and drive letter. Initialization and formatting are not a hardware-detection repair.
There is no safe undo for erasing the wrong disk; stop if its identity or data status is uncertain.
Next step: a documented manual procedure.
Open Microsoft’s new-disk instructionsVerify the boot configuration without erasing data
Verify the boot configuration without erasing data
Record the firmware boot entries and the previous working storage configuration. A detected drive may lack the required boot entry; do not initialize it merely because Windows will not start.
Model-specific recovery instructions that preserve existing data.
Next step: model-specific support.
Review Windows recovery optionsResolve the exact slot configuration
Resolve the exact slot configuration
Check the manual for your board revision and installed CPU. Shared lanes or disabled connections are conditional rules, not proof of a defective drive.
Next step: verify the exact documentation.
See a documented B650 TOMAHAWK exampleStart with the exact model’s manual
Start with the exact model’s manual
Find the motherboard model and revision, CPU, memory kit and GPU model. Use their official support pages for indicators, slots and procedures. Stop before an internal step you cannot verify.
Next step: verify the exact documentation.
Find hardware and official source linksASUS: no power, no boot or no display · MSI: motherboard boot and display checks
Bring the recorded evidence to model-specific support
Bring the recorded evidence to model-specific support
Keep the symptom, exact models, firmware version, persistent indicator and checks already performed. Remaining possibilities need model-specific investigation; this guide has not proven a part defective.
Next step: model-specific support.
Review documented checks and unknownsMore diagnostic checklists
Keep the starting state
Record the application or game version, settings, driver version, recent hardware changes and the circumstances that reproduce the issue. Compare the same scene and workload after each change. A single utilization reading cannot diagnose every constraint.
Use official drivers and exact support manuals. Never open a power supply, reuse undocumented modular cables, or use unofficial firmware and automatic driver-updater utilities.