Black screen upon wakeup after longer sleep...

In the last 2 months or so, I have seen my MacMini 2011 OSX 10.7.3 crashing withing a minute of wakeup, after sleeps of more than 2-3 hours.
Sometimes the Black screen occurs almost immediately, sometimes it takes up to a minute after the desktop appears (after logging in).
This did not occur until I got 10.7.3 and only within the last 2 months.

Anyone?
I am up to 100 crashes upon wakeup now. Various versions of Lion 10.7.x. I have done clean installs as well.
Does anyone else get the black screen of death shortly after wakeup from sleep?
This never happened on 10.7.0, 10.7.1 or 10.7.2
Crashes happen in both 10.7.3 and now 10.7.4, and for sleeps as short as 90 minutes.

Similar Messages

Macbook freezes upon wakeup after extended sleep

I have been having an issue with my Macbook that just started occurring within the last month or so. I am unable to relate it to any specific software update that I might have done, but in my trouble-shooting I have a strong hunch that it is a preference issue.
The issue happens when the Macbook is left in a state of sleep mode for a length of time greater than 1 hour, this is especially true when closing the clamshell to put the computer to sleep. Some things I can do to extend this time are listed farther below.
When returning to the computer it seems to be in the proper sleep mode. The light is pulsing as it always has. The issue is upon waking, opening the clamshell the screen flickers and then freezes up leaving the screen black and the system completely unresponsive. This is not a failed back light that does not come on, absolutely nothing works in this frozen state, caps lock light does not work, volume does not work, pressing the power button and return does not allow it to restart. Absolutely nothing works.
At this point I have two options, hard reset or just waiting it out. The hard reset option does not always work, but waiting it out always does. It can take about 30 - 45 minutes to come back to life. There is a serious drain on the battery in this frozen state if it is not plugged in.
Some things that I have noticed in trouble shooting this include: If I use the Apple menu or keyboard commands to put the system to sleep before closing the clamshell I can come back to it anytime within the day and it will work normally. If I extend that time longer, (like over night for example) I have a 70% chance it will wake normally and 30% chance it won’t. Leaving it in sleep mode longer than just overnight will always result in the freeze occurring.
The freezing occurs even when Airport is turned off prior to putting the computer to sleep using the Apple menu or keyboard commands. My hunch is that it is a preference issue that becomes corrupted somehow over time because the issue develops in the extended sleep. If I close the clamshell and open it again 10 minutes later it works normally 1 hour later and it is frozen. This freeze is not application specific, it can happen with or without any application running.
Some other things I have tried are deactivate and reactivating the Airport in Network Preferences (I also did this with the Ethernet even though I only use Airport).
I’ve Repaired all permissions. I’ve replaced the com.apple.AutoWake.plist.
I've reset PRAM and SMC.
Any suggestions would be appreciated.
This Macbook is 2.16 GHz, 2 GB RAM running OS 10.6.5.

An update to my earlier posting, doing some trial and error I have discovered that after removing all of my HP printer/scanner drivers and related software (which I was having less than an optimal experience with anyway), my freezing issue has been reduced from more than 1 hour down to 10 minutes. I'm definitely getting closer to the problem but haven't found the exact software preference causing the issue yet.

IOS app rejected due to a blank, black screen upon launch

I recently got my iPhone app rejected and the reason is below:
"We found that your app exhibited one or more bugs, when reviewed on iPhone 5 running iOS 6.1.3, on both Wi-Fi and cellular networks, which is not in compliance with the App Store Review Guidelines.
Specifically, the app displayed a blank, black screen upon launch. Please see the attached screenshot/s for more information.
The steps to reproduce are:
1. Launch app
2. Bug encountered"
I use FlashDevelop and the latest Apache Flex + Air SDK 3.7 + swfversion=20. I don't have an iPhone 5 to test on but I've tested the application on a 3GS, iPod touch (4th gen.) on IOS 4.3, 5.1 and 6.1.3 (latest) and the application works on all of them.
The attached screenshot mentioned above is here:
the "blank" screen is actually a deep blue one, which the color I've set to my project's background.
I didn't make any special modifications in the code to support iPhone 5 to be honest, and the project dimensions were set to 640x960, but I did include the [email protected], and it shows inside the .ipa at Payload/Myapp.app/
In almost all the iPhone 5 discussions I've read online, theat launch problem is due to the [email protected] not being there in the root of the release .ipa, but I'm sure it does exist on my ipa. Also, I have request high resolution set to high, and the Info.plist has the correct DTPlatformVersion (6.0) and DTSDKName (iphoneos6.0).
Any ideas what the problem could be?
Thanks.

