Time of Day Timecode Capture

Hi,
I am trying to capture (from tape) footage that was shot with Time of Day timecode (Panasonic DVCPro HD tapes). There are two cameras (multicam) and the timecode needs to sync between the two.
Now, the issue I'm having is capture.  The timecode seems to be rewritten after capture. The starting TC is correct but as the tape moves through different times of day it loses the original timecode and just keeps on going with more of a 'record run' timecode instead of the timecode from the deck.
Normally this wouldn't be a problem if I had no synce issues but I need to sync these two cameras together.  Plus I have about 10 hours of footage and there's no time to manually go through each tape to log.
Any ideas, help, comments, etc?

Yes, that is a method, and we've done that before - this is also a great way to do music videos where you need the TC of the tune.
But since I'm the editor on this project and the camera crew have chosen TOD timecode to ensure sync on all cameras I have to live with this. Each tape can and does have a multitude of 'broken' timecodes. What I am hoping for is to have Premiere CS5 capture the original timecode from the deck.
In my old Avid days we could have it capture across TC breaks where it would just start the next clip at the TC break. Plus we could have the deck use Control Track to do the pre roll but still use the TC from the deck on the capture. 99% of the time it worked perfectly (the other 1% problem was when there was an actual blank spot between the takes - like if they removed the tape or watched an earlier take, and then cued past the last recorded image).
I am using the AJ LHi card and there is no such option.

