ATI 5750 and Photoshop CC ISSUE

I'm having driver issues with the ATI Radeon HD 5750 and Photoshop CC. You can see from the screenshot the lines going through the image I have contacted Adobe they are aware of the problem.  Its in your hands now Apple to resolve

so I find this article on adobe site
Pete.Green writes:
Adobe and Apple have worked closely together to test Adobe® Creative Cloud applications and Adobe Creative Suite 6 applications for reliability, performance and user experience when installed on Intel® based systems running Mac OS X Mavericks. (v10.9). All Adobe CC and CS6 products are compatible, but a few products require updates to the latest builds to work properly.
Adobe Photoshop® CS5, CS4 and CS3 were tested with Mac OS X Mavericks and there are currently no major issues known.
I guess you missed this issue ....

Similar Messages

  • [SOLVED][ATI] Driver and/or Kernel Issue?

    Hi all,
    I've got a serious issue on my Workstation.
    The installation is only a few days old. It's the first Linux Installation on this system. So I don't know if ohter distributions/kernelversions would do it without any issue. I've not tried to install ATI propritary drivers as xorg 1.16 is installed.
    System specs:
    GPU ATI R9 270x
    CPU Intel Haswell i5-4440
    Board MSI H87-G43
    RAM 8 GB Mushkin DDR-3/1333
    Samsung SSD 830
    Problem discription:
    The system crahes randomly (after 5 mins. or after an two hours). Screen Blanks. Nothing is available. I had to do a hard reset every time. This happen in all circumstences e. g. Browsing Internet or even if there is nothing done on the computer. In all cases I've got no log-entries.
    But the last crash was different: the Display came back after a few minutes (just for the record: I've waited every crash for 10-15 mins. -.-).
    I've got the following log:
    Log:
    Aug 29 10:25:46 localhost kernel: radeon 0000:01:00.0: ring 0 stalled for more than 10013msec
    Aug 29 10:25:46 localhost kernel: radeon 0000:01:00.0: GPU lockup (waiting for 0x00000000001d5b16 last fence id 0x00000000001d5b12 on ring 0)
    Aug 29 10:25:46 localhost kernel: radeon 0000:01:00.0: scheduling IB failed (-35).
    Aug 29 10:25:46 localhost kernel: radeon 0000:01:00.0: Saved 27536 dwords of commands on ring 0.
    Aug 29 10:25:46 localhost kernel: radeon 0000:01:00.0: GPU softreset: 0x0000006C
    Aug 29 10:25:46 localhost kernel: radeon 0000:01:00.0: GRBM_STATUS = 0xA0003028
    Aug 29 10:25:46 localhost kernel: radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000006
    Aug 29 10:25:46 localhost kernel: radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000006
    Aug 29 10:25:46 localhost kernel: radeon 0000:01:00.0: SRBM_STATUS = 0x20000AC0
    Aug 29 10:25:46 localhost kernel: radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000
    Aug 29 10:25:46 localhost kernel: radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000
    Aug 29 10:25:46 localhost kernel: radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00010000
    Aug 29 10:25:46 localhost kernel: radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000002
    Aug 29 10:25:46 localhost kernel: radeon 0000:01:00.0: R_008680_CP_STAT = 0x80010243
    Aug 29 10:25:46 localhost kernel: radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44483146
    Aug 29 10:25:46 localhost kernel: radeon 0000:01:00.0: R_00D834_DMA_STATUS_REG = 0x44C84246
    Aug 29 10:25:46 localhost kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000
    Aug 29 10:25:46 localhost kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000
    Aug 29 10:25:47 localhost kernel: radeon 0000:01:00.0: GRBM_SOFT_RESET=0x0000DDFF
    Aug 29 10:25:47 localhost kernel: radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00100140
    Aug 29 10:25:47 localhost kernel: radeon 0000:01:00.0: GRBM_STATUS = 0x00003028
    Aug 29 10:25:47 localhost kernel: radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000006
    Aug 29 10:25:47 localhost kernel: radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000006
    Aug 29 10:25:47 localhost kernel: radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0
    Aug 29 10:25:47 localhost kernel: radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000
    Aug 29 10:25:47 localhost kernel: radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000
    Aug 29 10:25:47 localhost kernel: radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000
    Aug 29 10:25:47 localhost kernel: radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000
    Aug 29 10:25:47 localhost kernel: radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000
    Aug 29 10:25:47 localhost kernel: radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57
    Aug 29 10:25:47 localhost kernel: radeon 0000:01:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57
    Aug 29 10:25:47 localhost kernel: radeon 0000:01:00.0: GPU reset succeeded, trying to resume
    Aug 29 10:25:47 localhost kernel: [drm] probing gen 2 caps for device 8086:c01 = 261ad03/e
    Aug 29 10:25:47 localhost kernel: [drm] PCIE gen 3 link speeds already enabled
    Aug 29 10:25:47 localhost kernel: [drm] PCIE GART of 1024M enabled (table at 0x0000000000276000).
    Aug 29 10:25:47 localhost kernel: radeon 0000:01:00.0: WB enabled
    Aug 29 10:25:47 localhost kernel: radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0xffff8800da15ec00
    Aug 29 10:25:47 localhost kernel: radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and cpu addr 0xffff8800da15ec04
    Aug 29 10:25:47 localhost kernel: radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and cpu addr 0xffff8800da15ec08
    Aug 29 10:25:47 localhost kernel: radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0xffff8800da15ec0c
    Aug 29 10:25:47 localhost kernel: radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and cpu addr 0xffff8800da15ec10
    Aug 29 10:25:47 localhost kernel: radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc90004fb5a18
    Aug 29 10:25:47 localhost kernel: [drm] ring test on 0 succeeded in 4 usecs
    Aug 29 10:25:47 localhost kernel: [drm] ring test on 1 succeeded in 1 usecs
    Aug 29 10:25:47 localhost kernel: [drm] ring test on 2 succeeded in 1 usecs
    Aug 29 10:25:47 localhost kernel: [drm] ring test on 3 succeeded in 2 usecs
    Aug 29 10:25:47 localhost kernel: [drm] ring test on 4 succeeded in 1 usecs
    Aug 29 10:25:47 localhost kernel: [drm] ring test on 5 succeeded in 2 usecs
    Aug 29 10:25:47 localhost kernel: [drm] UVD initialized successfully.
    Aug 29 10:25:57 localhost kernel: radeon 0000:01:00.0: ring 0 stalled for more than 10003msec
    Aug 29 10:25:57 localhost kernel: radeon 0000:01:00.0: GPU lockup (waiting for 0x00000000001d5c59 last fence id 0x00000000001d5b12 on ring 0)
    Aug 29 10:25:57 localhost kernel: [drm:r600_ib_test] *ERROR* radeon: fence wait failed (-35).
    Aug 29 10:25:57 localhost kernel: [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on GFX ring (-35).
    Aug 29 10:25:57 localhost kernel: radeon 0000:01:00.0: ib ring test failed (-35).
    Aug 29 10:25:58 localhost kernel: radeon 0000:01:00.0: GPU softreset: 0x00000048
    Aug 29 10:25:58 localhost kernel: radeon 0000:01:00.0: GRBM_STATUS = 0xA0003028
    Aug 29 10:25:58 localhost kernel: radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000006
    Aug 29 10:25:58 localhost kernel: radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000006
    Aug 29 10:25:58 localhost kernel: radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0
    Aug 29 10:25:58 localhost kernel: radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000
    Aug 29 10:25:58 localhost kernel: radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000
    Aug 29 10:25:58 localhost kernel: radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00010000
    Aug 29 10:25:58 localhost kernel: radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000002
    Aug 29 10:25:58 localhost kernel: radeon 0000:01:00.0: R_008680_CP_STAT = 0x80010243
    Aug 29 10:25:58 localhost kernel: radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57
    Aug 29 10:25:58 localhost kernel: radeon 0000:01:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57
    Aug 29 10:25:58 localhost kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000
    Aug 29 10:25:58 localhost kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000
    Aug 29 10:25:58 localhost kernel: radeon 0000:01:00.0: GRBM_SOFT_RESET=0x0000DDFF
    Aug 29 10:25:58 localhost kernel: radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100
    Aug 29 10:25:58 localhost kernel: radeon 0000:01:00.0: GRBM_STATUS = 0x00003028
    Aug 29 10:25:58 localhost kernel: radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000006
    Aug 29 10:25:58 localhost kernel: radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000006
    Aug 29 10:25:58 localhost kernel: radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0
    Aug 29 10:25:58 localhost kernel: radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000
    Aug 29 10:25:58 localhost kernel: radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000
    Aug 29 10:25:58 localhost kernel: radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000
    Aug 29 10:25:58 localhost kernel: radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000
    Aug 29 10:25:58 localhost kernel: radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000
    Aug 29 10:25:58 localhost kernel: radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57
    Aug 29 10:25:58 localhost kernel: radeon 0000:01:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57
    Aug 29 10:25:58 localhost kernel: radeon 0000:01:00.0: GPU reset succeeded, trying to resume
    Aug 29 10:25:58 localhost kernel: [drm] probing gen 2 caps for device 8086:c01 = 261ad03/e
    Aug 29 10:25:58 localhost kernel: [drm] PCIE gen 3 link speeds already enabled
    Aug 29 10:25:58 localhost kernel: [drm] PCIE GART of 1024M enabled (table at 0x0000000000276000).
    Aug 29 10:25:58 localhost kernel: radeon 0000:01:00.0: WB enabled
    Aug 29 10:25:58 localhost kernel: radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0xffff8800da15ec00
    Aug 29 10:25:58 localhost kernel: radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and cpu addr 0xffff8800da15ec04
    Aug 29 10:25:58 localhost kernel: radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and cpu addr 0xffff8800da15ec08
    Aug 29 10:25:58 localhost kernel: radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0xffff8800da15ec0c
    Aug 29 10:25:58 localhost kernel: radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and cpu addr 0xffff8800da15ec10
    Aug 29 10:25:58 localhost kernel: radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc90004fb5a18
    Aug 29 10:25:58 localhost kernel: [drm] ring test on 0 succeeded in 4 usecs
    Aug 29 10:25:58 localhost kernel: [drm] ring test on 1 succeeded in 1 usecs
    Aug 29 10:25:58 localhost kernel: [drm] ring test on 2 succeeded in 1 usecs
    Aug 29 10:25:58 localhost kernel: [drm] ring test on 3 succeeded in 2 usecs
    Aug 29 10:25:58 localhost kernel: [drm] ring test on 4 succeeded in 1 usecs
    Aug 29 10:25:59 localhost kernel: [drm] ring test on 5 succeeded in 2 usecs
    Aug 29 10:25:59 localhost kernel: [drm] UVD initialized successfully.
    Aug 29 10:25:59 localhost kernel: [drm] ib test on ring 0 succeeded in 0 usecs
    Aug 29 10:25:59 localhost kernel: [drm] ib test on ring 1 succeeded in 0 usecs
    Aug 29 10:25:59 localhost kernel: [drm] ib test on ring 2 succeeded in 0 usecs
    Aug 29 10:25:59 localhost kernel: [drm] ib test on ring 3 succeeded in 0 usecs
    Aug 29 10:25:59 localhost kernel: [drm] ib test on ring 4 succeeded in 0 usecs
    Aug 29 10:26:09 localhost kernel: radeon 0000:01:00.0: ring 5 stalled for more than 10000msec
    Aug 29 10:26:09 localhost kernel: radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000000004 last fence id 0x0000000000000002 on ring 5)
    Aug 29 10:26:09 localhost kernel: [drm:uvd_v1_0_ib_test] *ERROR* radeon: fence wait failed (-35).
    Aug 29 10:26:09 localhost kernel: [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on ring 5 (-35).
    Aug 29 10:26:09 localhost kernel: [drm:radeon_pm_resume_dpm] *ERROR* radeon: dpm resume failed
    Aug 29 10:26:09 localhost kernel: radeon 0000:01:00.0: GPU fault detected: 146 0x04a44804
    Aug 29 10:26:09 localhost kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x000111A5
    Aug 29 10:26:09 localhost kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x04048004
    Aug 29 10:26:09 localhost kernel: VM fault (0x04, vmid 2) at page 70053, read from TC (72)
    Aug 29 10:26:09 localhost kernel: radeon 0000:01:00.0: GPU fault detected: 146 0x01443d04
    Aug 29 10:26:09 localhost kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0001118A
    Aug 29 10:26:09 localhost kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0403D004
    Aug 29 10:26:09 localhost kernel: VM fault (0x04, vmid 2) at page 70026, read from DMA1 (61)
    Aug 29 10:26:09 localhost kernel: radeon 0000:01:00.0: GPU fault detected: 146 0x01443d04
    Aug 29 10:26:09 localhost kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00011199
    Aug 29 10:26:09 localhost kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0403D004
    Aug 29 10:26:09 localhost kernel: VM fault (0x04, vmid 2) at page 70041, read from DMA1 (61)
    Aug 29 10:26:09 localhost kernel: radeon 0000:01:00.0: GPU fault detected: 146 0x01643d04
    Aug 29 10:26:09 localhost kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x000111A3
    Aug 29 10:26:09 localhost kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0403D004
    Aug 29 10:26:09 localhost kernel: VM fault (0x04, vmid 2) at page 70051, read from DMA1 (61)
    Aug 29 10:26:09 localhost kernel: radeon 0000:01:00.0: GPU fault detected: 146 0x01643d04
    Aug 29 10:26:09 localhost kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x000111A7
    Aug 29 10:26:09 localhost kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0403D004
    Aug 29 10:26:09 localhost kernel: VM fault (0x04, vmid 2) at page 70055, read from DMA1 (61)
    Aug 29 10:26:09 localhost kernel: radeon 0000:01:00.0: GPU fault detected: 146 0x03c44404
    Aug 29 10:26:09 localhost kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0001119E
    Aug 29 10:26:09 localhost kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x04044004
    Aug 29 10:26:09 localhost kernel: VM fault (0x04, vmid 2) at page 70046, read from TC (68)
    Aug 29 10:26:09 localhost kernel: radeon 0000:01:00.0: GPU fault detected: 146 0x01a4c404
    Aug 29 10:26:09 localhost kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0001118D
    Aug 29 10:26:09 localhost kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x040C4004
    Aug 29 10:26:09 localhost kernel: VM fault (0x04, vmid 2) at page 70029, read from TC (196)
    Aug 29 10:26:09 localhost kernel: radeon 0000:01:00.0: GPU fault detected: 146 0x0424c804
    Aug 29 10:26:09 localhost kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x000111A1
    Aug 29 10:26:09 localhost kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x040C8004
    Aug 29 10:26:09 localhost kernel: VM fault (0x04, vmid 2) at page 70049, read from TC (200)
    The last three lines will repaet for a few minutes with different ADDR and STATUS messages. I've cut the log.
    Please help me to fix this. Thanks in advance.
    Last edited by vanquish (2014-09-05 17:57:05)

    Ironically I've begun to see a very similar problem on my desktop.  My hardware is a bit different:
    GPU: ATI R9 280x
    CPU: AMD Phenom 1100T
    Gigabyte Mobo
    OSS Drivers: Mesa 10.2.6/libdrm 2.4.54
    Kernel: 3.16.1
    I received the following error last time:
    Aug 30 21:52:23 DCRIG kernel: \x09\x09power level 2 sclk: 100000 mclk: 150000 vddc: 1144 vddci: 875 pcie gen: 2
    Aug 30 21:52:23 DCRIG kernel: \x09\x09power level 3 sclk: 110000 mclk: 150000 vddc: 1200 vddci: 875 pcie gen: 2
    Aug 30 21:52:23 DCRIG kernel: \x09status: r
    Aug 30 21:52:23 DCRIG kernel: [drm:si_dpm_set_power_state] *ERROR* si_set_sw_state failed
    Aug 30 21:52:23 DCRIG kernel: radeon 0000:07:00.0: GPU fault detected: 146 0x0f02a004
    Aug 30 21:52:23 DCRIG kernel: radeon 0000:07:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x000097F8
    Aug 30 21:52:23 DCRIG kernel: radeon 0000:07:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x020A0004
    Aug 30 21:52:23 DCRIG kernel: VM fault (0x04, vmid 1) at page 38904, read from CB (160)
    Aug 30 21:52:23 DCRIG kernel: radeon 0000:07:00.0: GPU fault detected: 146 0x0f029004
    Aug 30 21:52:23 DCRIG kernel: radeon 0000:07:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x000097F9
    Aug 30 21:52:23 DCRIG kernel: radeon 0000:07:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x020A0004
    Aug 30 21:52:23 DCRIG kernel: VM fault (0x04, vmid 1) at page 38905, read from CB (160)
    Aug 30 21:52:23 DCRIG kernel: radeon 0000:07:00.0: GPU fault detected: 146 0x0f02a004
    Aug 30 21:52:23 DCRIG kernel: radeon 0000:07:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x000097F8
    Aug 30 21:52:23 DCRIG kernel: radeon 0000:07:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x020A0004
    Aug 30 21:52:23 DCRIG kernel: VM fault (0x04, vmid 1) at page 38904, read from CB (160)
    Aug 30 21:52:23 DCRIG kernel: radeon 0000:07:00.0: GPU fault detected: 146 0x0f029004
    Aug 30 21:52:23 DCRIG kernel: radeon 0000:07:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x000097F9
    Aug 30 21:52:23 DCRIG kernel: radeon 0000:07:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x020A0004
    Aug 30 21:52:23 DCRIG kernel: VM fault (0x04, vmid 1) at page 38905, read from CB (160)
    Aug 30 21:52:24 DCRIG kernel: radeon 0000:07:00.0: GPU fault detected: 146 0x0f02a004
    Aug 30 21:52:24 DCRIG kernel: radeon 0000:07:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x000097F8
    Aug 30 21:52:24 DCRIG kernel: radeon 0000:07:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x020A0004
    Aug 30 21:52:24 DCRIG kernel: VM fault (0x04, vmid 1) at page 38904, read from CB (160)
    Aug 30 21:52:24 DCRIG kernel: radeon 0000:07:00.0: GPU fault detected: 146 0x0f029004
    Aug 30 21:52:24 DCRIG kernel: radeon 0000:07:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x000097F9
    Aug 30 21:52:24 DCRIG kernel: radeon 0000:07:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x020A0004
    Aug 30 21:52:24 DCRIG kernel: VM fault (0x04, vmid 1) at page 38905, read from CB (160)
    Aug 30 21:52:24 DCRIG kernel: radeon 0000:07:00.0: GPU fault detected: 146 0x0f22a004
    Aug 30 21:52:24 DCRIG kernel: radeon 0000:07:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000
    Aug 30 21:52:24 DCRIG kernel: radeon 0000:07:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x02084004
    Aug 30 21:52:24 DCRIG kernel: VM fault (0x04, vmid 1) at page 0, read from TC (132)
    Aug 30 21:52:25 DCRIG kernel: radeon 0000:07:00.0: GPU fault detected: 146 0x0f02a004
    Aug 30 21:52:25 DCRIG kernel: radeon 0000:07:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x000097F8
    Aug 30 21:52:25 DCRIG kernel: radeon 0000:07:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x020A0004
    Aug 30 21:52:25 DCRIG kernel: VM fault (0x04, vmid 1) at page 38904, read from CB (160)
    Aug 30 21:52:25 DCRIG kernel: radeon 0000:07:00.0: GPU fault detected: 146 0x0f029004
    Aug 30 21:52:25 DCRIG kernel: radeon 0000:07:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x000097F9
    Aug 30 21:52:25 DCRIG kernel: radeon 0000:07:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x020A0004
    Aug 30 21:52:25 DCRIG kernel: VM fault (0x04, vmid 1) at page 38905, read from CB (160)
    Aug 30 21:52:26 DCRIG kernel: radeon 0000:07:00.0: GPU fault detected: 146 0x0f02a004
    Aug 30 21:52:26 DCRIG kernel: radeon 0000:07:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x000097F8
    Aug 30 21:52:26 DCRIG kernel: radeon 0000:07:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x020A0004
    Aug 30 21:52:26 DCRIG kernel: VM fault (0x04, vmid 1) at page 38904, read from CB (160)
    Aug 30 21:52:26 DCRIG kernel: radeon 0000:07:00.0: GPU fault detected: 146 0x0f029004
    Aug 30 21:52:26 DCRIG kernel: radeon 0000:07:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x000097F9
    Aug 30 21:52:26 DCRIG kernel: radeon 0000:07:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x020A0004
    Aug 30 21:52:26 DCRIG kernel: VM fault (0x04, vmid 1) at page 38905, read from CB (160)
    Aug 30 21:52:27 DCRIG kernel: radeon 0000:07:00.0: GPU fault detected: 146 0x0f02a004
    Aug 30 21:52:27 DCRIG kernel: radeon 0000:07:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x000097F8
    Aug 30 21:52:27 DCRIG kernel: radeon 0000:07:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x020A0004
    Aug 30 21:52:27 DCRIG kernel: VM fault (0x04, vmid 1) at page 38904, read from CB (160)
    Aug 30 21:52:27 DCRIG kernel: radeon 0000:07:00.0: GPU fault detected: 146 0x0f029004
    Aug 30 21:52:27 DCRIG kernel: radeon 0000:07:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x000097F9
    Aug 30 21:52:27 DCRIG kernel: radeon 0000:07:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x020A0004
    Aug 30 21:52:27 DCRIG kernel: VM fault (0x04, vmid 1) at page 38905, read from CB (160)
    Aug 30 21:52:28 DCRIG kernel: radeon 0000:07:00.0: GPU fault detected: 146 0x0f02a004
    Aug 30 21:52:28 DCRIG kernel: radeon 0000:07:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x000097F8
    Aug 30 21:52:28 DCRIG kernel: radeon 0000:07:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x020A0004
    Aug 30 21:52:28 DCRIG kernel: VM fault (0x04, vmid 1) at page 38904, read from CB (160)
    Aug 30 21:52:28 DCRIG kernel: radeon 0000:07:00.0: GPU fault detected: 146 0x0f029004
    Aug 30 21:52:28 DCRIG kernel: radeon 0000:07:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x000097F8
    Aug 30 21:52:28 DCRIG kernel: radeon 0000:07:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x02050004
    Aug 30 21:52:28 DCRIG kernel: VM fault (0x04, vmid 1) at page 38904, read from CB (80)
    Aug 30 21:52:28 DCRIG kernel: radeon 0000:07:00.0: GPU fault detected: 146 0x0f225004
    Aug 30 21:52:28 DCRIG kernel: radeon 0000:07:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x000097F8
    Aug 30 21:52:28 DCRIG kernel: radeon 0000:07:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x02088004
    Aug 30 21:52:28 DCRIG kernel: VM fault (0x04, vmid 1) at page 38904, read from TC (136)
    As the message implies, it seems to occur when the kernel changes power states.  In use it does align, as the hard locks tend to occur most frequently in steam or if I encounter rich web content.  I'm beginning to suspect a hardware fault, but I'm going to try disabling DRM and test.
    Last edited by Devcon (2014-08-31 12:49:00)

  • Photoshop for phone and Photoshop CC issue's

    Photoshop CC can't open today psdx files (Photoshop Touch for phone generated files), while not recognize this file type.
    In principle, the app does not synchronize once all files correctly also, or there is a faulty synchronization.
    What's wrong, it takes long to resolve this issue?

    Please follow the steps from here  http://helpx.adobe.com/photoshop/kb/psdx-files-dont-open-photoshop.html<here...http://helpx.adobe.com/photoshop/kb/psdx-files-dont-open-photoshop.html>
    Guido

  • Anyone have Lion and Photoshop CS5 issues?

    I was using Photoshop CS successfully on my iMac (bought in 2008) until I upgraded from Snow Leopard to Lion and it stopped working.  I installed CS5, and it doesn't work well at all; when I try to open and work on an 800 MB file it freezes and sticks and I get the spinning ball continuously. I am currently 4GB RAM. CS5 works great on my husband's computer and he has the same amount of Ram, and he is still using Snow Leopard. I also use Wacom Intuos 3 but the same thing happens with my mouse . I don't know what to do to improve the performance of CS5. Any help would be appreciated. Thanks.

    See the response I made here:
    https://discussions.apple.com/message/16654674#16654674

  • Graphics Card and Photoshop (CS5) Issue - Please Help!

    This morning, I went to open a photo with Adobe CS5. It wouldn't open and it crashed (quit unexpectedly). After playing around a bit, I realized that I could fix it by disabling the OpenGL option under preferences. Thus, I think that it may have to do with my graphics card. I have a lat 2013 MacBook Pro with Retina display. The card that it has is a NVIDIA GeForce GT 650M card. Can anyone help me with this? I can leave the Open GL unchecked, but would really like to fix the problem if possible so that I can have full CS5 utility. Thank you!!!

    Hi Curt,
    Thank you so much for your reply, the info/advice you have given me is really helpful!!! I think its important that I also keep in mind what I might need to use it for in a couple of years time, which could be video editing and of course who knows what demands newer versions of PS, LR etc will put on the PC. I think I am going to have to bite the bullet and go for the PC that is pushing the absoulte limit of my budget (and a bit extra!) as then I have something with a spec I am not going to out grow for a reasonable period of time - so long as the computer does not give up on me first! The one I am looking at has 256GB mSATA SSD + 2TB SATA hard drive. It also has 16 GB ram.
    Thanks again, really apprecaite your help!
    Keri

  • Issues with Win 7 & CS2. Illustrator and Photoshop have "Stopped Working"

    Hi,  New to this so I apologize in advance.  Bought a new computer in December '09. 6gig quad processor and plenty of 500gigs of disc space. NOt a Memory Issue! Installed CS2 ( 'cause the computer took all of my money!)  and all worked fine until 4 days ago.  I mainly use illustrator and photoshop. When I tried to save a document... The programs simply "Stopped Working"  I'm a rookie with the tech stuff so please speak slowly and simply....  I would appreciate any help as I'm losing money and work right now!  Thanks

    CS2 is totally unsupported under Win 7. And if you have 6 gigs of RAM I'll guess that it's a 64 bit system which simply adds to the complexity.
    Sorry, but the best advice you'll get is to upgrade.
    Bob

  • Recently upgraded to a Canon Mark 3 and now having issues with my RAW files in Bridge and Photoshop. I am operating with CS4. Photoshop produces an error " Could not complete your request because photoshop does not recognize this type of file"

    Recently upgraded to a Canon Mark 3 and now having issues with my RAW files in Bridge and Photoshop. I have operating with CS4. Photoshop produces and error " Could not complete your request because photoshop does not recognize this type of file"

    Assuming you mean 5D Mark III, Photoshop CS4 cannot directly open raw files from your camera.
    Generally speaking, Adobe stopped updating older versions to be able to read raw files from newer cameras when they released a new major version of Photoshop. Photoshop CS4 is no longer receiving Camera Raw updates.
    You can double check this yourself:
    First you need to determine whether Adobe has released support for your new camera in your version of Photoshop. To do that, look at these two pages. You'll want to find out the earliest version of Camera Raw that can support your camera, then what version of Photoshop can run that version of Camera Raw.
    Camera Raw plug-in | Supported cameras
    Camera Raw-compatible Adobe applications
    If you find your camera is supported by your version of Photoshop, you need to download the latest update for Camera Raw. There's more information on how to do that here:
    Keeping Photoshop Up-To-Date
    If your version of Photoshop cannot support your camera, you can download and install the latest version of the free Adobe DNG Converter, which can take your raw files as input and put out DNG format files, which your version of Photoshop can open.
    Photoshop Help | Digital Negative (DNG)
    The DNG converter DOES work, but if you want maximal quality from your raw files (not to mention the convenience and ease of use of directly opening your raw files) you'll want the latest version of Photoshop. Adobe has made substantial improvements in raw conversion quality in recent years.
    -Noel

  • NEF files from Nikon d800 not visible in bridge and photoshop cs6- using mac ver.10.8.5. downloaded plugin from site 8.3 but issue unresolved

    NEF files from Nikon d800 not visible in bridge and photoshop cs6- using mac ver.10.8.5. downloaded plugin from site 8.3 but issue unresolved

    You can install and use Camera Raw 8.8 with OSX 10.8  Go to Help > Updates in Photoshop CS6

  • Images appear fine in Photoshop cs6 and cc, but print too dark, and also show too dark in Windows picture viewer. How can I correct this? Is this a Photoshop setting issue or what?

    Images appear fine in Photoshop cs6 and cc, but print too dark, and also show too dark in Windows picture viewer. How can I correct this? Is this a Photoshop setting issue or what?

    Ok, look at your files in Photoshop. What is the profile assigned to them? You can find this out by going to the Status bar at the bottom, clicking on the right-pointing triangle and choosing document Profile from the list.
    Then in Windows, go to your Control Panel > Color Management and add sRGB (if it isn't there) and select it as your default profile.
    I hope that will work.

  • Plug in Issue with Bridge and Photoshop

    When attempting to access Bridge in Photoshop (CS5 Extended) I received the following message: "Could not complete the browse in Bridge command because Photoshop was unable to find the JavaScript Plug-in".  I have never received this message when using Bridge.  I do not know how to access the plug in file.  I am not sure how to correct this issue.  Any help would be sincerely appreciated.  Thanks, DanOmaha
    OS Windows 7 (64), Photoshop CS5 Extended, V12.1, Lightroom 3,

    Can you open BRidge by clicking on bridge icon?
    In bridge if you click edit/preferene/startup scirpts do you have a check mark for bridge and photoshop?

  • Every since I updated to the latest Camera Raw and Photoshop I have the following issue: when I finish the photo in Raw and bring it into Photoshop I have white squares in the Photo. If I crop the photo the white square disappears until I zoom to enlarge

    Every since I updated to the latest Camera Raw and Photoshop I have the following issue: when I finish the photo in Raw and bring it into Photoshop I have white squares in the Photo. If I crop the photo the white square disappears until I zoom to enlarge it then the white square reappears. I do not believe the squares are saved

    Does turning off »Use Graphics Processor« in the Performance Preferences and restarting Photoshop have any bearing on the issue?
    Please read this (in particular the section titled "Supply pertinent information for quicker answers"):
    http://forums.adobe.com/docs/DOC-2325

  • Issues with Mavericks and Photoshop and Illustrator Cs6

    My illustrator cs6 and photoshop are unable to save documents, every time I try to save or save as the save window keeps disappearing. Occasionally I can save if I am really quick, but on average this is not an option,
    The same happens when I try and open something through either program, the open window disappears before I can click on anything.
    I can open psd or ai docs in finder but just not in the program.
    This has only happened since I installed Mavericks.
    any help?

    Same problem for me with CS5 so I downloaded the trial version of Photoshop CC--same problem again and Adobe does not know how to fix the issue.
    For a while holding down the shift key while opening Photoshop worked, then it failed yesterday. I'll try Alljeffedup's key combination solution.
    Current workaround is the Open With command in the finder.

  • NIK and Photoshop Issues

    I've had a need to use my various NIK software quite a bit more, than I normally do, and doing so has uncovered a ton of issues for me. I previously had these issues, but not to the same degree that I do now.
    My work flow is to import images into LR3 as RAW from a Canon (5D MkII or 40D), make minor adjustments in LR3, and then export to PS CS5 as 16-bit ProPhoto TIFFs. I normally start with Dfine, then on to Viveza2, and then Color Efex Pro, collapse my layers, save and return to LR3. I can usually repeat this process without any issues. Now, I'm finding that I can repeat this process maybe 2 or 3 times, before something goes wrong. By wrong I mean, I'll have to click multiple times on "Add Control Point" button in Viveza2, before I get the crosshair to drop the point. I frequently have to double or triple click in the location, just to be able to drop the point, otherwise it's "sticky" and follows the mouse, although I'm not holding the button down. Furthermore, once the point is dropped, if I click on a slider, it may not respond respond at all, or if it does respond, it's "sticky" in that I can't release it. At this point, I know that Photoshop needs to be quit and restarted. However, clicking on the "Cancel" or "OK" buttons, doesn't work, or if it does, there is a very long delay. I usually "Force Quit" Photoshop. I can reproduce these issues repeatedly in Viveza 2 and Silver Efex Pro. I don't recall having any issues with the other NIK software applications.
    I have had issues with Photoshop unexpected quitting as well, when I'm not in a NIK application. For instance, I may be using the Healing Brush or Clone Stamp, adjusting a Curve or something. I don't recall if I'd previously used a NIK product before the unexpected quit.
    To resolve these issues, I've run Apple's Disk Utility, checking for permission and disk related issues. I've also run DiskWarrior for the same issues, though none are found. I've removed the entire NIK suite of applications, uninstalled Photoshop and reinstalled it, as well as removing my mouse and Wacom drivers. The problem persist with just the Wacom software installed, without having the Razor Pro software installed.
    Using an iMac 27", with 8GB RAM, 10.6.5, and the most current versions of all other software and drivers.
    Ideas, thoughts, suggestions?

    I don't have a script as such -- but the installer cleanup tool helps after doing an uninstall.
    See http://www.adobe.com/support/contact/cs5clean.html
    And the initial release of Photoshop did have some bugs, which is why we put out 2 dot releases.
    And MacOS has had a few dot releases to fix bugs that were affecting Photoshop as well, and they still have more to go.

  • 27" iMac, ATI 5750, Bootcamp3.2 and the occasional black screen with XP SP3

    Wanted to share my experience with the subject setup and potentially save somebody a lot of time and frustration. My installation would occasionally work. Sometimes it would boot into a black screen and sometimes it would work perfectly. I tried a lot things:
    1. Deleting the bootcamp partition and clean install.
    2. Renaming AppleHFS.sys, etc to *.old.
    3. Downloading and installing some mobility graphic drivers from downloadatoz.com.
    4. Downloading and installing the desktop graphic drivers from amd.
    5. Using 7zip to unzip the bootcamp3.2.exe file and manually extracting and installing the graphic drivers.
    6. Following the directions from Apple support article TS3173.
    Everytime I thought it was fixed, the black screen would appear again. One of the comments I read on the forums really struck a chord with me. "XP is getting long in the tooth." So, I ditched my XP SP3 disc and bought an OEM, 64-bit disc of Win7 Professional. So far, this has worked perfectly with absolutely NO black screens (even during installation) on my 27" iMac with the ATI 5750 graphics card.
    Message was edited by: rc_sportpilot
    Message was edited by: rc_sportpilot

    So, a little update on the situation...
    I tried repairing the WinXP installation from the install CD and it did not solve the problem.
    Right now I'm trying to completely reinstall Windows XP (SP2 this time) and the Apple drivers to see where the problems start to appear (at WinXP SP2 install, at the SP3 install, at BootCamp 2.1 install,...)
    Also, something quite important I forgot to mention in my first post is that the problem appeared after cloning the BootCamp partition from another Mac (iMac 20" Alum) using Mike Bombich's NetRestore tool.
    If you have any suggestions, I would really appreciate it!
    thanks

  • Apple and ATI aware of iMac freezing issue

    Now they just need to figure out how to fix it.
    Here is a post from today by one of the Blizzard mac techs on the Mac Support forum of the World of Warcraft forums:
    There are at least two sides to customer support.
    One is, identifying issues that need to be fixed. In this case (ATI
    driver bug) that task is done. ATI and Apple are aware of the issue and
    working on it, I confirmed that with them today.
    Two is, finding a way to provide short term relief of the issue if at
    all possible.
    Since we can't make a driver update appear in seconds, bear with us if
    we make suggestions that may in fact improve stability for you until a
    more lasting fix is available.
    "

    wawalulu,
    If you can wait a few weeks for Apple and ATI to sort out the graphics driver problems, that might be your best bet. With any new model it does take Apple a couple months to iron out the glitches so when this happens, you will have a pretty solid Mac.
    I work supporting both Macs and PC's where the user base is in the thousands and I will tell you on the whole, Macs are definitely more trouble-free than PC's. However, I won't candy coat things like some of the posters on this forum. There WILL be issues that will crop up but usually Apple does the right thing and fixes them. Sending feedback and patience is the key. When the new Leopard OS (10.5) comes out this month, I guarantee there will be issues due to it's newness and lack of maturity. However, if Apple's past track record is any indication, it shouldn't have anywhere near the issues Windows Vista has. We won't even support Vista where I work because it's so troublesome!
    BTW, my 20" late 2006 iMac I use at work has been rock solid. This is because it's a revised version of the original intel iMac Apple released so most of the bugs were worked out. The G5 tower I had before that was perfect as well as the G4 and G3 towers I used before that. All of these Macs were at least second revision of their respective model lines. If memory serves, all of them has some teething pains in their first revisions.
    I have a new 20" aluminum iMac at home, breaking my cardinal rule to never buy the first revision of a new product and it does have the graphics freezing issue talked about in these threads but it's only happened twice. So, I knew full well what I was getting into and am patiently waiting for Apple to release an update and fix the issue. Why did it have to be so... darn... sexy?!
    I'll end this post on the following note: I use Macs at home precisely because I don't want to spend time fixing things... because I do that all day at work! If there was a better computer and OS out there, I'd be using it!
    Message was edited by: Martek

Maybe you are looking for

  • Low Resolution

    Have anyone notice the low quality pictures on there iPhone from time to using the safari browser and in some apps?

  • Hp2311x higher resolution with Acer Aspire TC-105

    Hello I have a new Acer Aspire TC-105 purchased, now do the following problem that my screen resolution can not be higher than 1366 x 768. In my previous PC had to choose. No problem for higher resolution I have the latest drivers geeinstalleerd, I g

  • Add a second blog summary widget?

    I couldn't find this discussion elsewhere. I have a site and want to add a second blog summary widget to my site. I want to add the bsw to my homepage and just show my latest single entry. Curious to know if anyone knows if you can add in a second bs

  • How/where to get more photo slideshows template/designs?

    I am trying to use iPhoto and iMovieHD to do some photo slide shows. Like to know where I can purchase/download more slideshow templates? Thanks

  • PDF maker stalls

    With Acrobat Pro 6 installed (and recently having downloaded a free Acrobat 9 Reader) any attempt to make a pdf stalls, process as follows: After starting the print process (and selecting "Adobe PDF"),  the horizontal 'progress graphic' simply freeze