Pattern to record: Windows Boot Manager or the expected loader is absent despite a healthy drive.

Record the boot configuration

Separate a stock configuration from memory profiles, CPU tuning and GPU changes. A boot fault that began after tuning should first be reproduced at supported defaults, without increasing voltage to make POST succeed. One possible explanation is that the reference to a valid operating-system loader has been deleted or reordered.

Preserve recovery options

Unstable overclocking can corrupt data and should not be used during diagnosis. Selecting an unrelated entry may hide the real storage problem.

Firmware and hardware checks

1. Return to documented baseline settings and test one hardware group at a time.
2. Verify the loader on disk and inspect the UEFI boot list.

Recovery and startup checks

If the checks support this cause, recreate the correct signed entry and place it in a sensible order. Verification should cover repeated cold boots, memory load, graphics initialisation, restart and sleep.

For an assessment of your gaming computer, contact AEPC in Burswood or call 027 908 8880. Provide the model and the conditions that reproduce this problem. Workshop visits are by appointment.