Black Screen After Wakeup / Sleep failure code 0x00000000 0x1f006500

Problem waking up from sleep on my mid-'09 MacBook Pro 5.4 running Lion. Bought new, under 2 years old. Upgraded RAM to 8GB and installed an SSD around Janurary this year. Problem started under Snow Liopard no more than a couple weeks back from today. Searched the web up and down for this, found a lot of people with the exact same issue, and tried quite a few suggestions.
- changed settings to wake up on pressed keyboard instead of lid open
- logged in under a different user
- repaired permissions and checked disk (some permission fail to repair)
- run extensive Apple's hardware test and memtest, together with AppleJack in single user mode (all passed, although Apple hardware test sometimes froze & I had to restart)
- removed all side programs that use kext files, only leaving Google's
- uninstalled istatpro, iAlertU and LittleSnitch
- set not to wake up for bluetooth nor network
- set fast sleep instead of hibernation so that RAM is not written to an SSD
- switched RAM modules around. Sometimes after a hard reset my RAM is cut in half and shows either 4GB or 7.75GB instead of normal 8GB (only the second module slot is displayed as empty)
- removed ethernet network settings (disabling it), restarted & added settings / reenabled it
- SMC, PMU resets
- deleted power management plist file
Haven't tried hibernation when RAM is written to a disk but this is an absolute last resort...
Now trying out the "SmartSleep" program / application.
After every hard reset the login screen freezes (mosue works but no response from the keyboard) so I wait for a few minutes or restart the boot and wait a minute or so again.
My plan now is to find a set of RAM modules somewhere to test and go into an Apple store for a check-up. I had AppleCare transferred from another laptop that expired on March this year. So I am not covered now. So far my Apple laptops haven't been all that reliable, it seems. This one went for nearly two years with no hardware problems - this could be the first one.
Here is a full log extract of the problem area:
Jul 27 23:09:39 Super-Bad-Dude kernel[0]: macx_swapon SUCCESS
Jul 27 23:35:13 Super-Bad-Dude kernel[0]: hfs: cat_lookup_siblinglinks: getkey for 2389754 failed 2
Jul 27 23:51:43 Super-Bad-Dude kernel[0]: 00000000 00000020 NVEthernet::setLinkStatus - not Active
Jul 27 23:51:43 Super-Bad-Dude kernel[0]:
Jul 28 09:12:55 Super-Bad-Dude kernel[0]: Wake reason: OHC1
Jul 28 09:12:55 Super-Bad-Dude kernel[0]: Previous Sleep Cause: 5
Jul 28 09:12:55 Super-Bad-Dude kernel[0]: The USB device Apple Internal Keyboard / Trackpad (Port 6 of Hub at 0x4000000) may have caused a wake by issuing a remote wakeup (2)
Jul 28 09:12:55 Super-Bad-Dude kernel[0]: wlEvent: en1 en1 Link DOWN
Jul 28 09:12:55 Super-Bad-Dude kernel[0]: AirPort: Link Down on en1. Reason 4 (Disassociated due to inactivity).
Jul 28 09:12:55 Super-Bad-Dude kernel[0]: en1: 802.11d country code set to 'X3'.
Jul 28 09:12:55 Super-Bad-Dude kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140
Jul 28 09:12:55 Super-Bad-Dude kernel[0]: HID tickle 24 ms
Jul 28 09:12:56 Super-Bad-Dude kernel[0]: 00000000 00000020 NVEthernet::setLinkStatus - not Active
Jul 28 09:12:57 Super-Bad-Dude kernel[0]: en1: 802.11d country code set to 'US'.
Jul 28 09:12:57 Super-Bad-Dude kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 149 153 157 161 165
Jul 28 09:12:59 Super-Bad-Dude kernel[0]: MacAuthEvent en1   Auth result for: 94:44:52:70:30:88 MAC AUTH succeeded
Jul 28 09:12:59 Super-Bad-Dude kernel[0]: wlEvent: en1 en1 Link UP
Jul 28 09:12:59 Super-Bad-Dude kernel[0]: AirPort: Link Up on en1
Jul 28 09:12:59 Super-Bad-Dude kernel[0]: en1: BSSID changed to 94:44:52:70:30:88
Jul 28 09:13:00 Super-Bad-Dude kernel[0]: AirPort: RSN handshake complete on en1
Jul 28 09:13:30 Super-Bad-Dude kernel[0]: nspace-handler-set-snapshot-time: 1311840811
Jul 28 09:25:04 Super-Bad-Dude kernel[0]: hfs: cat_lookup_siblinglinks: getkey for 2392242 failed 2
Jul 28 09:29:03 Super-Bad-Dude kernel[0]: nspace-handler-set-snapshot-time: 1311841745
Jul 28 09:29:08 Super-Bad-Dude kernel[0]: add_fsevent: unable to get path for vp 0xffffff80230b7b20 (sessions; ret 22; type 2)
Jul 28 09:29:08 Super-Bad-Dude kernel[0]: add_fsevent: unabled to get a path for vp 0xffffff80230b7b20. dropping the event.
Jul 28 09:29:09 Super-Bad-Dude kernel[0]: add_fsevent: unable to get path for vp 0xffffff802590a268 (chatsync; ret 22; type 2)
Jul 28 09:29:09 Super-Bad-Dude kernel[0]: add_fsevent: unabled to get a path for vp 0xffffff802590a268. dropping the event.
Jul 28 09:29:09 Super-Bad-Dude kernel[0]: add_fsevent: unable to get path for vp 0xffffff802590a268 (chatsync; ret 22; type 2)
Jul 28 09:29:09 Super-Bad-Dude kernel[0]: add_fsevent: unabled to get a path for vp 0xffffff802590a268. dropping the event.
Jul 28 09:29:10 Super-Bad-Dude kernel[0]: add_fsevent: unable to get path for vp 0xffffff802590a268 (chatsync; ret 22; type 2)
Jul 28 09:29:10 Super-Bad-Dude kernel[0]: add_fsevent: unabled to get a path for vp 0xffffff802590a268. dropping the event.
Jul 28 09:29:14 Super-Bad-Dude kernel[0]: add_fsevent: unable to get path for vp 0xffffff80235be930 (Keychains; ret 22; type 2)
Jul 28 09:29:14 Super-Bad-Dude kernel[0]: add_fsevent: unabled to get a path for vp 0xffffff80235be930. dropping the event.
Jul 28 09:29:14 Super-Bad-Dude kernel[0]: add_fsevent: unable to get path for vp 0xffffff80235be930 (Keychains; ret 22; type 2)
Jul 28 09:29:14 Super-Bad-Dude kernel[0]: add_fsevent: unabled to get a path for vp 0xffffff80235be930. dropping the event.
Jul 28 09:29:14 Super-Bad-Dude kernel[0]: add_fsevent: unable to get path for vp 0xffffff80235be930 (Keychains; ret 22; type 2)
Jul 28 09:29:14 Super-Bad-Dude kernel[0]: add_fsevent: unabled to get a path for vp 0xffffff80235be930. dropping the event.
Jul 28 09:29:14 Super-Bad-Dude kernel[0]: add_fsevent: unable to get path for vp 0xffffff80235be930 (Keychains; ret 22; type 2)
Jul 28 09:29:14 Super-Bad-Dude kernel[0]: add_fsevent: unabled to get a path for vp 0xffffff80235be930. dropping the event.
Jul 28 09:29:14 Super-Bad-Dude kernel[0]: add_fsevent: unable to get path for vp 0xffffff80235be930 (Keychains; ret 22; type 2)
Jul 28 09:29:14 Super-Bad-Dude kernel[0]: add_fsevent: unabled to get a path for vp 0xffffff80235be930. dropping the event.
Jul 28 09:29:14 Super-Bad-Dude kernel[0]: add_fsevent: unable to get path for vp 0xffffff80235be930 (Keychains; ret 22; type 2)
Jul 28 09:29:14 Super-Bad-Dude kernel[0]: add_fsevent: unabled to get a path for vp 0xffffff80235be930. dropping the event.
Jul 28 09:29:15 Super-Bad-Dude kernel[0]: add_fsevent: unable to get path for vp 0xffffff80235be930 (Keychains; ret 22; type 2)
Jul 28 09:29:15 Super-Bad-Dude kernel[0]: add_fsevent: unabled to get a path for vp 0xffffff80235be930. dropping the event.
Jul 28 09:29:15 Super-Bad-Dude kernel[0]: add_fsevent: unable to get path for vp 0xffffff80235be930 (Keychains; ret 22; type 2)
Jul 28 09:29:15 Super-Bad-Dude kernel[0]: add_fsevent: unabled to get a path for vp 0xffffff80235be930. dropping the event.
Jul 28 09:29:18 Super-Bad-Dude kernel[0]: add_fsevent: unable to get path for vp 0xffffff80235b4d90 (login.keychain; ret 22; type 9)
Jul 28 09:29:18 Super-Bad-Dude kernel[0]: add_fsevent: unabled to get a path for vp 0xffffff80235b4d90. dropping the event.
Jul 28 09:30:20 Super-Bad-Dude kernel[0]: IOSurface: buffer allocation size is zero
Jul 28 09:32:14 Super-Bad-Dude kernel[0]: IOSurface: buffer allocation size is zero
Jul 28 10:12:42 localhost kernel[0]: Darwin Kernel Version 11.0.0: Sat Jun 18 12:56:35 PDT 2011; root:xnu-1699.22.73~1/RELEASE_X86_64
Jul 28 10:12:42 localhost kernel[0]: vm_page_bootstrap: 1959200 free pages and 56032 wired pages
Jul 28 10:12:42 localhost kernel[0]: kext submap [0xffffff7f8072e000 - 0xffffff8000000000], kernel text [0xffffff8000200000 - 0xffffff800072e000]
Jul 28 10:12:42 localhost kernel[0]: zone leak detection enabled
Jul 28 10:12:42 localhost kernel[0]: standard timeslicing quantum is 10000 us
Jul 28 10:12:42 localhost kernel[0]: mig_table_max_displ = 72
Jul 28 10:12:42 localhost kernel[0]: AppleACPICPU: ProcessorId=0 LocalApicId=0 Enabled
Jul 28 10:12:42 localhost kernel[0]: AppleACPICPU: ProcessorId=1 LocalApicId=1 Enabled
Jul 28 10:12:42 localhost kernel[0]: calling mpo_policy_init for TMSafetyNet
Jul 28 10:12:42 localhost kernel[0]: Security policy loaded: Safety net for Time Machine (TMSafetyNet)
Jul 28 10:12:42 localhost kernel[0]: calling mpo_policy_init for Sandbox
Jul 28 10:12:42 localhost kernel[0]: Security policy loaded: Seatbelt sandbox policy (Sandbox)
Jul 28 10:12:42 localhost kernel[0]: calling mpo_policy_init for Quarantine
Jul 28 10:12:42 localhost kernel[0]: Security policy loaded: Quarantine policy (Quarantine)
Jul 28 10:12:42 localhost kernel[0]: Copyright (c) 1982, 1986, 1989, 1991, 1993
Jul 28 10:12:42 localhost kernel[0]: The Regents of the University of California. All rights reserved.
Jul 28 10:12:42 localhost kernel[0]: MAC Framework successfully initialized
Jul 28 10:12:42 localhost kernel[0]: using 16384 buffer headers and 10240 cluster IO buffer headers
Jul 28 10:12:42 localhost kernel[0]: IOAPIC: Version 0x11 Vectors 64:87
Jul 28 10:12:42 localhost kernel[0]: ACPI: System State [S0 S3 S4 S5] (S3)
Jul 28 10:12:42 localhost kernel[0]: PFM64 0xf10000000, 0xf0000000
Jul 28 10:12:42 localhost kernel[0]: [ PCI configuration begin ]
Jul 28 10:12:42 localhost kernel[0]: console relocated to 0xf10010000
Jul 28 10:12:42 localhost kernel[0]: PCI configuration changed (bridge=3 device=1 cardbus=0)
Jul 28 10:12:42 localhost kernel[0]: [ PCI configuration end, bridges 6 devices 18 ]
Jul 28 10:12:42 localhost kernel[0]: AppleIntelCPUPowerManagement: (built 13:08:12 Jun 18 2011) initialization complete
Jul 28 10:12:42 localhost kernel[0]: Sleep failure code 0x00000000 0x1f006500
Jul 28 10:12:42 localhost kernel[0]: FireWire (OHCI) Lucent ID 5901 built-in now active, GUID 60fb42fffef17f9a; max speed s800.
Jul 28 10:12:42 localhost kernel[0]: USBMSC Identifier (non-unique): 000000009833 0x5ac 0x8403 0x9833
Jul 28 10:12:42 localhost kernel[0]: [IOBluetoothHCIController::setConfigState] calling registerService
Jul 28 10:12:42 localhost kernel[0]: mbinit: done [64 MB total pool size, (42/21) split]
Jul 28 10:12:42 localhost kernel[0]: Pthread support ABORTS when sync kernel primitives misused
Jul 28 10:12:42 localhost kernel[0]: com.apple.AppleFSCompressionTypeZlib kmod start
Jul 28 10:12:42 localhost kernel[0]: com.apple.AppleFSCompressionTypeDataless kmod start
Jul 28 10:12:42 localhost kernel[0]: 2.4.0 Little Snitch: starting
Jul 28 10:12:42 localhost kernel[0]: com.apple.AppleFSCompressionTypeZlib load succeeded
Jul 28 10:12:42 localhost kernel[0]: com.apple.AppleFSCompressionTypeDataless load succeeded
Jul 28 10:12:42 localhost kernel[0]: AppleIntelCPUPowerManagementClient: ready
Jul 28 10:12:42 localhost kernel[0]: BTCOEXIST off
Jul 28 10:12:42 localhost kernel[0]: wl0: Broadcom BCM432b 802.11 Wireless Controller
Jul 28 10:12:42 localhost kernel[0]: 5.100.98.75
Jul 28 10:12:42 localhost kernel[0]: CoreStorage: fsck has finished successfully for lvg "9EE70322-2538-4C97-ABBF-840E47EC5495"
Jul 28 10:12:42 localhost kernel[0]: thr 0xffffff801357da40 cs_thread_create thread=0xffffff8013beac68 arg=0xffffff8013bea800
Jul 28 10:12:42 localhost kernel[0]: thr 0xffffff801357da40 cs_thread_create thread=0xffffff8013beaee0 arg=0xffffff8013bea800
Jul 28 10:12:42 localhost kernel[0]: rooting via boot-uuid from /chosen: 8AAB677E-1234-3FCA-A115-09A923BB759D
Jul 28 10:12:42 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
Jul 28 10:12:42 localhost kernel[0]: Got boot device = IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/SATA@B/AppleMCP79AHCI/PR T0@0/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageD river/OWC Mercury Extreme Pro SSD Media/IOGUIDPartitionScheme/X X X@2/CoreStoragePhysical/CoreStorageGroup/X X X@s0
Jul 28 10:12:42 localhost kernel[0]: BSD root: disk1, major 14, minor 4
Jul 28 10:12:42 localhost kernel[0]: jnl: unknown-dev: replay_journal: from: 12953088 to: 16393216 (joffset 0x37e000)
Jul 28 10:12:42 localhost kernel[0]: jnl: unknown-dev: journal replay done.
Jul 28 10:12:42 localhost kernel[0]: Kernel is LP64
Jul 28 10:12:42 localhost kernel[0]: hfs: Removed 53 orphaned / unlinked files and 3052 directories
Jul 28 10:12:43 localhost kernel[0]: NVEthernet: Ethernet address 60:fb:42:f1:7f:9a
Jul 28 10:12:43 localhost kernel[0]: AirPort_Brcm4331: Ethernet address 00:26:bb:18:46:7c
Jul 28 10:12:43 localhost kernel[0]: IO80211Controller::dataLinkLayerAttachComplete(): adding AppleEFINVRAM notification
Jul 28 10:12:43 localhost kernel[0]: IO80211Interface::efiNVRAMPublished():
Jul 28 10:12:45 localhost kernel[0]: Created virtif 0xffffff8015054000 p2p0
Jul 28 10:12:45 localhost kernel[0]: NVDANV50HAL loaded and registered.
Jul 28 10:12:45 localhost kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
Jul 28 10:12:45 localhost kernel[0]: Previous Shutdown Cause: -128
Jul 28 10:12:45 localhost kernel[0]: DSMOS has arrived
Jul 28 10:12:46 localhost kernel[0]: jnl: disk2s3: replay_journal: from: 24017408 to: 5658624 (joffset 0x6ff000)
Jul 28 10:12:46 localhost kernel[0]: macx_swapon SUCCESS
Jul 28 10:12:46 localhost kernel[0]: 00000000 00000020 NVEthernet::setLinkStatus - not Active
Jul 28 10:12:48 Super-Bad-Dude kernel[0]: nspace-handler-set-snapshot-time: 1311844369
Jul 28 10:12:48 Super-Bad-Dude kernel[0]: en1: 802.11d country code set to 'US'.
Jul 28 10:12:48 Super-Bad-Dude kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 149 153 157 161 165
Jul 28 10:12:48 Super-Bad-Dude kernel[0]: AppleLMUController found an AG vendor product (0x9cb1), notifying SMC.
Jul 28 10:12:48 Super-Bad-Dude kernel[0]: MacAuthEvent en1   Auth result for: 94:44:52:70:30:88 MAC AUTH succeeded
Jul 28 10:12:48 Super-Bad-Dude kernel[0]: wlEvent: en1 en1 Link UP
Jul 28 10:12:48 Super-Bad-Dude kernel[0]: AirPort: Link Up on en1
Jul 28 10:12:48 Super-Bad-Dude kernel[0]: en1: BSSID changed to 94:44:52:70:30:88
Jul 28 10:12:49 Super-Bad-Dude kernel[0]: AirPort: RSN handshake complete on en1
Jul 28 10:12:49 Super-Bad-Dude kernel[0]: en1: DAD detected duplicate IPv6 address fe80:0005::0226:bbff:fe18:467c: NS in/out=1/1, NA in=0 inx=0
Jul 28 10:12:49 Super-Bad-Dude kernel[0]: en1: DAD complete for fe80:0005::0226:bbff:fe18:467c - duplicate found
Jul 28 10:12:49 Super-Bad-Dude kernel[0]: en1: manual intervention required
Jul 28 10:12:49 Super-Bad-Dude kernel[0]: en1: possible hardware address duplication detected, disable IPv6
Jul 28 10:12:53 Super-Bad-Dude kernel[0]: nstat_lookup_entry failed: 2
Jul 28 10:12:56 Super-Bad-Dude kernel[0]: jnl: disk2s3: journal replay done.
Jul 28 10:13:02 Super-Bad-Dude kernel[0]: hfs: Removed 0 orphaned / unlinked files and 888 directories
Jul 28 10:18:51 Super-Bad-Dude kernel[0]: hfs: cat_lookup_siblinglinks: getkey for 2392900 failed 2
Jul 28 10:23:00 Super-Bad-Dude kernel[0]: 00000000 00000020 NVEthernet::setLinkStatus - not Active
Jul 28 10:23:00 Super-Bad-Dude kernel[0]:
Jul 28 10:23:13 Super-Bad-Dude kernel[0]: Wake reason: EC LID0
Jul 28 10:23:13 Super-Bad-Dude kernel[0]: HID tickle 0 ms
Jul 28 10:23:13 Super-Bad-Dude kernel[0]: Previous Sleep Cause: 5
Jul 28 10:23:13 Super-Bad-Dude kernel[0]: wlEvent: en1 en1 Link DOWN
Jul 28 10:23:13 Super-Bad-Dude kernel[0]: AirPort: Link Down on en1. Reason 4 (Disassociated due to inactivity).
Jul 28 10:23:13 Super-Bad-Dude kernel[0]: en1: 802.11d country code set to 'X3'.
Jul 28 10:23:13 Super-Bad-Dude kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140
Jul 28 10:23:14 Super-Bad-Dude kernel[0]: 00000000 00000020 NVEthernet::setLinkStatus - not Active
Jul 28 10:23:41: --- last message repeated 1 time ---
Jul 28 10:23:41 Super-Bad-Dude kernel[0]:
Jul 28 10:24:09 Super-Bad-Dude kernel[0]: Wake reason: EC LID0
Jul 28 10:24:09 Super-Bad-Dude kernel[0]: HID tickle 0 ms
Jul 28 10:24:09 Super-Bad-Dude kernel[0]: Previous Sleep Cause: 5
Jul 28 10:24:10 Super-Bad-Dude kernel[0]: 00000000 00000020 NVEthernet::setLinkStatus - not Active
Jul 28 10:24:12 Super-Bad-Dude kernel[0]: en1: 802.11d country code set to 'US'.
Jul 28 10:24:12 Super-Bad-Dude kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 149 153 157 161 165
Jul 28 10:24:17 Super-Bad-Dude kernel[0]: MacAuthEvent en1   Auth result for: 94:44:52:70:30:88 Auth timed out
Jul 28 10:24:19 Super-Bad-Dude kernel[0]: MacAuthEvent en1   Auth result for: 94:44:52:70:30:88 MAC AUTH succeeded
Jul 28 10:24:19 Super-Bad-Dude kernel[0]: wlEvent: en1 en1 Link UP
Jul 28 10:24:19 Super-Bad-Dude kernel[0]: AirPort: Link Up on en1
Jul 28 10:24:19 Super-Bad-Dude kernel[0]: en1: BSSID changed to 94:44:52:70:30:88
Jul 28 10:24:20 Super-Bad-Dude kernel[0]: AirPort: RSN handshake complete on en1

