Soldato
Had 3 crashes in BF1 last night with 17.11.1 driver, was fine on previous. No other game or benchmark is crashing.
-
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.
The AMD Driver Thread
- Thread starter LtMatt
- Start date
Soldato
Could it be that the game freaks out when it sees more than 4 cores ? I'll have to disable 4 cores and experiment.
Soldato
I have an ACER XR341CK and Vega64, when it wakes from sleep I often get link failure error (used to happen with my Fury X as well)?
Currently running 17.11.1 but issue has spanned multiple driver versions, I've submitted a report but annoyingly you don't get any way to track, you get a an email saying "Your feedback is extremely important to us and we review all submissions received" but nothing else!
Currently running 17.11.1 but issue has spanned multiple driver versions, I've submitted a report but annoyingly you don't get any way to track, you get a an email saying "Your feedback is extremely important to us and we review all submissions received" but nothing else!
Last edited:
Glad you said that Tony, i thought it was just me.
Can you try stock settings (no overclocks anywhere) with +50% power limit and let me know if you see the same?
If anyone else is experiencing crashing on BF1, please provide full system specs, driver version and settings used so i can raise it with engineering.
Soldato
I have the same monitor now paired with a Vega 64 and previously with a Fury X. I too get the same message with the Vega and before with the Fury X but it only happens occasionally, maybe once or twice every couple of weeks. I've never seen it actually effect anything although I usually reboot when I see it - I imagine it would affect Freesync though?
Soldato
For me sometimes it cuts the available resolutions down to 800 x 600, I have to reboot to resolve.
Last edited:
Check the video when it starts...the wall kinda have some white glitch...and when i am recording with relive the game is a bit laggy.
Only when recording with Relive? Vulkan API is not fully supported in Relive yet so these type of issues can be expected in the short term.
Soldato
Sure thing, will be later today though.
Never had that problem my self, had a fury at the time but I was on windows 7 so maybe it's a windows 10 issue
A lot of failed oc attempts with these 17.11.1 drivers....high frequency spikes which cause a crash when running Firestrike (which I use to test stability of overclock)......usually my new AIO 64 with EK block runs S7 1750 - 1150mv an S6 1168 - 1100mv and PL + 25% @ 1730MHz (+ 25% and + 50% PL seem to give very similar results) when the driver sticks the settings but sometimes it spazzes out and there are spikes to 1790MHz in gpu-z monitor and that's the crash time. Drivers are awfully buggy for sticking settings.
Associate
- Joined
- 31 Aug 2017
- Posts
- 2,209
I often see link failures on my fury pro going through an hdmi converter to the telly, i also see a lot of blank screens on windows start (after post) and the odd one when exiting a game.
Did it on my vega as well, and after wiping windows ... suspect its a 10 issue.
Did it on my vega as well, and after wiping windows ... suspect its a 10 issue.
<sigh> Wattman setting still not being retained at boot time. How many times has this been listed as fixed in the release notes, and it never is? How difficult it is to program a way to save the settings and then load them as Catalyst loads up at boot time?
Soldato
Does it pretty much all the time now since my move to VEGA.
Have you tried hitting apply every time you change a setting, I found this worked rather than change all the required settings and applying once
Now it's intermittent, so it only resets about once in every three boots (so it seems). So I'm not even changing setting and some boots Wattman will reset. They've hidden the pop-up notification, so now you have to go and look at it to see when it's done it.
Soldato
I found that while Wattman was displaying stock settings after reboot, the overclocks where still there on GPUZ? Might be the same for you?
Same here, intermittent resets to "balanced" mode on my V64. It has absolutely nothing to do with unstable overclocks or undervolts either. I could change from balanced to custom and only move the fan speed setting to manual and it will forget at the next boot.
It even resets if I have not went into 3d mode at all. A number of times I have booted, noticed it back to balanced, so I set my preferred values without even playing a game. Next reboot, back to balanced.
- Corruption when maximising Wattman window
- Wattman setting being "forgotten" almost every reboot
- Individual game profiles no longer working
Last edited:
Yes, it's a complete PITA, and I don't even have any particularly complex settings. You can google and see it's been going on for more than 18 months for some people. How difficult is it to write the values to a file and then load them when Wattman starts? I think AMD are trying to be too clever so that anyone doesn't oerclock too far and put their cards into a state where they can't boot to a screen, but (a) AMD obviously can't make it work properly and (b) that's what safe mode is for.
Soldato
they did have mouse corruption issues for far longer than that, but whenever i mentioned it people would say it doesn't happen to them so it must be my fault.
Last edited: