CS4: Flashing black screens between clips after exporting

I'm having some trouble with a particular project when exporting video, and I can't seem to track down the cause. The primary problem is flashing black screens between clips, with the additional problem of occasionally having a clip that I fade to be completely black (ie, the first clip just fades to black instead of fading to the second clip).
I say "occasionally" because the problem seems to migrate depending on what I do to try to fix it. I've noticed that if I shift the clips .1 seconds one way or another where there is a black screen, it will sometimes fix the problem, but when I fix one of them the exact same problem will pop up in another place where it didn't exist before. I can also export a few seconds of video where the problem occurs independently of the rest of the project and the issue won't occur, but will then reoccur in the same place if I export the project as a whole. All of the video is from the same source and is in the same format (.MOV from a Canon 7D). I've edited plenty of other stuff from the same source on the same computer, and the only other time I've seen this problem it's been fixed by just shifting the clips a little bit in the timeline as mentioned above. If anyone can suggest ANYTHING I can try to troubleshoot this problem I'd really appreciate it, because right now this is driving me up the wall.

I've been exporting to h.264 exclusively so far. Below is a screenshot of where one of the offending screens appears between the two clips on the timeline (the yellow in the bar up top is there because I had stepped that clip back .1 seconds like I mentioned earlier and not re-renered the sequence). I've also verified that this particular spot shows no black screen on the Program Monitor - it's a completely smooth jump from one cut to another. Please let me know if you see anything that might be causing this!

