A red horizontal line appear on my imac

2 days ago after i oke up, a red horizontal line appear at my iMac....try resetting still red line appear....any idead to to remove this?

Contact Apple Service, iMac Service or Apple's Express Lane. Do note that if you have AppleCare's protection plan and you're within 50 miles (80 KM) of an Apple repair station, you're eligible for onsite repair since yours is a desktop machine.

Similar Messages

Red horizontal lines appearing all over the screen accompanied with beeping

Today I had the weirdest of issues on my Macbook Pro (early-2011 13 inch core i5 hd 3000), while using Chrome, suddenly red horizontal lines appeared all over the screen with beeping sounds coming from the computer. I had to hard reset my macbook to make them go away. BTW I am on ML 10.8.2 and this is the second time I have had an issue after installing the updates, Digital Camera RAW update 4.04 and Airport utilitly 6.02. I have also installed the SMC update that was released earlier this month. A couple of days ago my macbook got stuck while shutting down and I had to close it manually and today this happened. Please tell me that this is not a hardware related issue because my warranty has expired

I ran the extended test and thankfully "No trouble was found" . Should I now report this to Apple Support, maybe there is a problem with the updates I have installed?
Here is the result of that test (the image uploading thingy inverted this image):

Hey recently there has been a turquoise/red horizontal line that appeared on my screen. i turned off my ipod but it appeared after about 5 minutes...what do i have to do to get rid of it?

recently there has been a turquoise/ red horizontal line that appeared on my screen. i turned my iPod off but the line appeared again after about 5 minutes...how do i get rid it?

Try the standard fixes:
- Reset. Nothing is lost
Reset iPod touch: Hold down the On/Off button and the Home button at the same time for at
least ten seconds, until the Apple logo appears.
- Restore from backup
- Restore to factory defaults/new iPod
If you still have the problem that indicates that you have a hardware porblem and an appointment at the Genius Bar of an Apple store.

Hp 2711x Monitor: Flickering red horizontal lines, dots, shapes

I'm not sure if I have two seperate problems or if they are the same problem. But lately my monitor has many red horizontal lines or red dots, or random red shapes on screen that flicker slightly. They only appear on parts of the screen that are dsplaying either black or any dark colors. Any part of the screen displaying white will have no lines at all. The problem will go away temporarily if I shut off the monitor for a while.
Also before it begins doing this, and during, the entire screen will go bank for about 1-2 seconds and then come back. It never gives an error message when it is blank. I run a dual monitor set up with my laptop display and the monitor and the lines only appear on the monitor, not the laptop display.
I have the most current drivers for the monitor installed.
The computer is a Clevo W110ER with i7 3630QM 2.4 Ghz and a 2 GB video card, running Windows 8.

Hi Blue07,
What is the model number of the monitor.
I worked on behalf of HP.

I7 MBP 8.2 AMD 6750M 2011 Crashes, Red Horizontal Lines, won't boots

Crash, horizontal red lines, won't boot, SMC PRAM reset, failed boots, successful boot cycles:
For about a week, I have been struggling with crashes, followed by red horizontal lines on the screen, and inability to boot into multi-user mode. It will boot into single user mode, with red stripes on black background. To get it to boot again I "shutdown -h now" from single user mode, SMC reset, PRAM reset 3 times, and attempt boots with <command> R two to three times unsuccessfully. Then, if I am lucky, when I do a boot into single-user mode (power, <command> S), it boots into single user mode with a black background and no stripes, then I "exit" to boot. If I am unlucky, the black screen will have red stripes or red snow in single-user mode. After several crashes, I also have to remove my hard drive, and do a disk repair and permission repair, while connected to a different mac, or format and restore ML. (I have two backups of my personal data.) The failed multi-user boots are terminated by grey or black screens of death, accompanied by heat and the fands running fast. The fans also run in single user mode without processor load if they red stripes are on the screen. A successful multi-user boot is cool without fans running. I didn't have any crashing problems before switching to ML recently.
Memtest fails in multi-user mode (but not single-user mode):
Running memtest on 8GB RAM in multi-user mode fails at a single address on the most significant byte (with 1 bit difference). However, memtest does not show a failure in single-user mode, nor with only a single 4GB module in multi-user mode.
Increased stability with gfxCardStatus and Flash unininstall:
Using gfxCardStatus Integrated Only mode, and uninstalling Flash, seems to help. However, I do get crashes or inability to wake up display which seems to be associated with processes like (google Chrome renderer) which forces gfxCardStatus out of "Integrated Only" mode. http://gfx.io/switching.html
Future plans:
I am in Mexico where RAM is outrageously expensive. So I will order RAM from the USA and try new 16 GB RAM because it is cheaper part swap than the logic board. It makes sense to try the cheap stuff first. I would rather switch to Linux and continue my bioinformatics work than pay and wait to replace the i7 logic board which warranty expired a few months ago. I refuse to hit it with a heatgun to reflow the BGA solder on the GPU. I really need the i7 data processing throughput I paid for.
Suggestions?
Does anyone understand the ambiguous memtest results?

I tested if my computer would hang, if I don't use the Mountain Lion GUI. I didn't log in on the GUI. I used ssh from my Mac Mini, to launch scripts while heavily load the i7 CPU while not logged on to the GUI. I woke up the screen a few time successfully. However Dec 30, early in the morning, the screen remained black and the login screen would not appear pressing a key. My ssh sessions were still working and I could continue to run scripts and load all the CPU cores verified by "top" on the command line. However, I could not ssh to my MacBook Pro!
     ssh [email protected]
     ssh: Could not resolve hostname hanalei.local: nodename nor servname provided, or not known
