Radeon Software Crimson Edition 16.8.3 Download & Discussion

you upgraded your 390s for the 480s?

was the upgrade worth it? or is the performance the same?

im thinking about upgrading my 290 vapor-x which is basically a 390 performance wise.

 

- apologies..
meant 2xSapphire R9 380 NITRO's..

- the 480's really are smashing..
- beautifully made - so quiet..
- all this and a lightshow as well..

- I'm not much for benchmarking
- so I'll just say these things really fly..!!

:tomcat:

 

rats, im still trying to find someone whos upgraded from a 390.

its obviously way faster than a 380.

 

Upgrading from 290X or 390 you can only look at nvidia offerings atm. Something like 1070 seems a good choice.

 

A 1070 and up is your only real choice. Depending on what and how you play, I'm not even sure it's worth it.

 

1080p.

but i want 60fps minimum all ultra.

my 290 doesn't quite make it.

 

My 390 gives me my 1080p@60 on Ultra in a lot of games I play. Seeing how the rumor mill is hinting at an October release for AMD's next card, I'd sit tight and wait.

 

Especially with how the games are made these days, all ultra is usually folly. But I guess you would be fine with a 1070 for that.

 

no thanks.

dont like nvidia.

 

not in the games i play, and not MINIMUM 60fps. as in never dips below.

witcher3, fallout4, DAI, etc.

 

Then you dont have a choice but to wait Vega.

 

Oh great. Idle clocks bug is also present on a Asus7870 DCII (non-top, non GHz/boost)) with W10 AU and 1.8.3. It happens the same as on my 7970 in the previous system.

When HW mode is enabled on Chrome and it starts idling at UVD's 450/1200 lowest state, if I launch MPC-HC and play a file, after exiting both I'll get 450/1200 on idle in the desktop instead of 300/150 without any 3D accelerated program running.
As expected, when in that state it won't also apply 3D OC when running in 3D mode, because it'll use the higher UVD state instead that is equal to the stock 3D clock (1000/1200, same #0 id).

 

This will get you close if you do not want to wait:

http://www.newegg.com/Product/Product.aspx?Item=N82E16814202186&cm_re=fury-_-14-202-186-_-Product

 

I have Asus 7870 DCII V2 and I don't have idle bug. Use 16.8.2.

 

Asus 7870 DCII V2 also, bios 015.017.000.001.000838 (original non UEFI). And I can reproduce it too with 16.8.2 with that Chrome + MPC-HC combination, after letting Chrome set 450/1200 clocks while browsing pages with HW accel.

 

yeah, ive been eyeing a fury or a nano, just a little too expensive when ill just replace it with vega in 6 months.

 

You could also buy a cheap second-hand 290 and go for CF; for games that CF works, it usually scales very well. But there are also a lot of cases in which it doesn't, especially in new games. I personally never play recent games and always wait until all patches and DLCs and other stuff are released and hence, I usually do not have scaling problems, but CF-related visual bugs and crashes are not that rare even on old games.

Honestly, with the death of RadeonPro and AMD being more incompetent than ever both in the hardware and software departments, I am seriously considering to switch to Nvidia in my next update (NVIDIA Inspector looks very promising); unless Vega turns out to be miracle (which it probably won't).

 

im a single gpu kinda guy.

ill just have to be patient.

 

Oh well.. computer turned on, doing "nothing".

BSOD'ed, 0x000000ea. Fun times ahead.

Spoiler

Code:

ADDITIONAL_DEBUG_TEXT:  

Use '!findthebuild' command to search for the target build information.

If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

FAULTING_MODULE: fffff8039e40e000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAULTING_THREAD:  ffffe20f042eb800

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0xEA

CURRENT_IRQL:  0

BAD_PAGES_DETECTED: dc5c

LAST_CONTROL_TRANSFER:  from fffff80da7962e0f to fffff8039e5580d0

STACK_TEXT:  
ffffb900`28127098 fffff80d`a7962e0f : 00000000`000000ea ffffe20f`042eb800 00000000`00000000 00000000`00000000 : nt+0x14a0d0
ffffb900`281270a0 fffff80d`a7962ece : ffffb900`28127178 fffff80d`a9a54efc ffffb900`28127178 ffffb900`28127240 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x3f
ffffb900`28127110 fffff80d`a99fdc20 : ffffe20f`08140000 ffffb900`28127281 ffffb900`28127240 fffff80d`a9a54ee8 : dxgkrnl!TdrTimedOperationDelay+0xbe
ffffb900`28127150 ffffe20f`08140000 : ffffb900`28127281 ffffb900`28127240 fffff80d`a9a54ee8 00000000`00002710 : atikmdag+0x4dc20
ffffb900`28127158 ffffb900`28127281 : ffffb900`28127240 fffff80d`a9a54ee8 00000000`00002710 00000000`00000028 : 0xffffe20f`08140000
ffffb900`28127160 ffffb900`28127240 : fffff80d`a9a54ee8 00000000`00002710 00000000`00000028 fffff80d`a99fdbf4 : 0xffffb900`28127281
ffffb900`28127168 fffff80d`a9a54ee8 : 00000000`00002710 00000000`00000028 fffff80d`a99fdbf4 00000000`00000101 : 0xffffb900`28127240
ffffb900`28127170 00000000`00002710 : 00000000`00000028 fffff80d`a99fdbf4 00000000`00000101 00000000`00000000 : atikmdag+0xa4ee8
ffffb900`28127178 00000000`00000028 : fffff80d`a99fdbf4 00000000`00000101 00000000`00000000 00000000`001ed831 : 0x2710
ffffb900`28127180 fffff80d`a99fdbf4 : 00000000`00000101 00000000`00000000 00000000`001ed831 ffff8fa3`d07e053b : 0x28
ffffb900`28127188 00000000`00000101 : 00000000`00000000 00000000`001ed831 ffff8fa3`d07e053b fffff80d`a99f6123 : atikmdag+0x4dbf4
ffffb900`28127190 00000000`00000000 : 00000000`001ed831 ffff8fa3`d07e053b fffff80d`a99f6123 00000000`00000001 : 0x101


STACK_COMMAND:  .thread 0xffffe20f042eb800 ; kb

SYMBOL_NAME:  PAGE_NOT_ZERO

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware_ram

BUCKET_ID:  WRONG_SYMBOLS

Followup: MachineOwner
---------

 *** Memory manager detected 56412 instance(s) of page corruption, target is likely to have memory corruption.

http://pastebin.com/Q9sakTYS

 

Yep same bios, I use firefox and vlc/splash w/o issues. Alley AMD just released new 16.9.1 and they acknowledged and hopefully fixed some of idle bugs.