All sorts of ways. Nothing here helped. Went into the store and the consensus is a faulty / failed logic board. Although on my first visit I was sent back home because the company doesn't support self installed SSDs, on my second visit Alex and his manager have graciously agreed to replace be part and weave the fee for me despite expired AppleCare. This is great. I am chuffed. Problem solved, hopefully. Thanks to Apple & it's professional and efficient staff.

Similar Messages

Black screen after login / sleep

Hoping somebody can help, I've spent like the last two days straight at the genius bar without success. When I boot up I see my profile and the guest, it boots as normal (not the delayed boot with black screen others have mentioned), but then I log in, see my desktop, icons, and then the screen goes black.
If I let it sleep for a few hours, when I wake it up the screen is also black and there's nothing I can do except hold the power till it shuts down.
In both cases I can tell the computer is still on because the backlit keyboard stays lit.
I've tried resetting nvram, smc, deleting the library cache file, doing a reinstall without wipe, and I only have one partition/HD so it's definitely the default boot disc.
I can boot into safe mode, and occasionally boot up regularly after being in safe mode for a bit.
I had the display replaced due to a physical defect just before this happened, but I also got 10.10.3, which I know has caused graphics glitches for other people. Hope you guys have some ideas! Thank you!
And here's a link to pastebin with a log: http://pastebin.com/EQqJLzsi
Thanks again!

