AudioPrefetch.cpp-87 Error

Hi everyone, I've been having this error: Src\AudioRender\AudioPrefetch.cpp-87 with Premiere CS5. It happens when I zoom in the timeline past a certain point. Does anyone have any suggestions?

>AudioRender
I would suggest you provide project and file DETAILS... actually, LOTS of details
Work through all of the steps (ideas) listed at http://ppro.wikia.com/wiki/Troubleshooting
If your problem isn't fixed after you follow all of the steps, report back with ALL OF THE DETAILS asked for in the FINALLY section, the questions at the end of the troubleshooting link... most especially the codec used... see Question 1

Similar Messages

  • ..\..\Src\AudioRender\AudioPrefetch.cpp-99   error message and what caused it.

    I found that when I zoomed into the sequence a lot using the +- keys, that the error message "..\..\Src\AudioRender\AudioPrefetch.cpp-99" kept jumping out at me. It was the last 3 steps of zooming in or out that brought the error message up on screen - a lot of times. It was only happening in one sequence in a particular project. I tried the suggestions for similar error messages that I found on this forum, but I eventually realised that in this project I had a WMV file (PowerPoint exported as a WMV file) which also had *audio* with it. (All the other sequences have WMV files but without audio.)
    Going to the troublesome sequence and deleting the sound track from the WMV file fixed the problem. Next, I deleted the WMV file and put it back again. No error message. I then dropped the audio level to zero using the yellow line and the problem came back.
    There is one other thing, the PowerPoint WMV file is 30fps and I’m in PAL land, so I interpreted the frame rate to 25fps. (So that PowerPoint transitions and movements etc. are smoother). I re-imported the original 30fps WMV file and put that in the sequence as 30 fps. Lowered the audio level to zero, and zoomed into the sequence. No error messages.
    So it looks like a combination of WMV file, interpreting the footage and lowering the audio level to zero that caused this problem.
    Do I need to post this somewhere so that Adobe gets to see this bug? (OK it is a rather unlikely combination of events.)

    It's not as unlikely as you think. I just ran into the same exact thing. But I don't think it's the WMV.
    I'm using footage from a Canon 5D Mark III shot at 60fps, then interpreted to 23.976 and dropped in a 23.976 timeline. I've also adjusted the volume on some of these clips, but not down to -∞. Since the error is "...AudioRender/AudioPrefetch.cpp-99" it makes sense that this is an audio related issue. I have also noticed that in the timeline, my yellow levels line and waveforms disappear when this error comes up.
    So far I've been able to get around this bug by copying the clips into a new timeline, but this eventually comes back again.
    The one question I have, is are you editing from an external hard drive? I've been editing at work off an external, then backing it up and working off internal drives when I get home. My external drive has been disconnecting itself lately, but it's never been around or at the same time as this error. Thought I'd still check with others though.

  • Regarding Adobe Media Encoder CS4 [../../src/component/component factory.cpp-119] error.

    Hi iam using adobe premire cs4 when i finished editing nd tried to xport my video as usual adobe media encoder opened for encoding . i clicked start quere and i recieved this [../../src/component/component factory.cpp-119] error. every time i try to encode this error appears. please help me solve this problem ASAP.

    CPU:
    Graphics Card and Motherboard
    Memory and Ram:
    And 250gb of hdd and 115gb free

  • Where is a link to the Premiere Pro CC 2014.1 (8.1) update? - Can I get help with the ticktime.cpp-290 error?

    Ola to precisando do premiere versao 8.1 caravan consegue o link?
    Message was edited by: Kevin Monahan
    Reason: needed better title

    Hi Kevin,
    I posted about the same problem (TickTime.cpp-290 error) in another thread, but since you're asking here specific questions to resolve it, I'm answering it here.
    Re: Debug Event: [...\ ...\src\TickTime.cpp-290]
    What were you doing when this error started to occur?
              Nothing special I remember. The only thing I do recall, is:
              I was working with Premiere Pro (where the main project is), After Effects but rendering some PNG sequence, and Adobe Media Encoder. I sent from AE to AME a project to render. Configured 2 outputs (PNG & MP4). The same way I sent from PP a project to render and one error occured. Unfortunately I didn't write down the error, but it was like a path C://AME_64/something. But the AME queue updated and everything seemed OK. I close AME to be sure that the error wouldn't be the source of future error during rendering, and relaunched it. And at that time I couldn't open it. I got the error "Adobe Media Encoder has encountered an unexpected error and cannot continue". The only way I found to resolve this is to remove the directory /Users/%USERNAME%/My Documents/Adobe/Adobe Media Encoder/8.0/". The problem seems to appear when I save the queue. And since that time, Premiere do the TickTime.cpp-290 error.
              Another thing I noticed, don't know if it was there before, is, the AEP file in AME queue setttings displayed framerate as "25 / 29.97 / 30 / ...", a 2 digits number for the framerate. But suddenly (I thought first it was because of the Premiere Pro file being added to the queue, but no because it appended after without it), it was displayed as "25 000 / 29 970 / 30 000", a 5 digit number.
              After that, the TickTime.cpp-290 appeared. Sometimes when opening project, sometimes and resetting or changing the workspace (because it was messed up), sometimes when closing.
    Do you have iCloud installed?
              No.
    Is this a Premiere Pro CC 2014.0 or Premiere Pro CC 2014.1 project that was updated to Premiere Pro CC 2014.2? If so:
              It started long time ago a draft in CS6, but since I reopen the project, I saved new versions in Premiere Pro CC 2014.2 (not sure if I have other version like 2014.1 or 2014.0). Is there a way to know which 2014 version are my files? If I look into the XML I only saw Version="28"
    Do you have a copy that can be opened in an earlier version?
                  An old draft version in CS6. But that version has footage in different framerate and not all be interpreted at the timeline framerate.
    Do you get the same error in that earlier version?
                   No error here, the file opens properly.
                  Additional info: I tried to open the 2014.2 file on another computer (where PP 2014.2 is installed) and same problem (this computer is on Win7 64-bit)
    Did you use any unusual footage types in your project?
         I used MOV (Animation), MP4 (H264), and PNG sequence. The framerates of the footages are 24,25,30 and 60fps (but everything has been interpreted in 30fps)
    If you remove them, do you still get an error?
                  When I had the error, but not when I open the project file, I resave the file removing anything not interpreted in 30fps (because at that time I still had footage interpreted in their original framerate). I was able to work for some time, but now I can't open it anymore despite that.
    Was the fps interpretation changed in any of the clips?
         Since the error appeared, and because I saw in another thread that it could be related to footage of different framerate, my timeline is now in 30fps and all the footage have been interpreted in 30fps. Footage are MP4, MOV, PNG sequence in 24, 25, 30 & 60fps.
    If so, restore them to their original fps and see if you still get the error.
                  Unfortunately, since I can't open the project anymore, I can't test that.
    Did you use Warp Stabilizer?
              No.
    Do you have any browser plug-ins?
              What do you call browser plug-in in Premiere?
    Are there any third party plug-ins used?
              I have Magic Bullet Looks 2, and I'm using it on this project.
    If so, remove the effect from those clips and see if it improves the situation.
                  Unfortunately, since I can't open the project anymore, I can't test that.
    Some additional infos on my computer.
    I use Windows 8.1 (64-bit),  all Adobe softwares installed have the last update (for video apps, it's 2014.2)
    The language settings are configured in French, but Windows and CC apps are in English.
    If needed the 2014.2 project file is here:
    https://dl.dropboxusercontent.com/u/68413846/showreel19_30fps.prproj
    Thanks in advance to help us to resolve this weird bug.
    Christophe.

  • PProHeadless.exe, FileImporter.cpp-1132 errors exporting short video

    Hi,
    I'm getting an error when I try and export my 3 minute movie. The error goes as follows:
    PProHeadless.exe
    AppVer: 0.0.0.0
    ModName: dvacore.dll
    Mod Ver: 2.0.0.0
    Offset: 002de00
    Encoding Failed
    Error compiling movie
    Unknown Error
    I tried removing the two clips from the timeline at which it always seemed to crash, and it did export but only as an mp4. I tried re-converting those clips thinking they were corrupted, and still get the error with the new clips. In this same area there are crossfading .jpgs, but they have been sized to 72dpi and are concurrent with the video size, so this shouldn't be the issue, correct?
    It also has listed a FileImporter.cpp-1132 error.
    I've never had this issue before. I'm running Premiere Pro CS4 on a windows xp machine. Should I be converting these videos to a specific format before using them in the timeline? Right now I'm importing them as mpeg2, after converting them in Media Encoder.
    Thanks for your help!
    -J

    Everyone may have already got what they wanted from the answers given in the post but I thought I'd add my PAL experience of this.
    I tried to media export a timeline to one large mixdown file. (blackmagic mjpeg) the timeline had simple premiere titles fading up and down to black before each video module.  The media encoder worked fine but none of the dissolves from timeline to title worked - they translated as cuts in the mixdown.  In the end I dropped premiere generated black video over the titles and used variable opacity to bring them in and out.  This worked fine and proves that you can export with black at the front.
    What it proves however is that CS4 really is working differently to CS3 in lots of ways.
    As far as media encoder is concered, I'm sure this is a grandmother sucking eggs business but it's critical for performance that the USE PREVIEW FILES option in the settings box is selected.  Otherwise CS4 starts to re-render everything and seems to be much slower at doing it than a basic timeline render. Including metadata files doesn't seem to offend too much but I only evr include this when I'm exporting final versions anyway.

  • Src/Win/WinFile.cpp-754" error

    I’m using PPRO in Production Premium CS4.
    I’m getting the “Src/Win/WinFile.cpp-754” error” when I AME starts or shortly after it starts. System worked fine since I installed the CS4 upgrade 4 months ago but today a project is due and this happens.
    My system: Dell Precision 690, 3Ghz Xeon processor, 4 GB ram, Internal HDs (1) 300 and (1) 400 GB, External HDs (2) 1 TB.
    I’ve read and searched the forums and now I’m frustrated and in need of some help. Has anyone found definitive solution to this “Src/Win/WinFile.cpp-754” problem?
    Thanks,
    Tony

    Hi,
    I searched the internet with that error mssg and it seems a lot of them have to do with video card drivers. There was some information about matrox drivers and that problem on the internet...
    Also some 'Axio' card driver problems related to that error message...
    Have you recently updated your video card drivers ?
    Rod

  • Premiere Elements Timecode.cpp-1014 error when adding media

    Software: Premiere elements 11
    Camera: Sony DCR TRV22E
    OS: Windows 7
    When selecting add media I get: [..\..\Src\Timecode.cpp-1014] error multiple times, when the capture window eventually comes up it says the capture device is offline.
    This happens not only when the camera is connected and powered but also when camera is not connected.
    I have tried the different IEEE1394 drivers available in windows 7 and none of them work.
              1394 OHCI Compliant Host Controller
              1394 OHCI Compliant Host Controller (Legacy)
              VIA 1394 OHCI Compliant Host Controller
    The connection to the camera through firewire is ok because I can download video from it using Nero Video Essentials, I just cannot do it through Premiere Elements 11.
    Message was edited by: foradobeuse
    Oops, I put the wrong error code in the title, it should be timecode.cpp-1014

    There is absolutely no reason you can't use this camcorder with Premiere Elements. It's a miniDV! There's clearly something going on with your computer that's unrelated to Premiere Elements.
    For instance, this appears to be a European camcorder. Is your program installed for PAL rather than NTSC? It's an obvious question but one that needs to be asked.
    Also, PLEASE try using the free program WinDV to capture your video over a FireWire connection. If it does,we know something is wrong with your Premiere Elements installation. If not, we know it's something more basic.
    Nero, by the way, it notorious for not sharing certain hardware resources. I've never known it to block access to the FireWire -- but I suppose it's possible.
    So, please, instead of just flipping off Premiere Elements, do a little basic troubleshooting. Problems with a FireWire/miniDV capture are virtually unheard of, and I'm really curious what's going on with your system!

  • ImporterProcessClient.cpp-127 Error . Premiere Cs 4 was tun ??

    ImporterProcessClient.cpp-127 Error hatte schon  mal jemand dieses Problem ?? habe mastercollection cs 4 installiert !  laüft unter win 7 !
    habe kein uptade oder eine sonstige veränderung vorgenommen.
    selbst neuinstallation der collection brachte keinen erfolg habe auch clean skript verwendent !
    hat noch jemand nen tipp ?? habe schon gegooglt nur zu dem problem gibts 
    scheinbar keine vernünftige lösung und vor allem tritts aus den unterschiedlichsten gründen auf....
    bei mir kam es wohl im zusammenhang mit bilddateien die premiere nicht  unterstützt, die sind mittlerweile aber raus aus dem projekt u wie  gesagt 2 mal schon neuinstalliert !!!!! 
    firewall ist aus und virenschutz gibts auch keinen der stören könnte....
    mir fehlt nix mehr ein ausser ein komplette neuinstallation des systems....

    Well, the Media Encoder actually works if I choose any video that's NOT in Premiere and want to encode it into something else. Apparently it can't find the media source location. Here is the error message.  Although, I have never changed the location and it has worked fine until I had the previous problem. The only other thing I can think of is that I permanently trashed m prefs folder (*doh* slaps forehead).  Otherwise, nothing has changed and it will not encode anything I exported nor send it to Encore.
    Thanks,
    Nik
    ERROR MESSAGE BELOW:
    - Source File: C:\Users\DANIKO\AppData\Local\Temp\New Cat Videos_4.prproj
    - Output File: F:\ADOBE PREMIERE PROJECT FILES\DEMO REEL Project Files\Sequence 03.wmv
    - Preset Used: NTSC Source to High Quality Download
    - Video:
    - Audio:
    - Bitrate:
    - Encoding Time: 01:39:00
    3/7/2010 1:14:25 PM : Encoding Failed
    Could not read from the source. Please check if it has moved or been deleted.
    - Source File: C:\Users\DANIKO\Desktop\Cat Videos (early 2010)\MVI_0901.AVI
    - Output File: C:\Users\DANIKO\Desktop\MVI_0901 test.wmv
    - Preset Used: NTSC Source to High Quality Download
    - Video: 720x480, 29.970 [fps]
    - Audio:  96 kbps, 48 kHz, stereo VBR
    - Bitrate: Compressed, VBR, 2 Pass, Audiences:1, Avg 1500.00 [kbps]
    - Encoding Time: 00:00:10
    3/7/2010 1:21:17 PM : Encoding Failed
    The Operation was interrupted by user
    - Source File: C:\Users\DANIKO\AppData\Local\Temp\New Cat Videos_5.prproj
    - Output File: F:\ADOBE PREMIERE PROJECT FILES\DEMO REEL Project Files\Sequence 03.avi
    - Preset Used: NTSC DV
    - Video:
    - Audio:
    - Bitrate:
    - Encoding Time: 00:00:28
    3/7/2010 1:21:35 PM : Encoding Failed
    Could not read from the source. Please check if it has moved or been deleted.

  • HelloClient.cpp(36) : error C2440: 'initializing' : cannot convert from 'class CORBA_WStringValue *' to '

    "HelloClient.cpp(36) : error C2440: 'initializing' : cannot convert from 'class CORBA_WStringValue *' to 'const char *'"Hi I am getting this error when I try toprint the value which I am getting fromthe RMI Implementation class.Thanks.

    What orb are you using in the client?
    LP wrote:
    "HelloClient.cpp(36) : error C2440: 'initializing' : cannot convert from 'class CORBA_WStringValue *' to 'const char *'"Hi I am getting this error when I try toprint the value which I am getting fromthe RMI Implementation class.Thanks.

  • Winfile.cpp-758 error

    I have my project using dynamic link from PPro.  So, as it is transcoding my BR project, I get this winfile.cpp-758 error. I then let it debug and it will continue, but the output BR file just has video, no audio.  Any ideas?  I found nothing on this on my search.
    Thanks

    For CS4 you must update the Roxio component http://forums.adobe.com/thread/400484?tstart=0
    More on Encore and Roxio http://forums.adobe.com/thread/528582?tstart=0 or direct to
    http://kb.roxio.com/search.aspx?URL=/content/kb/General%20Information/000070GN&PARAMS 
    Plus, Long File Names or odd characters Cause Crashing http://forums.adobe.com/thread/588273
    And #4 Here http://forums.adobe.com/thread/666558?tstart=0
    And This Message Thread http://forums.adobe.com/thread/665641?tstart=0 
    An Encore Tutorial http://www.precomposed.com/blog/2009/05/encore-tutorial/

  • [..\..\Src\pp\\PPixHandleUtilities.cpp-114] Error

    Im sorry if this is the wrong place to post this but I dont know what else to do. When i use AME or Export as Movie Im getting the ugly [..\..\Src\pp\\PPixHandleUtilities.cpp-114] error! Afterwards i get an unable to compile error. i have scoured the internet looking for answers. I have tried a few of the solutions but nothing seems to work. I have a project for my college class im working on and i need to figure this out. To start over would be a hefty process that does not sound like something i want to do. Any advice on what i can do or where i should to look for answers would be great! Thanks!
    So far i have tried zooming all the way in on my tracks and looking for blank spots, i have tried adding a transparent video on the top layer spanning the entire sequence, i have tried uninstalling and reinstalling, importing my project into another project, using different project setting, different export settings, and so far nothing has seemed to work.
    I know its ancient but im running CS3 and my machine is running AMD Quad-Core Processor with 8GB ram.

    Some general reading... and then some questions
    Run as Administrator http://forums.adobe.com/thread/771202
    -Set to always "run as" via icon http://forums.adobe.com/thread/969395
    Odd Errors http://forums.adobe.com/thread/670174
    Long File Names or odd characters cause problems
    Read http://forums.adobe.com/thread/588273
    And #4 http://forums.adobe.com/thread/666558
    And This Message Thread http://forums.adobe.com/thread/665641
    Read Bill Hunt on a file type as WRAPPER http://forums.adobe.com/thread/440037
    What is a CODEC... a Primer http://forums.adobe.com/thread/546811
    What CODEC is INSIDE that file? http://forums.adobe.com/thread/440037
    Report back with the codec details of your file, use the programs below... a screen
    shot works well to SHOW people what you are doing
    For PC http://www.headbands.com/gspot/ or http://mediainfo.sourceforge.net/en
    For Mac http://mediainspector.massanti.com/
    http://blogs.adobe.com/premiereprotraining/2011/02/red-yellow-and-green-render-
    bars.html
    If you have a red line over the timeline after importing a video and before adding any
    effects... your project is wrong for your video... read above about codecs
    Once you know exactly what it is you are editing, report back with that information...
    and your project setting, and if there is a red line above the video in the timeline,
    which indicates a mismatch between video and project

  • How to repair projects that get a "TickTime.cpp-290" error after opening a specific project.

    This is a guide to repair projects that get a "TickTime.cpp-290" error after opening a specific project.
    Prerequisites:
    Project repair tool (download link below)
    WinRAR or any file archiver
    Damaged project file
    As an example, let's say the name of my damaged project is 'test.prproj'
    Steps:
    1. Download the project repair tool here: https://www.dropbox.com/s/3fyja0ws7l5gkbt/pp-repair-0.1.35.zip?dl=0
    2. Rename your project file extension from 'test.prproj' to 'test.zip' (a warning appears saying the file might become unusable. Do not be concerned about the warning. Click OK and move to the next step.)
    3. Extract the contents of 'test.zip' to a location on your computer. (Right click on the file and select ‘Extract files’ > Choose a location > Click OK).
    4. Go to the extracted location. Note the file 'test' has no extension.
    5. Rename the file, 'test.prproj'.
    6. Launch the project repair tool, and then select the file 'test.prproj' (the one that we renamed in the last step).
    7. Deselect all the check-boxes in the project repair tool.
    8. Click the Repair button.
    9. After a few seconds you see a message saying 'Success'.
    10. Open the repaired file in Premiere Pro and then reset the workspace. Choose Window > Workspace > Reset Current Workspace.
    11. Click the Save button to reduce the project size.
    12. Your project is now repaired.
    NOTE: If a file containing letters such as ã, å, ê, í, ú don’t repair, rename the file to something that doesn't contain these letters.

    Hi Rameez,
    first of all thanks a bunch for the tool - it saved our neck this morning on a tight deadline.
    One minor note: I did get a message that the (already uncompressed + renamed) file is not uncompressed until I ran the tool as Administrator so you might want to add that to the FAQ entry...
    Other than that I'm very much interested in what triggers this bug so we can potentially prevent it.
    Background:
    Specs: Windows 8.1, German locale (ie comma is decimal symbol), Premiere Pro CC 2014.2 installed in English
    My colleague who ran into the TickTime.cpp-290 error remembers having created a new workspace while working on the project. That seems to have triggered the issue as we haven't had any trouble on other projects yet. It also got saved into the project file:
    <MZ.Project.WorkspaceName>Bearbeitung</MZ.Project.WorkspaceName>
    Any autosaves after he added the workspace were corrupted as well while the ones dating back to earlier still open fine.
    I'd like to mention that Premiere did import previous (German language) workspaces - dating back until CS5. Not sure if that comes into play.
    On the other hand, the debug log looks like there only is an issue with the decimal symbol:
    10:08:06: Input: C:/temp/trouble/uncompressed/final.prproj
    10:08:06: Path: C:/temp/trouble/uncompressed Basename: final Extension:prproj
    10:08:06: 19852-> from: <PlaybackSpeed>0,069148936170212769</PlaybackSpeed>
    10:08:06: 19852-> to:   <PlaybackSpeed>0.069148936170212769</PlaybackSpeed>
    10:08:06: 23970-> from: <PlaybackSpeed>0,0062741915889604422</PlaybackSpeed>
    10:08:06: 23970-> to:   <PlaybackSpeed>0.0062741915889604422</PlaybackSpeed>
    I really need to make sure that this is no general problem with German locales as we have multiple users on this kind of config and can't afford projects breaking.
    Or do we "just" need to watch out to get rid of the old workspaces? I'm a little puzzled to be honest.
    Maybe it helps to mention that we are on CC Enterprise
    Best regards,
    Mike

  • .\TixRestore.cpp(71): Error FC060002 - Errors while trying to restore A215-S5807

    Bro-in-law wiped HDD and tried to load XP Pro. Didn't work, no drivers. I ordered retore disks. Tried Toshiba Recovery Wizard. Got
    Toshiba Recovery Wizard
    <Error>
    An error has occurred.
    ERROR: 03-EEEE-0000
    An error has occurred.
    Please press [OK] to turn off the computer.
    Did -
    1. Boot the Recovery disc or HDD image and select System Recovery Options.
    2. Follow the prompts until you get to the menu and then select a command prompt.
    3. Copy the \zzimages\zzimages directory for all recovery discs to a temp directory on the hard drive (c:\temp).
    4. Change to the Bin directory on the first recovery disc and run "tosimagex /apply c:\temp\preinst.swm 1 c:\ /ref c:\temp\preinst*.swm" without the quotes.
    (Of course I had to create the c:\temp folder.) I tried without also.
    Got -
    WIM File: c:\temp\preinst.swm(1)
    Dst File: c:\
    App Name: /ref
    Total Parts: 11
    Add splited image: c:\temp\preinst2.swm
    Add splited image: c:\temp\preinst3.swm
    .\TixRestore.cpp(71): Error FC060002
    D:\BIN>
    I talked to TOshiba tech support and after going through this for a while. The tech ended up saying that the MBR is messed up and that I needed to buy a new hard drive. I can still access it via command prompt and SYstem Recovery. I booted up to DOS prompt with a WIN98 CD and did FDisk and format. Still got error. Tried startup repair. Received an "does not have a valid system partition" error.
    I booted up to Ultimate Boot CD. Fixed partition problem. Now getting BOOTMGR missing. It has been too long since I worked computer support and do not know what to do to get this fixed. I find it hard to believe that I need  new hard drive if I can do all of this with it. Please help.
    Thank you.

    hi. Here's the answer to your problem i think. when you are copying the zzimages files to the temp folder you have to copy the zzimage files from ALL the restore disks, or you'll get that error message. and you can use the bootrec tool to fix the boot record. here's a link that tells how to do that. good luck. http://support.microsoft.com/kb/927392

  • CPP Assertion Error when navigating in Obiee 11g

    Hi,
    I have a report which uses SQL filters and I am trying to navigate from this report to another page.
    And I see the following error :
    Dashboard Display Error
    Assertion failure: isXsiTypeSqlExpression(rExpr) at line 67 of C:\ADE\aime_bi\bifndn\analytics_web\main/project/webreport/exprformulautils.cpp
    Error Details
    Error Codes: ACIOA5LN
    Some forums mentioned that re-creation of saved SQL filters would help but it didn't.
    Has anyone faced similar errors ?
    Thanks for any pointers.
    - Sujana

    Sujana,
    This is a bug in 11g, apply patch 12561330.
    Rgds,
    Dpka

  • After System Update last night, the system will not boot with IOPlatformExpert.cpp:1504 error

    I have had Lion for a 2, 3 months on the iMac 27 inch purchased last October (2011). Last night I chose to update the system, and deselected iMoves update because it was 1GB, and chose only 4 updates, including iTunes, Safari (i think)... But the update says error, and ask to restart the system (it won't restart itself, so I waited 30 minutes, and then pressed the Power button for 10 seconds, to let it power down, and press Power again to power it up).
    However, after that, the system failed to boot up, showing a
    panic(cpu 0 caller .....)" "Unable to finder driver for this platform: \"ACPI\". ... xnu-1699.26.8/iokit/Kernel/IOPlatformExpert.cpp:1504
    This is not typical of the upgrade process. So I searched the Internet forIOPlatformExpert.cpp:1504 and some people said it is a hard drive error, but then I powered down and pressed Options when booting up, and was able to boot to Windows 7 (bootcamp)... and was able to boot to the "Recovery", which let me choose
    Restore from Time Machine Backup
    Reinstall Mac OS X
    Get Help Online
    Disk Utility
    what should I do now to fix it so that it can boot again?

    This error is caused by one of the updates you applied, namely the Thunderbolt Software Update 1.2.  Many people have been affected by it, including me.  I did what Linc Davis has suggested above to fix it.  The most extensive discussion about the problem, with ways to fix the problem, is here:
    https://discussions.apple.com/thread/4020399?start=0&tstart=0

Maybe you are looking for