(Previously established SSH sessions continued to work, but new ones could not be started.)
I ran memtest afteward 4 times without failure while I went to sleep.
Looking at the console log, something killed authentication, which I assume disabled the ability to ssh into my MacBook Pro.
     Dec 30 02:26:00 hanalei com.apple.launchd[1] (com.apple.coreservices.appleid.authentication[318]) <Notice>: Exited: Killed: 9
There were also lots of GPU restarts.
     Dec 29 22:23:41 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
syslog -C | grep Killed
Dec 29 13:48:54 hanalei com.apple.launchd.peruser.503[137] (com.apple.mdworker.shared.04000000-0000-0000-0000-000000000000[295]) <Notice>: Exited: Killed: 9
Dec 29 15:27:59 hanalei com.apple.launchd.peruser.503[150] (com.apple.talagent[170]) <Notice>: Exited: Killed: 9
Dec 29 16:58:42 hanalei com.apple.launchd[1] (com.apple.metadata.mds.scan[294]) <Notice>: Exited: Killed: 9
Dec 30 02:26:00 hanalei com.apple.launchd[1] (com.apple.coreservices.appleid.authentication[318]) <Notice>: Exited: Killed: 9
Dec 30 02:26:01 hanalei com.apple.launchd[1] (com.apple.audio.SandboxHelper[210]) <Notice>: Exited: Killed: 9
Dec 30 02:26:01 hanalei com.apple.launchd[1] (com.apple.xpcd.CA000000-0000-0000-0000-000000000000[209]) <Notice>: Exited: Killed: 9
Dec 30 02:26:02 hanalei com.apple.launchd[1] (com.apple.xpcd.F7010000-0000-0000-0000-000000000000[186]) <Notice>: Exited: Killed: 9
Dec 30 02:26:02 hanalei com.apple.launchd.peruser.503[140] (com.apple.tccd[153]) <Notice>: Exited: Killed: 9
Dec 30 02:26:43 hanalei com.apple.launchd.peruser.503[140] (com.apple.cfprefsd.xpc.agent[148]) <Notice>: Exited: Killed: 9
Dec 30 02:26:44 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[31]) <Notice>: Exited: Killed: 9
Dec 30 02:29:35 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[14574]) <Notice>: Exited: Killed: 9
Dec 30 02:29:48 hanalei com.apple.launchd.peruser.503[140] (com.apple.cfprefsd.xpc.agent[14579]) <Notice>: Exited: Killed: 9
Dec 30 02:29:49 hanalei com.apple.launchd.peruser.503[140] (com.apple.distnoted.xpc.agent[144]) <Notice>: Exited: Killed: 9
Dec 30 02:29:50 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[14591]) <Notice>: Exited: Killed: 9
Dec 30 02:29:51 hanalei com.apple.launchd[1] (com.apple.cfprefsd.xpc.daemon[21]) <Notice>: Exited: Killed: 9
Dec 30 02:30:01 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[14595]) <Notice>: Exited: Killed: 9
Dec 30 02:30:14 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[14601]) <Notice>: Exited: Killed: 9
Dec 30 02:30:14 hanalei com.apple.launchd[1] (com.apple.cfprefsd.xpc.daemon[14598]) <Notice>: Exited: Killed: 9
Dec 30 02:30:38 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[14602]) <Notice>: Exited: Killed: 9
Dec 30 02:31:27 hanalei com.apple.launchd[1] (com.apple.cfprefsd.xpc.daemon[14611]) <Notice>: Exited: Killed: 9
Dec 30 03:15:05 hanalei com.apple.launchd.peruser.503[14604] (com.apple.cfprefsd.xpc.agent[14610]) <Notice>: Exited: Killed: 9
Dec 30 03:26:42 hanalei com.apple.launchd[1] (com.apple.cfprefsd.xpc.daemon[14615]) <Notice>: Exited: Killed: 9
Dec 30 03:26:43 hanalei com.apple.launchd.peruser.503[14604] (com.apple.distnoted.xpc.agent[14608]) <Notice>: Exited: Killed: 9
Dec 30 03:26:43 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[14606]) <Notice>: Exited: Killed: 9
Dec 30 03:46:06 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[14684]) <Notice>: Exited: Killed: 9
Dec 30 04:26:44 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[14690]) <Notice>: Exited: Killed: 9
Dec 30 04:26:45 hanalei com.apple.launchd[1] (com.apple.cfprefsd.xpc.daemon[14685]) <Notice>: Exited: Killed: 9
Dec 30 04:42:03 hanalei com.apple.launchd[1] (com.apple.cfprefsd.xpc.daemon[14699]) <Notice>: Exited: Killed: 9
Dec 30 04:55:58 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[14698]) <Notice>: Exited: Killed: 9
syslog -C
Dec 29 11:05:40 localhost com.apple.launchd[1] <Notice>: *** launchd[1] has started up. ***
Dec 29 11:05:40 localhost com.apple.launchd[1] <Notice>: *** Shutdown logging is enabled. ***
Dec 29 11:06:29 localhost com.apple.launchd[1] (com.apple.automountd) <Warning>: Unknown key for boolean: NSSupportsSuddenTermination
Dec 29 11:06:34 hanalei com.apple.launchd[1] (com.apple.bsd.dirhelper) <Notice>: Throttling respawn: Will start in 10 seconds
Dec 29 11:07:43 hanalei com.apple.launchd.peruser.503[209] (com.apple.gamed) <Warning>: Ignored this key: UserName
Dec 29 11:07:43 hanalei com.apple.launchd.peruser.503[209] (com.apple.gamed) <Warning>: Ignored this key: GroupName
Dec 29 11:07:43 hanalei.local distnoted[213] <Warning>: # distnote server agent absolute time: 124.947278009   civil time: Sat Dec 29 11:07:43 2012   pid: 213 uid: 503 root: no
Dec 29 11:08:43 hanalei com.apple.launchd.peruser.503[209] (com.apple.afpstat-qfa[299]) <Notice>: Job failed to exec(3). Setting up event to tell us when to try again: 2: No such file or directory
Dec 29 11:08:43 hanalei com.apple.launchd.peruser.503[209] (com.apple.afpstat-qfa[299]) <Notice>: Job failed to exec(3) for weird reason: 2
Dec 29 11:08:43 hanalei com.apple.launchd.peruser.503[209] (com.apple.mrt.uiagent[293]) <Error>: Exited with code: 255
Dec 29 11:09:03 hanalei com.apple.launchd.peruser.503[209] <Error>: Bug: 12C60: launchd + 112364 [7DCC9489-2DF5-3807-83FA-EF5666EE8078]: 0x1
--- last message repeated 5 times ---
Dec 29 13:17:09 localhost com.apple.launchd[1] <Notice>: *** launchd[1] has started up. ***
Dec 29 13:17:09 localhost com.apple.launchd[1] <Notice>: *** Shutdown logging is enabled. ***
Dec 29 13:17:38 localhost com.apple.launchd[1] (com.apple.automountd) <Warning>: Unknown key for boolean: NSSupportsSuddenTermination
Dec 29 13:18:40 hanalei com.apple.launchd.peruser.503[137] (com.apple.gamed) <Warning>: Ignored this key: UserName
Dec 29 13:18:40 hanalei com.apple.launchd.peruser.503[137] (com.apple.gamed) <Warning>: Ignored this key: GroupName
Dec 29 13:18:40 hanalei.local distnoted[141] <Warning>: # distnote server agent absolute time: 95.663712636   civil time: Sat Dec 29 13:18:40 2012   pid: 141 uid: 503 root: no
Dec 29 13:18:50 hanalei com.apple.launchd.peruser.503[137] <Error>: Bug: 12C60: launchd + 112364 [7DCC9489-2DF5-3807-83FA-EF5666EE8078]: 0x1
--- last message repeated 5 times ---
Dec 29 13:18:53 hanalei com.apple.launchd.peruser.503[137] (com.apple.afpstat-qfa[267]) <Notice>: Job failed to exec(3). Setting up event to tell us when to try again: 2: No such file or directory
Dec 29 13:18:53 hanalei com.apple.launchd.peruser.503[137] (com.apple.afpstat-qfa[267]) <Notice>: Job failed to exec(3) for weird reason: 2
Dec 29 13:18:53 hanalei com.apple.launchd.peruser.503[137] (com.apple.mrt.uiagent[261]) <Error>: Exited with code: 255
Dec 29 13:39:25 hanalei com.apple.launchd.peruser.503[137] (com.apple.NetworkDiagnostics[388]) <Warning>: Check-in of Mach service failed. Already active: com.apple.NetworkDiagnostic.agent
Dec 29 13:42:21 hanalei.local spindump[403] <Notice>: Saved hang report for Mail version 6.2 (1499) to /Library/Logs/DiagnosticReports/Mail_2012-12-29-134221_hanalei.hang
Dec 29 13:48:54 hanalei com.apple.launchd.peruser.503[137] ([0x0-0x16016].com.apple.AppleSpell[277]) <Notice>: Exited: Terminated: 15
Dec 29 13:48:54 hanalei com.apple.launchd.peruser.503[137] (com.apple.mdworker.shared.04000000-0000-0000-0000-000000000000[295]) <Notice>: Exited: Killed: 9
Dec 29 14:29:38 localhost com.apple.launchd[1] <Notice>: *** launchd[1] has started up. ***
Dec 29 14:29:38 localhost com.apple.launchd[1] <Notice>: *** Shutdown logging is enabled. ***
Dec 29 14:29:49 localhost com.apple.launchd[1] (com.apple.automountd) <Warning>: Unknown key for boolean: NSSupportsSuddenTermination
Dec 29 14:32:05 hanalei.local distnoted[118] <Warning>: # distnote server agent absolute time: 155.593274130   civil time: Sat Dec 29 14:32:05 2012   pid: 118 uid: 503 root: no
Dec 29 15:21:29 localhost com.apple.launchd[1] <Notice>: *** launchd[1] has started up. ***
Dec 29 15:21:29 localhost com.apple.launchd[1] <Notice>: *** Shutdown logging is enabled. ***
Dec 29 15:21:40 localhost com.apple.launchd[1] (com.apple.automountd) <Warning>: Unknown key for boolean: NSSupportsSuddenTermination
Dec 29 15:22:23 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
Dec 29 15:22:28 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 4 seconds
Dec 29 15:22:33 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
Dec 29 15:22:34 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 8 seconds
Dec 29 15:22:40 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 2 seconds
Dec 29 15:22:43 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
Dec 29 15:22:46 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 6 seconds
Dec 29 15:22:53 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
Dec 29 15:22:58 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 4 seconds
--- last message repeated 6 times ---
Dec 29 15:23:04 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
Dec 29 15:23:20 hanalei com.apple.launchd.peruser.503[150] (com.apple.gamed) <Warning>: Ignored this key: UserName
Dec 29 15:23:20 hanalei com.apple.launchd.peruser.503[150] (com.apple.gamed) <Warning>: Ignored this key: GroupName
Dec 29 15:23:20 hanalei.local distnoted[154] <Warning>: # distnote server agent absolute time: 114.027753124   civil time: Sat Dec 29 15:23:20 2012   pid: 154 uid: 503 root: no
Dec 29 15:23:28 hanalei com.apple.launchd.peruser.503[150] <Error>: Bug: 12C60: launchd + 112364 [7DCC9489-2DF5-3807-83FA-EF5666EE8078]: 0x1
--- last message repeated 5 times ---
Dec 29 15:23:33 hanalei com.apple.launchd.peruser.503[150] (com.apple.afpstat-qfa[285]) <Notice>: Job failed to exec(3). Setting up event to tell us when to try again: 2: No such file or directory
Dec 29 15:23:33 hanalei com.apple.launchd.peruser.503[150] (com.apple.afpstat-qfa[285]) <Notice>: Job failed to exec(3) for weird reason: 2
Dec 29 15:23:33 hanalei com.apple.launchd.peruser.503[150] (com.apple.mrt.uiagent[278]) <Error>: Exited with code: 255
Dec 29 15:23:46 hanalei com.apple.launchd.peruser.503[150] (com.apple.NetworkDiagnostics[297]) <Warning>: Check-in of Mach service failed. Already active: com.apple.NetworkDiagnostic.agent
Dec 29 15:25:53 hanalei com.apple.launchd.peruser.503[150] (com.apple.NetworkDiagnostics[335]) <Warning>: Check-in of Mach service failed. Already active: com.apple.NetworkDiagnostic.agent
Dec 29 15:27:59 hanalei com.apple.launchd.peruser.503[150] (com.apple.talagent[170]) <Notice>: Exited: Killed: 9
Dec 29 15:35:00 hanalei com.apple.launchd.peruser.503[150] (com.apple.gamed) <Warning>: Ignored this key: UserName
Dec 29 15:35:00 hanalei com.apple.launchd.peruser.503[150] (com.apple.gamed) <Warning>: Ignored this key: GroupName
Dec 29 15:35:27 hanalei com.apple.launchd.peruser.503[150] <Error>: Bug: 12C60: launchd + 112364 [7DCC9489-2DF5-3807-83FA-EF5666EE8078]: 0x1
--- last message repeated 2 times ---
Dec 29 15:35:27 hanalei com.apple.launchd.peruser.503[150] (com.apple.afpstat-qfa[482]) <Notice>: Job failed to exec(3). Setting up event to tell us when to try again: 2: No such file or directory
Dec 29 15:35:27 hanalei com.apple.launchd.peruser.503[150] (com.apple.afpstat-qfa[482]) <Notice>: Job failed to exec(3) for weird reason: 2
Dec 29 15:35:28 hanalei com.apple.launchd.peruser.503[150] <Error>: Bug: 12C60: launchd + 112364 [7DCC9489-2DF5-3807-83FA-EF5666EE8078]: 0x1
--- last message repeated 3 times ---
Dec 29 15:35:28 hanalei com.apple.launchd.peruser.503[150] (com.apple.mrt.uiagent[475]) <Error>: Exited with code: 255
Dec 29 15:35:46 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 4 seconds
Dec 29 15:35:51 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
Dec 29 15:35:52 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 8 seconds
Dec 29 15:35:58 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 2 seconds
--- last message repeated 1 time ---
Dec 29 15:45:55 localhost com.apple.launchd[1] <Notice>: *** launchd[1] has started up. ***
Dec 29 15:45:55 localhost com.apple.launchd[1] <Notice>: *** Shutdown logging is enabled. ***
Dec 29 15:46:06 localhost com.apple.launchd[1] (com.apple.automountd) <Warning>: Unknown key for boolean: NSSupportsSuddenTermination
Dec 29 15:48:21 hanalei.local distnoted[147] <Warning>: # distnote server agent absolute time: 149.513792853   civil time: Sat Dec 29 15:48:21 2012   pid: 147 uid: 503 root: no
Dec 29 16:42:52 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
Dec 29 16:42:57 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 4 seconds
Dec 29 16:43:02 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
Dec 29 16:43:03 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 8 seconds
--- last message repeated 1 time ---
Dec 29 16:43:09 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 2 seconds
Dec 29 16:43:12 hanalei com.apple.launchd.peruser.503[144] (com.apple.gamed) <Warning>: Ignored this key: UserName
Dec 29 16:43:12 hanalei com.apple.launchd.peruser.503[144] (com.apple.gamed) <Warning>: Ignored this key: GroupName
Dec 29 16:43:24 hanalei com.apple.launchd.peruser.503[144] <Error>: Bug: 12C60: launchd + 112364 [7DCC9489-2DF5-3807-83FA-EF5666EE8078]: 0x1
--- last message repeated 5 times ---
Dec 29 16:44:12 hanalei com.apple.launchd.peruser.503[144] (com.apple.afpstat-qfa[311]) <Notice>: Job failed to exec(3). Setting up event to tell us when to try again: 2: No such file or directory
Dec 29 16:44:12 hanalei com.apple.launchd.peruser.503[144] (com.apple.afpstat-qfa[311]) <Notice>: Job failed to exec(3) for weird reason: 2
Dec 29 16:44:12 hanalei com.apple.launchd.peruser.503[144] (com.apple.mrt.uiagent[304]) <Error>: Exited with code: 255
Dec 29 16:44:29 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 4 seconds
Dec 29 16:44:34 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
Dec 29 16:44:35 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 8 seconds
Dec 29 16:44:41 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 2 seconds
--- last message repeated 1 time ---
Dec 29 16:55:35 localhost com.apple.launchd[1] <Notice>: *** launchd[1] has started up. ***
Dec 29 16:55:35 localhost com.apple.launchd[1] <Notice>: *** Shutdown logging is enabled. ***
Dec 29 16:55:45 localhost com.apple.launchd[1] (com.apple.automountd) <Warning>: Unknown key for boolean: NSSupportsSuddenTermination
Dec 29 16:56:21 hanalei com.apple.launchd.peruser.503[140] (com.apple.gamed) <Warning>: Ignored this key: UserName
Dec 29 16:56:21 hanalei com.apple.launchd.peruser.503[140] (com.apple.gamed) <Warning>: Ignored this key: GroupName
Dec 29 16:56:21 hanalei.local distnoted[144] <Warning>: # distnote server agent absolute time: 47.520354484   civil time: Sat Dec 29 16:56:21 2012   pid: 144 uid: 503 root: no
Dec 29 16:57:09 hanalei com.apple.launchd.peruser.503[140] <Error>: Bug: 12C60: launchd + 112364 [7DCC9489-2DF5-3807-83FA-EF5666EE8078]: 0x1
--- last message repeated 4 times ---
Dec 29 16:57:14 hanalei com.apple.launchd.peruser.503[140] (com.apple.afpstat-qfa[272]) <Notice>: Job failed to exec(3). Setting up event to tell us when to try again: 2: No such file or directory
Dec 29 16:57:14 hanalei com.apple.launchd.peruser.503[140] (com.apple.afpstat-qfa[272]) <Notice>: Job failed to exec(3) for weird reason: 2
Dec 29 16:57:15 hanalei com.apple.launchd.peruser.503[140] <Error>: Bug: 12C60: launchd + 112364 [7DCC9489-2DF5-3807-83FA-EF5666EE8078]: 0x1
Dec 29 16:57:15 hanalei com.apple.launchd.peruser.503[140] (com.apple.mrt.uiagent[265]) <Error>: Exited with code: 255
Dec 29 16:58:42 hanalei com.apple.launchd.peruser.503[140] ([0x0-0x19019].com.apple.AppleSpell[289]) <Notice>: Exited: Terminated: 15
Dec 29 16:58:42 hanalei com.apple.launchd[1] (com.apple.metadata.mds.scan[294]) <Notice>: Exited: Killed: 9
Dec 29 16:59:35 hanalei com.apple.launchd.peruser.503[140] <Error>: Bug: 12C60: launchd + 112364 [7DCC9489-2DF5-3807-83FA-EF5666EE8078]: 0x1
--- last message repeated 2 times ---
Dec 29 19:13:33 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
Dec 29 19:13:38 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 4 seconds
Dec 29 19:13:43 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
Dec 29 19:13:44 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 8 seconds
--- last message repeated 1 time ---
Dec 29 19:13:50 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 2 seconds
Dec 29 20:14:05 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
Dec 29 20:14:10 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 4 seconds
Dec 29 20:14:15 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
Dec 29 20:14:16 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 8 seconds
--- last message repeated 2 times ---
Dec 29 20:14:22 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 2 seconds
Dec 29 21:16:12 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
Dec 29 21:16:17 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 4 seconds
Dec 29 21:16:22 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
Dec 29 21:16:23 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 8 seconds
--- last message repeated 1 time ---
Dec 29 21:16:29 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 2 seconds
Dec 29 22:23:41 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
Dec 29 22:23:46 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 4 seconds
Dec 29 22:23:51 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
Dec 29 22:23:52 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 8 seconds
--- last message repeated 2 times ---
Dec 29 22:23:58 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 2 seconds
Dec 29 22:24:56 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
Dec 29 22:25:01 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 4 seconds
Dec 29 22:25:06 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
Dec 29 22:25:07 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 8 seconds
--- last message repeated 1 time ---
Dec 29 22:25:13 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 2 seconds
Dec 29 22:26:11 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
Dec 29 22:26:16 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 4 seconds
Dec 29 22:26:21 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
Dec 29 22:26:22 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 8 seconds
--- last message repeated 2 times ---
Dec 29 22:26:28 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 2 seconds
Dec 29 22:27:26 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
Dec 29 22:27:31 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 4 seconds
Dec 29 22:27:36 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
Dec 29 22:27:37 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 8 seconds
--- last message repeated 1 time ---
Dec 29 22:27:43 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 2 seconds
Dec 29 22:28:42 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
Dec 29 22:28:46 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 4 seconds
Dec 29 22:28:52 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
Dec 29 22:28:52 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 8 seconds
--- last message repeated 1 time ---
Dec 29 22:28:59 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 2 seconds
Dec 29 22:29:57 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
Dec 29 22:30:01 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 4 seconds
Dec 29 22:30:07 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
Dec 29 22:30:07 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 8 seconds
--- last message repeated 1 time ---
Dec 29 22:30:13 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 2 seconds
Dec 29 22:31:12 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
Dec 29 22:31:16 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 4 seconds
Dec 29 22:31:22 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
Dec 29 22:31:22 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 8 seconds
--- last message repeated 1 time ---
Dec 29 22:31:29 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 2 seconds
Dec 29 22:32:27 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
Dec 29 22:32:32 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 4 seconds
Dec 29 22:32:37 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
Dec 29 22:32:38 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 8 seconds
--- last message repeated 1 time ---
Dec 29 22:32:44 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 2 seconds
Dec 29 22:33:42 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
Dec 29 22:33:47 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 4 seconds
Dec 29 22:33:52 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
Dec 29 22:33:53 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 8 seconds
--- last message repeated 1 time ---
Dec 29 22:33:59 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 2 seconds
Dec 29 23:17:28 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
Dec 29 23:17:33 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 4 seconds
Dec 29 23:17:38 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 9 seconds
Dec 29 23:17:39 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 8 seconds
--- last message repeated 1 time ---
Dec 29 23:17:45 hanalei com.apple.launchd[1] (com.apple.DumpGPURestart) <Notice>: Throttling respawn: Will start in 2 seconds
Dec 30 02:24:01 hanalei com.apple.launchd.peruser.503[140] <Error>: Bug: 12C60: launchd + 112364 [7DCC9489-2DF5-3807-83FA-EF5666EE8078]: 0x1
Dec 30 02:26:00 hanalei com.apple.launchd[1] (com.apple.coreservices.appleid.authentication[318]) <Notice>: Exited: Killed: 9
Dec 30 02:26:01 hanalei com.apple.launchd[1] (com.apple.audio.SandboxHelper[210]) <Notice>: Exited: Killed: 9
Dec 30 02:26:01 hanalei com.apple.launchd[1] (com.apple.xpcd.CA000000-0000-0000-0000-000000000000[209]) <Notice>: Exited: Killed: 9
Dec 30 02:26:02 hanalei com.apple.launchd[1] (com.apple.xpcd.F7010000-0000-0000-0000-000000000000[186]) <Notice>: Exited: Killed: 9
Dec 30 02:26:02 hanalei com.apple.launchd.peruser.503[140] (com.apple.tccd[153]) <Notice>: Exited: Killed: 9
Dec 30 02:26:43 hanalei com.apple.launchd.peruser.503[140] (com.apple.cfprefsd.xpc.agent[148]) <Notice>: Exited: Killed: 9
Dec 30 02:26:44 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[31]) <Notice>: Exited: Killed: 9
Dec 30 02:29:35 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[14574]) <Notice>: Exited: Killed: 9
Dec 30 02:29:48 hanalei com.apple.launchd.peruser.503[140] (com.apple.cfprefsd.xpc.agent[14579]) <Notice>: Exited: Killed: 9
Dec 30 02:29:49 hanalei com.apple.launchd.peruser.503[140] (com.apple.distnoted.xpc.agent[144]) <Notice>: Exited: Killed: 9
Dec 30 02:29:50 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[14591]) <Notice>: Exited: Killed: 9
Dec 30 02:29:51 hanalei com.apple.launchd[1] (com.apple.cfprefsd.xpc.daemon[21]) <Notice>: Exited: Killed: 9
Dec 30 02:30:01 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[14595]) <Notice>: Exited: Killed: 9
Dec 30 02:30:14 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[14601]) <Notice>: Exited: Killed: 9
Dec 30 02:30:14 hanalei com.apple.launchd[1] (com.apple.cfprefsd.xpc.daemon[14598]) <Notice>: Exited: Killed: 9
Dec 30 02:30:38 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[14602]) <Notice>: Exited: Killed: 9
Dec 30 02:30:39 hanalei.local distnoted[14608] <Warning>: # distnote server agent absolute time: 18252.455382446   civil time: Sun Dec 30 02:30:39 2012   pid: 14608 uid: 503 root: no
Dec 30 02:31:27 hanalei com.apple.launchd[1] (com.apple.cfprefsd.xpc.daemon[14611]) <Notice>: Exited: Killed: 9
Dec 30 03:15:05 hanalei com.apple.launchd.peruser.503[14604] (com.apple.cfprefsd.xpc.agent[14610]) <Notice>: Exited: Killed: 9
Dec 30 03:26:42 hanalei com.apple.launchd[1] (com.apple.cfprefsd.xpc.daemon[14615]) <Notice>: Exited: Killed: 9
Dec 30 03:26:43 hanalei com.apple.launchd.peruser.503[14604] (com.apple.distnoted.xpc.agent[14608]) <Notice>: Exited: Killed: 9
Dec 30 03:26:43 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[14606]) <Notice>: Exited: Killed: 9
Dec 30 03:46:06 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[14684]) <Notice>: Exited: Killed: 9
Dec 30 04:26:44 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[14690]) <Notice>: Exited: Killed: 9
Dec 30 04:26:45 hanalei com.apple.launchd[1] (com.apple.cfprefsd.xpc.daemon[14685]) <Notice>: Exited: Killed: 9
Dec 30 04:42:03 hanalei com.apple.launchd[1] (com.apple.cfprefsd.xpc.daemon[14699]) <Notice>: Exited: Killed: 9
Dec 30 04:55:58 hanalei com.apple.launchd[1] (com.apple.sleepservicesd[14698]) <Notice>: Exited: Killed: 9
Dec 30 10:00:37 hanalei.local distnoted[14778] <Warning>: # distnote server agent absolute time: 45252.245296175   civil time: Sun Dec 30 10:00:37 2012   pid: 14778 uid: 503 root: no