Hoping somebody can help, I've spent like the last two days straight at the genius bar without success. When I boot up I see my profile and the guest, it boots as normal (not the delayed boot with black screen others have mentioned), but then I log in, see my desktop, icons, and then the screen goes black.
If I let it sleep for a few hours, when I wake it up the screen is also black and there's nothing I can do except hold the power till it shuts down.
In both cases I can tell the computer is still on because the backlit keyboard stays lit.
I've tried resetting nvram, smc, deleting the library cache file, doing a reinstall without wipe, and I only have one partition/HD so it's definitely the default boot disc.
I can boot into safe mode, and occasionally boot up regularly after being in safe mode for a bit.
I had the display replaced due to a physical defect just before this happened, but I also got 10.10.3, which I know has caused graphics glitches for other people. Hope you guys have some ideas! Thank you!
And here's a link to pastebin with a log: http://pastebin.com/EQqJLzsi
Thanks again!

Black Screen After Upgrading to Windows 8

Hi
I'm experiencing a black screen after upgrading a Dell N5050 B890 to Windows 8.
Tried to refresh the installation but the problem persited. re-installed the Windows 8, the machine logged in successfully but the problem arose again after reboot.
Urgent assistance needed

This problem is solved...
I guess the problem is concerned with the display module controller in the BIOS which is having a slight compatibility issue with windows 8.
This issue is solved by updating the BIOS of your Laptop/PC to the latest version. You can download the latest BIOS from the website of the Laptop company/Motherboard Company.
But for updating the BIOS, you have to start your computer/Laptop for at least one time in Normal Mode. So here are the steps to do so...
1) Boot the Laptop/PC.
2) After the boot screen (The Circle Animation & Windows 8 logo), you will be presented by the lovely & awesome blank screen.
3) Wait for 1 minute so that drivers load into the memory.
4) Press the Power button of your laptop/PC for only a moment (Just Press and release it quickly. Don't hold. We don't want to shut down).
5) This will force the laptop/PC to go into Sleep mode.
6) When the laptop/PC goes in sleep, the laptop fan & other sounds will stop.
7) After 4-5 seconds, press the power button again & release it quickly.
8) Voilllaa!!! The laptop/PC starts & you are presented with the lock screen. Now..... Login! What are you waiting for! :P
This is not the permanent solution. It just lets you start you Laptop/PC.
After updating the BIOS, I strongly suggest that you must download the latest graphics driver for your Computer/Laptop to avoid any further issues.

