Its true btw that motherboard vendors tweak defaults and push little bit more power, however this usually should not lead into problems, not saying this is oke, but some of the tips like JayzTwoCents gave to undervolt cpu is even worse then what mainboard vendors do, their is usually a setting to set it to default stock, its just not selected this may vary per motherboard, its usually right where you set everything like xmp / docp / expo
If your memory is in QVL then you should never fear run into stability issues at xmp/docp/expo do keep in mind tho kits can be in qvl for just docp for example but not expo or both
on ddr4 boards memory not being on qvl aint the end of the world, for AM5 however tho its new and still developing memory compatibility is awful, i had to tell my nephew to set expo from expo II to expo I to fix heās random reboots.
Well it does lead into problems, as both Nvidia and Intel have already stated. AMD might have also said something about the issue, but Iām not sure if they have or not. And losing a percent or two performance(margin of error) for stability is more than worth it for an undervolt, plus it will run considerably cooler as well. But you donāt have to undervolt, just simply disabling the motherboard enhancements(allowing the stock CPU profile for things like PL limits/timings and max currents) is enough to fix the issue for a lot of people.
Itās not pointing the finger, itās evidence based fact. The motherboard bios default profiles for CPUs run them outside of their designed operating specs. Things like the max current, PL1/PL2 timings, voltages, etc. It doesnāt always cause issues, but when it does it does. Some types of operations trigger things easier than others.
For example: Want to generate extreme amounts of heat(the most wattage your CPU can pull) while having deceptively low CPU utilization? Do a bunch of AVX calculations. Couple that with the CPU being set outside of the factory default settings and bam, overheating(on the micro to millisecond scale) and/or stability issues due to a bunch of microthrottling effects in the CPU. Like I said, these kinds of things can be deceptive because graphs in the seconds range wonāt always register them. These tiny transient spikes are one of the main causes of random application and/or system crashes.
Also extremely well known culprits for random crashes. They are overclocking profiles that run RAM at higher voltages. See what I just said about transients.
The rest of your post is just trolling. At any rate, the two main issues people are having with crashing are Intel 13900/14900 bios settings related crashes that can affect both Nvidia/AMD GPUs and AMD GPUs just having terrible drivers where the GPU can crash on Intel or AMD CPU systems.
I was just making fun of the fact this is always recommended, you shouldnāt have to follow any of these steps, it should just work if its in the QVL and everything.
modern cpuās are designed to boost until it hits either power or thermal limits whichever it does first, the only problem is when people also undervolt without understanding how they should undervolt, heck i would not recommend this at all, cos undervolt is kind of missleading now it requires less voltage to hit target, meaning it can clock it self higher leading to instability, which is exactly why users should not mess with settings on their own, but vendors should defiantly respect stock settings, but it does not always lead to problems.
I was reffering to the fact AMD is pointing fingers at Blizzard and Blizzard is pointing fingers at AMD, this is not helpful at all for users with problems, its just a clown show.
A good example: My CPU is set so that I can run PL2(turbo boost) mode indefinitely, but I have good cooling and itās only a 13600kf, though I had to undervolt a bit to keep the wattage down so that my cooler can keep up with it. I can run it in full PL2 mode all day if I want. Stock profiles donāt allow that and for most use cases, shouldnāt allow that. That constant hammering of the ārev limiterā can cause a ton of issues if you donāt pull it off correctly.
Most users arenāt going to know how to properly tune a system to pull something like that off and instead, do the typical āfollow leethaxorbestest settingsā guides on youtube blindly and then wonder why they have stability issues.
However, even people that donāt do that are technically getting lumped into that boat because their motherboard manufacturer is essentially doing the same thing for them without them having to touch anything, since they are the bios default settings; all so their graphs look bigger or smaller on youtube reviewer graphs.
Also i may have said you should not be having to go thru all these steps like disabling stuff like xmp or docp etc whatever, but you defiantly still should least try for troubleshooting, its far more easier usually, but i personally prefer just to run memory test cpu test overnight and sometimes even during the day and have done this for weeks.
That is why i am so mad about situation with World of Warcraft.
The game does not even run as great as it used to pre expansion patch or day 1 launch fps is halved to what i used to have, i know Blizzard released a patch that did this so this is not exactly AMD fault in this case, no idea what they are trying to achieve, you cannot brute force stability like this but that is probably why they did this, devs can correct me if i am wrong about this, regardless these issues are probably most annoying to reproduce at will.
Yeah its an annoying issue to reproduce, if you have no problems that means you are lucky, most of us are not that lucky, it also can mean it takes couple of days for it to manifest its not straight forward play for 1 hour and it happens, fastest way i used to reproduce is make a new character and level it to max level thru wod timeline, then repeat the next day and day after as fast as you can and as efficient, especially during dark moon event where you gonna go thru many loading screens to refresh exp buff, that is when i used to crash 3 times a day
Or should i say freeze 3 times a day
that issue has never gone away.
Litterally wanted to find issue with ram or cpu etc never found any, even running a 3D load for 48 hours straight in a window but at full load did not give me any issues, i ran it in window cos that rules out any instability as result of freesync cos i want to test stability of the hardware not software instability as result of freesync
rdna3 had past issues with freesync may actually still have them, probably is in usable/stable state tho.
Easier to fix hardware issue then be at mercy of AMD or Blizzard.
While thatās a good way to test certain things like thermals and voltage stability, itās not actually a reliable way to test for game related crashing. Games, especially MMOs, are far more dynamic than artificial benchmarks/stress testers. A silly analogy would be that I can easily sprint up a flight of stairs where I skip a step each time, but if I were to try to do the same taking every individual step, Iād trip left and right. Technically, going up two at a time should be harder vs one at a time, but for me, itās not. Certain types of loads can trigger system instabilities easier than others and itās not always the most hardware demanding that do.
Well that is one you use multiple test suites not just one, you may find no issue with 1 memtest but able to with another test suite, i really have no idea what more i can do, i doubt i still be having the issue tho when switching to NVIDIA, cos the problem is most defiantly Radeon related, its just a shame i do not want to switch NVIDIA, i do not want to go thru that hell ever again, especially considering gsync never worked fine to begin with in most modern games, that cant even run fullscreen exclusive which is pretty much most games these days that cannot run fullscreen exclusive.
The latest 24.4.1 AMD driver is out, and it fixes the driver timeoutā¦ in Overwatch 2ā¦ lol
Seems like a good driver for Helldivers 2 performance in particular.
Iāve finally hit the timeout a couple times now, but only when snapping into a heavy performance hit with like 150+ players being loaded at once (cancelling a stream when porting into Valdrakken, or alt-tabbing as I fly into a Dragonbane Keep gathering on reset). However, I still cannot reproduce this problem on command.
Now may be a good time to raise your voice on r/AMD driver thread regarding AMD ignoring the driver issues with World of Warcraft for the last 16+ months at least for me that is how long if been having problems, AMD is ignoring a lot of user reports, you can tell by just reading the comments.
My laptop was in repair to get new Fans. I picked it up yesterday. I had no update on my AMD card as I completely forgot so it was on the last version before this one everyone is saying was a problem. I was playing for awhile yay. Then went to make supper and thought about making sure to update everything and opened up that AMD software (this is an Alienware and Dell has the AMD enhance on it) to get all the AMD drivers I need. rebooted when done, load up to play and wow & was 10 mins in it crashed the whole puter down. Loaded back up, got wow going, 2 mins or so, crashed. Tried again and I didnāt even get 1 min. Like an idiot I call puter repair guy. First thing ihe says ādoes it crash on any thing else or just wow, I say just wowā ding ding ding lol. Its my laptop nothing he did. I still cant play, Tried all the suggestions from here to Reddit and it wont work. Going back on hubbys Alienware that has NVidea as no one is complaining about those cards.
I am going to make an assertion I cant prove because i am not a programmer, but I frequently find my āphone linkā program open ( that i have disabled at startup) on my computer and the Radeon host settings running and my framerate plummets after that till AMD resets it again or I restart the computer.
I think people are hacking other peoples game speed that have radeon video cards and although I cant prove it , there was a member of a guild named " Depletionā standing nearby the Tuskar soup pot tonight and I think that name is a " haha in your face blizzard look what we can do to people and you dont care" guildname.
Otherwise why the hell would you name any guild " Depletionā ?
I guess some motherboard manufacturers are finally starting to take the hint. For example, this is the new beta BIOS version for the motherboard in this PC:
PRIME B660M-A D4 BIOS 3210
Version 3210
Beta Version
11.39 MB
2024/04/23
The update introduces the Intel Baseline Profile option, allowing users to revert to Intel factory default settings for basic functionality, lower power limits, and improving stability in certain games.
Naturally, they will still load their āoptimizedā profiles by default, to look good for your average lazy benchmarker, but at least thereās an easy profile option now. Iām not going to bother messing with it since I donāt have the issues, but others should check around and see if they have similar updates for their motherboards to try out.
When i report other bugs off other games they ask me of save game, cos it saves them time makes it quick and easy to reproduce issue for them, but i guess with World of Warcraft its not quick and easy to reproduce they just choose to ignore it, i guess it fails due lack of cooperation of Blizzard end on this part as well.
There is definitely an issue either with shaders or particle effects, seeing recent trends i am pretty sure its particle effects, there have been effects in gogrond if never seen rendered before, that now render fine, when AMD reduced a visual bug by 99% in dying light 2 they disabled particle effects as well, so there might be actual proof of AMD actually tampering with World of Warcraft already in the old drivers, its just a shame my subscription ended.
The effects i suspect where missing are the volcano smoke effects in Gogrond, around drivers 22.5.2 - 23.2.1 for rx6000 series.
Areas if crashed the most in the past pre patch time.
Gogrond always areas with lots of particle effects.
In dragonflight its the same thing azure span i crashed the most, especially archives azure archives, there are lot of particle effects in Azure span.