http://www.pcworld.com/article/30414...res-a-fix.html
I personally had to do a system refresh
http://www.pcworld.com/article/30414...res-a-fix.html
I personally had to do a system refresh
Check out the directors cut of my project SCHISM, a festival winning short film
https://www.youtube.com/watch?v=DiHNTS-vyHE
There is already a replacement driver available that fixes this issue, your notice comes a tad bit late.
Rolling back to the previous driver isn't witchcraft though, failed driver installs happen sometimes, even if it isn't nice.
But... Only AMD has terrible drivers....
But seriously, I always wait before installing new drivers because 9 times out of ten, theres somethign like this, or overheating cards, or something stupid going on.
Im having no issues with the drivers in question.
There can't be that many who updated to it, I got 362 only recently (i slacked) and the next Game Ready for me is showing 364.51, I can't mind seeing a 364.47 show up at any point either.
Had issues in Windows 10 where ff14 would crawl to 15 fps so reverted back. No crashes though for the short time I had the driver.
Going to close this thread, as it's now obsolete information.
It really only applies to
-People who have Windows 10
-People who opted into Beta drivers (very few)
Currently the current most stable drivers are 362.00, and the buggy beta driver has already been replaced by 364.51.
Gaming: Dual Intel Pentium III Coppermine @ 1400mhz + Blue Orb | Asus CUV266-D | GeForce 2 Ti + ZF700-Cu | 1024mb Crucial PC-133 | Whistler Build 2267
Media: Dual Intel Drake Xeon @ 600mhz | Intel Marlinspike MS440GX | Matrox G440 | 1024mb Crucial PC-133 @ 166mhz | Windows 2000 Pro
IT'S ALWAYS BEEN WANKERSHIM | Did you mean: Fhqwhgads"Three days on a tree. Hardly enough time for a prelude. When it came to visiting agony, the Romans were hobbyists." -Mab