Hp pavilion s5715 - computer freezes / black screen after i use it somewhat intensively

Hi,
I recently bought the HP Pavilion s5715 but when I used it even somewhat intensively (playing Left 4 Dead for example) it'll freeze / black screen after a short while (10 minutes or so).
I assume this has to do with overheating, but what would be a good fix for this? And how can I figure out what component overheats?

Hi,
Please use the following instructions:
http://www.dummies.com/how-to/content/windows-81s-power-settings-and-sleep.html?cid=RSS_DUMMIES2_CON...
Regards.
BH
**Click the KUDOS thumb up on the left to say 'Thanks'**
Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.

GTX590 Cant access NVIDIA control panel Black screen after 10 mins

Hi,
I recently purchased an MSI GTX590 and encountered this problem " Cant access NVIDIA control panel Black screen after 10 mins". I am running Windows7 Ultimate SP1.
I did have an xfire setup of 2xHD6970's, I uninstalled all the old drivers then used driver sweeper to clean out any remaining folders, also uninstalling them from device manager.
Next I installed the latest version of drivers from the NVIDIA site only to find that I am stuck in safe mode resolutions for my screen I cant access the NVIDIA control panel as it is saying " You are not currently using a display attached to an Nvidia GPU ". In device manager it states that
"Windows has stopped this device because it has reported problems. (Code 43) ".
I have now uninstalled and reinstalled about 6 different versions of drivers from NVIDIA including the latest BETA drivers which all have the same issue??????
I have also gone to the MSI site and downloaded their latest recommended drivers for the GTX590 NVIDIA Graphics Drivers Version 267.91 which are the only ones that seem to work as in it fixes the screen to the proper resolution and lets me into the NVIDIA control panel yet after about 10-15 mins the screen will go black or the computer will just freeze. Rebooting causes the same issue after 10-15mins
I have noticed a few others out there experiencing the same problem but no fixes as of yet any ideas??