Horizontal lines appear in various programs on macbook pro that gets very hot.

Model Name:
MacBook Pro
Model Identifier:
MacBookPro1,2
Processor Name:
Intel Core Duo
Processor Speed:
2.16 GHz
Number Of Processors:
1
Total Number Of Cores:
2
L2 Cache:
2 MB
Memory:
2 GB
Bus Speed:
667 MHz
Boot ROM Version:
MBP12.0061.B03
SMC Version (system):
1.5f10
Serial Number (system):
W86241X4TJ1
Hardware UUID:
00000000-0000-1000-8000-0016CB902C12
Sudden Motion Sensor:
State:
Enabled
thin horizontal lines appear occasionally across window of firefox, if i switch to finder, not there. appears to stay with windows of different programs.
lately above the keyboard along back edge in the middle under monitor gets very hot almost to hot to touch, uncomfortable on lap.
i have no idea what the memory cards are. some have suggested i should replace memory cards?

I don't really know about the new models as far as typical operating temperatures. The ones you mention are not meaningfully high to me. My 2011 13" MBP with an i5 CPU typically idles near 50º C.
As for the speed issue that is hard to evaluate on the basis of personal opinion. You can download and run GeekBench benchmarks and compare the results to those reported for the same model configuration. You can use CineBench to benchmark video performance.

