7800x3d thread usage issue

[phanbuey]

Sorta specific to my system, as other people have reported having the same issue in this thread

But yeah, im still leaning towards undercooked win10 drivers.



Interesting that it spreads the load out so much - i would have thought it would have wanted to keep the load on a single ccx. But impressive fps ! I wonder how it would look like if you used that cyberpunk fix aswell.

Light question peppering :
Is this a clean install?
can you reinstall directX?
have you tried windows 11?

Have you tried setting cores at boot manually (really long shot - probably wont work but worth a shot) through msconfig?

 

[Dragam1337]

Light question peppering :
Is this a clean install?
can you reinstall directX?
have you tried windows 11?

Yes - reinstalled windows 4 times... lol

I suppose i could, but i don't think dx is the culprit, as spiderman works fine (only game i've tested that does though)

Spoiler

I haven't with this setup (use it at work, and hate it with a passion).

 

[oxrufiioxo]

Yes - reinstalled windows 4 times... lol

I suppose i could, but i don't think dx is the culprit, as spiderman works fine (only game i've tested that does though)

Spoiler

I haven't with this setup (use it at work, and hate it with a passion).

Makes sense Spiderman for PC was ported by Nixes one of the best Dev studios.

 

[Zubasa]

Sorta specific to my system, as other people have reported having the same issue in this thread

But yeah, im still leaning towards undercooked win10 drivers.



Interesting that it spreads the load out so much - i would have thought it would have wanted to keep the load on a single ccx. But impressive fps ! I wonder how it would look like if you used that cyberpunk fix aswell.

FYI for the 7800X3D it shouldn't be a driver issue, it just uses standard CPPC2 to flag for which CPU cores to prioritize.
That is done by the bios / firmware.
Asus recently posted a couple of new bios, see if those does anything. If you haven't already.
Also keep an eye out on the voltages your Asus boards feeds to the cpus, there are lately reports of Asus boards killing X3D chips.

 

[Darmok N Jalad]

Are you monitoring the temps and clocks on these cores with something like HWinfo? Does something like Cinebench load it down evenly? Maybe that would help confirm it’s not an actual hardware defect, where some cores aren’t ramping under load. HWinfo will tell you average and max clocks of each core. Might be worth the extra telemetry.

 

[Dragam1337]

FYI for the 7800X3D it shouldn't be a driver issue, it just uses standard CPPC2 to flag for which CPU cores to prioritize.
That is done by the bios / firmware.
Asus recently posted a couple of new bios, see if those does anything. If you haven't already.
Also keep an eye out on the voltages your Asus boards feeds to the cpus, there are lately reports of Asus boards killing X3D chips.
View attachment 292573

I'm gonna take a wild guess and say that's probably people who were pushing it to the max with pbo. Mine is running stock, and haven't seen vcore above 1.190.

As for bios, i wrote that in the very first post. Yes, i have tried the different ones.

Edit : just read up on it - apparently the safe limit core vcore is 1.15.... so if asus boards are running the chips a fair bit higher than that out of the box, that would deffo explain those issues ! Just did a -0.075 offset, just in case. Makes clocks boost ever so slightly lower, but isn't affecting fps.

Are you monitoring the temps and clocks on these cores with something like HWinfo? Does something like Cinebench load it down evenly? Maybe that would help confirm it’s not an actual hardware defect, where some cores aren’t ramping under load. HWinfo will tell you average and max clocks of each core. Might be worth the extra telemetry.

Yes.

the fact this topic has gone 5 pages and OP still hasn't done Windows 11 is laughable.

i will be unwatching this thread as soon as I post this. waste of fucking time.

you hate win 11? too bad so sad, you need it with new hardware. get used to it. this thread should have been locked until OP tests with Windows 11. stop wasting everyones time, ffs.

Goodbye and good riddance.

 

[Zubasa]

As for bios, i wrote that in the very first post. Yes, i have tried the different ones.

Edit : just read up on it - apparently the safe limit core vcore is 1.15.... so if asus boards are running the chips a fair bit higher than that out of the box, that would deffo explain those issues ! Just did a -0.075 offset, just in case. Makes clocks boost ever so slightly lower, but isn't affecting fps.

