Reactivate SN resume-from-sleep behavior in Lion?

Hi people,
Most of the time when I put my MacBook to sleep Lion will recreate my desktop environment as I left it, all eight spaces. Occasionally, however, when it wakes from sleep Lion will run that annoying resume feature. All kinds of windows get restored with content that doesn't interest me anymore I can't seem to get rid of Activity Monitor and the Console app, the Finder windows from Spaces 2 through 8 get bunched up in Space 1, resume just doesn't seem to know about the existence of mvim, texmaker doesn't open the last used files, Mathematica just stands there grinding away with all windows darkened and unrepsonsive... the list goes on.... and on..... and on....
I know you can close apps with the [alt]+[cmd]+[Q] shortcut to discard windows but I never remember to do that.
You can disable the resume crap on an app-for-app basis by running: 'defaults write com.apple.<INSERT_APPNAME> ApplePersistenceIgnoreState YES' from the command line. This already worked for over a dozen apps but chasing down the correct write string for a couple of dozen apps is tedious.
I also know about the check button in the quit screen and the global disabling option in system setting.
None are adequate solutions except for point #2 which helped alot but didn't solve the problem. So my question is: Is it possible to deactivate resume and reactivate the old sleep behaviour from Snow Leopard? It worked prefectly every time and didn't open files from last session which I have absoloutely no interest in now.
Cheers
K

Same happening here. I also have a problem with Mail.app crashing when I close the window with cmd+w. My upgrade to Mountain Lion was applied Lion that had been migrated from my old MacBook.
The migrated setup was working fine for just over a week before I upgraded to Mountain Lion. Unfortunately I didn't check that Time Machine was backing up my machine and it turns out I don't have that as an option of rolling back to Lion.
Hoping that a fix is found to both problems. Fairly confident given that other people are reporting the same, even on a clean upgrade.

Similar Messages

Mac Os X Lion Crashes after resuming from Sleep

Hi Everybody, i'm experiencing an issue on my 13'' MBP Early 2011 (i5 processor, 4GB RAM, 750GB HD SATA). My MBP often got stuc after i resume from my monitor sleep. I'll explain it in a better way: After i resume from sleep, there's at first a black screen in which the mouse can move, after that the mouse becmes the classic loading wheel and it freezes copletely, remaining in this situation. I thought it was a screensaver compatibility issue, but the problem stand still after i uninstalled screensaver and deactivate the screensaver options. I think it's a problem with Lion with the HD, but i have no evidence of it. Can Anyone help?
Thank you in advance,
Daniele.

Whenever someone comes to me with crashing and freezing on waking up I look at 3 things and typically in this order:
(1) Hard drive - usually if it is the hard drive SMART has already given a warning if the drive is actually failing or running Disk Utility reveals problems - often problems that cannot be fixed. Also, when the crashes are related to the hard drive there may actuallly be nothing wrong with the drive and a simple erase and reinstall will fix it.
(2) Software issues - the old trick of creating a new account and logging into it to see if the problem is in your account or global helps. Looking in console to see if there's an error message logged just before the crash can be instructive - or not. Often the crash occurs before an error is logged. Sometimes reinstalling the OS is the solution - that's where having a FireWire hard drive is helpful. I can just boot with it and see if the computer still crashes on waking. If not I know to reinstall the OS.
(3) RAM - marginal and faulty RAM can be the culprit in many cases. The frustrating thing about RAM is that RAM tests seldom give false positives, if the test says you have bad RAM, you do. Unfortunately when the test reveals nothing wrong the RAM might still be defective, just not enough for the test to catch.
However, past history has led me to put RAM at the top of the list after an OS upgrade. Marginal RAM has been the culprit of many crash on wake problems with previous OS upgrades. I especially recall Leopard and Snow Leopard being affected - at the shop where I sometimes work we did a lot of RAM warranty replacements after those two upgrades. And here at the support forum we saw lots of people complaining of crash on wake problems coming back and saying, "Yep, got my RAM replaced and all is well." So if any of you are like me and upgraded your RAM, if you have the original RAM sitting around swap it in and see if the crashes stop.

My Mountain Lion mac crashes after resuming from sleep

Hello
My Mountain Lion mac crashes after resuming from sleep every time I use it
It happens every time the mac resumes from sleep and it started like a week ago
I remember installing the new updates for flash? and xquartz and nothing else.
I have also had microsoft word installed on my mac for about 1 weeks before this problem started so might be related to that
Please share with me any tips on how to fix this because I am really annoyed of losing stuff after each time my mac resumes from sleep

I have an iMac bought may -11, and it worked fine with Snow Leopard.
About a week ago I bought and installed Mountain Lion 10.8.2. Everything went fine, and all software worked ok. iPhoto had some problems, but after installing update the system prompted to do, it has worked ok.
The propblem occurs now and then, when computer is waked up from sleep. The Desktop occurs, but no software starts, not even System Tools untlil rebooting the computer. Of course, I can not reboot the computer from "Apple menu", but holding the power button down.
This is very embarassing! OsX Mountain Lion has turned out to be a very big disappointment. I installed id because of iCloud (i have a new iPad, too with iOs 6 installed).
Can anyone help me? Is there any other way to solve the problem than re-installing good old Snow Leopard?
I would not like to do that, I bought Mac because I was bored in re-installing and recovering!
Thank you

