Hello,
PC:
AMD Ryzen 5 5600 3.5 GHz 6-Core Processor
ID-COOLING SE-224-XTS BLACK 70 CFM CPU Cooler
Gigabyte B550M DS3H AC Micro ATX AM4 Motherboard (rev.1.5/1.6)
Kingston HyperX Fury 16 GB (2 x 8 GB) DDR4-3200 CL16 Memory
Kingston NV2 1 TB M.2-2280 PCIe 4.0 X4 NVME Solid State Drive
Gigabyte GAMING OC GeForce GTX 1660 SUPER 6 GB Video Card
Montech AIR 100 LITE MicroATX Mid Tower Case
Corsair CX650 650 W 80+ Bronze Certified ATX Power Supply
Windows 11
After powering on PC wont boot, fans spin rgb on GPU on everything seams fine but the screen stays black,
in this state PC cannot be powered off via the power button.
After cutting the power the PC boots without any issue, restarting sleep mode works fine.
Turning off the PC via start menu turns it off but again it cannot boot only after the power is cut.
What we tried:
latest bios (F3d),all cables are connected, all ports work, same issue with XMP on/off, no overclocks,
after the second boot: all temps are good, no crashes while stress testing.
We never encountered such issue before. Any ideas?
PC:
AMD Ryzen 5 5600 3.5 GHz 6-Core Processor
ID-COOLING SE-224-XTS BLACK 70 CFM CPU Cooler
Gigabyte B550M DS3H AC Micro ATX AM4 Motherboard (rev.1.5/1.6)
Kingston HyperX Fury 16 GB (2 x 8 GB) DDR4-3200 CL16 Memory
Kingston NV2 1 TB M.2-2280 PCIe 4.0 X4 NVME Solid State Drive
Gigabyte GAMING OC GeForce GTX 1660 SUPER 6 GB Video Card
Montech AIR 100 LITE MicroATX Mid Tower Case
Corsair CX650 650 W 80+ Bronze Certified ATX Power Supply
Windows 11
After powering on PC wont boot, fans spin rgb on GPU on everything seams fine but the screen stays black,
in this state PC cannot be powered off via the power button.
After cutting the power the PC boots without any issue, restarting sleep mode works fine.
Turning off the PC via start menu turns it off but again it cannot boot only after the power is cut.
What we tried:
latest bios (F3d),all cables are connected, all ports work, same issue with XMP on/off, no overclocks,
after the second boot: all temps are good, no crashes while stress testing.
We never encountered such issue before. Any ideas?