Thankyou for the reply,
Tested the card in another working machine capable of running and its fine I am sure the PSU I have is more than capable of running this card I ran 2 6970's in xfire on the same PSU and motherboard with no problems.
I am running it on an 40"BRAVIA LCD and am using the DVI to HDMI converter that came with the GTX590 and I have also tried it with an DVI to HDMI cable also.
The system is stable under the latest NVIDIA drivers but the display drivers aren't recognized under device manager and the screen resolution is still stuck in the safe mode size, they are shown up as having the same "error 43" and I still can't get access to the NVIDIA control panel.
I strongly believe this is a driver issue or an issue relating to software within windows. To give you a rundown on several things that I have tried to isolate or fix the issue with is in a list here:
1. Installed every different version of drivers on an fresh install of windows7 including the latest Beta drivers
2. Tried to run the GTX590 on another machine and it runs using windows7
3. Run different graphics card setup using the same PSU RAM and mb on windows7 no problems.
4. Run the gfx card on only 1 gpu no change.
5. Last step I will take is to install Windows7 without the SP1 as I have read elsewhere that similar problems have been fixed by doing this if that don't work might just sell my soul to the devil n see if he can fix it lol.

Black Screen After Boot up

My T420s (2 months old) recently has been giving me a black screen after boot up (no "Thinkpad" image is displayed during boot up). System totally unresponsive -- I have to push on/off button multiple times. Subsequent boot up usually OK. Sometimes once I'm up and running, upon entering sleep mode, the machine will not wake up.
I have adjusted power management setting and and up-to-date on all drives. HELP!!!