Similar Messages

  • Black screen between every clip that does not appear on timeline, only on MOV file

    Hello
    I originially had this issue  https://discussions.apple.com/message/17086997#17086997
    I have now fixed the letterboxing issue but now have this problem (I did not have this issue before) where I get a very short black screen between each clip I put on the timeline. The black screen does not show up on the timeline, it only appears once I create the file. I'm not sure if this is affected but the fact I have an external hard drive. All my footage is stored on the hard drive and i save my Final Cut Pro file on the hard drive then upload it to YouTube. I made 2 quick short MOV files to test this theory (one made from footage on my EHD and the other from footage from my desk top) neither files had the black screen in the MOV files.
    http://www.youtube.com/watch?v=z9yBH8oAnx8
    http://www.youtube.com/watch?v=gI27LlWTdXE
    These links are to my latest video I uploaded which shows the blacks clips, it's not terrible to have them but it's very annoying.
    Thank you in advance for your help and Merry Christmas

    Hello Nick, thanks for the answer.
    I have fully lengthened my timeline and the black gaps are not there to delete (they only appear once the file has been exported).
    The issue I have (I think) is that im not sure what export settings I am meant to choose to export the footage.
    My camera records in widescreen so when I place my footage onto the time line and final cut pro automatically selects the correct settings for me, this is what is chooses
    This is then the export settings that are automatically in the box when I go to export
    As my footage is 1920 x 1080 I would expect to be given an option with that in but these are the only options available
    I am not sure if this should create the black spaces between each shot.

  • Getting black screen between chunks of clip

    Hi all,
    We are developing an application which plays the series of clips one after the other. We are releasing and re-starting player object in playerUpdate block.
    We are getting black screen in between the chunk of clips while switching from one clip to another, is there any way to avoid this black screen??
    Following is the code for reference
    public void playerUpdate(Player player, String event, Object arg2) {
    try{
    main.repaint();
    //End of clip event
    if(event == END_OF_MEDIA){
    //release player
    if (player != null) {
    if(player.getState() == Player.STARTED) {
    player.stop();
    if(player.getState() == Player.PREFETCHED) {
    player.deallocate();
    if(player.getState() == Player.REALIZED || player.getState() == Player.UNREALIZED) {
    player.close();
    player = null;
    //delete played clip
    main.deleteFile("clip_"+ (main.sequencePlay - 1) +".3gp");
    //if clip is constructed then play it, else turn off PLAY status
    if(main.sequencePlay < main.sequenceDownload )
    playVideo();
    else
    main.IS_PLAYING = false;
    catch(Exception e){
    main.showAlert("Error in PlayerUpdate",e.getMessage());
    Thanks

    To avoid black screen, I'd prepare and package some pre-defined ['default' clip|http://www.dailymotion.com/films4/video/x5yxqe_climate-change-according-to-koalas_fun] within my application.
    Then, I'd play that 'default' clip while switching from one clip to another:
    //if clip is constructed then play it, else play 'default' clip to avoid black screen
    else {playDefaultVideo();} // play 'default' clip instead of setting main.IS_PLAYING = false;
    //...

  • Black flashes appear every 2 seconds after exporting from final cut pro

    http://www.youtube.com/watch?v=b8jJNnk4s3g here is my video as an example of what is happening. It only shows up after exporting and on the original AVI footage, and not my outro footage which was a .mov.
    Please can somebody help me figure out what is wrong with it as it is happening with every video I try to make using the AVI filed my camcorder records in.

    AVI is not a supported wrapper in FCP (and who knows what's the codec)
    You probably should convert the material to an natively editable format before you bring it in to FCP. Mpeg Streamclip is a good app for this purpose. What format you convert to depends on the size and framerate of the original media.
    x

  • Why is there jumping between shots after exporting to quicktime from FCP7?

    Working in FCP7, after exporting a self contained quicktime, there is jumping between shots.  I tried to remove the transitions, rerendered then re exported but the jumping is still there.  I can't figure out what's going on as it's not happening on all the sequence. Please help!!

    Hi Kippybop - sorry to hear you sharing this problem, but nope....still not sorted. 
    So far I've got all the frame rates matching sequence settings.  I've done two exports with and without transitions and there is still jumping between shots - however, it does seem to be shorter without the transition.  So whatever the problem is, is something to do with the beginning and end of clips and is made worse, and extended by adding transitions - but this doesn't apply to all clips which is really baffling.
    I've also made a new sequence and copied the original clips from the problematic sequence - still no change.  So the only impovement is the removal of video transitions, which is not exactly ideal.  I can watch the jumpy .mov on the 'finder' viewer full screen with no jumping, but all other media players show glitches between clips.
    I've done a grab of a clip and the sequence settings, which I think are correct, but please if there are any generous FCP7 experts reading, any suggestions are very much appreciated...

  • Macbook Air 2014 Black Screen w cursor after waking from sleep.

    I just purchased a brand new macbook air this past week. I noticed within the first day of using that if my machine went into sleep mode, and I hit a key to take it out of sleep mode, it would go to a black screen with my cursor for about 30 seconds.
    It does not do it every time but enough that it is annoying. I am coming from a mid 2011 mac air that did not have any issues. (only replaced for all day battery)
    Do you think this a hardware or software issue? If i swap this mac out do you think I will just encounter the same thing?
    I have read numerous posts regarding waking from sleep issues but they all seem to be affecting MacBooks purchased between 2012 and 2013.
    Any help would be much appreciated.
    Nick

    UPDATE:
    I called apple tech support and after talking a bit decided best course of action was to replace the macbook air as I was inside my 14 day buyers remorse.
    I came home and hoped all was well when this one began doing the same thing. I made an appt with the genius bar to dive further in to this and we did a complete wipe on the computer and reinstalled the OS. The "genius" said I'm probably bringing something over from my previous mac air. (even though it never had this issue).
    So after completely reinstalling the OS and setting up my macbook as new I pretty much lost all my settings and what not accumulated after 3 years with my previous mac. They did use Time Machine to at least bring my iPhoto library over and iTunes music.
    It has been exactly one day since this was completed and the computer is doing the exact same thing. ***!!!

  • Red color clips after export to H.264

    Dear friends,
    I am very new to try use Color. I sent seq. from FCP to Color, changed some clips use Color FX, and than back to FCP.
    After export seq. from FCP to H.264 for web, some of the clips appeared red.
    Thanks for any answer.
    Libor

    Do you mean red render bars or the clips are actually Red? With Color you should avoid H.264 until after any rendering. ProRes or Uncompressed are the best codecs to bounce between Color and FCP.
    -Noah
    Creator of Call Box training series for FCP and Color.

  • MBP Black Screen on restart after software update

    Hello to all, Just after dowloading today's latest updates, iTunes, Safari, something about file exchanges and Apple remote I beleive, there needed to restart and once done, no chime and black screen...
    All was perfectly fine just before, and I did backup beforehand.
    Tried to reset PRAM, restart in Single user, Safe mode, Installation Disk, all with no success.
    I will let it powered off and let it cool down for a while if it can help, but it was not particularly hot when restarted.
    Any other suggestions ??
    Many thanks !!

    I'm having basically the same problem with my PowerBook 1Ghz Aluminum 17". After running the latest security update and latest iLife patches using SU, my system boots to the local Darwin consol login. I can see my HD and all it's files, but I can't get the machine to boot back into GUI mode. Safe mode doesn't work.
    This was a newly refreshed system running 10.4.6 and ONLY iLife installed - nothing funky and no 3rd-party apps other than those pre-installed in 10.4.x.
    I've booted with the 10.4 DVD, repaired permissions (again) and repaired the drive (reported not needed). Zapping the PRAM doesn't help.
    Perhaps I have a lemon because I have had problems with this machine in the past, but only when installing major system updates between 10.3-10.4 with non-apple RAM. I don't think this is the culprit this time as the machine has been functioning fine since the last fresh 10.4 install (with some OWC RAM).
    Any ideas? Anyone have tips for what can be done in the console to repair the system?
    ARGH
    PM G5-Quad 2.5GHz | eMac G4 1.25GHz | PM G4 800MHz | PB G4 1GHz 17 | PM G4 400MH   Mac OS X (10.4.5)  

  • Black screen with underscore after updating ubuntu on Lenovo G560

    hello everybody, I'm new here. I looked for this problem online during the past few days but I haven't found a solution. I have a Lenovo G560 and I divided my hard drive into two partition, I installed Ubuntu on C:\ and Windows on D:\ and I haven't had any problem, but after updating ubuntu to version 14 my computer couldn't boot anymore. the bios loads and I see the Lenovo icon but then I just get a black screen with an underscore (not a blinking underscore), I tried booting from a bootable USB stick but the same thing happened (I put it as the first device to boot from in BIOS settings). can anyone please tell me what are my other options ? what should I try now ? thanks in advance and have a good day !

    Hi s, and welcome to Apple Discussions.
    Try this:
    Hold down the Option+Command (Apple)PR keys, boot/restart your MBP while continuing to hold down those four keys, and after you hear the startup chime for the second time, release the keys. That should reset your PRAM and resolve the issue.
    If the issue persists, while you're booted into Open Firmware, just after the prompt, type in:
    reset-nvram
    then press return, then type in:
    reset-all
    and press return. This should restart your MBP and it should go back to starting normally.

  • Black screen of death after warning "Disk 1 has the same disk identifiers as one or more disks connected to the system. "

    Hi,
    I am having the same problem / event warning, only one second after the warning occurs, I face a black screen of death leaving me with no other option than to switch off and reboot. After reboot I can work for some time but as far as I can see there is a
    spontaneous re-occurance of the same warning and subsequent black screen of death.
    It is hugely frustrating and don't seem to be able to solve it. It occurred in W8/W8.1 and W10 TP. All hardware seems fine. There are no other events that occur near the time when the BSOD occurs so I suppose its that.
    HD (SSD'S) seem to have unique identifiers so I don't understand it at all. It does not matter whether I am browsing the internet, rendering images or simply leaving my laptop untouched (M6500 DELL).
    Please help. It occurs 3 - 5 times a day and it seems unworkable.
    Mike

    Hi MAVH2014,
    Which version are you running? Do you installed all updates for current Technical Preview?
    Can you find any related events in Event Viewer?
    For your disk identifier issue, if you have checked them already, I suggest you use following command to change the value:
    Uniqueid
    http://technet.microsoft.com/en-us/library/cc730793.aspx
    Alex Zhao
    TechNet Community Support

  • Vista Black screen with Cursor after Startup

    Recently, I had a crash in a Skype call with someone, and everything went downhill from there really. I started up my computer again, and I was able to get past the welcome screen, and to a black screen with a cursor. I tried opening up task manager, it
    didn't work at the time, and eventually after my computer freezing up, I shut it off, and this time windows wanted to run check disk. So I let it, I was able to get in this time but I got a blue screen saying REGISTRY_ERROR. I was freaking out badly now, thinking
    my entire system might be corrupted, but I wouldn't give up easily.
    I started it up in safe mode, which surprisingly worked. I had a boost in moral at this point, because all my files also loaded. I started windows normally. I had the black screen thing again, but after a while I had a program pop up. I proceeded to open
    task manager.
    It opened up, and I ended the old explorer process (which was using a very small amount of memory at the time, if that matters at all) and loaded up a new one. This one worked. I am currently posting this on the same computer that has the issue.
    I seen others who had similar issues, but I could open task manager and start up explorer.exe, so I am a special snowflake among these other ones.
    I don't quite know what a good way of going about the issue would be, should I system restore? Is there a problem with the shell? I don't exactly know what I should do, any sort of information should help.
    Some other possibly unrelated things:
    Recently, my driver has been crashing (should I update that, is that the reason this is happening?)
    My files are all intact, I saved important ones. What should I do?

    Nevermind. I took matters into my own hands and it took only a single system restore to fix the issue!
    Crisis averted!
    8)

  • [P6N SLI Platinum] black screen NO BOOT after D-bracket replug [RMA-SOLVED]

    Quick setup specs;
    P6N SLI Platinum
    E6600 (box/stock 2400mhz basic)
    2x 1Gb DDR2 6400 Gskill HZ
    Sapphire ATI X1600Pro (PCI-e basic)
    Aerocool Zero DBA 620W
    (2 HDs sata, 2 Hds pata, 2 optical pata at first -all OK at first, disconnected after, so irrelevant here ,( )
    (XP Pro clean new install from start)
    I tried to check the forum old posts before trying to write that new one, but could not find any really related totally adequate posts so far (or i missed them, sorry if so, then -?). I could already find very useful informations on first aid usual 'rebooting' procedures to follow with minimum new boot configurations, d-bracket new LED signals etc. But so far no luck, all same, nothing better, nothing cured here for the stuation here. ,(( Also excuse my english if not perfect, i am not english either. ,(
    VERY bad & sad problem here... ,(((( :
    All was working perfectly great during 5 days.. the P6N SLI platinum install went GREAT initially (as normal, not a first pc built, all normally happening, so far so good, etc).... all hardwares compatible together at first (dedicated ATX 'full' 8x8 pins connector too for the cpu only for ex -all working perfect at first try. quick tensions 5V/12V under msi dual core control tool perfect too etc), was great easy going/ great strong ultra-stability feeling on the hardware side.. i was just now concentrating on the software side (no special BIOS tweaks even attempted so far, all on basics-normal e6600/ddr2 auto-settings, apart at the end ddr2 quick test -when problem occured- on 450(900?)Mhz at 2.1V, far far easy under its possible specs max anyway.. and had been working perfect for 3 days with that little ddr2 boost try -no time for special bios further tweakings now, etc), reinstalling and transfering/reorganizing slowly my necessary files/hds/softwares from old to new setup, no oc, nothing special tempted (i was planning oc, new cpu more suited fan/silver6 etc only for the end..), LAN file sharing setup done, Realtek audio setup test done, etc ; installation had been so far one of the quickest and problem free ever... explaining maybe also my fatal lack of cautioun for just (too much) 3 sec in the end after 5/- days of perfect working new ring going on.. ,((( :
    At first, i also tried to immediately install the D-Bracket too to check possible hardware install problems -very useful feature i of course thought too..and wanted to try too, "in case of"..- (installing it from quick reading of the printed manual..with no colour pic coding inside..and quick error coming from there thereafter with an initial mismatch usb/jbd1 inverted plugs connections.. *both* having the exact same pins numbers and dispositions, beeing side by side on mainboard layout.. and so able to connect both headers indifferently.. so i did not see it immediately (( .. and no way to see it otherwise as such, anyway.. ,( ), just to be sure all was ok. I noticed that LED were of course, never lightning (not normal).. but as EVERYTHING else was working fine (GLAN, sound, etc etc).. i did not bother more than that -- error checking not necessary.
    Till that fatal clumsy day i wanted suddenly to.. check the D-bracket too. ((((
    All was working well, XP pro opened for hours as usual etc..
    i had not yet totally finished to install the motherboard in the pc-case (always on desk, free in sight..)... so i could always see the connections on it. ... and i noticed that ... the colour headers codes were NOT matching (usb=yellow..).. i had just stupidly initially badly connected the D-Bracket jdb1/usb adjacent plugs (inverting them), so... And still, all had ever worked perfect.. except the D-Bracket, of course, was sending back no lights then, obviously.. so i did the fatal error.. confident all was stable enough and strong if even that initial plug error had had no consequences at all.. i did the fatal bad move to try to UNPLUG the D-Bracket connectors and put them back in right orders WITHOUT switching OFF the power supply so... like an hot USB plug, sort of, in a way. fatal error.. :( :( :(
    As soon as i began to remove the usb/jdb1 connectors and put them back in normal order... the system suddenly SHUT DOWN ... no special bad noise, no special smell.. just sudden SHUT DOWN.
    From there.. impossible ever to boot back again the so far perfectly working machine (((((((((((( , always same till now :
    i switch on the power supply.. orange led appears on motherboard (ok)... i switch on the motherboard.. green led on motherboard appears (ok)... CPU fan begins (ok), video fan begins (ok) .... and... NOTHING.. total black video screen. no more even possibility to see the BIOS. :( total dead startup .. and the fans are going on eternally, blocked eternally in that inital startup with leds on too (no sudden shut down after a few seconds.. just.. nothing)... :(
    Suprem irony.. the D-bracket LED seems to 'work' now.. "of course". Just the PC no more booting at all ^. Only thing is that only green LEDs are appearing, no red ones... simply the sequence, from start and never changing :
    1. GREEN   2. GREEN
    3. GREEN   4. (---)    (not red, just nothing -?)
    If i look in manual, it means "Testing RTC (real time clock)". I don't know exactly what it means *here*, but sounds to me it is the most basic initial first BIOS checking.. and BIOS can't be reached for even that so ; BIOS fried???? :( :(
    I tried every 'standard' things recommanded usually here in older posts, for new boots recovery attempts thereafter in such 'boot errors' situations (clear cmos button pushed in every possible ways -quick, long, quick etc..-, removing little by little everything but the very minimal least energy taxing setup; keyboard, cpu, video, motherboard; 1 ddr2 nearest cpu slot.. point).. NOTHING. Worst, i tried to boot with one of those elements missing.. exact same D-Bracket lightning from start to.. eternally (123 GREEN 4-nothing). Even tried to remove the little (cmos?) KTS lithium battery for a few hours -that could work sometimes with the old already ultra-sensitive amd/nforce2 chipset bioses problems, so i tried there too-?-; same 3 green lights and fans running and nothing else happening from there.. ((
    Always the same; total dead boot as above. black screen. no possible access to even bios panel. ,(((
    So my desperate questions, now: of course, the origin is obvious here; all happened "by my fault" when i tried 'too quickly' to 'hot-plugging' replace correctly the D-BRACKET plugs *without* switching off the power supply... all shut down suddenly when i put back correctly the usb& jdb1 headers... :( ;
    - do you think there could be any possible last HOPES to recover the situation that i had missed (a well known situation in such d-bracket handling 'common' (?) connection error, a simple trick to try i had missed ??)
    - do you think i FRIED something in the process on the motherboard ?? :( :(
    - do you think it is 'only' the BIOS (fried????) ?? :( :(
    - do you think i could have fried a specifical external key component in the process (not necessarily motherboard) : ddr2 modules, cpu, video card????? :( :(
    - is my only solution is to send the motherboard to RMA (no other ways now) ???
    please, don't hesitate to give me any possible hints to try to avoid the RMA process.
    can i avoid it, right now?
    is that possible to fry an whole board just with such a D-Bracket 'hot plug switch' (on a so far perfectly working -light-  setup - no oc, little video card, etc) ???? :( :(
    That is the only C2D Intel/ddr2 motherboard i have here around. No possibility to test elements by elements for precise error checking (cpu, ddr2 modules, video card or powersupply).
    Only things i could check so far are;
    - the power supply (aerocool 620W zeroDBA) ;
    i tested it back on my old amd xp-m nforce2 setup.. always working apparently. NOT 'fried' so, apparently. but no way of course to test for exemple the special 8x8 (or 8x4) Intel ATX cpu connector on old xp-m motherboard. But power supply NOt fried at least, apparently -?
    - the video card.
    no way for me to really test the pci-e card on other motherboard around but.. i tried a very old PCI VGA card.. that one works on old setup.. and on P6N, no effect, doesn't improve the situation. So, not sure the new pci-e video card isn't fried.. but a new video card doesn't correct the dead boot problem.. (
    No way for me to test the ddr2 or CPU directly though.
    Do you think DDR2 or CPU could have been fried in the process too ???
    or just, as i fear anyway, 'simply', the motherboard BIOS fried -??? :-(
    Really, thx for any suggestions..
    if there could be an 'hidden' trick i did not try yet to try to recover the (initially working perfectly!!! (( ) setup, WITHOUT engaging the motherboard RMA process (at least 2 or 3 weeks lost here to wait the return..online store etc..)....
    please, suggest me.. ,((
    i am *really* very sad of that stupid clumsy idea to want to 'enable' the D-Bracket.. all was working great so far.. and i lost all with just that stupid idea to try an hot plug bracket reconnection without switching off the power supply it seems.. can it be possible,sigh?? all seemed so stable before that, that i.. just lost my usual cautious just 3 sec too long it seems... :-(
    Thanks in advance
    hoping post not too long too, but i tried to expose the situation as precisely as possible; first time i ever had such a problem with a motherboard/system install.. that is quiet ironical knowing it was also the best and quickest/easiest easy going new built i ever had so far too.. till then ,( .. and all came from the 'helper' d-bracket 'luxury second hand possible boot helper diagnostic tool' checking in the end too, here.. really hoping i can avoid an RMA process.. and no other hardware elements (apart the motherboard?) could have been damaged in the process ? ,(((

    hi, thx a lot for the quick answer. sorry for the length indeed (i did not know exactly how to describe the situation.. without omitting any later possibly important details).
    Alas, i already tried that many times in following interesting asnwers on similar problems in old posts here; did NOTHING. ,(
    But after your post, i tried it again, and removed for the remaining *hours* (6/8h?) the cmos battery as suggested again *too* so -pushed again the clear cmos button etc when battery out, then when in again, then replugging the powersupply etc; NOTHING better alas too. always same, no boot, black screen, no bios. ,(
    Problem always the same, to sum up, for clarity:
    power supply on => orange motherboard led is lightning up, motherboard on => green motherboard led is lightning up, cpu/video/case fans are working up as normal and.. that's all. nothing else forever. black screen. no signal. not a single chance to get again the bios setup screen.
    another detail i omitted, maybe; keyboard lights are all lightnng up too.. and stay blocked in that state too. tested with 2 different keyboards, same. to shut down the leds, fans etc, only one solution, shut down the power supply button directly, at that stage.
    right now, i test on barebone minimal system as recommanded too;
    cpu, 1 dimm (closest cpu slot), video, keyboard. all rest disconnected.
    i of course tried to reset the cmos with the 'magical red button' many times before, with power supply cable plugged out, pushed the button trying almost every possible way so far (quick, long, long sequences, short sequences etc etc)... changed NOTHING so far -is that thing working?? ,(. and right now, same after hours with cmos battery removed too. ,(
    the d-bracket leds are always (now it is correctly plugged..) :
    123 GREEN 4 (nothing)
    "Testing RTC (real time clock)"
    another 'interesting' detail is that; those leds are appearing IMMEDIATELY after the motherboard is switched on, from start (green led appearing on P6N). and it is staying as such till the end. nothing else. i tried to connect also the case speaker ; no bips, no sound signals at all too.
    I also remind the system was WORKING like a dream during 5 days *before* i had that sudden TOTAL boot problem.... AND i touched almost nothing in the bios too all along, for initial security reasons too.. (i was concentrating on the software installs anyway right now, NOT on the oc side..). The ddr2 quick little change i did was also the ONLY change i tempted to simply test quickly some setting i already saw working without problem with that P6N and that kind of ram.. and it was working without problem so far too, so.. all the time idem. And it had been perfectly working for 3 days as such untouched from there; no problems at all (those memory modules have been seen on that motherboard largely at those specs, why i did that quick test anyway.. far under their possible max -micron chips). it was even working so well i forgot to put the setting back as default after that quick ram test.. so much it was stable too (even if i had not time to do real memtest test on that one - i did for many hours with the initial automatical default settings too, to check the ram quality, was perfect for many hours, so ok too, no bad ram initially too-; was so stable for all my XP software installs operations etc.. that i forgot it thereafter, to be true..why it stayed like that till that moment (incidently).. but i preferred to mention it 'just in case' though, yes. i also did not push at all the dimm voltages in the process, it was always far inside the specs at 2.05V to be exact -usual for that ram too up to those numbers easy for it. i did not push the ram voltages either so..).
    The problem ONLY appears when i wanted to unplug the *initially* badly connected D-bracket headers so (inverted headers.. but that caused NO problems either so far too for the system stability.. only the LEDs were of course not working so far..) : i did the error to NOT switch off the power supply. :(
    *then* immediately the system shut down... and above situation appeared. ,(
    BUT all was working perfect before.. ram setting included so. ,((
    So my simple questions now too ;
    - do you know what means *exactly* the d-bracket message 'Testing RTC" (123 GREEN, 4 nothing).. initial bios problem, isn't it?? other ways to recover it now?? ,((
    - is it a WELL KNOWN PROBLEM when we try to disconnect and replug too hastily the d-bracket headers without switching off the power supply (*my* main erorr here, it seems :( :( ) ????
    ... and of course, do you think it could have *fried* another key component (cpu, ram -?? why i reminded the setting, just in case-?-, video card? .. ) with that d-bracket initial disconnection error ... ,(
    as i said, i have no secondary c2d/ddr2 motherboard here : no way to test the cpu and ddr2 modules on another motherboard to be sure too here. :( i absolutely can't know if they have been damaged or not, here.. :( :(
    any other idea for the motherboard itself though ??? ,(
    once again, thx a lot for any suggestions and precisions on that problem (is that a COMMON well known problem with the d-bracket, when we unplug and replug it without extrem care like i did -my main inattention error it seems.. mainly because all was so stable before too.. ((( - without shutting down the power supply/system FIRST ???? can it be possible 'only' that shut down all the system??? (( )
    thx in advance again +

  • Windows 7 Black screen with cursor after boot camp partition

    So I realise this is a problem that was plaguing people a few years back. So I'll go from the very start.
    I've downloaded a copy of windows 7 professional 64bit from the Microsoft website. My optical/CD drive isn't working, so I've been unable to use it
    to install windows. I decided I'd try booting from my USB. So I have the ISO file and formatted my USB and I've downloaded the latest drivers for boot camp assistant on my mac (version 5.0.4) I'm up to date with every update for my mac. Now, I do realise that Apple doesn't recommend using a USB to load windows, but I watched this http://www.youtube.com/watch?v=8z1gqw0ougo and it explained how to get the checkbox up when you're in boot camp so you can run from your USB.
    My problem now, is that straight after I have partitioned my hard drive, it goes on to install windows but upon restarting it reaches "the black screen of death" with just the white cursor blinking. I've tried multiple times and keep getting the same result. I've even tried what Apple suggested and only have one USB device plugged in http://support.apple.com/kb/TS4536
    The details for my mac are as follows:
    Model Name:
    iMac
      Model Identifier:
    iMac10,1
      Processor Name:
    Intel Core 2 Duo
      Processor Speed:
    3.06 GHz
      Number of Processors:
    1
      Total Number of Cores:
    2
      L2 Cache:
    3 MB
      Memory:
    4 GB
      Bus Speed:
    1.07 GHz
      Boot ROM Version:
    IM101.00CC.B00
      SMC Version (system):
    1.53f13
      Serial Number (system):
    W800992A5PE
      Hardware UUID:
    A108E54E-3C53-5AF8-BFDF-2CF7ED567A74
    and it's a late 2009 model.

    I have solved this issue now but seem to have encountered another one. I solved the above issue simply by keep on trying time and time again, partitioning the hard drive and trying to install windows 7.
    Anyway, I have encountered this error: windows setup could not apply the configuration set. The WINDOWS folder cannot be found.
    Please help!

  • Black screen on bootcamp after a year of use help please

    i have a macbook pro and I installed bootcamp  on the partition i made. after a little bit less then a year it crashed and gave me a black screen when i turned it back on after a improper shut down i need help please if some one can help me i would be most greatful. 

    https://discussions.apple.com/community/windows_software/boot_camp
    The gurus are there.

  • Black screen and looping after installing and updating Mountain Lion on Macbook pro 2011 13 "i5 2.4Ghz

    After first installing the new Mountain Lion upgrading Lion on my Macbook Pro was a little slow, so I decided to format and install Mountain Lion via a thumb drive. After installation on my Macbook Pro was restarting all the time and showing a black screen with codes on the screen. I decided to reformat and reset the PRAM, and that seems to have worked. Occasionally a black screen appears with the codes and my macbook restarts again. Last night I updated the Mountain Lion and error and looping retornartam. I thought I had lost all my works, do more entered in the login screen. I turned off my macbook, went to sleep and this morning I called and finally worked Do not know what's going on in my friends' macbook not occur this problem. The macbook them is the 2011 13 "i5 2.0Ghz and another 2010 and they both work perfectly with the Mountain Lion.
    Below is the error that occurred this morning after login.
    Interval Since Last Panic Report:  1690 sec
    Panics Since Last Report:          1
    Anonymous UUID:                    67D1DCE1-6759-7BF0-6682-40BCBB09D01B
    Thu Sep 20 07:24:10 2012
    panic(cpu 2 caller 0xffffff80206b7bd5): Kernel trap at 0xffffff8020687d02, type 14=page fault, registers:
    CR0: 0x0000000080010033, CR2: 0x00007ccd02000009, CR3: 0x00000000228a6000, CR4: 0x00000000000606e0
    RAX: 0x00007ccd02000001, RBX: 0x000000000000003e, RCX: 0xffffff8020cbd000, RDX: 0x000000000000003e
    RSP: 0xffffff8110da3720, RBP: 0xffffff8110da3740, RSI: 0xffffff8031ef80c8, RDI: 0xffffff8020cbd000
    R8:  0xffffff8031ef7750, R9:  0xffffff8031ef0438, R10: 0xffffff8020cbcc20, R11: 0xffffff814c6e0000
    R12: 0xffffff8033b0ec00, R13: 0xffffff8033b0ecb0, R14: 0x00000000000000c1, R15: 0xffffff8031ef0438
    RFL: 0x0000000000010296, RIP: 0xffffff8020687d02, CS:  0x0000000000000008, SS:  0x0000000000000010
    Fault CR2: 0x00007ccd02000009, Error code: 0x0000000000000002, Fault CPU: 0x2
    Backtrace (CPU 2), Frame : Return Address
    0xffffff8110da33c0 : 0xffffff802061d626
    0xffffff8110da3430 : 0xffffff80206b7bd5
    0xffffff8110da3600 : 0xffffff80206ce4ed
    0xffffff8110da3620 : 0xffffff8020687d02
    0xffffff8110da3740 : 0xffffff802065f445
    0xffffff8110da38a0 : 0xffffff8020681b58
    0xffffff8110da3bf0 : 0xffffff802065e1b4
    0xffffff8110da3c50 : 0xffffff8020a52e4f
    0xffffff8110da3d40 : 0xffffff8020a53052
    0xffffff8110da3d70 : 0xffffff7fa1e35434
    0xffffff8110da3de0 : 0xffffff7fa1e2412f
    0xffffff8110da3e10 : 0xffffff7fa1e33afe
    0xffffff8110da3e60 : 0xffffff8020a3181b
    0xffffff8110da3ea0 : 0xffffff8020a3133e
    0xffffff8110da3f30 : 0xffffff8020a2d2d0
    0xffffff8110da3f70 : 0xffffff8020a31e99
    0xffffff8110da3fb0 : 0xffffff80206b26b7
          Kernel Extensions in backtrace:
             com.apple.driver.AppleIntelHD3000Graphics(8.0)[EAD976F9-7469-3F17-AB8E-6A039213 8DCB]@0xffffff7fa1e06000->0xffffff7fa1e67fff
                dependency: com.apple.iokit.IOPCIFamily(2.7.1)[9901C237-547C-3B52-99DE-C4870A19E2B5]@0xffff ff7fa0caf000
                dependency: com.apple.iokit.IONDRVSupport(2.3.5)[86DDB71C-A73A-3EBE-AC44-0BC9A38B9A44]@0xff ffff7fa11fc000
                dependency: com.apple.iokit.IOGraphicsFamily(2.3.5)[803496D0-ADAD-3ADB-B071-8A0A197DA53D]@0 xffffff7fa11b9000
    BSD process name corresponding to current thread: kernel_task
    Mac OS version:
    12C54
    Kernel version:
    Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64
    Kernel UUID: 69A5853F-375A-3EF4-9247-478FD0247333
    Kernel slide:     0x0000000020400000
    Kernel text base: 0xffffff8020600000
    System model name: MacBookPro8,1 (Mac-94245B3640C91C81)
    System uptime in nanoseconds: 22884276012
    last loaded kext at 22356664762: com.apple.driver.AppleMikeyHIDDriver          122 (addr 0xffffff7fa1d76000, size 20480)
    loaded kexts:
    com.apple.driver.AppleMikeyHIDDriver          122
    com.apple.driver.AppleHDAHardwareConfigDriver          2.3.1f2
    com.apple.driver.AppleHDA          2.3.1f2
    com.apple.driver.AppleUpstreamUserClient          3.5.10
    com.apple.iokit.IOUserEthernet          1.0.0d1
    com.apple.Dont_Steal_Mac_OS_X          7.0.0
    com.apple.driver.ApplePolicyControl          3.2.11
    com.apple.driver.AppleIntelHD3000Graphics          8.0.0
    com.apple.driver.AppleSMCPDRC          1.0.0
    com.apple.driver.ACPI_SMC_PlatformPlugin          1.0.0
    com.apple.driver.AppleLPC          1.6.0
    com.apple.driver.AppleBacklight          170.2.3
    com.apple.driver.AppleMCCSControl          1.0.33
    com.apple.iokit.IOBluetoothUSBDFU          4.0.9f33
    com.apple.iokit.BroadcomBluetoothHCIControllerUSBTransport          4.0.9f33
    com.apple.driver.AppleMikeyDriver          2.3.1f2
    com.apple.driver.SMCMotionSensor          3.0.2d6
    com.apple.driver.AppleSMCLMU          2.0.2d0
    com.apple.driver.AppleIntelSNBGraphicsFB          8.0.0
    com.apple.driver.AppleMuxControl          3.2.11
    com.apple.driver.AppleUSBTCButtons          235.4
    com.apple.driver.AppleUSBTCKeyEventDriver          235.4
    com.apple.driver.AppleUSBTCKeyboard          235.4
    com.apple.driver.AppleIRController          320.15
    com.apple.driver.AppleFileSystemDriver          3.0.1
    com.apple.AppleFSCompression.AppleFSCompressionTypeDataless          1.0.0d1
    com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
    com.apple.BootCache          34
    com.apple.iokit.SCSITaskUserClient          3.5.1
    com.apple.driver.XsanFilter          404
    com.apple.iokit.IOAHCIBlockStorage          2.2.2
    com.apple.driver.AppleSDXC          1.2.2
    com.apple.driver.AppleUSBHub          5.2.5
    com.apple.iokit.AppleBCM5701Ethernet          3.2.5b3
    com.apple.driver.AppleAHCIPort          2.4.1
    com.apple.driver.AirPort.Brcm4331          602.15.22
    com.apple.driver.AppleFWOHCI          4.9.6
    com.apple.driver.AppleUSBEHCI          5.4.0
    com.apple.driver.AppleUSBUHCI          5.2.5
    com.apple.driver.AppleEFINVRAM          1.6.1
    com.apple.driver.AppleSmartBatteryManager          161.0.0
    com.apple.driver.AppleACPIButtons          1.6
    com.apple.driver.AppleRTC          1.5
    com.apple.driver.AppleHPET          1.7
    com.apple.driver.AppleSMBIOS          1.9
    com.apple.driver.AppleACPIEC          1.6
    com.apple.driver.AppleAPIC          1.6
    com.apple.driver.AppleIntelCPUPowerManagementClient          196.0.0
    com.apple.nke.applicationfirewall          4.0.39
    com.apple.security.quarantine          2
    com.apple.driver.AppleIntelCPUPowerManagement          196.0.0
    com.apple.driver.DspFuncLib          2.3.1f2
    com.apple.iokit.IOAudioFamily          1.8.9fc10
    com.apple.kext.OSvKernDSPLib          1.6
    com.apple.iokit.IOSurface          86.0.3
    com.apple.iokit.IOBluetoothFamily          4.0.9f33
    com.apple.driver.AppleThunderboltEDMSink          1.1.8
    com.apple.driver.AppleThunderboltEDMSource          1.1.8
    com.apple.driver.AppleThunderboltDPOutAdapter          1.8.5
    com.apple.driver.AppleHDAController          2.3.1f2
    com.apple.iokit.IOHDAFamily          2.3.1f2
    com.apple.driver.IOPlatformPluginLegacy          1.0.0
    com.apple.driver.IOPlatformPluginFamily          5.2.0d16
    com.apple.iokit.AppleBluetoothHCIControllerUSBTransport          4.0.9f33
    com.apple.driver.AppleSMBusController          1.0.10d0
    com.apple.driver.AppleSMBusPCI          1.0.10d0
    com.apple.iokit.IOFireWireIP          2.2.5
    com.apple.driver.AppleSMC          3.1.4d2
    com.apple.driver.AppleGraphicsControl          3.2.11
    com.apple.driver.AppleBacklightExpert          1.0.4
    com.apple.iokit.IONDRVSupport          2.3.5
    com.apple.iokit.IOGraphicsFamily          2.3.5
    com.apple.driver.AppleThunderboltDPInAdapter          1.8.5
    com.apple.driver.AppleThunderboltDPAdapterFamily          1.8.5
    com.apple.driver.AppleThunderboltPCIDownAdapter          1.2.5
    com.apple.driver.AppleUSBMultitouch          235.7
    com.apple.iokit.IOUSBHIDDriver          5.2.5
    com.apple.driver.AppleUSBMergeNub          5.2.5
    com.apple.driver.AppleUSBComposite          5.2.5
    com.apple.iokit.IOSCSIMultimediaCommandsDevice          3.5.1
    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.5.0
    com.apple.iokit.IOSCSIArchitectureModelFamily          3.5.1
    com.apple.driver.AppleThunderboltNHI          1.6.0
    com.apple.iokit.IOThunderboltFamily          2.1.1
    com.apple.iokit.IOEthernetAVBController          1.0.2b1
    com.apple.iokit.IOUSBUserClient          5.2.5
    com.apple.iokit.IOAHCIFamily          2.2.1
    com.apple.iokit.IO80211Family          500.15
    com.apple.iokit.IONetworkingFamily          3.0
    com.apple.iokit.IOFireWireFamily          4.5.5
    com.apple.iokit.IOUSBFamily          5.4.0
    com.apple.driver.AppleEFIRuntime          1.6.1
    com.apple.iokit.IOHIDFamily          1.8.0
    com.apple.iokit.IOSMBusFamily          1.1
    com.apple.security.sandbox          220
    com.apple.kext.AppleMatch          1.0.0d1
    com.apple.security.TMSafetyNet          7
    com.apple.driver.DiskImages          344
    com.apple.iokit.IOStorageFamily          1.8
    com.apple.driver.AppleKeyStore          28.21
    com.apple.driver.AppleACPIPlatform          1.6
    com.apple.iokit.IOPCIFamily          2.7.1
    com.apple.iokit.IOACPIFamily          1.4
    com.apple.kec.corecrypto          1.0
    Model: MacBookPro8,1, BootROM MBP81.0047.B27, 2 processors, Intel Core i5, 2.4 GHz, 8 GB, SMC 1.68f98
    Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In, 512 MB
    Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1333 MHz, 0x0198, 0x393955353432382D3034302E413031472020
    Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1333 MHz, 0x0198, 0x393955353432382D3034302E413031472020
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xD6), Broadcom BCM43xx 1.0 (5.106.98.81.22)
    Bluetooth: Version 4.0.9f33 10885, 2 service, 11 devices, 1 incoming serial ports
    Network Service: Wi-Fi, AirPort, en1
    Serial ATA Device: Hitachi HTS545050B9A302, 500,11 GB
    Serial ATA Device: MATSHITADVD-R   UJ-8A8
    USB Device: hub_device, 0x0424  (SMSC), 0x2513, 0xfd100000 / 2
    USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd110000 / 3
    USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x8509, 0xfa200000 / 3
    USB Device: hub_device, 0x0424  (SMSC), 0x2513, 0xfa100000 / 2
    USB Device: BRCM2070 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0xfa110000 / 5
    USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x821a, 0xfa113000 / 7
    USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0252, 0xfa120000 / 4
    Is there a hardware problem?
    thank you

    Before you upgrade, make sure all your software supports it based on post July, 25, 2012 reports on
    http://roaringapps.com/apps:table
    Reports prior to this date are unreliable, as they are likely with beta releases of Mountain Lion to developers. Other pitfalls to realize include:
    https://discussions.apple.com/docs/DOC-3761

Maybe you are looking for