Discussion in 'Videocards - AMD Radeon Drivers Section' started by Rich_Guy, Sep 28, 2015.
I have memory leak too.
Just got a warning for low memory. Firefox using 32GB while watching Youtube.
It is in beta so it's allowed to have bugs
Have to think positive sometimes. You can always go back to 15.8
I'm surprised they haven't pulled these drivers off of their site.
Indeed, me too. I haven't had any issues with them personally though.
For me, the memory bug was caused by atidxx64.dll. Replaced it with an older version; it seems to be stable for now.
Were all you guys who experienced the bug on x64 windows?
x64 here, no issues yet.
Memory leaks everywhere... But... it seems to cap out at 3gb and no warnings or anything and performance in the games I've played so far don't seem to be effected much if at all.
EDIT: Spoke too soon, getting warning messages now
Same here - Win 10 Pro x64 and Opera 34 Dev - no VRAM issues for me yet.
Actually, now when I did more testing, VRAM leak here too (Windows 10 PRO 64-Bit Build 10547 - Insider Preview + HD 7750) on Chrome while watching vids on Youtube and resizing the browser. Back to 15.7 or 15.8 for now. I hope AMD will fix this issue soon.
I can confirm too that there is a memory leak. This explains the BSOD I had yesterday. Did the window resizing test, eventually ran into low memory warning followed by BSOD can't remember exactly what the error message was but it was along the lines of "DX*** System thread exception".
Windows 10 64bit, R9 285
thank god i waited until the weekend to install the 15.9`s guess im staying with 15.8s for now.
i still have issue every driver after 15.6 my 4k asus pq321 mst split in two screen with vsync on and audio in crossfire get mest up when something runing backround while gaming 295x2 quadfire and with all drivers i have audio issue
No matter bro -> look into My Tweaks for CPU's FX also, Glad you have Sabertooth 990FX :banana:
Anyone give the atidxx64.dll from 15.8?
edit: the dll did not help.
Confirming the memory leak issue, I already rolled back to 15.8b. I'm on win10, x64 of course. Somehow I didn't manage to trigger any warnings, but I was able to reproduce the leak by resizing a window - it would easily jump 400MB in just a second of resizing.
Seems like its holding on to every framebuffer of the windows GUI redrawing the size of the window form. Maybe disabling "show window contents while resizing" would help - but idk if they still have that setting post-win7.
With this driver, for the first time ever, I'm experiencing issues with Firefox. W10 x64 build 10240.
Gaming performance is good though and stable so far, so kinda torn about rolling back or not.
I have a feeling that a really nice driver with nice memory management will (eventually) come out of this.
Since it's happening to everyone, it makes me optimistic that the memory optimizations won't only goes to the Fyries, but the whole range of current Catalyst.
Dont instal bro...
there was a memory leak
New driver on amd website 15.9.1 Beta, Fixed memory leak i presume without trying it.