if this is constantly occurring this would mean something is wrong with the Thinkpad's hardware, since this laptop is fairly new, you should consider getting it fixed under warranty.
Regards,
Jin Li
May this year, be the year of 'DO'!
I am a volunteer, and not a paid staff of Lenovo or Microsoft

Lenovo G560 - Issue with won't boot and black screen after HDD upgrade

Lenovo G560 - Issue with won't boot and black screen after HDD upgrade.
What happen: My laptop was working fine, no blue screen issue, no funny business at all. I bought a new SSD Intel 120 GB and thought it would be a good idea to replace the HDD. I shutdown and disconnected the power adapter, waited a couple of minutes and removed the battery. I opened up the back case and replaced the HDD. And put all the screws back and put the battery back in.
Problem: The very first time I turned the power on, nothing happens besides a black screen. I pressed the dvd drive it works and opens up and closes. I waited for about 30 mins and still has blac screen. When I mean black screen, no bios menu, no logo, just a black screen with the fan sound on.
I have tried these:
1. Unplugged everything - battery, adapter, and pressed the power on button for about 60 seconds, nothing, the laptop turns on with the LED display on for both on and battery LED's. But nothing but black screen, no sound of windows loading just the fan and black screen.
2. I tried putting back my old 2.5" and nothing but black screen.
Thoughts and suggestions?
Solved!
Go to Solution.

Hi Autoexit173,
Welcome to Lenovo Community!
As per the query we understood that you are facing issue with system not booting in your Lenovo G560 laptop.
As you have mentioned that the system not booting, please try to remove the RAM and turn on the system and check if you can hear any beep sound. Also try to clean the RAM slots and check for the issue.
Click here for the steps to remove the RAM and refer page number 40.
Hope this helps. Do post back if issue persists!
Best regards,
Ashwin.S
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter!

[SOLVED] Black screen after GRUB

Hello everyone
I was setting up a machine with E17 and was trying various DM's since none seemed to work. After attempting to use LightDM, I get a black screen after GRUB. I was trying to read the various logs at /var/log/ but I cannot understand them properly. I tried reinstalling entrance and LightDM with no luck. I even tried editing grub's entry appending '1' or 's' and still no dice. Any help would be appreciated.
Last edited by Linoman (2014-01-20 09:22:33)

Hi tnx for both answers.
I missed something important in Xorg.log. As you can see, fbdev and modesetting aren't loading as usual. I didn't check grub stuff, I don't think it's related, since loading in level 3 (text mode) I get a black screen but I can login as root and turn off the computer blindlessly.
[ 2.969] (II) LoadModule: "modesetting"
[ 2.969] (WW) Warning, couldn't open module modesetting
[ 2.969] (II) UnloadModule: "modesetting"
[ 2.969] (II) Unloading modesetting
[ 2.970] (EE) Failed to load module "modesetting" (module does not exist, 0)
[ 2.970] (II) LoadModule: "fbdev"
[ 2.970] (WW) Warning, couldn't open module fbdev
[ 2.970] (II) UnloadModule: "fbdev"
[ 2.970] (II) Unloading fbdev
[ 2.970] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 2.970] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
GM45, 4 Series, G45/G43, Q45/Q43, G41, B43, HD Graphics,
HD Graphics 2000, HD Graphics 3000, HD Graphics 2500,
HD Graphics 4000, HD Graphics P4000, HD Graphics 4600,
HD Graphics 5000, HD Graphics P4600/P4700, Iris(TM) Graphics 5100,
HD Graphics 4400, HD Graphics 4200, Iris(TM) Pro Graphics 5200
[ 2.970] (II) VESA: driver for VESA chipsets: vesa
[ 2.970] (++) using VT number 7
[ 2.974] (WW) Falling back to old probe method for vesa
javex wrote:Post the content of the following files:
Also does disabling LightDM again help resolve the issue, i.e. can you get it to work without LightDM?
No, I can't get it to work changing DM's. I'm not sure if I pacman -Syu before changing DM's another time. Maybe it wasn't LightDM's fault afterall.
Spider.007 wrote:Additionally; try booting without the 'quiet' entry that is in the kernel line by default; and disable https://wiki.archlinux.org/index.php/Ke … de_Setting too
Thanks for pointing out that. I didn't knew I had it on.
Last edited by Linoman (2014-01-11 21:34:08)