Mountain Lion Crashes on resume from sleep

Is anyone else having problems with Mountain Lion crashing frequently on resume from sleep? I have tried using both the default "sleep and hibernate" mode and switching to hibernate only. In both modes, OSX "gray" screens just after it appears to finish resuming from sleep mode. This is an Early 2011 MBP 15" with a clean Lion upgraded to Mountain Lion.
It is starting to look like another failed upgrade, "sigh". I haven't had any luck with OSX OS upgades and always seems like I end up rebuilding.

Same happening here. I also have a problem with Mail.app crashing when I close the window with cmd+w. My upgrade to Mountain Lion was applied Lion that had been migrated from my old MacBook.
The migrated setup was working fine for just over a week before I upgraded to Mountain Lion. Unfortunately I didn't check that Time Machine was backing up my machine and it turns out I don't have that as an option of rolling back to Lion.
Hoping that a fix is found to both problems. Fairly confident given that other people are reporting the same, even on a clean upgrade.

T440S OSD Brightness control failure after resume from Sleep

Hi,
I have owned a T440S since late 2013.
Relevant Details:
T440S
Model : 20AQCTO1WW
OS : Windows 7 professional (original installation by Lenovo)
Latest Drivers installed as of June 2014 - including HotKey and Power Management
HotKey ver : 8.30
Power Managment : 6.65.1
Since receiving this laptop, OSD birightness control has always failed to work, i.e. does not appear on the screen
when using the Fn+F5/F6 key combination nor does it control actual screen brightness AFTER FIRST resuming from sleep
mode.
Sequence of steps that demonstrates the above symptom:
1. OSD brightness works fine after reboot
2. Putting the machine to sleep (I do not use hibernate) for a duration longer than a few minutes
3. Open lid the first time, hit Fn to resume machine
4. Pressing Fn+F5/F6 key combo does not display the brightness slider nor does it control brightness
5. Closing the lid and opening it again, causes OSD brightness slider to flash brifely and is now fully functional
using Fn+F5/F6 keys
Your tech department should easily be able to re-create this issue on any stock T440S/Win7pro machine, as
I have seen others comment about this very issue across other T440/OS variants.
This very same behavior has been there since the beginning.
When is Lenovo going to FINALLY FIX IT ONCE AND FOR ALL?
Thx,
--Alon
Solved!
Go to Solution.

Try this hotfix:
https://support.microsoft.com/kb/2752407
W520: i7-2720QM, Q2000M at 1080/688/1376, 21GB RAM, 500GB + 750GB HDD, FHD screen
X61T: L7500, 3GB RAM, 500GB HDD, XGA screen, Ultrabase
Y3P: 5Y70, 8GB RAM, 256GB SSD, QHD+ screen

Resume from Sleep / Hibernate issues

