F5F Stay Refreshed Hardware Desktop No signal available for display or peripheral operation with the updated specifications.

No signal available for display or peripheral operation with the updated specifications.

No signal available for display or peripheral operation with the updated specifications.

H
Hydr0ph0bia
Junior Member
41
12-26-2022, 10:22 AM
#1
Completed the upgrade of the motherboard, CPU, and GPU. Now when I attempt to boot, fans start spinning up and the GPU and cooler lights activate, but there’s no display and neither the mouse nor keyboard lights up. After a few minutes everything powers off and restarts.

I’m fairly sure everything is properly seated and all cables are connected. I’ve tried removing the GPU, rearranging components, shorting the CMOS jumper, taking out the CMOS battery, using various monitors and HDMI/display cables, switching to a different keyboard, and connecting different USB ports—including one labeled for BIOS flashing. I believe the peripherals, their cables, and RAM shouldn’t be the problem since they worked in my PC a few days ago. I don’t have another motherboard or CPU available for troubleshooting, and it seems this particular motherboard doesn’t have debugging LEDs or a buzzer/speaker. The power supply unit also shouldn’t be the cause as it was just purchased.

I noticed that my Windows installation USB stick became warm after running for a minute, indicating the USB ports are functioning at least partially. I also tried booting without any RAM installed, and it followed a similar pattern—fans and GPU/cooler lights on, no display, but this time it shut down and restarted in about 30 seconds rather than several minutes, suggesting the RAM might not be the issue.

My only suspicion is related to my storage setup. In my previous build, I had SSD 1 (C, boot drive), HDD (D), and SSD 2 (E). They were all placed in the same locations, and I planned to wipe the C drive during the fresh Windows installation. I don’t see why this would cause all these problems, but it’s possible there are boot instructions from my previous 10th-gen CPU.

Details:
- CPU: i7-13700K
- CPU cooler: NZXT Kraken X53 240mm
- MOBO: Gigabyte B760M Gaming X AX DDR4
- RAM: G.Skill Ripjaws V 32 GB (2 x 16 GB)
- Storage: 2x Samsung 980 PRO SSD 500GB - M.2 NVMe, 1x Seagate BarraCuda 2TB Internal HDD
- GPU: RTX 3080 Ti
- PSU: Corsair RMX Series RM850x 80 Plus Gold
- Chassis: Obsidian Series 750D Full Tower ATX Case
- OS: Windows 10
- Monitor: 2x AOC 24" 144Hz (also tested with older BENQ GL2460HM)
- Previous build differences:
- CPU: i7-10700K
- MOBO: MPG Z490 Gaming Edge WiFi
- GPU: RTX 2060 Super
- PSU: Corsair RM Series RM650 80 Plus Gold
H
Hydr0ph0bia
12-26-2022, 10:22 AM #1

Completed the upgrade of the motherboard, CPU, and GPU. Now when I attempt to boot, fans start spinning up and the GPU and cooler lights activate, but there’s no display and neither the mouse nor keyboard lights up. After a few minutes everything powers off and restarts.

I’m fairly sure everything is properly seated and all cables are connected. I’ve tried removing the GPU, rearranging components, shorting the CMOS jumper, taking out the CMOS battery, using various monitors and HDMI/display cables, switching to a different keyboard, and connecting different USB ports—including one labeled for BIOS flashing. I believe the peripherals, their cables, and RAM shouldn’t be the problem since they worked in my PC a few days ago. I don’t have another motherboard or CPU available for troubleshooting, and it seems this particular motherboard doesn’t have debugging LEDs or a buzzer/speaker. The power supply unit also shouldn’t be the cause as it was just purchased.

I noticed that my Windows installation USB stick became warm after running for a minute, indicating the USB ports are functioning at least partially. I also tried booting without any RAM installed, and it followed a similar pattern—fans and GPU/cooler lights on, no display, but this time it shut down and restarted in about 30 seconds rather than several minutes, suggesting the RAM might not be the issue.