[Solved]Black screen after "waiting for udev uevents to be processed"

Hello friends,
Starting from late Dec., my laptop goes black screen after "waiting for udev uevents to be processed", after updating kernel to 2.26.32.*. The strange thing is that even the screen is black, the keyboard is working. For example, I can turn on/off the status lights of capslock and others. I guess something might be wrong with udev uevents configuration with regard to the latest kernel. I've noticed that in the new kernel, there are two drivers for intel integrated graphics. My laptop has a 855G, which is supposed to be functional by both drivers, at least according to the kernel description. Maybe because the udev is configured to use the second driver (for newer graphic chips), rather than the first driver, which caused the problem?
Regards,
Wen
Last edited by Wen (2010-01-28 13:14:28)

Have a look here: http://bbs.archlinux.org/viewtopic.php? … 70#p695670

Black Screen After Windows 8 64-bit Upgrade (Clean Install) on TouchSmart IQ508A (IQ500 series)

Hi there,
Just installed Windows 8 and am getting a black screen after booting up like many others. I currently have disabled the graphics driver and this has solved the black screen issue but I can no longer use my web cam for Skype (although web cam works for W8 Camera App oddly).
To date I have tried the following:
Loading up the latest Nvidia drivers from the Nvidia website
Attempting to use the drivers for Windows 7 both in compatability mode and normally. I unzipped SP44488 to get this working
I know many others are having this problem so I really would like someone from HP to respond and state whether a Windows 8 display driver for the Nvidia GE Force 9300M GS is being developed.
I ran the compatability wizard prior to the clean install and it came up with no issues so I am very disappointed I am having these problems.
I've found out that HP have a customised version of the above card so that explains why the Nvidia drivers dont work so I believe HP is therefore obligated to provide a driver.
If anyone else is having similar issues please respond as this will hopefully lead to more action.
cheers
Steve

I'm in the same boat. On my IQ804, the Nvidia GE Force 9300M GS card crashes when I use NVidia's latest Windows 8 driver and Microsoft's LIVE UPDATE drivers. I have to resort to the Standard VGA driver in order for the pc not to crash into a black screen.
I read on another forum you can try installing a July 2012 version of the driver from NVidia and that should solve the problem. I tried it once. Using the July 2012 version, the screen would stay on longer, but eventually it crashes into a black screen...but definitely more usable than the latest from NVidia and Microsoft.
I too have heard that HP used a customized version of the graphics card and that's why neither HP nor NVidia's drivers work.
I also tried installing the Nvidia GE Force 9300M GS drivers for Windows 7 that I downloaded from the HP website. It didn't work either. It actually failed to install altogether, saying my system is incompatible.
As is, the pc works fine. But videos and games that require motion is noticably choppy.
Any help from HP??

Black Screen after logging in locally to Windows 7 that previously had an open RDP session.

Here is what happens. I leave my home computer on (running Windows 7 Ultimate) and sometimes I will remote to it from another location (work, friends house, or wherever). When I return home, I will go to login, the screen then goes blank (no mouse cursor
or anything). I have to do a cold boot to get back into Windows. This only happens if I ever RDP into it sometimes during the day. It seems random. I've tried logging off the RDP session, just closing it without logging off, nothing seems to be the answer
in that regard. It seems very random at times. I'll go a week and I can come home and it will login fine with no problems. Then the next week it starts giving me the black screen after I come home and login locally. I've seen several black screen issues here,
but usually they are getting it before logon. Anyone have a clue what might be causing this?

Hello,
The Windows Desktop Perfmon and Diagnostic tools forum is to discuss performance monitor (perfmon), resource monitor (resmon), and task manager, focusing on HOW-TO, Errors/Problems, and usage scenarios.
As the question is off topic here, I am moving it to the
Where is the Forum... forum.
Karl
When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer.
My Blog: Unlock PowerShell
My Book: Windows PowerShell 2.0 Bible
My E-mail: -join ('6F6C646B61726C40686F746D61696C2E636F6D'-split'(?<=\G.{2})'|%{if($_){[char][int]"0x$_"}})

Black screen after login while on battery with graphics switching enabled

Getting a black screen after entering my password while logging into my account while on battery with graphics switching enabled. Everything is up and running, I just can't see it.
I can log into the guest account on battery
I can log into my account while plugged into power
I can log into my account on battery if graphics switching is disabled
I believe something that is starting up in my account is causing the system to switch from integrated to discrete graphics on login, and that switch isn't working correctly on battery power.
As a work around for now, I can run with graphics switching disabled, but I'd like to solve this so I get longer battery life.
MacBook Pro Retina 15"
Mountain Lion
All updates applied