Hi all,
First time poster. I have a Helix and am running into a heap of resume from sleep (and hibernate) issues.
The sleep issues tend to happen overnight - I do not have this issue if I sleep the machine and then wake it up 5-10 minutes later (e.g. moving between meetings at work). However, when I attempt to wake the machine up in the morning, it fails to resume from sleep, and instead boots from scratch.
Typically, when the unit is in this state, the status led on the lid is rapidly blinking (which I believe means that it's trying to enter sleep) Since there is nothing in the Windows event log during the overnight period, I'm wondering whether it's trying to enter a deeper sleep mode and failing.
This happens every second day or so. Which is really frustrating as a tend to lose some work.
I tried enabling hibernate as a trial, to see if that would avoid the issue, but resuming from hibernate fails as well. At least I get a Windows event log entry for this (source: kernel-power. The unit fails to resume from hibernate with status 0xC000000D)
I have the September 10 BIOS update, and am running Windows 8.1 Enterprise (though I had the issue with Windows 8 as well).
Any ideas on how I can troubleshoot this?
Regards
AC

Windows 8: In Windows 8, the default shutdown behavior puts the system into hybrid shutdown (S4) and all devices are put into D3. Remote wake from hybrid shutdown (S4) or classic shutdown (S5) is completely unsupported. In Windows 8, NICs are explicitly not armed for wake in both the classic shutdown (S5) and hybrid shutdown (S4) cases because users expect zero power consumption and battery drain in the shutdown state. This behavior removes the possibility of spurious wakes when explicit shutdown was requested. As a result, Wake-On-LAN is only ever supported from sleep (S3) or hibernate (S4) in Windows 8.
Note that in Windows 8, hybrid shutdown (S4) stops user sessions but the contents of kernel sessions are written to hard disk. This enables faster boot.
http://msdn.microsoft.com/en-us/library/windows/desktop/aa373229(v=vs.85).aspx
From the Helix User Guide:
•Slow blinking: The tablet is in sleep mode.
•Fast blinking: The tablet is entering hibernation mode or sleep mode.
That was my reason for clarifying if hybrid-sleep was enabled; since it's the default setting and you noted that the LED was blinking fast. Does the LED ever stop blinking fast?
There can/may be multiple log entries during a normal sleep operation, because "the system uses the lowest-powered sleep state supported by all enabled wake-up devices." If one of those devices wakes the system (this does not mean power on) then the logs will report the devices and will likely return to a another level of sleep, but this does not mean full power loss or empty logs.
If the system has successfully entered sleep state, then you should see the following message in System Event logs.
Event 42, Kernel - Power
This system is entering sleep.
Sleep Reason: Button or lid
When the system is successfully woke you will see a System Event Log similar to this:
Event 1, Power - Troubleshooter
The system has returned from a low power state.
Sleep time: 2013-10-08T01:42:25.XXXXXXXX
Wake time: 2013-10-08T05:53:21.XXXXXXXX
However, there will be other events in the logs after sleep and prior to this wake period, such as hardware device issues(My helix has Bluetooth device warnings, nfc driver warnings and some other nondescript hardware errors), kernel messages (about boot manager, boot options, etc.).
Have you changed the behavior of the power button?
You also can program the power buttons so that by pressing the power button you can shutdown the tablet or put it into sleep or hibernation mode. To achieve this, you need to change your power plan settings. To access power plan settings, do the following:
From the desktop, tap the battery status icon in the Windows notification area.
Tap More power options.
In the navigation panel, tap Choose what the power buttons do
Follow the onscreen instructions to configure settings.
Lastly, when you updated to Windows 8.1, did you format the whole C:\ (mSATA) drive?
Helix: 3697 CTO.
Thinkpad user since IBM. I do not work for Lenovo or any entity working for Lenovo.

MacBook Pro resumes from sleep, but keyboard types symbols as opposed to correct letters

Hi, all,
Having been a mac owner for a few years now, I guess it actually shows the quality of the product that this is the first time I've had to post on this site.
I've recently upgraded from my 2008 model MacBook to an early 2011 model MacBook Pro 17" with Lion. This machine was brand new when I purchased it, and is a very lovely bit of kit.
The problem comes from the sleep functionality. Approximately one time of three, when I resume from sleep, the keyboard will be malfunctioning. What I mean by this is that when I type letters, they come out as symbols instead. I haven't been sharp enough to get a direct mapping of A-Z yet (I will do next time), but these aren't the 'ALT' key symbols (å∂ß∫å˙∂©ß), they're more like this (which is what I typed into Notepad last time this happened) =
ƒ∆∂∆ßåß∂ƒ∂∆ß∆å˚¬ß∆¬ß
In order to resolve this, I need to restart the computer, which, thus far, has resolved the issue every time. That said, it's a bit of a pain, so would like to know what's going on and if there is any way to prevent it.
All the software on the mac is up to date at time of writing, there have been no expansions to the machine (yet), so it's exactly as shipped. It's the 2.2GHz i7 Quad Core device, and is the first one supporting the thunderbolt graphics connector.
Does anyone have any idea about this? Could it be a hardware problem (if so, I want to return it asap to get it sorted). I've looked all over google for this, but not found a single result, so was keen to see if anyone on here had experienced it before I start the arduous process of working out if it's a hardware issue.
Cheers,
SB

No one else experienced anything like this, then?

Touchpad and trackpoint problems, especially when resuming from sleep

I am having persistent problems with the touchpad and trackpoint on my L530. I prefer to use the trackpoint usually, and found that the touchpad was super-sensitive and caused the cursor to jump around during normal (touch) typing so I disabled the touchpad. Next time the thinkpad resumed from sleep mode, the mouse was frozen. Nothing would reactivate it. I had to switch user, which temporarily fixed it, and then reactivate the touchpad.
If I try and change trackpad settings at any time other than directly after a reboot, the settings are greyed-out and I can't touch them. Right now, both trackpad and trackpoint are completely dead again, but I've plugged in a USB mouse and that seems to be working, so I've given up fiddling with it. This will be a pain when I'm moving around with the laptop though!
The OS is Windows 7. Yesterday I went looking for the most recent driver, uninstalled the existing one (as per guidance) and installed the new driver. No luck.
I've heard this is a common problem and apparently installing a generic driver works, but I'm not completely sure what to use. Anyone know?
Oh, and I'm not sure if this is related, but quite often when I resume from sleep mode the keyboard is also dead. However, if I switch user it comes back to life. So annoying but not the end of the world.

Thanks for posting this information in this forum. You just saved me a couple thousand dollars!
Based on my experience if you want to get this problem fixed as soon as possible you need to do the following:
1. www.apple.com/feedback
2. Post a video of the problem on www.youtube.com
3. Send www.apple.com/feedback a link to the video on youtube.
4. Encourage others to visit your youtube video and to post their own.
Good luck!

Laptop Crashes when resuming from sleep

Hi
I am running a Macbook Pro with retina display. OS X 10.8.3 - Mountain Lion.
Model Name:          MacBook Pro
Model Identifier:          MacBookPro10,1
Processor Name:          Intel Core i7
Processor Speed:          2,3 GHz
Number of Processors:          1
Total Number of Cores:          4
L2 Cache (per Core):          256 KB
L3 Cache:          6 MB
Memory:          8 GB
Peripherals: Magic Mouse, Thunderbolt to gigabyte Ethernet connector
I use this machine while connecting to a network using an Ethernet cable at work. During the day, I leave the machine and it automatically goes to sleep and when I resume from sleep there does not seem to be any problems.
The problem is when I put the machine off to sleep before going home, and then when I resume the next day; the system crashes.
I have been searching high and dry for a solution. Some forums talk about the OS' bluetooth management having a bug, others talk about network unable to reconnect and even read something that talks about a wifi issue.
I cant pin point the root cause of the problem nor do I have a workaround. I have to shutdown every night.
It seems that this problem has been around for a while and it scares me that Apple has not released a fix for this issue.
What should I do to resolve this issue?

Here is the latest panic log as requested:
Mon May 20 09:22:22 2013
panic(cpu 4 caller 0xffffff80234b7e95): Kernel trap at 0xffffff7fa4bf7064, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0x0000000000000010, CR3: 0x000000003e75f00e, CR4: 0x00000000001606e0
RAX: 0x0000000000000001, RBX: 0xffffff80f4ea7000, RCX: 0xffffff8038dc1000, RDX: 0xffffff81138aba38
RSP: 0xffffff81138abb60, RBP: 0xffffff81138abb60, RSI: 0x0000000000000000, RDI: 0x0000000000000000
R8: 0x0000000000000000, R9: 0x00000000000003ff, R10: 0xffffffffffffffff, R11: 0x00000000ffffffff
R12: 0xffffff80f4ea7000, R13: 0x0000000000000000, R14: 0x0000000000000002, R15: 0x0000000000000000
RFL: 0x0000000000010246, RIP: 0xffffff7fa4bf7064, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x0000000000000010, Error code: 0x0000000000000000, Fault CPU: 0x4
Backtrace (CPU 4), Frame : Return Address
0xffffff81138ab800 : 0xffffff802341d626
0xffffff81138ab870 : 0xffffff80234b7e95
0xffffff81138aba40 : 0xffffff80234cd4dd
0xffffff81138aba60 : 0xffffff7fa4bf7064
0xffffff81138abb60 : 0xffffff7fa4be0d64
0xffffff81138abbb0 : 0xffffff7fa4be0cba
0xffffff81138abbd0 : 0xffffff7fa4bbc7ae
0xffffff81138abc00 : 0xffffff7fa3acb3a0
0xffffff81138abc40 : 0xffffff7fa3acb30f
0xffffff81138abc60 : 0xffffff7fa3ad075c
0xffffff81138abcf0 : 0xffffff7fa3ac8e50
0xffffff81138abd20 : 0xffffff7fa3b19b8b
0xffffff81138abd70 : 0xffffff8023832e7b
0xffffff81138abdc0 : 0xffffff80238634f7
0xffffff81138abe30 : 0xffffff8023497fef
0xffffff81138abe80 : 0xffffff8023420aed
0xffffff81138abeb0 : 0xffffff8023410448
0xffffff81138abf00 : 0xffffff802341961b
0xffffff81138abf70 : 0xffffff80234a5dd6
0xffffff81138abfb0 : 0xffffff80234cdd43
      Kernel Extensions in backtrace:
         com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0 xffffff7fa3abf000->0xffffff7fa3af6fff
            dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7fa3a81000
         com.apple.NVDAResman(8.1)[A26D2A3D-C06F-3A0F-BCFF-901A98C93C3D]@0xffffff7fa3b16 000->0xffffff7fa3e23fff
            dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7fa3a81000
            dependency: com.apple.iokit.IONDRVSupport(2.3.7)[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xff ffff7fa3b02000
            dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0 xffffff7fa3abf000
         com.apple.GeForce(8.1)[A15BB65E-3501-340F-87CB-2FD2BAD33E35]@0xffffff7fa4bb9000 ->0xffffff7fa4c85fff
            dependency: com.apple.NVDAResman(8.1.0)[A26D2A3D-C06F-3A0F-BCFF-901A98C93C3D]@0xffffff7fa3b 16000
            dependency: com.apple.iokit.IONDRVSupport(2.3.7)[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xff ffff7fa3b02000
            dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7fa3a81000
            dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0 xffffff7fa3abf000
BSD process name corresponding to current thread: WindowServer
Mac OS version:
12D78
Kernel version:
Darwin Kernel Version 12.3.0: Sun Jan 6 22:37:10 PST 2013; root:xnu-2050.22.13~1/RELEASE_X86_64
Kernel UUID: Kernel_UUID
Kernel slide:     0x0000000023200000
Kernel text base: 0xffffff8023400000
System model name: MacBookPro10,1 (Mac-C3EC7CD22292981F)
System uptime in nanoseconds: 37416231729
last loaded kext at 11253530868: com.apple.filesystems.autofs          3.0 (addr 0xffffff7fa4e19000, size 45056)
loaded kexts:
com.apple.filesystems.autofs          3.0
com.apple.driver.AudioAUUC          1.60
com.apple.iokit.IOBluetoothSerialManager          4.1.3f3
com.apple.driver.AGPM          100.12.87
com.apple.driver.ApplePlatformEnabler          2.0.6d1
com.apple.driver.X86PlatformShim          1.0.0
com.apple.driver.AppleMikeyHIDDriver          122
com.apple.driver.AppleHDAHardwareConfigDriver          2.3.7fc4
com.apple.iokit.IOUserEthernet          1.0.0d1
com.apple.driver.AppleHDA          2.3.7fc4
com.apple.driver.AppleUpstreamUserClient          3.5.10
com.apple.iokit.IOBluetoothUSBDFU          4.1.3f3
com.apple.driver.AppleMikeyDriver          2.3.7fc4
com.apple.driver.AppleBacklight          170.2.5
com.apple.iokit.BroadcomBluetoothHCIControllerUSBTransport          4.1.3f3
com.apple.GeForce          8.1.0
com.apple.driver.AppleIntelHD4000Graphics          8.1.0
com.apple.driver.AppleMCCSControl          1.1.11
com.apple.Dont_Steal_Mac_OS_X          7.0.0
com.apple.driver.AppleSMCPDRC          1.0.0
com.apple.driver.ACPI_SMC_PlatformPlugin          1.0.0
com.apple.driver.AppleSMCLMU          2.0.3d0
com.apple.driver.AppleLPC          1.6.0
com.apple.driver.AppleMuxControl          3.3.0
com.apple.driver.ApplePolicyControl          3.3.0
com.apple.driver.AppleIntelFramebufferCapri          8.1.0
com.apple.nvidia.NVDAStartup          8.1.0
com.apple.driver.AppleUSBTCButtons          237.1
com.apple.driver.AppleUSBTCKeyEventDriver          237.1
com.apple.driver.AppleUSBTCKeyboard          237.1
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.driver.XsanFilter          404
com.apple.iokit.IOAHCIBlockStorage          2.3.1
com.apple.driver.AppleUSBHub          5.5.5
com.apple.driver.AppleSDXC          1.4.0
com.apple.iokit.AppleBCM5701Ethernet          3.6.0b1
com.apple.driver.AirPort.Brcm4331          614.20.16
com.apple.driver.AppleAHCIPort          2.5.1
com.apple.driver.AppleUSBEHCI          5.5.0
com.apple.driver.AppleUSBXHCI          5.5.5
com.apple.driver.AppleEFINVRAM          1.7
com.apple.driver.AppleSmartBatteryManager          161.0.0
com.apple.driver.AppleRTC          1.5
com.apple.driver.AppleACPIButtons          1.7
com.apple.driver.AppleHPET          1.8
com.apple.driver.AppleSMBIOS          1.9
com.apple.driver.AppleACPIEC          1.7
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.kext.triggers          1.0
com.apple.iokit.IOSCSIArchitectureModelFamily          3.5.5
com.apple.iokit.IOSerialFamily          10.0.6
com.apple.driver.DspFuncLib          2.3.7fc4
com.apple.iokit.IOAudioFamily          1.8.9fc11
com.apple.kext.OSvKernDSPLib          1.6
com.apple.iokit.IOSurface          86.0.4
com.apple.iokit.IOBluetoothFamily          4.1.3f3
com.apple.iokit.AppleBluetoothHCIControllerUSBTransport          4.1.3f3
com.apple.nvidia.gk100hal          8.1.0
com.apple.NVDAResman          8.1.0
com.apple.iokit.IOAcceleratorFamily          30.14
com.apple.driver.AppleSMBusController          1.0.11d0
com.apple.driver.IOPlatformPluginLegacy          1.0.0
com.apple.driver.X86PlatformPlugin          1.0.0
com.apple.driver.AppleSMC          3.1.4d2
com.apple.driver.AppleSMBusPCI          1.0.11d0
com.apple.driver.IOPlatformPluginFamily          5.3.0d51
com.apple.driver.AppleBacklightExpert          1.0.4
com.apple.driver.AppleGraphicsControl          3.3.0
com.apple.driver.AppleThunderboltEDMSink          1.1.8
com.apple.driver.AppleThunderboltEDMSource          1.1.8
com.apple.driver.AppleThunderboltDPOutAdapter          1.8.9
com.apple.driver.AppleHDAController          2.3.7fc4
com.apple.iokit.IOHDAFamily          2.3.7fc4
com.apple.iokit.IONDRVSupport          2.3.7
com.apple.iokit.IOGraphicsFamily          2.3.7
com.apple.driver.AppleThunderboltDPInAdapter          1.8.9
com.apple.driver.AppleThunderboltDPAdapterFamily          1.8.9
com.apple.driver.AppleThunderboltPCIDownAdapter          1.2.6
com.apple.driver.AppleUSBMultitouch          237.3
com.apple.iokit.IOUSBHIDDriver          5.2.5
com.apple.driver.AppleUSBMergeNub          5.5.5
com.apple.driver.AppleUSBComposite          5.2.5
com.apple.driver.AppleThunderboltNHI          1.6.3
com.apple.iokit.IOThunderboltFamily          2.2.6
com.apple.iokit.IOEthernetAVBController          1.0.2b1
com.apple.iokit.IOUSBUserClient          5.5.5
com.apple.iokit.IO80211Family          522.4
com.apple.iokit.IONetworkingFamily          3.0
com.apple.iokit.IOAHCIFamily          2.3.1
com.apple.iokit.IOUSBFamily          5.5.5
com.apple.driver.AppleEFIRuntime          1.7
com.apple.iokit.IOHIDFamily          1.8.1
com.apple.iokit.IOSMBusFamily          1.1
com.apple.security.sandbox          220.2
com.apple.kext.AppleMatch          1.0.0d1
com.apple.security.TMSafetyNet          7
com.apple.driver.DiskImages          345
com.apple.iokit.IOStorageFamily          1.8
com.apple.driver.AppleKeyStore          28.21
com.apple.driver.AppleACPIPlatform          1.7
com.apple.iokit.IOPCIFamily          2.7.3
com.apple.iokit.IOACPIFamily          1.4
com.apple.kec.corecrypto          1.0

Wifi Lost and Network Preferences Inaccessible after Resume from Sleep

Macbook Pro, shipped with Lion.
I've had a problem when Lion resumes from sleep of not being able to access any networks. Specifically, the wifi symbol in the menu bar shows the pulsating waves, when clicked it reports that it is searching for networks, however it doesn't find the standard wireless network it is normally connected to at home, nor can I choose any further options in that dropdown menu. Specifically, I cannot access Network Preferences, via any GUI based method (don't know enough CLI to know how).
Most alarming is that this has happened in a couple of different scenarios:
1) normally putting the laptop to sleep if 2 different users are logged in via fast user switching
2) if the computer shuts itself down from the sleep position because it has been unplugged for too long.
Restarting does revert everything back to normal, but I was hoping for a less drastic fix. Sorry to gripe, but I'm especially disappointed because I'm a mac newbie, and between this and other problems, have had to restart this mac due to spinning pinwheels of death and the like more in 2 months than I ever have a Sony Vaio Z running Windows 7. Kind of disappointing that Mac has the less stable operating system.

That's awkward. It may not be the Mac itself making it unstable, but yet programs on it making it unstable (lazy developers maybe). Although do remember that OS X Lion is fairly new, and a few bugs are still being ironed out.
First thing you should do is Repair permissions. Open up Disk Utility, Chose your disk on the Left and click on the Repair Permissions button. This can take about 20 minutes and fixes most problems.
Questions:
Have you installed any additonal system prefence panels?
Have you installed any programs that alter with WiFi?
Does your WiFi Access point have enough strength for where you are?
If you have installed addional system preferences then I suggest that you go to Finder, and in the top bar click on "Go" and navigate to "Go To Folder". In that box put this: "~/Library/PreferencePanes" (No quotes though - and remember the "~" ).
It'll take you to a folder, copy those into a safe location and remove the contents of that folder.
If you are an Administrator of your computer then do the same in "/Library/PreferencePanes".
Hope all goes well! Good luck!

Msi Z68 GD65 (B3) will not resume from sleep with multiplier above 43

I have an i5 2500k that is otherwise stable (can pass prime95 for hours) at 4.4 ghz, but no matter what I do I cannot get my computer to resume from sleep properly when I go over 4.3 ghz. At 4.3 ghz it resumes from sleep fine, but once the multiplier goes over 43 it simply will not resume. The monitor stays in standby mode, but my PC's fans spin up and my keyboard backlight turns on.
I have tried disabling and enabling pll overvoltage, but it does not help.
It resumes from hibernation fine, but that takes quite a bit longer than resuming from sleep because the POST on this board isn't particularly fast.
This happened both with my previous card (560 ti) and my current card (7950), so I seriously doubt it is a GPU issue. I have a seasonic x750 PSU, so I doubt it is a power issue. I have very good cpu cooling and my temperatures are pretty low even under load. Is this a board defect? I see that ASUS boards had a similar issue that was apparently fixed, but I can't find as much info about an MSI isssue.

Being an experienced OC'er, then you know that trial and error is the tried and true time honored method in the attempt to solve problems. The solution I would recommend is to accept an OC of 4.3, stick with hibernation, or continue with experimentation of combinations of settings, or you can hope someone comes along that 'may' know of a 'solution'.
Quote
I see that xxxx boards had a similar issue that was apparently fixed, but I can't find as much info about an MSI isssue.
Big difference between 'apparently' fixed and actually fixed. You might try MSI Technical, but it may be interesting what they say once they know OC'ing is involved.
>> How To Contact MSI <<
Quote
Thank you for the patronizing response. Does anyone have a response that is actually useful instead of generic "you don't know what OCing does" comments? I have been OCing for years; I know what it does to a system. I am looking for SOLUTIONS here.
Some friendly advice is to watch the attitude, or not many will be inclined to offer any assistance at all. Yours is not a situation that the mainboard is non functional, and is more related to an OC'ing behavior.

Update to 10.6.8 - system hang (mouse issue) after resume from sleep

I am on older
MacBook Pro3.1
Intel Core 2 Duo
2.6GHz
Run on 10.6.8 almost flawelessly. Shortly after upgrade to 10.6.8 system started to hang periodically after resuming from sleep. Symptoms are that it stops responding to mouse (be it touch pad or USB mouse). Keyboard seems to be ok but system doesn't seem to be fully functional. I am able to ssh from the other computer and 'shutdown -r now' after reboot system seem to be ok until next resume from sleep. What interesting though is that this problem newer manifests then I am using external monitor.

Found problem. It was due to magic mouse that I left on. I carry this mouse in the laptop bag but rarely use it. Last time I used it (around the same time I install the update) I left it on in the bag. It was apparently disconnecting/connecting on its own and by some reason sometimes was breaking touch pad and other usb mouse connected to laptop, as soon as I switched magic mouse off broblem was fixed

X120E Touchpad inoperable after resuming from sleep

hello friends I'm a happy X120E user and a tech [pc's, mac's, lans, etc] - I do all sorts of tasks with my x120e and its been great. I recently "upgraded" my SSD so a fresh new install of Windows 7 was in order. After updating everything I have a problem I did not experience previously at all - not once in 3 years of use.
Upon resuming from sleep [and as far as I can remember this only occurs when resuming on battery], the touchpad/cursor is inoperable, frozen in the centered position, and I have found no way to 'wake' it. I finally have to shutdown/restart to get things functioning again. Keyboard works fine, but not touchpad or trackpoint [either/both].
maddeningly, its not consistent in this. sometimes it works, sometimes it does not.
I have seen the same issue with, and without, the supplied Lenovo Ultranav driver installed.
Question: in the X120E implementation, is the touchpad a PCI bus device or a USB device? I see no power plan options [i.e. "Advanced" >"Allow this device to wake the computer"] available via Device properties. There are no pointer/mouse/touchpad options whatsoever under Power Plan Settings.
Will Fn+F8 enable/disable the touchpad on this notebook? or,... should it?

No. Powering off and on again didn't work. My drive is a Seagate 750GB internal SATA drive in a Vantec NexStar-3 external enclosure. I don't think it is a driver issue. After the device removal error it won't mount on my PC or my Mac via FireWire or USB.
What I need to know is if there is some way to connect to the drive and make it mount with other software, using some kind of keystroke during startup, or maybe through terminal or something. I can't even try to repair the drive because it won't show up in disk utility.

Windows explorer + other windows applications crashing regularly at resume from sleep and hibernate

Good evening,
I have a Thinkpad W510 (4319-29G) running Windows 7 Pro 64bit. The system is loaded with the latest software and drives from Lenovo including BIOS 6NET74WW (1.34), upgrade was done Dec 7th (windows update performed Dec 15th).
The machine has
- 8Gb RAM
- nVidia Quadro FX880M, driver version is 8.17.12.5896, 7-9-2010 and video card BIOS is 70.16.5f.0.b
- dual harddrives,
- one Seagate Momentus XT 500Gb (ST95005620AS) FW rev SD23 in the main location with C: and some other partitions
- one Hitatchi 320 Gb (HTS723232L9SA60) FW rev FC4ZC50B in the bay.
- Intel Centrino Advanced-N 6200 AGN, driver version 13.3.0.24, 7-14-2010
- Intel 82577LM Gigabit Network Connection, driver version 11.5.10.1030, 7-22-2010
Recently I have experienced crashes of multiple windows components at resume from sleep and hibernate.
It seems to happen when swithing location (from work to home) and thus switching from docking station with wired network connection to no dock and wireless network connection (dont know if this has any bearing but anyway).
In the event viewer I typically have some 6-12 application errors logged. Sample output from event viewer is:
Log Name: Application
Source:Application Error
EventID:1000
Level:Error
Logged:2010-12-15 20:30:02
Task category100)
Keywords: Classic
Computer: xxxxxxx (my computername)
Then for each application the following detailed data is written in event viewer in the general tab:
#1
Faulting application name: rundll32.exe_nview64.dll, version: 6.1.7600.16385, time stamp: 0x4a5bc9e0
Faulting module name: nview64.dll, version: 6.14.10.13527, time stamp: 0x4c35752f
Exception code: 0xc0000005
Fault offset: 0x00000000000f0786
Faulting process id: 0x115c
Faulting application start time: 0x01cb9bd59882f1f6
Faulting application path: C:\Windows\system32\rundll32.exe
Faulting module path: C:\Program Files\NVIDIA Corporation\nView\nview64.dll
Report Id: b606b17d-0881-11e0-be39-00a0c6000000
#2
Faulting application name: taskhost.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1
Faulting module name: nview64.dll_unloaded, version: 0.0.0.0, time stamp: 0x4c35752f
Exception code: 0xc000041d
Fault offset: 0x00000001800bb350
Faulting process id: 0x10c0
Faulting application start time: 0x01cb9bd5694caebe
Faulting application path: C:\Windows\system32\taskhost.exe
Faulting module path: nview64.dll
Report Id: b6ae8cb2-0881-11e0-be39-00a0c6000000
#3
Faulting application name: sidebar.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc9e1
Faulting module name: nview64.dll_unloaded, version: 0.0.0.0, time stamp: 0x4c35752f
Exception code: 0xc000041d
Fault offset: 0x00000001800bb350
Faulting process id: 0x6f0
Faulting application start time: 0x01cb9bd5986a397a
Faulting application path: C:\Program Files\Windows Sidebar\sidebar.exe
Faulting module path: nview64.dll
Report Id: b6bd0bd9-0881-11e0-be39-00a0c6000000
#4
Faulting application name: Explorer.EXE, version: 6.1.7600.16450, time stamp: 0x4aebab8d
Faulting module name: nview64.dll_unloaded, version: 0.0.0.0, time stamp: 0x4c35752f
Exception code: 0xc000041d
Fault offset: 0x0000000008c3b350
Faulting process id: 0x1210
Faulting application start time: 0x01cb9bd569d9ae8e
Faulting application path: C:\Windows\Explorer.EXE
Faulting module path: nview64.dll
Report Id: b6d21ac7-0881-11e0-be39-00a0c6000000
#5
Faulting application name: Dwm.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc541
Faulting module name: nview64.dll_unloaded, version: 0.0.0.0, time stamp: 0x4c35752f
Exception code: 0xc000041d
Fault offset: 0x00000001800ba570
Faulting process id: 0x11c4
Faulting application start time: 0x01cb9bd569aa125c
Faulting application path: C:\Windows\system32\Dwm.exe
Faulting module path: nview64.dll
Report Id: b72bfbe8-0881-11e0-be39-00a0c6000000
#6
Faulting application name: rundll32.exe_PWMTR64V.DLL, version: 6.1.7600.16385, time stamp: 0x4a5bc9e0
Faulting module name: nview64.dll_unloaded, version: 0.0.0.0, time stamp: 0x4c35752f
Exception code: 0xc000041d
Fault offset: 0x00000001800bb350
Faulting process id: 0x1450
Faulting application start time: 0x01cb9bd59995023a
Faulting application path: C:\Windows\system32\rundll32.exe
Faulting module path: nview64.dll
Report Id: b7e4521b-0881-11e0-be39-00a0c6000000
It seems that a module "nview64.dll" is always the first application to crash. I suspect this has something with graphics to do.
I dont know if this event triggers the following crashes or if it is so that the display is initialized before the other programs.
After all crash diagnostic messages have been shown windows explorer restarts and also other applications restart but a lot of system tools in the system tray are gone so a cold start is needed to restore all tools again.
I really would appreciate any help and suggestions how to fix this really annoying issue.
Thanks, Anton

I had a similar issue, as soon as a described even a little bit of it to warrenty support they sent someone to swap the board
It seems thats the only fix, its been fine since

Airport no longer works after resuming from sleep

I got a new MacIntel a month or so ago, and it has always done this, under 10.4.4 and now 10.5.5
When resuming from sleep, airport shows full strength for second, then the signal disappears. NOTHING in settings, reconnecting etc will get it to work again. (this is 'deep' sleep, not just the display turning off)
If you restart (restart not shut down), then when it comes back, airport is just gone - even the menu bar indicator. The computer now thinks it has no airport installed at all. No matter how many times you restart, there is no longer any airport.
If you shut down, wait a minute and restart, it works as normal.
Since airport is the only way I connect to the network, and I don't want to waste electricity, this is unacceptable and clearly a flaw.
I called tech support and they had me move airport to the top of the list, delete plists and other stuff, none of which made any difference. I'm thinking this is a low level system software fault, and I hope I don't have to take it back for a motherboard replacement.

I also have this problem, although, not very often.
I'm still running 10.4.4. This never happened with
prior versions. Rebooting is the only way to
correct the problem. Simply turning off Airport and
turning it back on does not help.
Thats interesting actually because I Never had any trouble on my G5 iMac of otherwise identical specification, on on intel. Hmm. I was thinking this was an intel issue.
Wonder if its a hardware problem (though I suspect not).

Reactivate SN resume-from-sleep behavior in Lion?

Similar Messages

Maybe you are looking for