Similar Messages

  • OS X freezes few times per day

    Hello. I've a problem with my Macbook Pro Retina 15". Few times per day system freeze. After freeze and manual reboot (power button) sometimes system have a problem with boot (i need turn on and off few times). Now i check in logs when i open Diablo 3 and have something like this:
    24.07.2014 17:56:59,158 WindowServer[135]: CGXMuxCapture: Starting
    24.07.2014 17:56:59,158 WindowServer[135]: CGXMuxCapture: Acquired
    24.07.2014 17:56:59,159 WindowServer[135]: Display 0x4280642 captured by conn 0x1cc8f
    24.07.2014 17:56:59,202 Diablo III[28354]: *** WARNING: Method convertPointFromBase: in class NSView is deprecated on 10.7 and later. It should not be used in new applications.
    24.07.2014 17:56:59,394 Diablo III[28354]: *** WARNING: Method convertRectToBase: in class NSView is deprecated on 10.7 and later. It should not be used in new applications.
    24.07.2014 17:57:31,000 kernel[0]: NVDA(OpenGL): Channel exception! Exception type = 0x8 DMA Engine Error (FIFO Error 8)
    24.07.2014 17:57:31,000 kernel[0]: 4443564e 00000118 88c93bc5 01f794e7 00000001 00000014 d3793533 46d3a4a6
    24.07.2014 17:57:31,000 kernel[0]: 4614f297 e71edccf 00088301 000000e1 12f2500a 081d0a4d 1002a0ad 20001801
    24.07.2014 17:57:31,000 kernel[0]: 30002800 02803800 0c828040 00500048 00601258 01080d22 808e8010 81042202
    24.07.2014 17:57:31,000 kernel[0]: 22188093 1001080d 02808a84 9c820422 0e2268b4 84100108 22028180 80a6b805
    24.07.2014 17:57:31,000 kernel[0]: 030a0880 0a00149a 1f138222 41100008 81200218 9b862808 5000480c 60015802
    24.07.2014 17:57:31,000 kernel[0]: 78007064 01019000 0a000198 00138a03 13923d0a 24380a3a 0e000000 01000000
    24.07.2014 17:57:31,000 kernel[0]: 490000e0 0100000f 49000000 0000000b 47000000 ff000304 ff000000 ff000000
    24.07.2014 17:57:31,000 kernel[0]: ff000000 ff000000 ff000000 0a000000 1d13c220 00100008 e480a818 12200bf7
    24.07.2014 17:57:31,000 kernel[0]: 03300828 a7a6a038 0dd7b0b6 48028040 00000000 4443564e
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to start of command buffer processing!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
    24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
    24.07.2014 17:57:31,835 WindowServer[135]: CGXMuxCapture: Released
    24.07.2014 17:57:31,835 WindowServer[135]: Display 0x4280642 released by conn 0x1cc8f
    24.07.2014 17:58:18,000 bootlog[0]: BOOT_TIME 1406217498 0

    The logic board is defective and must be replaced under warranty.

  • Add Date/Time Stamp to Timecode Effect

    The Timecode effect of CS5 Premiere Pro is a very useful feature. However, it is missing a Date/Time Stamp. I would encourage everyone to submit a feature request for this. I have enclosed one I submitted. You can cut and paste it into the Feature Request Submission Form.
    Feature Request Submission Form
    Feature Request: Add Date / Time Stamp to Timecode Effect
    The Timecode effect of CS5 Premiere Pro is a very useful feature. However, the Timecode effect is missing the ability to also display the Date/Time Stamp from Premiere captured video. This is a very important feature to include. Many videographers are archiving their miniDV tapes as AVI files since disk prices have become affordable. When I retrieve archived AVI files, I often need to look at the Date/Time Stamp, but unfortunately, Premiere does not offer that ability.
    I would encourage you to add Date/Time Stamp capability to the Timecode effect so timecode, date, and time could be displayed all at once, or selectively picked via checkboxes.
    Others in the Premiere forum have requested this capability.
    Date / Time Stamp - Premiere CS4
    http://forums.adobe.com/message/2564766
    Hopefully, you could add this as an update to CS5. And hopefully, as soon as possible. Thanks

    I am fairly new to Adobe CS6 however I have to totally disagree with some of the replies here on this subject. The package cost me well over £1200 and I expect a say in improving it along the way if I am to progress on to CS Cloud. The suggestion that engineers could spend their time elswere is total rubbish,its what they are well paid for..to listen to consumers suggestions and act on them (I am paying for their time).  I would for one love to see the simple add in plug where the original date/time code could be added and burned into the video timeline. It is obvously not something needed by all but for some it could be essential. For my work I entirely rely on the original date/time code to be visible and burned in. My work is editing surveilance video and I also have to pixellate all faces of young persons so the addition of a date and time code plug in is something I would like to see in After Effects and Premier. Adobe add hundreds of filters/plug-ins that nobody in the world are likely to ever see or use or even asked for, so I cant't see why it would be a big task for them to include it in CS6 or Cloud for the future, especially as many ask for it.
    On the suggestion of DVMPro, yes this is an excellent package which I already use along with vATS (which is quicker),  however the big downside for both these programmes is they do not combine the clips so if I put in 60. mts clips I will get  out 60 clips of what ever format I picked (limited to AVI/Wmv/AVCHD). You would then need combine and re-render the clips or work along the timeline with lots of clips (obviously not in AE as it wont combine clips along one layer....at least I cant see a way to do it (no doubt will be flamed on that one)
    Sony vegas 11 also does not have the capability neither to add and burn in the original timecode however there is an excellent and tiny .dll third party extension called SVDTS that will add the original time/date/seconds to the timeline and burn in to the video. My point on this comparison is that it would not take a lot of time and work for a capable Adobe enineer to develop and implement such a plug in.
    A crude way and free to actually achieve this is to use Freemake Video Converter, add all  your .mts (or what ever format they are so long as its original), turn on the Subtitle 1 option for each clip (no batch turn on Im afraid) and chose to join the clips for output to what ever file format you choose. The original timecode and date will be on your output video clip, not as pretty as DVMPro or vAts but is there and accurate.

  • How to display the real recording time of day in a video?

    I want to create a video in which the real recording time of day is displayed though the whole video.
    I already tried with the timecode generator, but this shows the time progress of the video being played back. What I need is the real recording TOD of every scene even after lots of cuts and trims and even after changing the clip speed.
    Does anyone have an idea, how this could be accomplished?

    Hi Wei,
    As far as I know the parent key needs to be initial for the top row. A workaround would be to create an additional attribute and fill it with an artificial parent key. In case you are using a DDIC structure at the node in question, you could add a sub node of 1:1 cardinality and place the attribute there.
    Best regards,
    Thomas
    P.S: I forwarded your question to a colleague of mine who happens to be the expert for the table. Perhaps he knows another solution.

  • TIME CODE in live capture

    I want to record live recording to Digibeta and capturing to FCP (AJA IO LD) in the same time with same TIMECODE!
    If I connect RS422 to AJA box, and begin record on VTR and FCP, FCP stops after couple of seconds...
    Any help???

    Not sure you can do this, because you have to have FCP set for 'non-controllable' device for the live capture.
    Maybe the AJA box supercedes this...others may know.
    Are you set for 'non-controllable device'? With this capture setting, FCP will generate it's own timecode.
    K

  • How many mails i can send at a time per day using APEX mail system?

    HI,
    I am working on application, when i have written a process to send mail, i have a project where i have to send mail at a time for all the email id's
    given list there are upto 5000 email id's where text body also include certain set of data from a report. thinking at a time 3000 its difficult i divided
    it region wise, but still each region have 2000 odd email id's. during testing when i run the process just 950 mails i could send then i got a error
    saying "ORA-20001: You have exceeded the maximum number of email messages per workspace. Please contact your administrator." so please
    can any one help me to know How many mails i can send at a time per day using APEX mail system?
    Thanks in advance
    Gowthami

    Hi jfosteroracle,
    You are getting the error may be the following reason,
    Check the following,
    Login as ADMIN and Goto -->Manage Instance-->Instance Settings--> Mail-->Maximum Emails per workspace
    Actually this number denotes the Number of mails can be sent per 24 hour for the workspace,It may exceeded.
    It may be the reason.
    Thank you.     
    Regards,
    Gurujothi
    Edited by: Gurujothi on Jun 27, 2012 5:54 AM

  • Doing something at a specific time of day

    Hi all,
    Basically what I am doing is an alarm clock, to wake me up to some MP3s. It all works fine.
    My only concern is the following:
         private Thread tTimeCheck = new Thread() {
              public void run () {
                   while (true) {
                       cal = new GregorianCalendar();
                       int hour24 = cal.get(Calendar.HOUR_OF_DAY);
                       int min = cal.get(Calendar.MINUTE);
                       if (hour24 == JSelectHour.getValeur() && min == JSelectMinute.getValeur()) {
                            playMusic = true;
                       } else {
                            playMusic = false;
                       try {
                            t.sleep(1000);
                       } catch (InterruptedException e) {
         };Is it unefficient to check every second, to see if the time of day is equal to the set time on the alarm clock? It seems to me that there has to be a better way to do this.

    Thank you for your reply.
    This is my thread that plays the music.
    while (true) {
       if (playMusic && jpnl.getAlarmStatus() == 1) {
           testPlay("C:/Documents and Settings/Seb/Desktop/Music/01-nirvana-smells.like.teen.spirit.mp3"); //hardcoded for now
    }testPlay is executed the the entire song plays before the next iteration.
    Next step: I'll look to put this in the taskbar (windows tray / whatever it's called), never done that before =)
    Thanks,
    Message was edited by:
    Robocrotch

  • Hard lock ups multiple times a day - How can I troubleshoot?

    My machine locks up hard multiple times a day. If I happen to be sitting in front of it, I observe that the image on the monitors stops changing. Mouse and keyboard will not work at all (including Magic key SysRq sequences). I cannot ping the box from another machine. The system has not made it to 24 hours of uptime for some weeks.
    I am beginning to suspect that this may be an issue with the NVIDIA driver, but that's only a guess since it's the only thing I've seen before that can lock up a machine hard like this. I have checked journalctl and the Xorg logs, but don't see anything telling.
    What should be my next steps toward solving this issue?

    When it locks up, do any indicators on the keyboard blink?  That would be an indication of a kernel panic. 
    If there are no blinking lights, does it unlock eventually?
    Has the machine ever been stable?
    Have you tried installing a RAM test in your boot loader and running it?
    Next, I would start blacklisting any kernel module you don't absolutely need to see if you can isolate it that way.
    Also, this looks ominous:
    Apr 29 07:49:48 lore kernel: This system BIOS has enabled interrupt remapping
    on a chipset that contains an erratum making that
    feature unstable. To maintain system stability
    interrupt remapping is being disabled. Please
    contact your BIOS vendor for an update
    I redouble my suggestion you pare down loaded modules to try and isolate this.
    Also, I see that it looks at the microcode
    Apr 29 07:49:48 lore kernel: microcode: CPU0 sig=0x106a5, pf=0x1, revision=0x11
    Apr 29 07:49:48 lore kernel: microcode: CPU1 sig=0x106a5, pf=0x1, revision=0x11
    Apr 29 07:49:48 lore kernel: microcode: CPU2 sig=0x106a5, pf=0x1, revision=0x11
    Apr 29 07:49:48 lore kernel: microcode: CPU3 sig=0x106a5, pf=0x1, revision=0x11
    Apr 29 07:49:48 lore kernel: microcode: CPU4 sig=0x106a5, pf=0x1, revision=0x11
    Apr 29 07:49:48 lore kernel: microcode: CPU5 sig=0x106a5, pf=0x1, revision=0x11
    Apr 29 07:49:48 lore kernel: microcode: CPU6 sig=0x106a5, pf=0x1, revision=0x11
    Apr 29 07:49:48 lore kernel: microcode: CPU7 sig=0x106a5, pf=0x1, revision=0x11
    But I don't see it being updated.  That might be normal for your processor, but double check that and ensure you have the microcode update stuff installed in the boot loader correctly.

  • IPhone 4S battery draining too fast...Need to charge 3 times a day

    Finally after 4 years I was very excited to get an iPhone that has all the features I wanted…but I am disappointed so far.
    I purchased an iPhone 4S 32GB on 10/7 and has not been impressed with the battery life. I have to charge my iPhone at least 3 times a day. I go to work at 8 AM and by 11:30 AM the battery is at 20 %, so I charge it again which takes only about 60 to 120 minutes to charge, and by 5:30 PM I have to start charging again…the third charge has start around 11:30 PM and I have to keep the phone plugged overnight otherwise it will be dead by 6 AM.
    I have read other posts on the web and people have suggested turning notifications, location services…etc which I went ahead and did but that did not change the battery issue. What is the purpose of having the iPhone 4S if all the features have to be turned off.
    I always try to kill apps that running in background but still no fix to battery issue.
    on 10/19/11 I went to Apple store and exchanged the phone with new one. The apple rep activated the phone for me and the charge was at 78 %. I left the store and 10 minutes later I was at my house, but again I was surprised to see the battery has drooped to 65 % within 10 minutes. While I was driving home I did not touch the phone or make/receive calls.
    When I got home I plugged the phone and when it was charge at 100 % I unplugged it and 40 minutes later the battery dropped to 70 %.
    Today I unplugged my iPhone 4s at 8:20 this morning with 100% and by 10:43 AM I am down to 63%. By 11:13 AM the battery was at 54% and by 11:46 AM the battery was down to 44% with me not touching it. I have turned everything off such notifications, locations services...etc and nothing in the background is working and I only used it for a 10 minute conversation.
    It seemed that a lot of users are have similar issue. Not sure if the issue related to iOS 5, iPhone or bad batch of iPhone or iPhone batteries.
    Before getting the iPhone 4S i had a 3GS from a family member that i had to charge at least 3 times a day. The only reason I got the new 4S is to not have to deal with frequent charge. I think I am 90 % close to returning the phone back to Apple and wait few months before attempting to purchase another phone.
    Thanks.....B

    What made the trick for me was to drain the phone completely - until it dies. (It took quite a while to go from 3% to 0...). Then, charge it overnight.
    Previous days I would start charging it with the battery at 10-15%, on red. Also for the last week I've been trying disabling functions, with the hope of finding what was the "offending" piece but without much success. Still was loosing about 10% per hour, just by using it to check emails, maps, and sometimes a call.
    Today is almost two hours since I left home, with everything turned on again, used mail, maps with traffic during the ride to work, some browsing - using it "normally" - and the battery is still at 95%.
    That looks more like normal to me.!!
    Might try to drain it to 0% again as many other suggested, but if it is a battery charger "calibration", it shouldn't be necesary to do it more than once.

  • Just installed Mavericks and my computer crashes 4-5 times a day now.

    Hi. Just a few days ago I finally gave in and upgraded to Mavericks (10.9.5) from 10.6.8 as there was some software that I needed to use that necessitated the upgrade. Since I've upgraded, my MacBook Pro crashes at least 4-5 times daily. I am not doing anything unusual when it occurs. Usually typing an email, or switching between tabs in Safari or clicking save on a word file. In another post I was introduced to an app called Etrecheck which seemed to me to be a fine way to show all the Mac geniuses on this forum whats going with my computer (unfortunately I am not savvy enough to look through it and understand what's going on). I've posted the report below. Maybe someone can help me figure out what's causing my computer to crash?
    The next time it happens I can also copy the report that shows up after the crash and post it as well. Many thanks in advance.
    Problem description:
    Since I downloaded Mavericks (10.9.5) my computer crashes randomly 4-5 times per day.
    EtreCheck version: 2.0.4 (89)
    Report generated October 15, 2014 at 8:07:20 AM EDT
    Hardware Information: ℹ️
      MacBook Pro (15-inch, Mid 2010) (Verified)
      MacBook Pro - model: MacBookPro6,2
      1 2.66 GHz Intel Core i7 CPU: 2-core
      4 GB RAM Upgradeable
      BANK 0/DIMM0
      2 GB DDR3 1067 MHz ok
      BANK 1/DIMM0
      2 GB DDR3 1067 MHz ok
      Bluetooth: Old - Handoff/Airdrop2 not supported
      Wireless:  en1: 802.11 a/b/g/n
    Video Information: ℹ️
      Intel HD Graphics - VRAM: 288 MB
      Color LCD 1680 x 1050
      NVIDIA GeForce GT 330M - VRAM: 512 MB
    System Software: ℹ️
      OS X 10.9.5 (13F34) - Uptime: 9:9:52
    Disk Information: ℹ️
      ST9500420ASG disk0 : (500.11 GB)
      S.M.A.R.T. Status: Verified
      EFI (disk0s1) <not mounted> : 210 MB
      Macintosh HD (disk0s2) /  [Startup]: 499.25 GB (75.82 GB free)
      Recovery HD (disk0s3) <not mounted>  [Recovery]: 650 MB
      MATSHITADVD-R   UJ-898
    USB Information: ℹ️
      Apple Inc. Apple Internal Keyboard / Trackpad
      Apple Inc. BRCM2070 Hub
      Apple Inc. Bluetooth USB Host Controller
      Apple Internal Memory Card Reader
      Apple Inc. Built-in iSight
      Apple Computer, Inc. IR Receiver
    Gatekeeper: ℹ️
      Mac App Store and identified developers
    Kernel Extensions: ℹ️
      /Applications/Toast 6 Titanium.app
      [not loaded] com.roxio.TDIXController (1.2) Support
      /System/Library/Extensions
      [loaded] com.Cycling74.driver.Soundflower (1.5.1) Support
      [not loaded] com.IKMultimedia.driver.StompIO1 (1.0.0) Support
      [not loaded] com.digidesign.fwfamily.driver (8.0.5f2) Support
      [loaded] com.digidesign.iokit.DigiDal (8.0.5f2) Support
      [not loaded] com.digidesign.mbox2.boot.driver (8.0.5f2) Support
      [not loaded] com.digidesign.mbox2.driver (8.0.5f2) Support
      [not loaded] com.digidesign.usb.elevenrack.driver (1.0.1) Support
      [not loaded] com.frontierdesign.iokit.alphatrack (1.4.1f1) Support
      [not loaded] com.ikmultimedia.driver.StealthPedal (1.0.0) Support
      [not loaded] com.paceap.kext.pacesupport.master (5.9 - SDK 10.6) Support
      /System/Library/Extensions/PACESupportFamily.kext/Contents/PlugIns
      [not loaded] com.paceap.kext.pacesupport.leopard (5.9 - SDK 10.4) Support
      [not loaded] com.paceap.kext.pacesupport.panther (5.9 - SDK 10.-1) Support
      [loaded] com.paceap.kext.pacesupport.snowleopard (5.9 - SDK 10.6) Support
      [not loaded] com.paceap.kext.pacesupport.tiger (5.9 - SDK 10.4) Support
    Startup Items: ℹ️
      Digidesign Mbox 2: Path: /Library/StartupItems/Digidesign Mbox 2
      DigidesignLoader: Path: /Library/StartupItems/DigidesignLoader
      Qmaster: Path: /Library/StartupItems/Qmaster
      Startup items are obsolete and will not work in future versions of OS X
    Launch Agents: ℹ️
      [running] com.amazon.sendtokindle.launcher.plist Support
      [running] com.eastwest.server.plist Support
      [running] com.frontierdesign.alphatrack.daemon.plist Support
      [running] com.sony.PMBPortable.AutoRun.plist Support
    Launch Daemons: ℹ️
      [loaded] com.adobe.fpsaud.plist Support
      [running] com.digidesign.elevenrack.helper.plist Support
      [running] com.digidesign.fwfamily.helper.plist Support
      [running] com.paceap.eden.licensed.plist Support
      [loaded] PACESupport.plist Support
    User Launch Agents: ℹ️
      [invalid?] com.amazon.cloud-player.plist Support
      [loaded] com.google.keystone.agent.plist Support
    User Login Items: ℹ️
      iTunesHelper UNKNOWN (missing value)
      Dropbox Application (/Applications/Dropbox.app)
      TomTomHOMERunner ApplicationHidden (/Users/[redacted]/Library/Application Support/TomTom HOME/TomTomHOMERunner.app)
      Android File Transfer Agent Application (/Users/[redacted]/Library/Application Support/Google/Android File Transfer/Android File Transfer Agent.app)
    Internet Plug-ins: ℹ️
      WidevineMediaOptimizer: Version: 6.0.0.12757 - SDK 10.7 Support
      FlashPlayer-10.6: Version: 15.0.0.152 - SDK 10.6 Support
      Default Browser: Version: 537 - SDK 10.9
      Flash Player: Version: 15.0.0.152 - SDK 10.6 Mismatch! Adobe recommends 15.0.0.189
      QuickTime Plugin: Version: 7.7.3
      CitrixICAClientPlugIn: Version: 11.2.0 Support
      OfficeLiveBrowserPlugin: Version: 12.3.6 Support
      iLokClientHelper: Version: 3.4 Support
      iPhotoPhotocast: Version: 7.0
    User Internet Plug-ins: ℹ️
      WebEx64: Version: 1.0 - SDK 10.6 Support
    Audio Plug-ins: ℹ️
      DVCPROHDAudio: Version: 1.3
      JackRouter: Version: JackRouter Support
      Digidesign CoreAudio: Version: 8.0.5 Support
    3rd Party Preference Panes: ℹ️
      Citrix Online Plug-in  Support
      Digidesign Eleven Rack  Support
      DigidesignMbox2  Support
      Digidesign Mbox 2 Pro  Support
      Flash Player  Support
      Perian  Support
    Time Machine: ℹ️
      Time Machine not configured!
    Top Processes by CPU: ℹ️
          10% com.apple.WebKit.Networking
          7% fontd
          2% com.apple.WebKit.Plugin.64
          1% WindowServer
          0% configd
    Top Processes by Memory: ℹ️
      172 MB com.apple.WebKit.WebContent
      125 MB WindowServer
      112 MB softwareupdated
      86 MB Safari
      82 MB Mail
    Virtual Memory Information: ℹ️
      25 MB Free RAM
      1.46 GB Active RAM
      1.45 GB Inactive RAM
      856 MB Wired RAM
      2.11 GB Page-ins
      414 MB Page-outs

    Sure enough the computer just crashed a few minutes after posting. Here's the report after the computer rebooted:
    Anonymous UUID:       40656744-595E-FDB7-F6E9-0497F4D35619
    Wed Oct 15 08:27:05 2014
    panic(cpu 0 caller 0xffffff7f9fa95f7c): "GPU Panic: [<None>] 5 3 7f 0 0 0 0 3 : NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xc0000000 0xffffff80c5ad5000 0x0a5480a2, D0, P3/4\n"@/SourceCache/AppleGraphicsControl/AppleGraphicsControl-3.6.22/src/Apple MuxControl/kext/GPUPanic.cpp:127
    Backtrace (CPU 0), Frame : Return Address
    0xffffff80b3abaf80 : 0xffffff801d622f79
    0xffffff80b3abb000 : 0xffffff7f9fa95f7c
    0xffffff80b3abb0d0 : 0xffffff7f9e11bf1b
    0xffffff80b3abb190 : 0xffffff7f9e1e550a
    0xffffff80b3abb1d0 : 0xffffff7f9e1e557a
    0xffffff80b3abb240 : 0xffffff7f9e464056
    0xffffff80b3abb370 : 0xffffff7f9e208ba9
    0xffffff80b3abb390 : 0xffffff7f9e12296d
    0xffffff80b3abb440 : 0xffffff7f9e120478
    0xffffff80b3abb640 : 0xffffff7f9e121dc7
    0xffffff80b3abb710 : 0xffffff7f9f086e1d
    0xffffff80b3abb890 : 0xffffff7f9f086823
    0xffffff80b3abb8a0 : 0xffffff7f9f04baf0
    0xffffff80b3abb8b0 : 0xffffff7f9f04bb65
    0xffffff80b3abb8c0 : 0xffffff7f9f037c51
    0xffffff80b3abb8e0 : 0xffffff7f9f036fd9
    0xffffff80b3abba60 : 0xffffff7f9f066940
    0xffffff80b3abbb20 : 0xffffff7f9f035ad9
    0xffffff80b3abbb70 : 0xffffff801dacf146
    0xffffff80b3abbb90 : 0xffffff801dad0741
    0xffffff80b3abbbf0 : 0xffffff801dace1af
    0xffffff80b3abbd40 : 0xffffff801d6b6998
    0xffffff80b3abbe50 : 0xffffff801d626bc1
    0xffffff80b3abbe80 : 0xffffff801d6139c5
    0xffffff80b3abbef0 : 0xffffff801d61e013
    0xffffff80b3abbf70 : 0xffffff801d6c9b9d
    0xffffff80b3abbfb0 : 0xffffff801d6f4196
          Kernel Extensions in backtrace:
             com.apple.nvidia.classic.NVDAResmanTesla(8.2.4)[D61B2BB9-4289-318D-9197-5E1E13B 1FF32]@0xffffff7f9e0cc000->0xffffff7f9e334fff
                dependency: com.apple.iokit.IOPCIFamily(2.9)[2852ACFE-FD28-3C37-9B39-885201BB8D25]@0xffffff 7f9dcbf000
                dependency: com.apple.iokit.IONDRVSupport(2.4.1)[D41125CE-69BD-32E7-9B1D-4E83431662DD]@0xff ffff7f9e0bc000
                dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[75D81741-64C1-3941-ADFA-9D6B6C434EE4]@0 xffffff7f9e079000
             com.apple.nvidia.classic.NVDANV50HalTesla(8.2.4)[B0E6AAA7-E970-3D81-8B43-145D56 A3A4AC]@0xffffff7f9e33f000->0xffffff7f9e5e8fff
                dependency: com.apple.nvidia.classic.NVDAResmanTesla(8.2.4)[D61B2BB9-4289-318D-9197-5E1E13B 1FF32]@0xffffff7f9e0cc000
                dependency: com.apple.iokit.IOPCIFamily(2.9)[2852ACFE-FD28-3C37-9B39-885201BB8D25]@0xffffff 7f9dcbf000
             com.apple.GeForceTesla(8.2.4)[B0074750-2FC6-3E26-BEA0-5AD5469686CF]@0xffffff7f9 f024000->0xffffff7f9f0eefff
                dependency: com.apple.iokit.IOPCIFamily(2.9)[2852ACFE-FD28-3C37-9B39-885201BB8D25]@0xffffff 7f9dcbf000
                dependency: com.apple.iokit.IONDRVSupport(2.4.1)[D41125CE-69BD-32E7-9B1D-4E83431662DD]@0xff ffff7f9e0bc000
                dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[75D81741-64C1-3941-ADFA-9D6B6C434EE4]@0 xffffff7f9e079000
                dependency: com.apple.nvidia.classic.NVDAResmanTesla(8.2.4)[D61B2BB9-4289-318D-9197-5E1E13B 1FF32]@0xffffff7f9e0cc000
             com.apple.driver.AppleMuxControl(3.6.22)[32862231-50BC-3AF6-87A2-703321AE4F90]@ 0xffffff7f9fa87000->0xffffff7f9fa9afff
                dependency: com.apple.driver.AppleGraphicsControl(3.6.22)[AA46D551-BE0F-33DA-93A3-8F46197BB 36F]@0xffffff7f9fa7f000
                dependency: com.apple.iokit.IOACPIFamily(1.4)[045D5D6F-AD1E-36DB-A249-A346E2B48E54]@0xfffff f7f9df7f000
                dependency: com.apple.iokit.IOPCIFamily(2.9)[2852ACFE-FD28-3C37-9B39-885201BB8D25]@0xffffff 7f9dcbf000
                dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[75D81741-64C1-3941-ADFA-9D6B6C434EE4]@0 xffffff7f9e079000
                dependency: com.apple.driver.AppleBacklightExpert(1.0.4)[80899285-3952-30DA-A0F9-357C51E104 CF]@0xffffff7f9fa82000
    BSD process name corresponding to current thread: WindowServer
    Mac OS version:
    13F34
    Kernel version:
    Darwin Kernel Version 13.4.0: Sun Aug 17 19:50:11 PDT 2014; root:xnu-2422.115.4~1/RELEASE_X86_64
    Kernel UUID: 9477416E-7BCA-3679-AF97-E1EAAD3DD5A0
    Kernel slide:     0x000000001d400000
    Kernel text base: 0xffffff801d600000
    System model name: MacBookPro6,2 (Mac-F22586C8)
    System uptime in nanoseconds: 8076473822747
    last loaded kext at 654256352755: com.apple.filesystems.smbfs 2.0.3 (addr 0xffffff7f9fb9f000, size 335872)
    last unloaded kext at 334416608476: com.apple.driver.AppleUSBUHCI 656.4.1 (addr 0xffffff7f9e8bd000, size 65536)
    loaded kexts:
    com.paceap.kext.pacesupport.snowleopard 5.9
    com.Cycling74.driver.Soundflower 1.5.1
    com.digidesign.iokit.DigiDal 8.0.5f2
    com.apple.filesystems.smbfs 2.0.3
    com.apple.filesystems.autofs 3.0
    com.apple.driver.AppleHWSensor 1.9.5d0
    com.apple.iokit.IOBluetoothSerialManager 4.2.7f3
    com.apple.driver.AGPM 100.14.34
    com.apple.driver.AppleMikeyHIDDriver 124
    com.apple.driver.AppleMikeyDriver 2.6.3f4
    com.apple.driver.AppleHDA 2.6.3f4
    com.apple.driver.AudioAUUC 1.60
    com.apple.driver.AppleSMCLMU 2.0.4d1
    com.apple.iokit.IOUserEthernet 1.0.0d1
    com.apple.Dont_Steal_Mac_OS_X 7.0.0
    com.apple.driver.AppleHWAccess 1
    com.apple.driver.AppleLPC 1.7.0
    com.apple.driver.AppleSMCPDRC 1.0.0
    com.apple.driver.AppleMuxControl 3.6.22
    com.apple.driver.AppleIntelHDGraphics 8.2.4
    com.apple.driver.AppleIntelHDGraphicsFB 8.2.4
    com.apple.GeForceTesla 8.2.4
    com.apple.driver.AppleUpstreamUserClient 3.5.13
    com.apple.driver.AppleMCCSControl 1.2.5
    com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.2.7f3
    com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
    com.apple.driver.SMCMotionSensor 3.0.4d1
    com.apple.driver.AppleUSBTCButtons 240.2
    com.apple.driver.AppleUSBTCKeyboard 240.2
    com.apple.driver.AppleUSBCardReader 3.4.1
    com.apple.driver.AppleIRController 325.7
    com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
    com.apple.AppleFSCompression.AppleFSCompressionTypeLZVN 1.0.0d1
    com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
    com.apple.BootCache 35
    com.apple.iokit.SCSITaskUserClient 3.6.7
    com.apple.driver.XsanFilter 404
    com.apple.iokit.IOAHCIBlockStorage 2.6.0
    com.apple.driver.AppleUSBHub 683.4.0
    com.apple.driver.AppleFWOHCI 5.0.2
    com.apple.iokit.AppleBCM5701Ethernet 3.8.1b2
    com.apple.driver.AirPort.Brcm4331 700.20.22
    com.apple.driver.AppleUSBEHCI 660.4.0
    com.apple.driver.AppleAHCIPort 3.0.5
    com.apple.driver.AppleSmartBatteryManager 161.0.0
    com.apple.driver.AppleACPIButtons 2.0
    com.apple.driver.AppleRTC 2.0
    com.apple.driver.AppleHPET 1.8
    com.apple.driver.AppleSMBIOS 2.1
    com.apple.driver.AppleACPIEC 2.0
    com.apple.driver.AppleAPIC 1.7
    com.apple.driver.AppleIntelCPUPowerManagementClient 217.92.1
    com.apple.nke.applicationfirewall 153
    com.apple.security.quarantine 3
    com.apple.driver.AppleIntelCPUPowerManagement 217.92.1
    com.apple.kext.triggers 1.0
    com.apple.iokit.IOSerialFamily 10.0.7
    com.apple.AppleGraphicsDeviceControl 3.6.22
    com.apple.driver.DspFuncLib 2.6.3f4
    com.apple.vecLib.kext 1.0.0
    com.apple.iokit.IOFireWireIP 2.2.6
    com.apple.iokit.IOAudioFamily 1.9.7fc2
    com.apple.kext.OSvKernDSPLib 1.14
    com.apple.iokit.IOSurface 91.1
    com.apple.iokit.IOBluetoothFamily 4.2.7f3
    com.apple.driver.AppleSMBusPCI 1.0.12d1
    com.apple.driver.AppleGraphicsControl 3.6.22
    com.apple.driver.AppleBacklightExpert 1.0.4
    com.apple.nvidia.classic.NVDANV50HalTesla 8.2.4
    com.apple.driver.AppleSMBusController 1.0.12d1
    com.apple.nvidia.classic.NVDAResmanTesla 8.2.4
    com.apple.iokit.IONDRVSupport 2.4.1
    com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.2.7f3
    com.apple.driver.AppleHDAController 2.6.3f4
    com.apple.iokit.IOGraphicsFamily 2.4.1
    com.apple.iokit.IOHDAFamily 2.6.3f4
    com.apple.driver.IOPlatformPluginLegacy 1.0.0
    com.apple.driver.IOPlatformPluginFamily 5.7.1d6
    com.apple.driver.AppleSMC 3.1.8
    com.apple.driver.AppleUSBMultitouch 240.10
    com.apple.iokit.IOSCSIBlockCommandsDevice 3.6.7
    com.apple.iokit.IOUSBMassStorageClass 3.6.0
    com.apple.iokit.IOUSBHIDDriver 660.4.0
    com.apple.driver.AppleUSBMergeNub 650.4.0
    com.apple.driver.AppleUSBComposite 656.4.1
    com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.6.7
    com.apple.iokit.IOBDStorageFamily 1.7
    com.apple.iokit.IODVDStorageFamily 1.7.1
    com.apple.iokit.IOCDStorageFamily 1.7.1
    com.apple.iokit.IOAHCISerialATAPI 2.6.1
    com.apple.iokit.IOSCSIArchitectureModelFamily 3.6.7
    com.apple.iokit.IOUSBUserClient 660.4.2
    com.apple.iokit.IOFireWireFamily 4.5.5
    com.apple.iokit.IOEthernetAVBController 1.0.3b4
    com.apple.driver.mDNSOffloadUserClient 1.0.1b5
    com.apple.iokit.IO80211Family 640.36
    com.apple.iokit.IONetworkingFamily 3.2
    com.apple.iokit.IOAHCIFamily 2.6.5
    com.apple.iokit.IOUSBFamily 686.4.1
    com.apple.driver.AppleEFINVRAM 2.0
    com.apple.driver.AppleEFIRuntime 2.0
    com.apple.iokit.IOHIDFamily 2.0.0
    com.apple.iokit.IOSMBusFamily 1.1
    com.apple.security.sandbox 278.11.1
    com.apple.kext.AppleMatch 1.0.0d1
    com.apple.security.TMSafetyNet 7
    com.apple.driver.AppleKeyStore 2
    com.apple.driver.DiskImages 371.1
    com.apple.iokit.IOStorageFamily 1.9
    com.apple.iokit.IOReportFamily 23
    com.apple.driver.AppleFDEKeyStore 28.30
    com.apple.driver.AppleACPIPlatform 2.0
    com.apple.iokit.IOPCIFamily 2.9
    com.apple.iokit.IOACPIFamily 1.4
    com.apple.kec.pthread 1
    com.apple.kec.corecrypto 1.0
    Model: MacBookPro6,2, BootROM MBP61.0057.B0C, 2 processors, Intel Core i7, 2.66 GHz, 4 GB, SMC 1.58f17
    Graphics: Intel HD Graphics, Intel HD Graphics, Built-In, 288 MB
    Graphics: NVIDIA GeForce GT 330M, NVIDIA GeForce GT 330M, PCIe, 512 MB
    Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1067 MHz, 0x802C, 0x31364A53463235363634485A2D3147314631
    Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1067 MHz, 0x802C, 0x31364A53463235363634485A2D3147314631
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x93), Broadcom BCM43xx 1.0 (5.106.98.100.22)
    Bluetooth: Version 4.2.7f3 14616, 3 services, 23 devices, 1 incoming serial ports
    Network Service: AirPort, AirPort, en1
    Serial ATA Device: ST9500420ASG, 500.11 GB
    Serial ATA Device: MATSHITADVD-R   UJ-898
    USB Device: Hub
    USB Device: BRCM2070 Hub
    USB Device: Bluetooth USB Host Controller
    USB Device: Internal Memory Card Reader
    USB Device: Apple Internal Keyboard / Trackpad
    USB Device: Hub
    USB Device: Built-in iSight
    USB Device: IR Receiver
    Thunderbolt Bus:

  • New to FiOS - Set Top Box isn't showing time of day

    I just had FiOS installed on multiple TV's HD and non-HD.  All the set-top boxes don't show a time of day except the HD DVR.  Is there a way to set the others up to show the time of day?  If so, how?

    The new HD STB's do no have a display at all. cannot get a clock on the QIP7100-2 STB's
    ====================================================================================
    Error exists between keyboard and chair.

  • DVR STB will not hold the display of the time of day.

    I am new to FIOS.  I have a DVR Set Top Box for my HD TV.  I prefer to see the time of day displayed.  I set this option in Menu/Settings/Set Top/Display and it works OK UNTIL you change the channel.  Then it displays the new channel and DOES NOT revert back to the time of day as it is supposed to do.
    Called Verizon.  They reset the box.  It worked OK for about 30 minutes then went back to the same problem.  I don't want them to reset it again because when they did it wiped all of my favorites.
    Any solutions will be greatly appreciated.
    Solved!
    Go to Solution.

    Try rebooting the STB and then change the clock setting and change it back. That worked for me when i had this issue. I have seen this reported a couple of times and most of the time if this fix didnt work, the issue resolved itself within a couple of days.
    Also, it should be noted that with the 1.7IMG release they changed the way the front display functioned. It now changes to show the channel number at every program change and then reverts back to showing the clock after about 2 minutes.
    "If your problem has been solved, please mark it as such. Don't forget to hand out your Kudos!"

  • Have you noticed the newest version 3.6.23 crashes frequently? Mine does it a few times a day on web pages that used to work fine before the upgrade.

    Since the last Firefox update was installed on my system, Firefox crashes several times a day on websites that used to be no problem. I have five crash report id's from the last two days (I usually don't send the report). Do you want all of them?
    I'm running Firefox 3.6.23
    I'm running MacOS X version 10.5.8, on 1.5ghz powerPC G4
    with 2gb memory and over 100gig still available on my 150gig hard drive.
    I checked for updates - there are no new updates.
    I tried sending feedback, but the feedback page said I had to be running the latest version of firefox. So I clicked on "latest version of Firefox", and got "Unfortunately the latest version of Firefox isn't compatible with your computer's operating system"
    The "learn more" link took me to http://www.mozilla.org/en-US/firefox/4.0/system-requirements/ which says that OS 10.5 is supported.
    So - how do I get back to my previous version of Firefox so it doesn't keep crashing
    AND/OR
    Is there a fix coming to stop all the crashing
    AND/OR
    What do I do about Firefox versions on my computer?
    Thanks

    That can be a problem with a plugin, possibly Java.
    * [https://bugzilla.mozilla.org/show_bug.cgi?id=573055 bug 573055] - Reproducible [@ nsNPAPIPluginInstance::InitializePlugin()] crashes / Java

  • Why do I need to reset my Airport Express multiple times a day?

    I purchased an Airport Express (AE) in 2008.  Ocassionaly since I've owned the device, I've had a problem connecting to it via iPod touch, iPhone, Macbook Pro, Macbook, etc.  I would see the AE in my wifi router list, I just couldn't connect to it.  I simple reboot always seemed to fix the problem.  As time has passed, I found myself having to reboot it more and more often.  Within the past few months, it seems to be a daily occurance.  Within the past couple weeks, I've had to reboot it multiple times a day.  I have also performed a facory reset via the button and via airport utility - neither seem to affect the issue.
    I like the AE for the simple fact that it has AirTunes abilities, this is quite frankly the only reason I have it.  I would like to replace it, but I fear another unit would have similar issues.
    Is anyone else having these same problems on a 2+ year old AirPort Express?  if so, is there a fix action?  thanks.

    Hi, I'm having the same problem and have to reboot my Airport Express at least once a day. It is extremely frustrating.
    Firmware is 6.5
    Hopefully someone can help us

  • Why does my MBP restart itself randomly several times a day? Something about a "Panic Report".

    Ok so my MacBook Pro shuts itself down and restarts at least 4 times a day. Usually this happens when im away from my computer and its been idle or sleeping or whatever it does, however just 30 minutes ago this happened while i was using it and then it wouldnt restart it just kept showing the loading "apple" logo with loading bars comntinuously spinning... I had to shut it down manually and then it took an extra long time to load before finally loading to the user login page. Now generally... upon start up after this "panic" i will recieve a"Panic report" that says something aloong the lines of...
    Interval Since Last Panic Report:  27841 sec Panics Since Last Report:          2 Anonymous UUID:                    6EBC0F43-E7CB-480C-8D91-9EA7C74EEECC  Wed Jun  5 01:28:29 2013 panic(cpu 0 caller 0xffffff80002c4794): Kernel trap at 0xffffff7f816c8e1f, type 14=page fault, registers: CR0: 0x0000000080010033, CR2: 0xffffff80d17a0628, CR3: 0x000000008a22e00d, CR4: 0x00000000001606e0 RAX: 0xffffff80d15621f8, RBX: 0xffffff80d1562000, RCX: 0x000000000003cb26, RDX: 0x0000000000000000 RSP: 0xffffff80ef4f3960, RBP: 0xffffff80ef4f3a40, RSI: 0x000000807e876986, RDI: 0xffffff80ef4f39d9 R8:  0x000000000000001f, R9:  0xffffffffffffff00, R10: 0xffffffffffffffdf, R11: 0x0000000000000000 R12: 0xffffff80d179e000, R13: 0x0000000000000000, R14: 0x0000000000000000, R15: 0xffffff80ef4f3960 RFL: 0x0000000000010286, RIP: 0xffffff7f816c8e1f, CS:  0x0000000000000008, SS:  0x0000000000000010 CR2: 0xffffff80d17a0628, Error code: 0x0000000000000000, Faulting CPU: 0x0  Backtrace (CPU 0), Frame : Return Address 0xffffff80ef4f3610 : 0xffffff8000220792  0xffffff80ef4f3690 : 0xffffff80002c4794  0xffffff80ef4f3840 : 0xffffff80002da55d  0xffffff80ef4f3860 : 0xffffff7f816c8e1f  0xffffff80ef4f3a40 : 0xffffff7f816e5c05  0xffffff80ef4f3a80 : 0xffffff7f816c7257  0xffffff80ef4f3ab0 : 0xffffff7f80c95832  0xffffff80ef4f3af0 : 0xffffff7f80c9593d  0xffffff80ef4f3b10 : 0xffffff7f80c9ecff  0xffffff80ef4f3b70 : 0xffffff7f80c9edc8  0xffffff80ef4f3b90 : 0xffffff7f80c9c138  0xffffff80ef4f3bb0 : 0xffffff7f80c9c4bc  0xffffff80ef4f3be0 : 0xffffff80006565fe  0xffffff80ef4f3c40 : 0xffffff8000656fbb  0xffffff80ef4f3d80 : 0xffffff80002a3f08  0xffffff80ef4f3e80 : 0xffffff8000223096  0xffffff80ef4f3eb0 : 0xffffff80002148a9  0xffffff80ef4f3f10 : 0xffffff800021bbd8  0xffffff80ef4f3f70 : 0xffffff80002aef10  0xffffff80ef4f3fb0 : 0xffffff80002daec3        Kernel Extensions in backtrace:          com.apple.iokit.IOGraphicsFamily(2.3.4)[D0A1F6BD-E66E-3DD8-9913-A3AB8746F422]@0 xffffff7f80c8a000->0xffffff7f80cc2fff             dependency: com.apple.iokit.IOPCIFamily(2.7)[5C23D598-58B2-3204-BC03-BC3C0F00BD32]@0xffffff 7f80849000          com.apple.driver.AppleIntelHD4000Graphics(7.3.2)[AD64F3E5-2838-3046-A9EA-1CB6C9 769436]@0xffffff7f816c4000->0xffffff7f8172afff             dependency: com.apple.iokit.IOPCIFamily(2.7)[5C23D598-58B2-3204-BC03-BC3C0F00BD32]@0xffffff 7f80849000             dependency: com.apple.iokit.IONDRVSupport(2.3.4)[7C8672C4-8B0D-3CCF-A79A-23C62E90F895]@0xff ffff7f80cc3000             dependency: com.apple.iokit.IOGraphicsFamily(2.3.4)[D0A1F6BD-E66E-3DD8-9913-A3AB8746F422]@0 xffffff7f80c8a000  BSD process name corresponding to current thread: WindowServer  Mac OS version: 11G63  Kernel version: Darwin Kernel Version 11.4.2: Thu Aug 23 16:25:48 PDT 2012; root:xnu-1699.32.7~1/RELEASE_X86_64 Kernel UUID: FF3BB088-60A4-349C-92EA-CA649C698CE5 System model name: MacBookPro9,2 (Mac-6F01561E16C75D06)  System uptime in nanoseconds: 5870204567267 last loaded kext at 49584802694: com.apple.driver.AppleMikeyHIDDriver     122 (addr 0xffffff7f8167a000, size 20480) last unloaded kext at 200341249727: com.apple.driver.AppleUSBTCKeyEventDriver     227.6 (addr 0xffffff7f814f7000, size 8192) loaded kexts: com.apple.driver.AppleMikeyHIDDriver     122 com.apple.driver.X86PlatformShim     5.0.0d8 com.apple.driver.AGPM     100.12.75 com.apple.driver.AppleHDA     2.2.5a5 com.apple.driver.AppleUpstreamUserClient     3.5.9 com.apple.driver.AudioAUUC     1.59 com.apple.driver.AppleMikeyDriver     2.2.5a5 com.apple.driver.AppleSMCLMU     2.0.1d2 com.apple.driver.AppleIntelHD4000Graphics     7.3.2 com.apple.driver.SMCMotionSensor     3.0.2d6 com.apple.driver.AppleSMCPDRC     5.0.0d8 com.apple.iokit.IOUserEthernet     1.0.0d1 com.apple.iokit.IOBluetoothSerialManager     4.0.8f17 com.apple.Dont_Steal_Mac_OS_X     7.0.0 com.apple.driver.AudioIPCDriver     1.2.3 com.apple.driver.ApplePolicyControl     3.1.33 com.apple.driver.AppleLPC     1.6.0 com.apple.driver.AppleBacklight     170.2.2 com.apple.driver.AppleMCCSControl     1.0.33 com.apple.driver.AppleIntelFramebufferCapri     7.3.2 com.apple.filesystems.autofs     3.0 com.apple.driver.BroadcomUSBBluetoothHCIController     4.0.8f17 com.apple.driver.AppleUSBTCButtons     227.6 com.apple.driver.AppleUSBTCKeyboard     227.6 com.apple.driver.AppleIRController     312 com.apple.AppleFSCompression.AppleFSCompressionTypeDataless     1.0.0d1 com.apple.AppleFSCompression.AppleFSCompressionTypeZlib     1.0.0d1 com.apple.BootCache     33 com.apple.iokit.SCSITaskUserClient     3.2.1 com.apple.driver.XsanFilter     404 com.apple.iokit.IOAHCISerialATAPI     2.0.3 com.apple.iokit.IOAHCIBlockStorage     2.1.0 com.apple.driver.AppleSmartBatteryManager     161.0.0 com.apple.driver.AppleFWOHCI     4.9.0 com.apple.driver.AirPort.Brcm4331     561.7.22 com.apple.driver.AppleSDXC     1.2.2 com.apple.driver.AppleUSBHub     5.1.0 com.apple.iokit.AppleBCM5701Ethernet     3.2.4b8 com.apple.driver.AppleEFINVRAM     1.6.1 com.apple.driver.AppleAHCIPort     2.3.1 com.apple.driver.AppleUSBEHCI     5.1.0 com.apple.driver.AppleUSBXHCI     1.1.0 com.apple.driver.AppleACPIButtons     1.5 com.apple.driver.AppleRTC     1.5 com.apple.driver.AppleHPET     1.7 com.apple.driver.AppleSMBIOS     1.9 com.apple.driver.AppleACPIEC     1.5 com.apple.driver.AppleAPIC     1.6 com.apple.driver.AppleIntelCPUPowerManagementClient     195.0.0 com.apple.nke.applicationfirewall     3.2.30 com.apple.security.quarantine     1.4 com.apple.security.TMSafetyNet     8 com.apple.driver.AppleIntelCPUPowerManagement     195.0.0 com.apple.driver.DspFuncLib     2.2.5a5 com.apple.iokit.IOSurface     80.0.2 com.apple.iokit.IOSerialFamily     10.0.5 com.apple.iokit.IOFireWireIP     2.2.5 com.apple.iokit.IOAudioFamily     1.8.6fc18 com.apple.kext.OSvKernDSPLib     1.3 com.apple.driver.AppleHDAController     2.2.5a5 com.apple.iokit.IOHDAFamily     2.2.5a5 com.apple.driver.X86PlatformPlugin     5.1.1d6 com.apple.driver.AppleSMC     3.1.3d10 com.apple.driver.AppleSMBusPCI     1.0.10d0 com.apple.driver.IOPlatformPluginFamily     5.1.1d6 com.apple.driver.AppleGraphicsControl     3.1.33 com.apple.driver.AppleBacklightExpert     1.0.4 com.apple.iokit.IONDRVSupport     2.3.4 com.apple.driver.AppleSMBusController     1.0.10d0 com.apple.iokit.IOGraphicsFamily     2.3.4 com.apple.kext.triggers     1.0 com.apple.driver.AppleUSBBluetoothHCIController     4.0.8f17 com.apple.iokit.IOBluetoothFamily     4.0.8f17 com.apple.driver.AppleUSBMultitouch     230.5 com.apple.driver.AppleThunderboltDPInAdapter     1.8.5 com.apple.driver.AppleThunderboltDPAdapterFamily     1.8.5 com.apple.driver.AppleThunderboltPCIDownAdapter     1.2.5 com.apple.iokit.IOUSBHIDDriver     5.0.0 com.apple.driver.AppleUSBMergeNub     5.1.0 com.apple.driver.AppleUSBComposite     5.0.0 com.apple.iokit.IOSCSIMultimediaCommandsDevice     3.2.1 com.apple.iokit.IOBDStorageFamily     1.7 com.apple.iokit.IODVDStorageFamily     1.7.1 com.apple.iokit.IOCDStorageFamily     1.7.1 com.apple.iokit.IOSCSIArchitectureModelFamily     3.2.1 com.apple.driver.AppleThunderboltNHI     1.6.0 com.apple.iokit.IOThunderboltFamily     2.0.3 com.apple.iokit.IOFireWireFamily     4.4.8 com.apple.iokit.IO80211Family     420.3 com.apple.iokit.IOEthernetAVBController     1.0.1b1 com.apple.iokit.IONetworkingFamily     2.1 com.apple.iokit.IOUSBUserClient     5.0.0 com.apple.iokit.IOAHCIFamily     2.0.8 com.apple.iokit.IOUSBFamily     5.1.0 com.apple.driver.AppleEFIRuntime     1.6.1 com.apple.iokit.IOHIDFamily     1.7.1 com.apple.iokit.IOSMBusFamily     1.1 com.apple.security.sandbox     177.9 com.apple.kext.AppleMatch     1.0.0d1 com.apple.driver.DiskImages     331.7 com.apple.iokit.IOStorageFamily     1.7.2 com.apple.driver.AppleKeyStore     28.18 com.apple.driver.AppleACPIPlatform     1.5 com.apple.iokit.IOPCIFamily     2.7 com.apple.iokit.IOACPIFamily     1.4 Model: MacBookPro9,2, BootROM MBP91.00D3.B08, 2 processors, Intel Core i7, 2.9 GHz, 8 GB, SMC 2.2f38 Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In, 512 MB Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80CE, 0x4D34373142353237334448302D434B302020 Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80CE, 0x4D34373142353237334448302D434B302020 AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xF5), Broadcom BCM43xx 1.0 (5.106.198.19.22) Bluetooth: Version 4.0.8f17, 2 service, 18 devices, 1 incoming serial ports Network Service: Wi-Fi, AirPort, en1 Serial ATA Device: TOSHIBA MK7559GSXF, 750.16 GB Serial ATA Device: HL-DT-ST DVDRW  GS31N USB Device: hub_device, 0x8087  (Intel Corporation), 0x0024, 0x1a100000 / 2 USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x8509, 0x1a110000 / 3 USB Device: hub_device, 0x8087  (Intel Corporation), 0x0024, 0x1d100000 / 2 USB Device: hub_device, 0x0424  (SMSC), 0x2513, 0x1d180000 / 3 USB Device: BRCM20702 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0x1d181000 / 6 USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x821d, 0x1d181300 / 9 USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0252, 0x1d183000 / 5 USB Device: IR Receiver, apple_vendor_id, 0x8242, 0x1d182000 / 4
    What the HECK is happening and whats causing this???? How do i fix it?

    That panic was not caused by third-party software. If the problem is recurrent, the possibilities are:
    A stale or corrupt kernel cache
    A damaged OS X installation
    A fault in a peripheral device, if any
    Corrupt non-volatile memory (NVRAM)
    An internal hardware fault (including incompatible memory)
    An obscure bug in OS X
    You may already have ruled out some of these.
    Rule out #1 by booting in safe mode and then rebooting as usual. Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Post for further instructions.
    You can rule out #2 and #3 by reinstalling the OS and testing with non-essential peripherals disconnected and aftermarket expansion cards removed, if applicable. Sometimes a clean reinstallation (after erasing the startup volume) may solve a problem that isn't solved by reinstalling in place, without erasing.
    Corrupt NVRAM, which rarely causes panics, can be ruled out by resetting it.
    If your model has user-replaceable memory, and you've upgraded the memory modules, reinstall the original memory and see whether there's any improvement. Be careful not to touch the gold contacts. Clean them with a mild solvent such as rubbing alcohol. Aftermarket memory must exactly match the technical specifications for your model. Memory that is either slower or faster than specified may be incompatible.
    The Apple Hardware Test, though generally unreliable, will sometimes detect a fault. A negative test can't be depended on. Run the extended version of the test.
    In the category of obscure bugs, reports suggest that FileVault may trigger kernel traps under some unknown conditions. Most, though not all, of these reports seem to involve booting from an aftermarket SSD. If those conditions apply to you, try deactivating FileVault.
    Connecting more than one display is another reported trigger for OS X bugs.
    In rare cases, a malformed network packet from a defective router or other network device can cause panics. Such packets could also be sent deliberately by a skillful attacker. This possibility is something to consider if you run a public server that might be the target of such an attack.
    If none of the above applies, make a "Genius" appointment at an Apple Store to have the machine tested. You may have to leave it there for several days. There isn't much point in doing this unless you can reproduce the panic, or if you can't, it happens often enough that it's likely to be repeated at the store. Otherwise you may be told that nothing is wrong.
    Print the first page of the panic report and bring it with you.
    Back up all data on the internal drive(s) before you hand over your computer to anyone. If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you know how to restore, and you have at least  two independent backups.) Don’t erase the recovery partition, if present.
    Keeping your confidential data secure during hardware repair
    *An SSD doesn't need to be zeroed.

Maybe you are looking for