MPG X670E CARBON WIFI (Late start and When restarting windows the bios orange light stays on.)

hakanylmz

New member
Joined
Jul 30, 2024
Messages
5
I have Bios version 7D70v1J3 (beta version). The boot time was much longer before. With this version the system boots a bit better, but again after waiting 15-20 seconds at startup the keyboard lights up and the system boots. I don't mind this, my biggest problem is below.

When I try to reboot the computer while Windows is open, or when the computer reboots after an update, the system hangs. When I reboot, the Bios orange light is on and the motherboard LED indicator says 00 and stays there. I have to press and hold the power button, turn off and restart.

Is this a common problem?


MAINBOARD: MPG X670E CARBON WIFI
CPU: AMD R7 7800X3D
RAM: Corsair Vengeance RGB 32 GB (2x16) 6000MHz DDR5 CL30 CMH32GX5M2B6000Z30K
 
Yep, same thing with me. Long boot from the begining, but I don't know about the lights. Windows restart in black screen and the computer stays on. I have an other CPU and other memory.
 
Just took a look at the Bois Support and it seems there are new updates after a long time I did look anymore.

- Fix the issue where the system cannot boot the operating system and keeps restarting.
- Optimize system boot time.

Related changes are from last mounth, So maybe we should try that.
 
Evry time. I did and OC before, but out precaution removed all manual setting. Going to check the iGPU, but I think I disabled that. Back in a minute.
 
Hi all, same (long-standing) issue for me, although with a slightly different motherboard: MAG X670E TOMAHAWK WIFI.
I've recently updated bios to 7E12v1E2(Beta) as I saw there were some fixes that could be related, but sadly that didn't help.

System start sometimes works, sometimes doesn't:
- Half of the time it takes about 20 seconds until the keyboard lights up and boot starts, no problems after that.
- Half of the time it doesn't start booting even if I wait several minutes, and then I have to cycle power and try again.
- Restarting from Windows has never worked, always have to hold power button to turn off and start the system again.

Not sure if a BIOS update resets all settings or just some, but the only changes I've made after the update were EXO (6000MHz) and fan settings (DC to PWM).

System:
MB: MSI MAG X670E TOMAHAWK WIFI
CPU: AMD Ryzen 7 7700X 4.50GHz
GPU: MSI NVIDIA GeForce GTX 1070 8GB
RAM: 32GB 6000MHz DDR5 RAM Kingston Fury Beast CL36 (2x16GB) (KF560C36BBEK2-32)
SSD1: SAMSUNG 500GB 980 PRO M.2 2280
SSD2: KINGSTON 4TB NV2 M.2 2280 SNV2S/4000G
PSU: SEASONIC Focus GX 750W
 
I am using the latest now 7D70v1J3(Beta version) and still have issues. All other drivers are also uptodate now. Normally when I start I see a cursor flashing, but not on restart. Than I got that message "no display input" and then the screen turnes and stays black (fans keep spinning).

Not sure if a BIOS update resets all settings or just some, but the only changes I've made after the update were EXO (6000MHz) and fan settings (DC to PWM).

That was set the first time with me too and now I set it back to 6000MHz. I believe it was 30-36-36-76 in the try mode. Last number not sure. There are 3 EXPO's with the same name '30-36-36-76' and one with the *. I have selected the one before the * because the voltage is 1.350V. Screen freeze are mostly the sticks. Think we need to search in that way.

So now I tried with only expo enabled (red block on top of the screen). Could also not restart, but the timings are like on the sticks. I think one of the timings is set to sharp. Now I will adjust RC clocks manualy.
 

Attachments

  • Screenshot 2024-08-08 134915.png
    Screenshot 2024-08-08 134915.png
    110.5 KB · Views: 100
Last edited:
Adapting the timings did not workout. Had to clear Cmos and only disabled the iGPU.

I left RAM to default 4800MHz, but something is still off.

"no display input" was still there. Cursor could be seen now (so I think he is passed the bootloader), but didn't blink and had to wait for 30seconds before the windows logo was there.
 
I've now tried turning off EXPO completely and setting Memory Context Restore from Auto to Enabled, neither did help. In fact the latter seemed to reduce the chances to actually boot at all, but could have been just random (mis)luck.

Also found this thread about older GPUs in this motherboard, downloaded the NVidia firmware updater that's linked in there, and that actually said my GPU needed an update, so I had high hopes. Alas, after the update there was still no change to my boot times.

Edit: sorry I didn't want to hijack the topic with long boot times as that seems to be a common problem, but the OP's main issue (system hangs after windows restart) still stands, as I'm experiencing the same still.
 
Last edited:
I have updated my MSI GPU too and forgot to tell. When I was doing date I got the msi center installer window to install (can be downloaded too. Sorry for that. I had some mobo driver update missing, but the issue still remains.
 
This Agesa version should also not be used by anyone with a 7000 CPU! AMD has destroyed the 7000 series when optimizing RAM for the 9000 series. The Ryzen 7000 was only corrected again with patch AB. It was here in the neighboring post several times but was censored away again and again.
In the review instructions from AMD for the new Ryzen 9000 it was not written for fun that the old CPUs should not be used with the new AGESA because it slows down the old ones.
It's working fine for me, in fact, I'm getting slightly better R23 scores with my 7900X3D using 7D70v1J3 than I was with previous versions :unsure:
 
yesterday I got windows update

2024-08 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 11, version 23H2 for x64 (KB5042099)
2024-08 Cumulative Update for Windows 11 Version 23H2 for x64-based Systems (KB5041585)

after the update my computer crashed, because it couldn't restart. So I did a check on what NET Framework version I am now.

Microsoft Windows [Version 10.0.22631.4037]
(c) Microsoft Corporation. All rights reserved.

C:\Users\Daen>reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP"

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\CDF
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v2.0.50727
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.0
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4.0

C:\Users\Daen>reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\full" /v version

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\full
version REG_SZ 4.8.09032


C:\Users\Daen>reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5" /v version

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5
version REG_SZ 3.5.30729.4926

Don't know about 3.5, but it is for sure not 4.8.1. The issue just got bigger!
 
Hi. I have the identical problem as described by OP (power on takes 15-20 seconds, restart hangs with amber LED, Only BIOS change is switching to the EXPO profile on the RAM).

I have the same RAM, but my CPU and Mainboard are different.

MAINBOARD: X870E GAMING PLUS WIFI (MS-7E16)
CPU: AMD Ryzen 9950X
RAM: Corsair Vengeance RGB 32GB (2x16) 6000MHz DDR5 CL30 CMH32GX52B6000Z30
GPU: NVIDIA GeForce GTX 1080Ti FE
 
You are not allone having that led. I looked it up and it seems that the UEFI has problems with the CPU. Not much we can do about that. I hope somebody from MSI is working on this to solve this.

Reported CPU's we have right now are
AMD Ryzen 9950X, 7700X, 7800X3D,...

Bios:
I see that there has been an update after I updated to the latest on the 2024-08-08.
Bios files
latest version is form 2024-08-13
 
Last edited:
Those stick seems to be flawless working with my other intel PC with ajustments for a long time without a GPU, thinking of those stick are specialy made for an AMD PC and not working. Maybe it are the sticks. I allways thought that the RAM is cleared after a power down. I I have a very strong power supply, so it would be my doubt that it didn't catch up the need for those. In the beginning it worked perfectly with me, and recently it start to fail. No offence to you.
 
Last edited:
Back
Top