Asus apperently went and nuked all off their older bios from their AM5 webpages and posted a new version. So it seems something is up.
The 1408 from early today is gone an replaced with 1409 with the new firmware.

As for voltages, also keep an eye out on if the board is over-zealous with LLC again, often what is set in the bios is not what you actually get.
BTW GN is on the issue now:

 

[Dragam1337]

Asus apperently went and nuked all off their older bios from their AM5 webpages and posted a new version. So it seems something is up.
The 1408 from early today is gone an replaced with 1409 with the new firmware.
View attachment 292617
As for voltages, also keep an eye out on if the board is over-zealous with LLC again, often what is set in the bios is not what you actually get.
BTW GN is on the issue now:
View attachment 292623

Thanks for the heads up! Will update it when i get home.

With my -0.075 offset, the vcore maxed out at 1.120, so within the safe limit.

 

[Zubasa]

Thanks for the heads up! Will update it when i get home.

With my -0.075 offset, the vcore maxed out at 1.120, so within the safe limit.

It is not only the Vcore that you need to look out for, some users reported high VSOC/V IO Die as well. Some boards tends to feed really high VSOC when running fast memory and hope for the best. Often all it does is makes thing worst for memory compatibility.

 

[docnorth]

Out of topic maybe, but all 7000X3D users please be careful until this is cleared:

Redditor's Ryzen 7 7800X3D CPU burns out, GamersNexus immediately offers to buy it - VideoCardz.com

Redditor’s Ryzen 7 7800X3D goes into flames Some users are now reporting their Ryzen CPUs with X3D are burning up. AMD Ryzen 7 7800X3D with burn mark, Source: Reddit There is a very popular thread on Reddit featuring a picture of one of the Ryzen 7 7800X3D. But this is not a story from a […]

videocardz.com

 

[Zubasa]

Out of topic maybe, but all 7000X3D users please be careful until this is cleared:

Redditor's Ryzen 7 7800X3D CPU burns out, GamersNexus immediately offers to buy it - VideoCardz.com

Redditor’s Ryzen 7 7800X3D goes into flames Some users are now reporting their Ryzen CPUs with X3D are burning up. AMD Ryzen 7 7800X3D with burn mark, Source: Reddit There is a very popular thread on Reddit featuring a picture of one of the Ryzen 7 7800X3D. But this is not a story from a […]

videocardz.com

Ah yes another "article" that just copy and pasted a reddit post.
FYI the OP of that post later suspect it is his board that kill the cpu and not the other way around. Given it is the mobo's job to supply the correct voltages to the CPU.
Also so far it seems to be an Asus problem, with users using the ROG Hero / Extreme / Strix.

 

[Ferather]

Just opening MS Edge hits all cores with my 5800X on Win10, cant say its perfectly even, but mostly.



I am also playing music which populates 4 of them.

AMD Refutes Reports of Ryzen 7000 Performance Inconsistencies Between Windows 11 and Windows 10

AMD on Monday issued a statement refuting reports of performance deltas noticed for its Ryzen 7000-series "Zen 4" desktop processors observed between Windows 11 and Windows 10 operating systems when gaming. The company said that while it is investigating the reports, it has not been able to...

www.techpowerup.com

 

[Dragam1337]

It is not only the Vcore that you need to look out for, some users reported high VSOC/V IO Die as well. Some boards tends to feed really high VSOC when running fast memory and hope for the best. Often all it does is makes thing worst for memory compatibility.

Right - im not sure what it's supposed to be at though ?

 

[docnorth]

Ah yes another "article" that just copy and pasted a reddit post.
FYI the OP of that post later suspect it is his board that kill the cpu and not the other way around. Given it is the mobo's job to supply the correct voltages to the CPU.
Also so far it seems to be an Asus problem, with users using the ROG Hero / Extreme / Strix.

Everybody here can read and the article indeed says that it might be more an Asus problem burning CPUs with the sensitive 3D V-cache. Does this mean we should not warn TPU members until this is cleared?
It's not bashing, it's a friendly warning.

 

