RX 7900xtx causing problems?
Hello,
I have owned the RX 7900XTX Powercolor Hellhound for about half a year.
Until about 2-3 weeks ago, everything was running smoothly, and the FPS was flying. However, since then, I've been having some driver issues. Previously, the problem always occurred about 5 to 10 minutes after launching a game: The game would freeze and an AMD error message would appear. Afterward, I removed the driver with DDU and reinstalled it, and it worked again. Now I'm having the same problem again.
Graphics card is also not overclocked or anything like that.
Does anyone else have these problems and maybe a solution?
PC: Rx 7900xtx powercolor hellhound
CPU: Ryzen 7 7800x3d
RAM: Corsair vengeance 32gb 6000mh
Motherboard: ASRock X670E Taichi Carrara (latest BIOS version)
Power supply: Gigabyte UD1000gm (1000w)
Hello
Since you have already updated the BIOS/UEFI and the error continues, I would exclude the motherboard and BIOS/UEFI as a cause of error or at least sort it further back in the row of suspects.
Possibly, the graphics card has suffered damage, so what should have happened.
It can also be that the driver you use has a defect. Uninstall this one again and install an older version if AMD offers one.
The driver may be damaged only after loading in the RAM. This can be at faulty RAM or a partially defective processor because the RAM is directly connected to it, or at an overclocked storage system because you operate XMP or EXPO MEM overclocking. As a result, on the one hand, the RAM modules are only overclocked to their intended speed and, in addition, the memory controller, which, by the way, is also overclocked in the processor, which can function, but which can also cause memory errors, which then end up in crashes.
Deactivate the XMP or EXPO from the RAM modules in the BIOS/UEFI, so that the RAM modules run only with the slow standard storage speed, then reinstall the graphics card driver and check the system files for errors. To do this, open a command prompt with administrator rights, i.e. open the command prompt with right click and select “Run as administrator”. In the command prompt then the command
run and wait what can take a bit. Then check if the drivers are gone.
If the graphics card drivers should then work in a stable manner, then the problem lies with an excessively high XMP or EXPO MEM overclocking.
The achievable storage speed no longer depends solely on the mainboard and the RAM modules, as in the past, but especially on the processor.
But in turn. Let’s start with the motherboard and then we start working slowly to the processor.
According to the motherboard specifications of the specified X670 AM5 motherboard, the BIOS/UEFI of the motherboard can manage the following storage capacities and set the following storage speeds at the memory controller:
https://www.asrock.com/mb/AMD/X670E%20Taichi%20Carrara/index.de.asp#Specification
AsRock gives only the maximum adjustable storage speed. It contains all adjustable storage speeds which can be set without and with overclocking. This has been formulated very sloppy and misleading by AsRock. AsRock had something more detailed and better. Too bad.
The data in the motherboard specifications, however, are not guaranteed memory speeds, as is repeatedly mistakenly assumed, but there is only what memory speeds can be set at the memory controller by the BIOS/UEFI of the motherboard, including the storage speeds that can only be achieved with the overclocking of the memory controller, there is no longer any way.
Storage speeds that can only be achieved via overclocking, which are usually characterized in the motherboard specifications as follows: (OC), (O.C.), (by A-XMP OC Mode) or (EXPO)
Therefore, the data in the motherboard specifications also do not mean that the memory controller must run as naturally with all adjustable storage speeds, especially not with the storage speeds that can only be achieved with the memory controller overclocked.
The memory controller is now in the processor and not somewhere on the motherboard and also not in the RAM modules. And there in the processor, the storage speed is now set by the BIOS/UEFI and not somewhere on the motherboard and also not on the RAM modules themselves. The memory clock then results only from the number of accesses per second to the RAM. Otherwise, the RAM itself is not clocked and does not run independently at any speed. However, it is also the processor that is responsible for the actual memory speed and not the motherboard and RAM modules alone.
However, the RAM modules also have to be able to maintain the storage speed set at the memory controller. They must therefore also be designed for the storage speed set at the storage controller. This is specified by the memory profiles which bring the RAM modules and are configured according to their specifications by the memory controller, in the processor used, by the BIOS/UEFI.
These memory profiles also include the XMP or EXPO. The XMP or EXPO is determined by XMP or EXPO overclocking RAM modules and can then be selected and activated in the BIOS/UEFI. These RAM modules are then even overclocked to their intended speed via XMP or EXPO. However, the storage speed is also set at the memory controller in the processor and not at the RAM modules themselves.
That’s how a shoe gets out.
The storage controller in the Ryzen 7 7800X3D AM5 processor is just like all other Ryzen series 7000/8000G AM5 processors also, designed for operation with up to DDR5-5200 RAM modules, when fitted with a storage bank (rank) per storage channel. This can also be read in the specifications of the respective processor.
https://www.amd.com/en/product/12731
For storage speeds in each case, which can then also be used with faster RAM modules, the memory controller is also forcibly overclocked in the processor used, which can function, but which does not have to function in advance guaranteed and which somewhat reduces the life expectancy of the overclocked components. This would then affect memory controllers, i.e. the processor, and the XMP overclocking RAM modules. The same applies to AMD EXPO RAM modules introduced with the AM5 platform.
In addition, the maximum achievable storage speed decreases, the more storage banks (rank) are used per storage channel. This is due to the additional load of the memory controller by more memory banks and to the physical properties of the memory bus in the high-frequency range. It is easier to say that higher storage speeds can be achieved with two RAM modules, as with four RAM modules. This should be considered especially at MEM overclocking.
A memory bank is not always a RAM module. There are single rank RAM modules, since one memory bank corresponds to a complete RAM module and there are RAM modules on which are already two memory banks. These are Dual Rank RAM modules. A Dual Rank RAM module is roughly the same as two single Rank RAM modules used in single channel configuration.
Therefore, it is also more likely to work on an AM5 motherboard with 4 RAM slots, 4 DDR5-5200 RAM modules than 4 RAM modules with higher storage speeds, which then restricts or at least complicates the possibilities of RAM.
It also plays no role, which can still be set to such a high memory speed from the BIOS/UEFI of the motherboard, at the memory controller in the processor, and for which the RAM modules are still designed so high, because if the processor does not play with the MEM overclocking, then it is still vinegar.
Whether and how high the memory controller can be overclocked in a specific processor cannot be predicted, because this depends on the individual properties of each individual processor, also from the same series. One can do more and the other can’t stop. This means that even if the MEM overclocking works with other functions that cannot be closed from it, which must be the same in any further case.
The motherboards have been successfully tested with the storage speeds specified in the respective specifications and the RAM modules that have managed this are now also found in the Memory Support list (QVL) to the respective motherboard, but for these tests the motherboard manufacturers use specially selected engineering sample processors. Processors for the end customer market usually create these storage speeds not or only rarely and also not under warranty with the RAM modules from the memory support lists. Even with these RAM modules, the specified storage speeds are only reached when the inserted processor plays along, that is the condition.
If now, for correspondingly fast RAM modules, a higher storage speed via XMP or EXPO is set when the processor is natively supported, i.e. without overclocking the memory controller and the computer should then run unstable or no longer start after the XMP or EXPO was activated by the RAM modules in the BIOS/UEFI, then the simple MEM clocking worked via XMP or EXPO not because the settings by the XMP or EXPO is too good for the processor.
In this case, the storage speed would have to be manually engaged to set the storage speed. There may also be several XMP or EXPO storage profiles available, one of which might work. Otherwise, the storage speed, with activated XMP or EXPO, can be additionally manually throttled until the processor is stable with it or the storage speed, the timings and the RAM module voltage are completely manually set. Have fun.
Since overclocking, by the higher clock and the associated increase in the voltage of the overclocked components, increases the effect of electromigration, ages overclocked components faster, which in the case the XMP or EXPO MEM overclocking RAM would affect the memory controller in the processor. Precise predictions can not be made either.
https://de.wikipedia.org/wiki/electromigration
By overclocking, the computer can also become unstable or no longer function. See also here:
https://www.heise.de/meinung/Bit-Rauschen-der-Processor-Podcast-Ueberclocken-nuetzlich- or-gefaehrlich-7464285.html?wt_mc=nl.red.ho.ho-nl-newsticker.2023-06-21.link.link
That’s why I guess from overclocking.
If you still want to try MEM overclocking, with storage speeds outside the CPU specifications, to use these storage speeds with correspondingly fast XMP or To be able to use EXPO RAM modules and possibly also with more than two RAM modules, you can do this with all the problems that can arise from them. This is your decision and not my recommendation.
mfG computer tomb
Hello Tom, thank you for your detailed answer. I would follow the steps you proposed and see if the problem continues. I have not overclocked my CPU or the GPU, which are already strong enough from work. The problem is that I don’t have the problem anymore, so I don’t know how much the tests are.
That’s not quite true. You overclocked at least parts of your CPU and the RAM modules, whether you are aware or not.
You have DDR5-6000 RAM modules and with certainty the storage speed is via XMP or EXPO in BIOS/UEFI set to 6000MT/s. This is XMP or EXPO MEM overclocking.
The memory controller of your processor is overclocked from 5200MT/s to 6000MT/s. 5200MT/s is the upper limit for the processor without overclocking its memory controller.
In addition, the RAM modules themselves will only be via XMP or EXPO “overclocked” to its speed provided by the manufacturer. XMP or EXPO RAM modules are always overclocked when the XMP or the EXPO of these RAM modules is activated in the BIOS/UEFI.
I’d look for the mistake and get rid of it. What helps if the error always occurs against sometimes sporadic, at the best place in the game or after two hours, just before completing a newly rendered video. Isn’t it Ka… if the PC is smashed at the most unfavorable moment?
Would you leave it like that for the first time and see if the mistake occurred again?
Do it.
Yeah, I’ll test it if I have time.
Did you install a beta driver or WHQL driver? If Beta, then uninstall with DDU and install the WQHL driver.
If WQHL drivers, then see if you get a previous version of the driver that ran everything smoothly and install it. In the AMD Control Center, you will then deactivate the driver updates and only update all 3-5 new versions to the driver.
Installed the WQHL drivers. I will try it when I have time with an old version of the drivers, thank you for that! At the moment the card is running again that surprises me.