I had the same issue and managed to reslove it.
Shut down your machine.
Power it back on while holding the 'shift' key (left or right, doesn't matter)
You will see a greay progress bar go across the screen while you boot in to 'safe boot'
Once booted, login, and go to Energy Saver and turn on 'Automatic Graphics Switching'.
Reboot back in to normal mode, and you should be able to log back in and see again.
I did this without being plugged into AC power.
Hope it helps!
Cheers!

Qosmio X870-149 - Black screen after Update to win 8.1

After an update to win 8.1 I got a black screen after login , the only thing I could do was to press zero during startup and make a recovery installation .
It took 40 houres , I do not know why it took so long , but when it was over, the HDD was completely empty , so I installed win 7 instead , since I had not made ??a recovery CD . The problem now is that I still get black screen in between , and thinking that it might be a heat problem , I still have warranty , but I do not know if it applies when I installed win 7 on the machine.
I still have a warranty on my toshiba Qosmio

Hi
Well, the warranty covers the hardware related problems. It does not cover any issues related to the software.
Now the open question is: why the black screen appears?
Is it hardware or software issue?
What happens if you access the BIOS?
Can you see anything on the screen?
Is something visible on the external monitor?

WINDOWS 8 BLACK SCREEN AFTER LOGIN PROBLEM

Please help me i have a problem with my computer it goes black screen after i login
my desktop is hp pavilion a5055d my os is windows 8 i dont know what the problem
i have a ati radeon xpress 1100 for videocard ..
I tried to restart many times.

Hi,
Did this issue occur before?
Try to logon with Safe Mode to see if the same issue occurs.
Furthermore, you can try to update BIOS for your machine?
You can refer these article to update BIOS if your machine cannot boot:
http://www.ehow.com/how_7356859_update-bios-windows-won_t-boot.html
http://www.wikihow.com/Fix-a-PC-Which-Won't-Boot
Hope that helps.
Leo Huang
TechNet Community Support

IOS adhoc displays black screen after launch

Hi,
my iOS application displays black screen after slash screen.nothing happens and couldn't see any proper errors on debug utility.
I can build adhoc using flash builder and it's works fine but problem occurs when I create ipa using dumped config file on command line(ant)
I'm using flex sdk 4.6 and AirSDK 15.0(overladed) .my application includes few native extensions.
mxmlc
mxmlc -load-config app-config.xml src/mobapp.mxml -output myapp.swf
adt
<target name="build-release-adhoc-package-ipa">
    <echo>::building captive-runtime release-adhoc ipa..</echo>
    <exec executable="${FLEX_BIN}/adt" failonerror="true">
        <arg line="-package" />
        <arg line="-target ipa-ad-hoc" />
        <arg line="-storetype pkcs12" />
        <arg line="-keystore ${provision.dir}/release-adhoc.p12" />
        <arg line="-storepass 12345" />
        <arg line="-provisioning-profile ${provision.dir}/release_adhoc.mobileprovision" />
        <arg line="${adhoc.dir}/ios-adhoc.ipa" />
        <arg line="${src}/mobapp-app.xml" />
        <arg line="myapp.swf" />
        <arg line="${icon.dir}/applicationIcon16.png" />
        <arg line="${icon.dir}/applicationIcon32.png" />
        <arg line="${icon.dir}/applicationIcon36.png" />
        <arg line="${icon.dir}/applicationIcon48.png" />
        <arg line="${icon.dir}/applicationIcon57.png" />
        <arg line="${icon.dir}/applicationIcon72.png" />
        <arg line="${icon.dir}/applicationIcon76.png" />
        <arg line="${icon.dir}/applicationIcon114.png" />
        <arg line="${icon.dir}/applicationIcon120.png" />
        <arg line="${icon.dir}/applicationIcon128.png" />
        <arg line="${icon.dir}/applicationIcon152.png" />
        <arg line="${base.dir}/[email protected]" />
        <arg line="-extdir ${src}/ane" />
        <arg line="-platformsdk /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPh oneOS.sdk" />
    </exec>
    </target>
please help.

Hi,
my iOS application displays black screen after slash screen.nothing happens and couldn't see any proper errors on debug utility.
I can build adhoc using flash builder and it's works fine but problem occurs when I create ipa using dumped config file on command line(ant)
I'm using flex sdk 4.6 and AirSDK 15.0(overladed) .my application includes few native extensions.
mxmlc
mxmlc -load-config app-config.xml src/mobapp.mxml -output myapp.swf
adt
<target name="build-release-adhoc-package-ipa">
    <echo>::building captive-runtime release-adhoc ipa..</echo>
    <exec executable="${FLEX_BIN}/adt" failonerror="true">
        <arg line="-package" />
        <arg line="-target ipa-ad-hoc" />
        <arg line="-storetype pkcs12" />
        <arg line="-keystore ${provision.dir}/release-adhoc.p12" />
        <arg line="-storepass 12345" />
        <arg line="-provisioning-profile ${provision.dir}/release_adhoc.mobileprovision" />
        <arg line="${adhoc.dir}/ios-adhoc.ipa" />
        <arg line="${src}/mobapp-app.xml" />
        <arg line="myapp.swf" />
        <arg line="${icon.dir}/applicationIcon16.png" />
        <arg line="${icon.dir}/applicationIcon32.png" />
        <arg line="${icon.dir}/applicationIcon36.png" />
        <arg line="${icon.dir}/applicationIcon48.png" />
        <arg line="${icon.dir}/applicationIcon57.png" />
        <arg line="${icon.dir}/applicationIcon72.png" />
        <arg line="${icon.dir}/applicationIcon76.png" />
        <arg line="${icon.dir}/applicationIcon114.png" />
        <arg line="${icon.dir}/applicationIcon120.png" />
        <arg line="${icon.dir}/applicationIcon128.png" />
        <arg line="${icon.dir}/applicationIcon152.png" />
        <arg line="${base.dir}/[email protected]" />
        <arg line="-extdir ${src}/ane" />
        <arg line="-platformsdk /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPh oneOS.sdk" />
    </exec>
    </target>
please help.

Black Screen After Wakeup / Sleep failure code 0x00000000 0x1f006500

Similar Messages

Maybe you are looking for