IPhoto '11: Horizontal lines appear across photo printed on card stock; don't appear on drafts printed on paper. How to get rid of them?

iPhoto '11: Horizontal lines appear on photo printed on card stock; don't appear on photos printed on paper or other card stock. How to get rid of them?

Horizontal lines appear on photo printed on card stock; don't appear on photos printed on paper or other card stock.
What's the difference between the first card stock and the other card stock? What's the finish on the problem card stock? What printer are you using? Does is have a physical adjustment for different stock thicknesses?

I have the new ipad and when I stretch the screen a horizontal line appears when I scroll whatever page or location I am on. The line is not there if the screen is minimised. Any solutions?

I have the new ipad and when I stretch the screen a horizontal line appears when I scroll whatever page or location I am on. The line is not there if the screen is minimised. Any solutions?

I can't personally as I never really liked nor used the picture frame feature in iPad. Just search in the App Store and read customer reviews and you'll likely find something you'll like.

Red dotted line appear on the screen

There is a red dotted horizontal line will occasionally appear on the playbook's screen while I'm browse the web. It will stay there for from seconds to minutes. That only appear with the browser app and happen once on the Pictures app. Seems like a software problems? Or hardware( stuck pixies)?
Anyone gets clue about what is this thing about?
Updated: Just found out there are blue dotted line as well.

