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

G

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: 538
Last edited:
Sort by date Sort by votes
hdizzl150502d0 said:
Yea, I have also seen suggestions that other vendors have patched the issue out in newer BIOS but MSI have not. Well, we are about to test this theory my Gigabyte replacement X870 board should be here with me in a day or two. I will of course let all know if the problem persists with the replacement board, we all want to get to the bottom of this it is so very stressful!
Click to expand...
please keep us posted! indeed we really want to pinpoint what is causing this
 
Upvote 0 Downvote
I am pleased to report that my new Gigabyte Aorus X870 Elite Wifi7 board has no issues. I conclude that the MSI MAG X870 Tomahawk Wifi board was the issue. MSI support have been dreadful as they just blame everything else and say they cannot replicate it their end. i would recommend everyone to avoid MSI motherboards as a result of my experience. Even with spread spectrum disabled in the BIOS of my Gigabyte still I have no drops, my 5090 is running solid at PCIe 5.0 x 16 on all cold boots and wakes from sleep etc. and also relevant my gen 5 M.2 NVMe drive is maintaining 5.0 x 4, I will never buy another MSI motherboard ever again they have burned me. My first one was DoA wouldn't even post, then the second one this PCIe issue, 2 bad boards in a row what are the odds? No thanks. I was tearing hair and the whole thing was incredibly stressful.

Support is totally useless and just keeps saying "sorry for inconvenience to you" in every single email, it's not even sincere it's just a script they say in every email.
 
Last edited:
Upvote 0 Downvote
for those still having issues, please try to downgrade bios to those from November-January. it seems those who have X3D chips are mostly affected. - Just read this on a reddit post
 
Upvote 0 Downvote
Someone said that connected ARGB-connector of your computer case to the motherboard causing problem with PCI Express version changing, can somebody with that problem check it? Cause I don't have this problem with my 4070ti
 
Upvote 0 Downvote
I've been trying to solve this issue for months now. I have the MSI X670 Meg Ace and 7950x and RTX 5080. Using the latest bios on MSI website. Only on multiple boots will it eventually get to PCI-e 5.0 x16 I really wish there was an answer for this.
 
Upvote 0 Downvote
reijkelho15d702ea said:
Even with FCH Spread Spectrum enabled in the bios?
Click to expand...
Spread Spectrum does not fix it, people saying it does are just lucky it seems.

I thought it fixed my issue last year when i put it on but eventually on restarting i got the stutter lag and when trying to do anything with the gpu it resulted in a BSOD: "VIDEO_SCHEDULER_INTERNAL_ERROR"

You can't fix a flawed motherboard without replacing it. Only thing that fixed my issues was putting back my 7800x3d.
I had the x870 tomahawk w/ 7800x3d for 2 months no issues, 9800x3d install -> issues -> back to 7800x3d no issues.

The 9800x3d has worked fine in many b650 tomahawks and multiple x870e boards though, these msi motherboards are just a lottery with every hardware swap, seeing people mention a gpu swap caused it, for me a cpu swap. "BIOS will fix it" i thought that too, back in January 2025.
 
Upvote 0 Downvote
Limiting SoC-voltage (aka VSoC) <1.25V was the only reliable option I've found to avoid the problem. With the maximum of 1.3V as AMD allows the PCIe-version got stuck rather often.

The issue also doesn't seem to be limited to PCIe5-GPUs or only particularly to Founders Edition-cards with a split PCB-design, as other vendors have been affected as well (both on the GPU- and mainboard-side).

My system had it happen with
both 7800X3D and 9800X3D
and
both PNY GeForce RTX 4090 Verto TF (which is PCie4, original thread) and Nvidia RTX 5090 FE,
even changed up PSU and SSD too -
the only common denominators were the
MSI MPG X670E Carbon WIFI and the RAM-kit.

