- Joined
- Sep 20, 2019
- Messages
- 524 (0.28/day)
Processor | i9-9900K @ 5.1GHz (H2O Cooled) |
---|---|
Motherboard | Gigabyte Z390 Aorus Master |
Cooling | CPU = EK Velocity / GPU = EK Vector |
Memory | 32GB - G-Skill Trident Z RGB @ 3200MHz |
Video Card(s) | AMD RX 6900 XT (H2O Cooled) |
Storage | Samsung 860 EVO - 970 EVO - 870 QVO |
Display(s) | Samsung QN90A 50" 4K TV & LG 20" 1600x900 |
Case | Lian Li O11-D |
Audio Device(s) | Presonus Studio 192 |
Power Supply | Seasonic Prime Ultra Titanium 850W |
Mouse | Logitech MX Anywhere 2S |
Keyboard | Matias RGB Backlit Keyboard |
Software | Windows 10 & macOS (Hackintosh) |
Little bit of a PSA kinda post. Using a RX 5700 XT in my main build for a couple years until I upgraded to a RX 6900 XT. Later building a separate SFF system and repurposing the RX 5700 XT in that SFF system this issue got even worse it seemed. (to clarify, regarding the RX 5700 XT in the SFF system is what got worse) I would now constantly get an error from AMD Radeon Software that "Default Radeon WattMan settings have been restored due to an unexpected system failure" and this always happened whenever I entered in custom settings in Wattman. The major problem here is there was no system failure....so wtf was causing it to think there was? Mind you this didn't happen because I had out of bounds settings entered, something the card or system cannot handle.....not the case at all. Also keep in mind this occurred right at startup of the OS, it only happened on cold boots, rather than warm boots/reboots. This never occurred when putting a heavy load on the card. I never noticed this issue much at all on my main rig because I would leave default settings and only load custom profiles based on game ABC or program XYZ booting. So the GPU always had default settings on a cold boot. But when I was "dialing in" custom settings I would sometimes make those settings defaults just as I test them out and this is when I first noticed the issue. Not until the RX 5700 XT went to live in the SFF system where I purposely wanted to put a 24/7 undervolt and powerlimit on it to keep temps in check did I start to experience this on a 100% repeatable and frequent basis.
The nail in the coffin that something was fishy was when I tried selecting the "custom" button in Wattman but did not change a single setting so still had default gpu and mem clock, voltages, fan curve etc and it STILL produced this error on a cold boot. At first I thought it got worse in my SFF system because I only plugged in a single PCIe cable that had a Y at the end to populate both the 6 and 8pin PCIe ports. After changing that to two dedicated cables the situation didn't improve. I only used a single cable at first to keep clutter down in the small case, but adding the 2nd cable was an effort made in vain.
I dealt with this for a while and it's wide spread enough that there are lots of posts out and about going back several years detailing this issue with lots of suggestions, none which worked for me except for disabling fast startup.
Turning fast startup OFF in Power & Sleep Settings fixed this for me. The only connection I can draw is the issue did occur only on cold boots, and this setting has something to do with how the system deals with a shutdown and cold boot. Sounds like it goes into pseudo hibernation (closing programs and log out users instead of leaving your session in tact) instead of a true shutdown just so it boots a little quicker?! I really cannot tell a difference with it on or off, so whatever time save happens seems to be minuscule for me. So if you happen to have this error occurring when you are certain your custom settings are not the culprit, this would be a good first thing to try because it's such an easy low hanging piece of fruit to go after, just disable this setting! The picture shows it as enabled, so make sure there is no check mark to set it to disabled. You likely will need to click the text "Change settings that are currently unavailable" in order to change it one way or the other. You can find the fast startup setting in "Power & Sleep Settings" > "Additional power settings" > "Choose what the power buttons do".
The nail in the coffin that something was fishy was when I tried selecting the "custom" button in Wattman but did not change a single setting so still had default gpu and mem clock, voltages, fan curve etc and it STILL produced this error on a cold boot. At first I thought it got worse in my SFF system because I only plugged in a single PCIe cable that had a Y at the end to populate both the 6 and 8pin PCIe ports. After changing that to two dedicated cables the situation didn't improve. I only used a single cable at first to keep clutter down in the small case, but adding the 2nd cable was an effort made in vain.
I dealt with this for a while and it's wide spread enough that there are lots of posts out and about going back several years detailing this issue with lots of suggestions, none which worked for me except for disabling fast startup.
Turning fast startup OFF in Power & Sleep Settings fixed this for me. The only connection I can draw is the issue did occur only on cold boots, and this setting has something to do with how the system deals with a shutdown and cold boot. Sounds like it goes into pseudo hibernation (closing programs and log out users instead of leaving your session in tact) instead of a true shutdown just so it boots a little quicker?! I really cannot tell a difference with it on or off, so whatever time save happens seems to be minuscule for me. So if you happen to have this error occurring when you are certain your custom settings are not the culprit, this would be a good first thing to try because it's such an easy low hanging piece of fruit to go after, just disable this setting! The picture shows it as enabled, so make sure there is no check mark to set it to disabled. You likely will need to click the text "Change settings that are currently unavailable" in order to change it one way or the other. You can find the fast startup setting in "Power & Sleep Settings" > "Additional power settings" > "Choose what the power buttons do".