Hi Byron,
I am creating an application that could possibly identify and fix your issue. Based on the pictures, it could be one of three things
Dead Pixels
Misbehaving Pixels
Hardware/Screen defect
The app will try to solve 1 & 2 by cycling through all the pixels using an algorithm I made. Hopefully this will fix.
Cheers

Horizontal Lines appear in random spots on display

Hey everyone.
Recently, my white iMac has been locking up a lot lately (forcing me to hard-reset, boo) and horizontal lines have been appearing. It freezes most often during more graphically-intense applications like games and Pro Tools. It's not the regular Mac freeze, where the grey dialogue box politely and multi-ligual-ly informs you that you need to reset. When my computer freezes, things just lock up, or the screen will go black.
I thought since I had not done a whole lot of computer maintenance since I bought it, there was a possibility it was just a horrible software glitch.
So I zero'd my hard drive and reformatted. Almost immediately the lines returned. Interestingly enough, I don't need a digital camera because these awful lines can get captured by screenshots.
The lines are typically pinkish or black, but if you look close, the individual pixels in the lines seem to be coloured arbitrarily. If the lines appear on a window, I can drag it around and the lines will follow. If I resize the window, the lines disappear.
Here's a screenshot. Note how the lines only affect the one window, and do not span the entire screen.
http://img161.imagevenue.com/img.php?image=29918lines_122708lo.jpg
These lines aren't bound to a particular window, just the desktop as a whole.
http://img142.imagevenue.com/img.php?image=45631lines2_1221119lo.jpg
How are these things getting captured on screenshot if I just reformatted my computer?
If it's not a software error, could a worn-out graphics card produce odd artifacts that are screen-capture-able? Apple ships hardware that can't last 2 years? Am I going to get shafted if I try to call them? Is there possibly a fix for this?
Thank you everyone for taking the time to read my post, and thanks in advance if you have some advice or want to express that you share the same issues.

