• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

Poll: Ryzen 7950X3D, 7900X3D, 7800X3D

Will you be purchasing the 7800X3D on the 6th?


  • Total voters
    191
  • Poll closed .
Has the drama around chip burnout subsided now?

How people finding their 7xxx3D's now? Happy? Anything you feel you ste missing due to the nature of the chip compared to a normal 7 series?
I don`t think there was any drama, more a storm in a teacup, mines been flawless since day one, SOC manually set to 1.2v for peace of mind. I haven`t even finished tuning my RAM yet or started with CO, just been happily gaming on it.
 
Regarding this. Whenever I try to uninstall the previous drivers? It always leave behind one or two things. Do you know a better way of uninstalling rather than through the windows uninstaller?
I have had issues uninstalling the chipset driver in the past so now I always install over the last one. Not had any issues so far.
 
So I reinstalled the Division 1 the other day to give it another playthrough, but was getting really big stutters while playing and couldn't work out why, tried loads of different things and nothing worked. The game was running on CCD0 (7950x3d) but every now and then 1 core on CCD1 would spike, which i think was causing the stuttering.

Anyway I just installed the new chipset drivers and now the game is running smooth. Also noticed it's running on all 16 cores. Must have been a problem where the game engine was asking to use more cores and the AMD Driver was conflicting with it.

Wonder if this also fixes the problem Metro Exodus had with 7950x3d and stuttering.
 
I have had issues uninstalling the chipset driver in the past so now I always install over the last one. Not had any issues so far.
A lot of people do it this way. I always thought the best and safest way was to remove the previous first but it seems like this is not needed. It m the same with GPU drivers, I make sure I uninstall fully before installing the new one.

I feel this hobby is creating my OCD to get worse.
 
https://imgur.com/gallery/apHahnt

Could anyone help with this new kit. These settings error very fast in Karuh.

It could be any of the timings at fault tbh.

You can't just input all the values that worked on 1 kit and expect them to work on a different kit.

Ram tuning takes time, 1 setting at a time then test for stability - then move onto the next.

Set it to c30 EXPO and see if thats stable, then change 1 setting at a time and test for stability each time.
 
Last edited:

What cpu is it firstly ?

a 7800x3D would have throttled around 90 degrees.

Re-install HWINFO and check again, no way its hitting 118 degrees ( I hope )

And what SOC value is it showing ( see my image / Last value CPU VDDCR_SOC )

fJC98qU.png
 
Last edited:
2.48v on vddcr soc maximum value
HWINFO64 reporting bug. Sometimes, randomly, it multiples (2x, 3x even as high as 4x+) the actual values of the SOC Voltage, CPU temp etc in the max reported values.

It does not happen to everyone, for most people its fine. Some people have this issue when using HWINFO64.

Whilst you should always monitor your temps, use another app which reports correct values such as Ryzen Master Tool or Hardware Monitor if you are concerned about temperatures and are getting values on HWINFO64 that would normally = instant death of the CPU/Board.

Refer to the last few pages of this thread. https://www.hwinfo.com/forum/threads/hwinfo64-cpu-die-average-spike.8044/page-6#post-41555

HWINFO64 works fine for me btw.
 
Last edited:
HWINFO64 reporting bug. Sometimes, randomly, it multiples (2x, 3x even as high as 4x+) the actual values of the SOC Voltage, CPU temp etc in the max reported values.

It does not happen to everyone, for most people its fine. Some people have this issue when using HWINFO64.

Whilst you should always monitor your temps, use another app which reports correct values such as Ryzen Master Tool or Hardware Monitor if you are concerned about temperatures and are getting values on HWINFO64 that would normally = instant death of the CPU/Board.

Refer to the last few pages of this thread. https://www.hwinfo.com/forum/threads/hwinfo64-cpu-die-average-spike.8044/page-6#post-41555

HWINFO64 works fine for me btw.
Welcome back Matt.
 
Back
Top Bottom