Remember - they gave you a very specific device and version. It might be working on all other configurations. So if you are unable to get your hands on that device and version you are going to be left stabbing in the dark as to what is going wrong.
My advice would just be to figure out what's different with that device and make sure everything is configured properly.
Another option - if you don't want this app on the iPad anyway - is to remove it from the configuration:
<key>UIDeviceFamily</key>
<array>
<string>1</string>
<string>2</string>
</array>
You would delete the <string>2</string> part.

Intel iMac Black screen on wake up from sleep

Hi, has anyone come across this? My imac intel 20" running 10.4.11 now routinely presents me with a black screen on waking up from sleep. The computer still seems to run as normal, the mail application beeps when new mail is received but the screen is black. I have to switch off the computer, reboot and do a NVRAM reset, sometimes up to 8 times in order to get a functioning screen. The beautiful Lexus has turned into a 10 year old Ford Escort; i think -not sure though- that this started with the latest system update. All advice greatly appreciated. Jan

I, too, have this problem. I don't have a cure but I do have a workaround.
If you close the lid again and watch the light on the front it will be solid on. Keep the lid closed and keep waiting (which might take a minute or two) and eventually the light will start "breathing". Now you can open the lid and your computer should be up and running normally.
Although waiting for the light to start breathing is a pain (especially if you're pressed for time) it's still quicker and safer than shutting down and restarting.
Bob

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. ***!!!

Black screen upon wake from sleep when I change power state while in sleep

Hi,
I'm having this problem where my MacbookPro won't always wake from sleep.
OSX is 10.6.3 and fully updated.
I've done a lot of troubleshooting, and I can now replicate the issue 100%:
1 - Put the MacbookPro to sleep by closing lid
2 - Change power source (from plugged-in to battery or vice versa)
3 - open lid - MacbookPro will wake, but stays at black screen and is unresponsive.
Only if I change power state while sleeping will this issue show. Anyone else experincing this issue, and anygot got a clue on what to do?
regards,
Lasse

I've seen the same issue after upgrading to 10.6.3. I have a one year old MacBook Pro. I would have the screen be black after coming back from sleep or hibernate (tried both).
The workaround I found is to close the lid -almost- all the way and then immediately open it back up again, like I am catching the Mac going back to sleep and then changing my mind. For whatever reason, this has been reliably solving my issue for the last couple weeks reliably.
Only other oddity I noticed is that immediately after upgrading OS X told me that my one year old battery needed to go in for servicing...
Anyway, now all looks right with the world assuming you don't mind a quick close/open cycle.. Lovely...
Tim

Black screen upon waking from sleep

Hello,
I have an intermittent problem with waking my entry-level MBP from sleep; on some occasions, the screen remains black instead of the system waking up and displaying the Finder.
Recently, upon waking from sleep, the authentication dialog displayed, I typed my password and pressed return, the dialog dismissed, the screen remained black, and the wait cursor displayed without spinning.
To recover, I needed to force power down and cold reboot.
system.log (in Console) contained the following entry at the time of the crash.
Aug 14 07:39:51 BF-H-MBP kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0xd = GR: SW Notify ErrorAug 14 07:39:51 BF-H-MBP kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0xd = GR: SW Notify Error
The entries surrounding the one above were as follows (the next to last one evidently was the final entry before the forced power down).
Aug 14 07:39:47 BF-H-MBP kernel[0]: IOBluetoothHCIController::restartShutdownWL this is a wake from sleep
Aug 14 07:39:47 BF-H-MBP kernel[0]: System Wake
Aug 14 07:39:47 BF-H-MBP kernel[0]: IOUSBWorkLoop::closeGate - interrupt Thread being held off
Aug 14 07:39:51 BF-H-MBP kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0xd = GR: SW Notify Error
Aug 14 07:39:51 BF-H-MBP BatteryUpdater[3590]: Battery does not need the BatteryUpdate v 1.2 (0x2)
Aug 14 07:39:51 BF-H-MBP lookupd[3588]: lookupd (version 369.6) starting - Tue Aug 14 07:39:51 2007
Aug 14 07:50:08 localhost kernel[0]: hi mem tramps at 0xffe00000
Can someone diagnose the problem based upon the above Console entries?
Thanks in advance!

Hi,
Thanks for taking time to post.
My question is different than the one your posting answers.
My question is, what is the diagnosis of the problem based upon the Console log entries that I've posted (rather than "How do I recover from the black screen?")?
Cheers!

Screen jitter after long sleep

Hi Folks -
I have macbook air (about 2 years old) running Mac OS X 10.8.3. Lately I'm veen noticing that the LCD screens jitters and jumps when awaking from a long sleep. If I sleep the computer again, and then wake it up immediately, the problem goes away.
Anybody seen anything like that?
Paul

Consider a possible third party software issue.
Consider a visit to the optometrist.

Black screen upon waking Mac

Mac Mini 2011 with 2x4GB RAM, 2.3Ghz i5, 500GB 5400RPM HDD
So I need some help regarding my Mac and it's driving me mad! Its a bit tempermental and it isnt always the same occurance each time, but basically symptons are (somtimes it occurs, sometimes not with each one!):
Turning on It will freeze on white screen (no logo)
upon waking up from sleep it will display black screen with mouse and notifications. no login UI or wallpaper. Can SOMETIMES login if i just type password (as if login screen is still there). mouse dissapears once typing begins
Sometimes when the previous event occurs (^) and i put computer to sleep it will then do the opposite and display just the wallpaper with no input from mouse, keyboard
I have tried removing all devices (webcam, USB mouse etc) and turning on computer but as its tempermental
I have also reinstalled a new OS X over the top from internet recovery
Also reformated HDD and restored OS X.
Also reset SMC and NVRAM.
Also checked in
/private/var/run/StartupItems   -doesnt exsist
/Library/StartupItems - nothing in this folder
/System/Library/StartupItems - nothing either
/System/Library/LaunchDaemons - Loads of files in this folder
/Library/LaunchDaemons - only a few files
Also only 3rd party pref are Java and Flash.
Internet Plug-ins:
          FlashPlayer-10.6: Version: 12.0.0.38 - SDK 10.6 3rd-Party support link
          QuickTime Plugin: Version: 7.7.3
          DivX Web Player: Version: 3.0.1.5 - SDK 10.5 3rd-Party support link
          Flash Player: Version: 12.0.0.38 - SDK 10.6 3rd-Party support link
          OVSHelper: Version: 1.1 3rd-Party support link
          Default Browser: Version: 537 - SDK 10.9
          SharePointBrowserPlugin: Version: 14.3.4 - SDK 10.6 3rd-Party support link
          Unity Web Player: Version: UnityPlayer version 4.1.5f1 3rd-Party support link
          Silverlight: Version: 5.1.10411.0 - SDK 10.6 3rd-Party support link
          JavaAppletPlugin: Version: Java 7 Update 51 3rd-Party support link
3rd Party Preference Panes:
          Flash Player 3rd-Party support link
          Java 3rd-Party support link
Also run the AHT extended test, no issues detected.
Also set "sudo pmset autopoweroff 0" and "sudo pmset standby 0" in Kernal.
Also repaired disk permissions, it only repaired the printer stuff.
After i gave this in kernal, i then reset SMC again to check.
Checked console and noticed a 40 second gap before this error:   "05/02/2014 07:03:00.266 configd[55]: inet_set_autoaddr(en1, 1) failed, Resource busy"
turned off my WiFi and issues still persisted.
This had previously been on forums last week in Mac Mini section with the help of 'BDAqua' however im out of options and need some more help. If anyone could be helpful enough to give some suggestions on why my screen is black upon waking up (exc. notifications. they appear) and most time i need to hard reboot (sometimes i can type in password and it unlocks).
I can not afford to start fresh, i have a 110GB iTunes Library with 210 iOS apps and photos too important to me to be forgotten.
PLEASE HELP ME

Try setting up another admin user account to see if the same problem continues. If Back-to-My Mac is selected in System Preferences, the Guest account will not work. The intent is to see if it is specific to one account or a system wide problem. This account can be deleted later.
Isolating an issue by using another user account
If the problem is still there, try booting into the Safe Mode using your normal account. Disconnect all peripherals except those needed for the test. Shut down the computer and then power it back up after waiting 10 seconds. Immediately after hearing the startup chime, hold down the shift key and continue to hold it until the gray Apple icon and a progress bar appear. The boot up is significantly slower than normal. This will reset some caches, forces a directory check, and disables all startup and login items, among other things. When you reboot normally, the initial reboot may be slower than normal. If the system operates normally, there may be 3rd party applications which are causing a problem. Try deleting/disabling the third party applications after a restart by using the application un-installer. For each disable/delete, you will need to restart if you don't do them all at once.
Safe Mode
Safe Mode - About

Macbook Air (mid-2013) Black Screen Upon Opening Screen

Hi Everyone,
I have a mid-2013 Macbook Air (bought in August) that I updated to OS X 10.9 a few weeks ago. Recently I've been noticing that when I flip the screen up it'll work fine, but if I do so consecutively for two times (ie. opening it once, closing it, then opening it again), the screen goes black (sometimes a half-black that's still lit up, othertimes it's completely black as if it were off). This also happens when I put it in sleep mode by pressing the power button once. If I do it twice, the black screen appears as well. Nothing I press on the keyboard will cause the screen to come back on. The only thing I can do is to force it shut down and then reboot. I reset the SMC and PRAM and neither has helped. Apple told me that I need to take it into a store but I have several essays due in the next week and finals after that. I can't be without a laptop so I can't send it in for repair until at least mid-December. I'm hoping it's not a hardware issue (since other people have posted about this as well) and it'll be solved by an update. Any suggestions?
Thanks for the help!

1. Reset SMC.     http://support.apple.com/kb/HT3964
    Choose the method for:
    "Resetting SMC on portables with a battery you should not remove on your own"
2.Reset PRAM. http://support.apple.com/kb/PH4405
3. http://support.apple.com/kb/PH10930
If this does not help, contact Apple as soon as possible.
Best.

[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 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

Double authentication upon wake from long sleep

Hello - When my MacBook Pro (details below) sleeps for more than 12 hours or so, it goes into some kind of deep sleep. I authenticate, it gives a little progress bar at the bottom of the screen as if it is resuming OS X or something, then I get the same authentication screen again to log into my computer. But the second screen is not active for quite a while, maybe 2 minutes or so (I cannot type, the trackpad does not register any movements, etc.). Then finally I can start using the computer.
I changed the hibernate settings to traditional sleep mode (suspend to RAM), but that did not do anything that I can tell to solve the problem. Can anyone help me with ideas about how to fix this terrible situation? My older iMac does not exhibit this behavior at all.
MacBook Pro (13-inch, Mid 2012) 2.9 GHz Intel Core i7 running 10.10.3

I am really not convinced that this is a "display" problem in and of itself now since I have seen scores of posts throughout the Apple Forums with various Macs and Displays that complain of the same symptom.
I have been chasing this problem now for 3 months (looks like it started for some people going back to at least September 2009). I have (3) identical SONY 23" CRTs connected to my Mac Pro via two PCI video cards, but I am having trouble with only ONE monitor so far (doing the same thing you describe in previous posts - won't wake up from a long sleep - a few hours).
• First I purchased a new monitor cable for the monitor in question - no change
• Next, I purchased a new VGA to DVI Apple Adapter - no change
• Next, after talking to AppleCare Tech support and trying SMC reset, PRAM reset, etc. they sent me a NEW ATI 2600 video card - installed new card - no change
• Tried swapping suspect monitor to connection on other card (known good card) - same monitor would not wake up!!!
• Purchased new GT-120 video card to replace the new ATI-2600 - same problem.
This leads me to believe that it is either a problem with the OS somehow or perhaps some monitors just need a stronger signal to wake up??? Maybe my 3rd monitor is just getting tired compared to the other two and need a bigger kick to wake up?? Maybe some of these new flat screen LCD/LEDs need that extra kick out of the box?.
All I know is that I have seen scores of complaints on this issue all over these forums with different Macs, Different types of displays (new and old) and various video cards - the only common denominator I can find is the OS.
Message was edited by: ChoreoGraphics
Message was edited by: ChoreoGraphics

Black screen upon waking

Twice now since installing 10.5 my Mac has woke up with a black screen, forcing me to hold the button down and attempt rebooting several times. Is this a known problem?

I can confirm the same problem here on a PowerPC Dual G5 with 2 Apple Cinema 23" monitors on both Tiger (10.4.11) and Leopard (10.5.5). The secondary monitor is blacked out upon waking from sleep and/or reboot, yet it appears in the Displays Preference Pane. Mirroring the displays or changing its resolution does not help.
Now, when I plug and replug the monitor's DVI, I get this in the console...
Sep 29 10:51:41 XXXXXX kernel[0]: USBF: 198.392 AppleUSBHubPort: Port 2 of Hub at 0x4b300000 reported error 0xe00002c0 while doing getting port status (2)
So, apparently it's a USB issue. Did a quick search on this forum, but I havn't found out a solution yet.
Any clues!?
Message was edited by: Mircea Turcan

Black screen upon wakeup after longer sleep...

Similar Messages

Maybe you are looking for