Just to add a few comments to this thread, I had similar problems (green dots appearing at random locations on the display, lines, then corrupted icons graphics / text, and eventually computer lock-ups that required a power/hard reset).
It took me weeks to realize that heat was the root cause of these display artifacts / computer lock-ups. I had run zillions of memory tests, ran the Apple Diagnostic so many times, tried TechTool Pro, and I never ever got reported with a single error by any of these tools. I swapped RAM, disconnected all external Firewire / USB devices, tried different versions of Tiger / Leopard, to eventually conclude it had to be something else...
... and then it struck me one evening this week. I realized that I was now using my Mac Mini to transcode video (a task that I used to perform with my iMac, but that I stopped to use as a transcoding device as this would eventually lead to the symptoms described above), and that the Mac Mini's fan would increase in speed when the CPU would get loaded. It is then that I realized that I had never heard my iMac's fan change in pitch... with the exception of when I was running the Apple Diagnostic tool !!!
Gotcha !
I also downloaded the latest version of smcFanControl, and changing the fan settings to 1200 (ODD), 2200 (HDD), 2000 (CPU) fixed all the symptoms.
I submitted a bug report to Apple about this, as I consider this is a major issue. I have seen the temperature of the power supply reach 80+ Celsius. Water boils at 100 Celsius. That is hot, way too hot.
I hope Apple will fix this issue ASAP through a SMC firmware update as fans control is meant to be automated.
Just my 0.02$CAD.