[Klemc]

Well, my B650E-E and 7800X3D, that i'm not an overclocker, except enabling XMP (DOCP)... has no risks in that case ?

I tried Asus AI suite today, but, i'm not sure i want it running in the background tbh, disabled for now, and also, perhaps it needs that BIOS's "Publish HII Resources" to be activated ?..

 

[R0H1T]

Well most BIOS' these days have that 1click OC thing, even for the mid/low range models. You can easily safely OC through that, no need to use something under Windows to make it work.

 

[izy]

Seems that a bad motherboard can be the problem , check hardware unboxed video:

 

[Ferather]

Indeed it can be, I've had issues in the past with bios-motherboard and throttle-parking, including laptops, then serious performance issues.
I have even had a bios problem in the past with sleep and system+cpu fans not turning back on, then 100*c .....

In my case I set performance bias to none, disabled PBO and set the clocks.

----

This is before I upgraded the cooling, memory and graphics card: AMD Ryzen 7 5800X @ 4647.1 MHz - CPU-Z VALIDATOR (x86.fr)

 

[Dragam1337]

It is not only the Vcore that you need to look out for, some users reported high VSOC/V IO Die as well. Some boards tends to feed really high VSOC when running fast memory and hope for the best. Often all it does is makes thing worst for memory compatibility.

Well i tried the new bios, and it didn't fix the threading - i reckon it's the amd mobo drivers for win10 that is the issue.

In regards to the voltage... with stock memory settings it runs soc voltage at 1.040v and vddio / mc at 1.120v.

When you enable memory profile 1, and voltage settings are set to auto, soc voltage gets increased to 1.270v and vddio / mc to 1.360v... which seems a "little" excessive.

Lowered them manually to 1.140v and 1.230v... so far it runs ok.

 

[Ferather]

What version of AMD mobo drivers? I recently updated mine, and I am on Win10. I also found some info in another sites thread, maybe this helps:

 

[Dragam1337]

What version of AMD mobo drivers? I recently updated mine, and I am on Win10. I also found some info in another sites thread, maybe this helps:

View attachment 292764

Newest one. And no offense intended, but you aren't on the same platform (neither is the other guy), so not the same thing at all.

 

[Ferather]

Have you tried a fresh install without any added drivers? Unplug internet, install Windows (no updates, no extra drivers), and then try.
I am almost certain all cpu cores can be used and parked, power saved so on, without any added mobo drivers.

If you install the driver and it suddenly behaves differently then that indeed would be the issue.


You also wouldn't install Windows drivers on Linux, but thats just to point out that there isn't a CPU driver you install.

 

[Dragam1337]

Have you tried a fresh install without any added drivers? Unplug internet, install Windows (no updates, no extra drivers), and then try.
I am almost certain all cpu cores can be used and parked, power saved so on, without any added mobo drivers.

If you install the driver and it suddenly behaves differently then that indeed would be the issue.


You also wouldn't install Windows drivers on Linux, but thats just to point out that there isn't a CPU driver you install.

View attachment 292767

Yes. All of this has already been answered in this thread.

 

[Ferather]

Then you are left with OS or hardware, if you eliminate all driver possibility. OS's obviously need to support a CPU in order to function, but mostly its done at hardware.
A simple example is the need to use a certain motherboard bios version in order to use a newer build of a CPU with the same socket.

In the past the issues I have had on various PC's with parking tended to be due to bios, even cases where an OS workaround was needed to bypass the bios.

 

[evelynharthbrooke]

This issue could probably be fixed if you just upgrade to Windows 11. Windows 10 doesn't have proper support for the Ryzen 7000 series - while yes it is still a single CCX / CCD, the intricacies of the CPU can still change, requiring a better CPU scheduler, which Windows 11 has. Windows 10 IIRC lacks the improved CPU scheduler of Windows 11. If you try upgrading to Windows 11 your thread usage issue would more than likely go away. Using Windows 10 with new hardware is strongly discouraged because it has older hardware support - its relying on older CPU code and other various stuff that won't be fully optimized for newer hardware, while Windows 11 is actually optimized for the newer hardware.