F5F Stay Refreshed Hardware Desktop PC starts only via Windows using BIOS settings

PC starts only via Windows using BIOS settings

PC starts only via Windows using BIOS settings

X
x78green
Member
60
12-16-2022, 05:17 AM
#1
Hello everyone,
I'm facing a challenge.
My system originally had 32 GB RAM (16+16), but I upgraded it to 128 GB (32x4). After turning it on, the screen goes black. Once I press and hold the shutdown button before restarting, a message appears indicating the issue lies in the BIOS settings. It advises using Stable or suggests that a long press of the power button might have caused the shutdown. It also recommends pressing F1 to access BIOS settings.

In the BIOS, I navigate to the Boot section and select the appropriate disk, which leads to Windows.

I've removed or reinserted my tablet, reset the BIOS to its default settings, and updated it to the latest version. Additionally, I enabled D.O.C.P. in Windows, but the memory settings now differ from those recorded in the profile and shown in BIOS.

My specifications are:
- Motherboard: ASUS PRIME Z790-P (LGA 1700, Intel Z790, 128 GB, PCIe 5.0)
- CPU: Intel Core i7-13700KF (Raptor Lake)
- Old RAM: G.Skill Trident Z5 DDR5 6000 Mhz (2x16 GB)
- New RAM: G.Skill TRIDENT Z5 Neo [F5-6000J3040G32GX2-TZ5N] 64 GB (32 x 2)
More info: https://imgur.com/a/r1WbOpy
X
x78green
12-16-2022, 05:17 AM #1

Hello everyone,
I'm facing a challenge.
My system originally had 32 GB RAM (16+16), but I upgraded it to 128 GB (32x4). After turning it on, the screen goes black. Once I press and hold the shutdown button before restarting, a message appears indicating the issue lies in the BIOS settings. It advises using Stable or suggests that a long press of the power button might have caused the shutdown. It also recommends pressing F1 to access BIOS settings.

In the BIOS, I navigate to the Boot section and select the appropriate disk, which leads to Windows.

I've removed or reinserted my tablet, reset the BIOS to its default settings, and updated it to the latest version. Additionally, I enabled D.O.C.P. in Windows, but the memory settings now differ from those recorded in the profile and shown in BIOS.

My specifications are:
- Motherboard: ASUS PRIME Z790-P (LGA 1700, Intel Z790, 128 GB, PCIe 5.0)
- CPU: Intel Core i7-13700KF (Raptor Lake)
- Old RAM: G.Skill Trident Z5 DDR5 6000 Mhz (2x16 GB)
- New RAM: G.Skill TRIDENT Z5 Neo [F5-6000J3040G32GX2-TZ5N] 64 GB (32 x 2)
More info: https://imgur.com/a/r1WbOpy

T
TheFreshKing
Junior Member
5
12-18-2022, 07:57 AM
#2
Welcome to the forums, newcomer! After updating the BIOS to the latest version, did you reset the CMOS? If not, reset it and then install two sticks of RAM in slots A2 and B2. If everything works smoothly, proceed to add the remaining two sticks from the G.Skill kit.

The issue I noticed about your setup is:
https://www.gskill.com/specification/165...cification
You chose a RAM kit compatible with AMD's AM5 platform. You should have considered a kit featuring Intel's X.M.P. Instead, I recommend returning the current kit and selecting one that matches your memory QVL for a 128GB configuration. If you're unable to do that, opt for a kit with Intel's X.M.P.
T
TheFreshKing
12-18-2022, 07:57 AM #2

Welcome to the forums, newcomer! After updating the BIOS to the latest version, did you reset the CMOS? If not, reset it and then install two sticks of RAM in slots A2 and B2. If everything works smoothly, proceed to add the remaining two sticks from the G.Skill kit.

The issue I noticed about your setup is:
https://www.gskill.com/specification/165...cification
You chose a RAM kit compatible with AMD's AM5 platform. You should have considered a kit featuring Intel's X.M.P. Instead, I recommend returning the current kit and selecting one that matches your memory QVL for a 128GB configuration. If you're unable to do that, opt for a kit with Intel's X.M.P.

P
Poi_Sorg
Junior Member
19
12-23-2022, 08:30 AM
#3
Yeah, I thought you mentioned a memory issue, but that was already said!
P
Poi_Sorg
12-23-2022, 08:30 AM #3

Yeah, I thought you mentioned a memory issue, but that was already said!