Horizontal line appearing on the Mac Book Pro 13" Retina Display

I RECENTLY BOUGHT A 13"RETINA DISPLAY MACBOOK PRO. IT IS SO DISAPPOINTING. THERE IS A HORIZONTAL LINE THAT APPEARS ON THE SCREEN AND DISAPPEARS. THIS WAS FOR THE THIRD TIME I HAD TO FACE THE SAME ISSUE. WHEN I EXPLAIN TO THE STAFF AT THE APPLE STORE THEY SAY THAT THEY HAVE NOT COME ACROSS SUCH ISSUE, FOR WHICH I SHOWED A PROOF FROM THE OTHER PART OF THE WORLD. VERY DISAPPOINTED.APOLOGIES TO WRITE IN THE UPPER CASE.BUT IT IS FRUSTRATING WHEN YOU HAVE A LOT OF EXPECTATIONS FROM APPLE LAPTOPS.

Thanks. But What at the most they can do. They are going to tell me to take the laptop to the apple store.

Horizontal lines appear in grab acquision after a while

Hello everyone,
My system is using 4 cameras. this system worked for about 3 years and never had a problem with this. But now, When I start my process for less than an hour, I start to see horizontal lines in my acquisition image. Even when I close all my VI, this also happen in MAX.
For the Xmas holiday's, I've turn all the system off. When I started everything back, My PXI chassis wasn't in MAX. So I've finally figured out that I had to open the PXI chassis before opening the computer. But, by doing that, I've lost some seting that I've manage to recover from backups.
Is there a seting in MAX that could do this? A seting that could have a link with the image buffer?
I'm also getting errors about the IMAQ acquisition that I never had before like "IMG_ERR_TIM0"
Thank you for your help.
Solved!
Go to Solution.