Leaning towards AM5 hardware-(chipset-?)weakness (since other vendors' boards can have it too) that can't be fixed with a simple BIOS-update, as we would've seen improvements by now instead of the fact that the 800-series are also affected.
It's laughable that MSI always just reports back that they can't replicate the glitch on their end, imo they're just covering their own behinds and don't want to address it.
 
Last edited:
Upvote 0 Downvote
WakeX said:
Limiting SoC-voltage (aka VSoC) <1.25V was the only reliable option I've found to avoid the problem. With the maximum of 1.3V as AMD allows the PCIe-version got stuck rather often.

The issue also doesn't seem to be limited to PCIe5-GPUs or only particularly to Founders Edition-cards with a split PCB-design, as other vendors have been affected as well (both on the GPU- and mainboard-side).

My system had it happen with
both 7800X3D and 9800X3D
and
both PNY GeForce RTX 4090 Verto TF (which is PCie4, original thread) and Nvidia RTX 5090 FE,
even changed up PSU and SSD too -
the only common denominators were the
MSI MPG X670E Carbon WIFI and the RAM-kit.

Leaning towards AM5 hardware-(chipset-?)weakness (since other vendors' boards can have it too) that can't be fixed with a simple BIOS-update, as we would've seen improvements by now instead of the fact that the 800-series are also affected.
It's laughable that MSI always just reports back that they can't replicate the glitch on their end, imo they're just covering their own behinds and don't want to address it.
Click to expand...
It does seem that way. It's a shame that someone from MSI doesn't monitor there official forums. Nvidia have Manuel G monitor and help out on a few different forums, MSI should really do the same. Disappointing as the motherboard itself is very nice and easily customizable.
 
Upvote 0 Downvote
AM5 is definetly a major issue with pcie gen 5 i.m.o

Too many issues, the msi stutter boot thing i've not experienced or heard about with gigabyte, asus, asrock etc...

But i do know the other vendors, gigabyte especially, had nvme speed issues at points too on the pcie gen 5 boards but as far as i know, they fixed that with a bios update.
The whole msi stutter boot, has not been fixed with bios, ever, as far as i'm aware, people change hardware, whether that me board or other components, it's hardware.
Also, for me the Soc voltage wasn't the issue, my first x870 tomahawk ran Soc at 1.17v, spread spectrum was the only thing i found to help me but it didn't fix it, just make it less likely.

But i what i would like to know is why i can't find people with x870E tomahawk experiencing the same stutter boot where gpu is locked to low speeds until crash - if they have a working board, the x870e tomahawk, why do most of their other pcie gen 5 boards suffer from it, if it's a simple bios tweak, they can do that easily then surely?... i very much doubt it's possible though,
again msi aren't the only people having weird quirks/issues - but they are (As far as i know / can find), the only ones having the weird boot up, stutter -> crash issue.

If RAM wasn't such a PITA i would actually be tempted to build intel at this point, yeah they have issues with their cpus dying too but so does AMD at this point, we still don't know the truth behind that despite AMD replacing chips left and right. Ofc, i've not kept up with intel at all since switching to AMD so maybe their pcie gen 5 issues are just as bad...
 
Upvote 0 Downvote
I think I finally found out what is causing this. The culprit is MPO / multiplane overlay used in Windows. To test for this do the following:

Using Edge/Chrome/UngoogledChrome, go to yandex and do a random search then hit F11 for full screen, then run the mouse pointer over all the results in circular motion touching the top of the screen on every rotation, keep doing it over and over. Have Latency Monitor tool open and check it regularly. You will notice super high DPC latency spikes. What happens the whole system stutters. (audio will stutter if you have something playing, USB sound devices will also stutter since this is system wide freeze)

The same happens when you bring the PC out of sleep or at boot. Randomly, the Multiplane Overlay used by modern windows, causes the PC to briefly freeze stutter therefore negotiating a slow GPU link speed. This can happen at boot or when waking up PC from sleep.

To fix this, download MPOGPUFIX v6.6 tool and flip the MPO Fix toggle switch to enable it. Reboot and if I'm correct, you will never see this link speed problem again. Please test this and report back. So far on my end the problem no longer occurs after using the tool.
The tool is not intrusive it just adds a registry entry to disable MPO and when switched off it removes it.

(IF my finding is correct this is a huge discovery as many people are affected by this)
 
Upvote 0 Downvote
Back
Top