My only suspicion is related to my storage setup. In my previous build, I had SSD 1 (C, boot drive), HDD (D), and SSD 2 (E). They were all placed in the same locations, and I planned to wipe the C drive during the fresh Windows installation. I don’t see why this would cause all these problems, but it’s possible there are boot instructions from my previous 10th-gen CPU.

Details:
- CPU: i7-13700K
- CPU cooler: NZXT Kraken X53 240mm
- MOBO: Gigabyte B760M Gaming X AX DDR4
- RAM: G.Skill Ripjaws V 32 GB (2 x 16 GB)
- Storage: 2x Samsung 980 PRO SSD 500GB - M.2 NVMe, 1x Seagate BarraCuda 2TB Internal HDD
- GPU: RTX 3080 Ti
- PSU: Corsair RMX Series RM850x 80 Plus Gold
- Chassis: Obsidian Series 750D Full Tower ATX Case
- OS: Windows 10
- Monitor: 2x AOC 24" 144Hz (also tested with older BENQ GL2460HM)
- Previous build differences:
- CPU: i7-10700K
- MOBO: MPG Z490 Gaming Edge WiFi
- GPU: RTX 2060 Super
- PSU: Corsair RM Series RM650 80 Plus Gold

G
Goddesss
Member
103
12-28-2022, 12:48 AM
#2
Welcome to the forums, newcomer!
When posting a thread of troubleshooting nature, it's customary to include your full system's specs. Please list the specs to your build like so:
CPU:
CPU cooler:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:
Monitor:
include the age of the PSU apart from it's make and model. BIOS version for your motherboard at this moment of time.
Since you mentioned upgrading your PC, we should see a before and after to your specs.
G
Goddesss
12-28-2022, 12:48 AM #2

Welcome to the forums, newcomer!
When posting a thread of troubleshooting nature, it's customary to include your full system's specs. Please list the specs to your build like so:
CPU:
CPU cooler:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:
Monitor:
include the age of the PSU apart from it's make and model. BIOS version for your motherboard at this moment of time.
Since you mentioned upgrading your PC, we should see a before and after to your specs.

Z
zamys
Senior Member
690
12-28-2022, 01:25 AM
#3
I updated the original post to add all missing details and typos. The PSU is newly bought. The MOBO BIOS version remains unclear; I assume F1, the oldest, since I haven’t even seen the BIOS yet.

I also attempted to remove everything from the case and connect only essential components: 8 pin CPU power, 24 pin ATX, one RAM stick, an HDMI link between MOBO and monitor, a USB keyboard, one SSD, and the cooler powered via SATA cable, connected to CPU_FAN and F_USB1.

This setup has led to the same problem. My initial thought was that running it for a few minutes might have caused an overshoot. When timed properly, it runs around 90 seconds before shutting down and restarting. Removing the RAM causes about 30 seconds before shutdown. I observed a click sound a few seconds after powering on through the power switch, followed by another click when everything powered off. This doesn’t seem like a beep code, as one beep should confirm successful POSTing. Another possibility was running it without the SSD, which also resulted in a similar 90-second shutdown and restart.
Z
zamys
12-28-2022, 01:25 AM #3

I updated the original post to add all missing details and typos. The PSU is newly bought. The MOBO BIOS version remains unclear; I assume F1, the oldest, since I haven’t even seen the BIOS yet.

I also attempted to remove everything from the case and connect only essential components: 8 pin CPU power, 24 pin ATX, one RAM stick, an HDMI link between MOBO and monitor, a USB keyboard, one SSD, and the cooler powered via SATA cable, connected to CPU_FAN and F_USB1.

This setup has led to the same problem. My initial thought was that running it for a few minutes might have caused an overshoot. When timed properly, it runs around 90 seconds before shutting down and restarting. Removing the RAM causes about 30 seconds before shutdown. I observed a click sound a few seconds after powering on through the power switch, followed by another click when everything powered off. This doesn’t seem like a beep code, as one beep should confirm successful POSTing. Another possibility was running it without the SSD, which also resulted in a similar 90-second shutdown and restart.