iRish wrote:
Coolaid,
I am a little bit confused, but if you can clarify my comments below, I will do my best to help you.
What I understand is that you have a PXI 1000b, and a 1409 in it. You have 4 cameras connected to it and it was working fine for quite some time. Now you see horizontal lines in the acquistion image if your application is running less than an hour? You powered down the PXI Chassis over the Xmas break, and your settings were lost.
To start with, your PXI device has to be powered on before you turn on your computer as it sends signals to your PC, which is what allows it to be seen in Measurement & Automation Explorer (MAX). Your settings should be saved when you power down the device, so I am surprised that you lost some of them. Did you perhaps make some changes to the device settings and not remember to save them before powering down?
Also, which versions of LabVIEW and NI-IMAQ are you using? Which Cameras do you have? What operating system?
You mention that you see a horizontal line across your acquisition image in MAX and LabVIEW. Does this only show up in the active capture window or also in the images you save to your hard drive. Do the lines go away after your system is running for more than 1 hour?
Hello,
Sorry for the confusion.
Here's my configuration.
Labview 6.1
Windows 2000
NI-IMAQ 2.5.1
4 cameras JAI CV-A60
You are right, my PXi-1409 is in my PXI 1000b. When I've started everything and noticed that MAX didn't saw my PXI-1000b, I've search in this forum and found the same solution that you gave me. It worked but my motion settings wasn't the good one. I've finally manage to found the right setting. I didn't touch the setting of the cameras because it was working right when I've tried in MAX.
Just to let you in the context, the cameras are used to do fiber optic inspection. I've got 5 points in my process that I do the inspection of the fiber. There's 3 places in my process that I acquire (grab) the image process it live. I beleive that in that case, the images are store in a buffer. The other inspections only take pictures (snap) and analyse it. It seams that my problems only occure when I acquire the image. I can then see this in MAX. When I take a picture by "snap" the picture is ok. But I take pictures by "grab" I can see the horizontal bars. It's like if I have a TV that the horizontal sync need adjustment. My VI's cannot analyse thoses images so I restart the computer then.
It happen about 30-45min after I've start my vi to produce. I should be able to send you a picture of what's happening today.
Hope that it will help you to help me .
Do you have a book that you suggest to me that could help me have a better understanding of camera acquisition?
Thank you for your time.
Coolaid

6310 horizontal line appears when copying

Officejet 6310 all in one when I try to copy the page the copied page has 3 horizontal lines going right through the centre of the page one wider than the other two lines. What can I do. Also I am trying to print on a thicker page which I have previously done before and the paper doesnt go through the printer is printing but the paper has only moved slighting into the printer.

Just in case a potective plastic film is still on the lense ...

Why am I seeing a thin white horizontal line on my 27" iMac?

Why am I seeing a thin white horizontal line across the center of my monito?

Obvious suspects are the monitor itself or the video card.
Boot in safe mode and see if the line is still there (just to see what happens when quarts extreme isn't running).

Nasty horizontal line appeared on display

My MBA has suddenyl developed a nasty horizontal line right across the display. Looks about a pixel in thickness.
Any thoughts please?

Took it into a Genius and they're replacing the screen for free. No quibbles at all. And its 2 years old. And its not in warranty! And I get the loose hinge issue solved at the same time!
Happy bloke...

A red horizontal line appear on my imac

Similar Messages

Maybe you are looking for