The AMD Driver Thread

[TheMorningStar]

Are you using after burner overlay? If so turn it off.

Yup, that's fixed it, cheers for that

 

[xb8browney]

I only get that on driver 16.10.2.. when I reverted back to 16.10.1 no issues.

Same here but NOW it's happening on both drivers for me.

 

[shankly1985]

Same here but NOW it's happening on both drivers for me.

Because its not a driver issue

 

[TonyTurbo78]

Well, since turning off crossfire, bf1 is kinda enjoyable now, and the fps is actually very impressive. Will keep it disabled for now until we get some proper optimisation for it

 

[xb8browney]

Switching to DX11 made no difference to me, still getting error.

 

[xb8browney]

Because its not a driver issue

How come it's happening all the time tonight compared with once every few days before?

 

[thebennyboy]

DX12 is broken to hell on the latest 16.10.2 drivers, crashing every 15 - 20 mins. Also have a crash whilst on the desktop... 16.10.2 seems like a very rushed driver.

 

[shankly1985]

How come it's happening all the time tonight compared with once every few days before?

No idea its very random, they is a massive thread on the Battlefield forums of people changing all different settings to reduce it.

Some people are having more luck locking the FPS down to 60fps to reduce the CPU spiking.

https://forums.battlefield.com/en-u...-statement-from-ea-23-10-16-18-12-cest#latest

 

[shankly1985]

DX12 is broken to hell on the latest 16.10.2 drivers, crashing every 15 - 20 mins. Also have a crash whilst on the desktop... 16.10.2 seems like a very rushed driver.

I had more crashes on 16.10.1 than I have on 16.10.2

The game is very strange! Conquest 64 players one game is perfect CPU load the next a spiking mess..

Dice have lot of work to be done.

 

[YB2ndBEST]

This is very odd indeed. I don't know if I just got lucky but everything has been pure titsmcgee since going back to 16.10.1 hell I'm pretty addicted to this damn game now

 

[thebennyboy]

I had more crashes on 16.10.1 than I have on 16.10.2

The game is very strange! Conquest 64 players one game is perfect CPU load the next a spiking mess..

Dice have lot of work to be done.

Forgot to add that's in DX12 on BF1 exclusively, not DX12 in general. Pretty sure you knew that already though by your reply.

Rolling back to 16.10.1 has got rid of all the issues. It ran very well on 16.10.1 even without any optimisations in 16.10.2, performance was actually worse in 16.10.2 though... Loads of frame drops and the random crashing.

 

[YB2ndBEST]

I spoke a little too soon earlier haaaaaahahahhaa.. I did finally get a dxerror crash today on 16.10.1 but 1 out of every 10 hours of gameplay, not so bad vs 1 every 15 minutes.

 

[xb8browney]

managed to get an hour or so game play in without a crash, whats everyone going on about CPU usage? mines always nearly 100% but it was just the same on some maps on BF4.

 

[GinG]

GPU - 100%
CPU - 60 - 70%

FPS around 90 - 100

GPU Mem usage - just under 3gb

Ultra settings

 

[Captain_Bosh]

Can anyone confirm if Crossfire works in Mirrors Edge Catalyst yet?

 

[Nexus18]

Is HBAO+ broken for anyone else in the division?

Even before the patch released today, I noticed this:

 

[shankly1985]

People still play that?

 

[Nexus18]

People still play that?

A few thousand do Got a massive patch today changing a lot of things.

 

[Nexus18]

Also, does anyone use custom settings for "all games" here i.e. texture filtering and so on.

 

[LoadsaMoney]

LMFAO! had a small patch for ROTTR down today, so banged it on in Xfire (used to run ok), its bloody broken now, constant flashing (Win 7 so Dx11)

EDIT: took the game back 2x patches, and its still doing it, wtf

Thought it may have been my 2nd card, as not had it enabled for yonks, but tried a few other games, and fine, so wtf has happened to Tombi.