Even after replacing the CPU, the PCIe slot version is still stuck.

gjrtm343154402df

New member
Joined
Feb 23, 2025
Messages
5
My previous setup was:
9700X
X870 Tomahawk WiFi
G.Skill 64GB CL30 6000MHz
RTX 5080
FSP 1000W PSU

Everything was working perfectly fine. But after replacing my CPU with the 9800X3D, everything went completely wrong.

From the very first boot with the 9800X3D, I immediately noticed stuttering on the Windows lock screen—my mouse, keyboard, and display were lagging. It felt like the system was freezing every 3–5 seconds. As the issue worsened, the screen would go black, or I would get a Video Scheduler Internal Error blue screen, causing the system to restart. However, sometimes after a reboot, the system would work normally.

When the system was stuttering, I checked GPU-Z, and I noticed that the PCIe version was stuck at 1.1x16. Even under load, it remained locked at 1.1x16. In some cases, it was stuck at 2.0x16 or 3.0x16, causing severe lag. During these moments of lag, even when the system was idle, the GPU usage would spike abnormally. And when the system did work "normally," the PCIe version remained locked at 5.0x16, rather than dynamically adjusting between 2.0x16 (idle) and 5.0x16 (load) as it should.

Since all of these problems started only after installing the 9800X3D, I decided to swap back to my 9700X, and everything returned to normal. Even in GPU-Z, I could see that PCIe behavior was back to normal—2.0x16 in idle and 5.0x16 under load.

The 9800X3D has already been sent for RMA and replaced. and I have installed the latest version, 1A26 Beta, but the issue remains the same.
 

Attachments

  • 33.gif
    33.gif
    31.7 KB · Views: 560
Last edited:
Oh I think I found a way : setting aspm to L0 in bios + on windows the settings for aspm to moderate energy save.



I had two days without issues. Hoping it will work on the long run..
In my opinion, changing settings that affect how PCIe lanes are shared or indirectly or directly affect voltage—like turning on/off spread spectrum, tweaking L0, or changing the Windows power plan, etc—can make us think the problem is really fixed when it’s not. For example, when I turned on spread spectrum, I had no issues for a few days, which made me feel safe. But when I connected an external hard drive and restarted the computer, the problem came back. I also noticed that when I changed the settings for m2_2<->USB4 and then switched them back, everything was fine for a few days before the issue returned. It seems these settings only delay the problem instead of fixing it completely.
 
Last edited:
Hello
I had the same problem with my Asus TUF GAMING B650-PLUS WIFI (after changing my CPU from 7700x to 9700x).
I got very strong lagging, bsod error, bios selfmade restarts, fails post etc. I could not find a solution and returned the board as defective.

I should certainly not compare a cheaper Asus board with a more expensive MSI board, however the replacement mainboard, Asus ROG Strix B650E-E wasn't that great either: EXPO was not saved, audio issue, WIFI issue.

At present I have the MAG B850 TOMAHAWK MAX WIFI, which is also not bugs-free.

Which manufacturer have you changed to?
(Late Reply) I can't recall where I watched a video on an issue presenting with swapping Ryzen series CPU's causing all sorts of issues. The issue I recall was the OS stored details of the previous cpu's architecture, cores and how they are utilised, parked, not parked etc. Tests verified by using a fresh OS install and or an OS that had previously been used with an Intel CPU resulted in many issues not presenting. As soon as the OS (drive) that had experienced two different Ryzen CPUs was re used in the same motherboard the issue re-presented. I had read of such conflicts prior and was concerned as I was going to put in a R9 7900X in a PC that had previously had an Intel CPU, I had no issues.

EDIT: Just found one of of the links to the issue as explained by Gamers Nexus. Also Jayz two cents, has put in his two cents worth in on similar issues he had with swapping Ryzen CPU's; not confined to X3D variants.

Gamers Nexus

I had experienced PCIe lane issues and that was due to an old PCIe capture card not playing nice, stuttering, pauses etc and the fix was to disable 4G Crypto and Re Size bar – they go hand in hand as they are linked and my issue went away at the expense of the GPU now obtaining data in smaller chunks.
 
Last edited:
My previous setup was:
9700X
X870 Tomahawk WiFi
G.Skill 64GB CL30 6000MHz
RTX 5080
FSP 1000W PSU

Everything was working perfectly fine. But after replacing my CPU with the 9800X3D, everything went completely wrong.

From the very first boot with the 9800X3D, I immediately noticed stuttering on the Windows lock screen—my mouse, keyboard, and display were lagging. It felt like the system was freezing every 3–5 seconds. As the issue worsened, the screen would go black, or I would get a Video Scheduler Internal Error blue screen, causing the system to restart. However, sometimes after a reboot, the system would work normally.

When the system was stuttering, I checked GPU-Z, and I noticed that the PCIe version was stuck at 1.1x16. Even under load, it remained locked at 1.1x16. In some cases, it was stuck at 2.0x16 or 3.0x16, causing severe lag. During these moments of lag, even when the system was idle, the GPU usage would spike abnormally. And when the system did work "normally," the PCIe version remained locked at 5.0x16, rather than dynamically adjusting between 2.0x16 (idle) and 5.0x16 (load) as it should.

Since all of these problems started only after installing the 9800X3D, I decided to swap back to my 9700X, and everything returned to normal. Even in GPU-Z, I could see that PCIe behavior was back to normal—2.0x16 in idle and 5.0x16 under load.

The 9800X3D has already been sent for RMA and replaced. and I have installed the latest version, 1A26 Beta, but the issue remains the same.
Some of what I replied to in post #24 may be of interest to you? https://forum-en.msi.com/index.php?...ot-version-is-still-stuck.410048/post-2326738
 
I have the same problem. When I do a cold boot, the BIOS reads the PCIe value wrong and starts the system with the bus locked at 1.1, sometimes 2.0. This causes big stutters, lags, and finally a restart of the computer. Sadly, MSI’s support and attitude are the worst I’ve seen, so we will probably never get a BIOS update. Other companies released fixes a month ago, but MSI is still doing nothing. I suggest either changing the motherboard to anything that is not MSI, or just keep waiting.
 
I have the same problem. When I do a cold boot, the BIOS reads the PCIe value wrong and starts the system with the bus locked at 1.1, sometimes 2.0. This causes big stutters, lags, and finally a restart of the computer. Sadly, MSI’s support and attitude are the worst I’ve seen, so we will probably never get a BIOS update. Other companies released fixes a month ago, but MSI is still doing nothing. I suggest either changing the motherboard to anything that is not MSI, or just keep waiting.
I just returned my ASRock B850 Steel Legend due to the 9800X3D cooking issues. Here I was thinking the MSI B850 EDGE would be a good replacement.

As for Gigabyte - I have a Z97 board from 2014 that the new AM5 system was supposed to replace. Guess what problem I have had with it for the past 5 years? The PCI-E mode gets locked to 1.1 on random cold boots. :biggrin:I'll be damned if I have waited for 10 years of progress and end up having the same exact issue!

It seems I can't buy anything reliable. All boards seem to have issues.
 
For me it was fixed by updating the bios to version 1.A24 and it has been 100% stable since then.

And prior to that switching the PCI-E to 4.0.
 
It's not a permanent solution to the problem. Although SS significantly reduces issues with cold boot, the problem still exists and is annoying.
For me, no PCI stuck on boot since 21th march the day after the release date of BIOS 1A30.
If I set to "Auto", 1 boot out of 4-5 is with PCI stuck on 1.1 or 2.0x
 
@Bedouille69 It worked for about a month for me. But then suddenly the problem came back. It's a bit better now because it doesn't happen every time I turn on the computer, but it's still there. What's worse, I didn't change any settings or update any drivers. It just came back on its own.
 
@Bedouille69 It worked for about a month for me. But then suddenly the problem came back. It's a bit better now because it doesn't happen every time I turn on the computer, but it's still there. What's worse, I didn't change any settings or update any drivers. It just came back on its own.
Have you tried the latest bios? https://forum-en.msi.com/index.php?threads/mag-x870-tomahawk-wifi-beta-bios.409819/page-2#posts

An admin on another forum said that the godlike bios was supposed to fix the stutters so i feel like our fix is finally... knock on wood... coming.
 
I have the same problem. When I do a cold boot, the BIOS reads the PCIe value wrong and starts the system with the bus locked at 1.1, sometimes 2.0. This causes big stutters, lags, and finally a restart of the computer. Sadly, MSI’s support and attitude are the worst I’ve seen, so we will probably never get a BIOS update. Other companies released fixes a month ago, but MSI is still doing nothing. I suggest either changing the motherboard to anything that is not MSI, or just keep waiting.
I bought an MSI MPG X670E CARBON WIFI. The same problem has been bothering me for two months. The PCIe3 4 slot cannot use the capture card. I always thought it was my own problem until I searched for more users who encountered this problem. This problem has been reported since November 2022, and there is no solution so far! This is the worst motherboard I have experienced in the past ten years, no doubt about it! ! !
 
I have the same problem. When I do a cold boot, the BIOS reads the PCIe value wrong and starts the system with the bus locked at 1.1, sometimes 2.0. This causes big stutters, lags, and finally a restart of the computer. Sadly, MSI’s support and attitude are the worst I’ve seen, so we will probably never get a BIOS update. Other companies released fixes a month ago, but MSI is still doing nothing. I suggest either changing the motherboard to anything that is not MSI, or just keep waiting.
i got that on a 670e board. but i also get alot of "153 nvlddmkm" errors ressetting my grafikcard solution found so far 2 times rma. and also all kind of driver install orgies and benchmarks/tests. drives me nuts since 10 months alrdy so only solution i see is step bakc from the contract and hopefully get my money back.
 
Back
Top