Skip to main content
Z
Zottwalker
Participating Frequently
October 28, 2012
Question

Photoshop CS6, Windows 8 and crazy GPU behavoir

  • October 28, 2012
  • 14 replies
  • 53013 views

Hi!
I just installed windows 8 and i got a lot of problems with CS6 Extended (Design and web premium creative suite installed) and GPU use (i never had a problem under windows 7).

My sistem is updated and equipped with a I7, 8 GB RAM and a Radeon HD 5870 card and i'm working winth Canon EOS 1Dx and EOS 5D mkIII raw files (but the problems appear also with snall jpg)

When PS use the GPU acceleration the display becone crazy showing a lot of different things.

This is the first list of things appening:
A) very often (about 95% of times) when i use the crop tool the image start to flicker from visible to black ( http://www.asf-images.com/ps1.jpg ) so it is impossible to work; sometimes (50% of times) images become visible again moving the mouse to a different location and after moving again the mouse the images fade to black and so on... frustrating.

B) cropping become very slow

C) during crop images a big distorsion appear ( http://www.asf-images.com/ps2.jpg)

D) sometimes during crop or changing the GPU setting the border outside the image become filled of gray/white little square as a trasparent layer (http://www.asf-images.com/ps4.jpg)

E) after canceling the crop tool action (using the cancel button in the Option tool bar) the image fade to black (http://www.asf-images.com/ps5.jpg )

This appens also with blur tool, liquify and all that use the mercury engine.

Changing GPU drawing mode from normal to basic or advanced all works but after closing and reopening PS problems are still visible
Sometimes the graphic card GPU disapper (http://www.asf-images.com/ps3.jpg)

Pleae, Help!!!
Last: sorry for my english 🙂

This topic has been closed for replies.

14 replies

Show previous replies
J
jetpower30
Participant
November 11, 2012

Further to my earlier post, have a look here http://www.minecraftforum.net/topic/1086017-ati-radeons-and-windows-8-the-fix/

J
jetpower30
Participant
November 10, 2012

Hi Zottwalker, My graphics processor was disabled by the latest display driver, this may be related to your problem . I searched and replaced it we an older driver, works fine now, hope this helps.

Carl

W
wally_lopez
Participant
November 2, 2012

I've had the exact same issue after uprgrading to WIN8 PRO so I've tested a couple of things like changing the Photoshop.exe to run in compatibility mode or to install the latest Catalyst suite (12.11 beta) but neither approach managed to resolve the problem. Anyway I've found a temporary work around: Go to EDIT > PREFERENCES > PERFORMANCE and uncheck the "USE GRAPHIC PROCESSOR" box - close Photoshop and restart it.

Works like charm here and hopefully on your side too.

Noel Carboni
Noel Carboni
Legend
November 2, 2012

"Works like a charm" usually means that something provides all the functionality.  With Use Graphics Processor unchecked you have disabled a number of features some would consider critical.  That may be a workaround to having a working GPU driver, but it's not going to be an acceptable fix for most folks.

-Noel

Noel Carboni
Noel Carboni
Legend
October 28, 2012

You're not alone.

Apparently the display drivers provided with the OS are insufficient to support Photoshop's GPU usage well enough.

Have you tried visiting the AMD web site, seeking out the latest Catalyst driver release for your hardware and OS, and downloading/installing it?

Unfortunately, this is one good reason among many that you really should avoid upgrading to a brand new operating system on the first day of its release.  I know this doesn't help you, Zottwalker, but this is written for those who haven't upgraded  yet.

-Noel

A
Anonymous
October 28, 2012

But if everyone waited for the dust to clear, who would blaze the path through all the problems?

All the Win 8 users who change in 6 months will thank you, Zottwalker.

Noel Carboni
Noel Carboni
Legend
October 28, 2012

Hm, maybe the manufacturers of the products ought to be the ones to "blaze through" the problems before the products are released.

Gee, what a concept - Microsoft, AMD, and Adobe all working together with the pre-release versions so that the released version actually works for users.

I believe that Chris Cox worked on trying to get AMD and Microsoft to include proper and working drivers for the Windows 8 release.  But apparently that input wasn't enough to get the job done, becuase in these modern times greedy businessmen always push to release software products before they're finished.  It can always be fixed later through the "cloud", right?  Sheesh.

But even beyond that, there has been an important shift:  Microsoft no longer considers it a high priority that you should actually be able to WORK with Windows.  Their focus has shifted from powering business to powering toys (consumer tablets, that sort of thing).  As such, they care most about the applications that they'll be selling in their shiny new App Store, and almost not at all whether you and your desktop applications work.  Thus the very basis for the philosophy "Microsoft released it, it must be worth having" is now suspect.

Some of that can be mitigated.  I've been running Windows 8 for a year now, and I've had my Windows 8 book done and on sale well before the public release.  Some folks have taken advantage of it and have had a much smoother experience, but I can't document around software that just doesn't work.

As it is, my best advice was and remains this:  Watch and wait while other poor users blaze through the problems.

I sound like a helluva skeptic, don't I?  But I'm really an early adopter technophile who has been around since before there ever was a Microsoft.  That should help you understand the weight of my statement above.

-Noel

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices