Resume from sleep speed - 2011 Air

2011 Mac Air Core i7 - 256 gig HDD - LION
When i close lid for air to sleep, then i re-open it takes about 3-4 seconds.
At first I see a black screen and my cursor, a about 3 seconds then the desktop.
What is your speed - I have a friend with a 2010 Mac Air and it resumes instantly!!
PS My startup disk wasnt selected, i did this and it made no difference.
Is my Air a Dudd ?

Good find! I think you're absolutely right.
I just opened my Air after not using it for a couple of days and noticed the slow wake from sleep often and thought by myself "I thought this thing is supposed to wake quickly because of the SSD?".
I use my 2011 Air mostly as a 2nd machine and so it's often been sleeping for a couple of hours.
The difference between waking the Air a couple of minutes after sleeping it and when it's been lying around for a couple of hours are night-and-day and the support article explains why this is the case.

Similar Messages

  • Slow LAN Networking Speeds after Resuming from Sleep

    I use my mac mini as a HTPC running Plex. I have it connected to my Windows media server with 802.11n. Works fine but sometimes after resuming from sleep the network speed drops off to an unacceptable level (from 72 Mb/sec to 5 Mb/sec). Disconnecting and reconnecting doesn't help. Switching to G doesn't help. Only restarting the mini restores the connection to full speed.
    None of my Windows clients on the same network have any troubles.
    Thoughts?

    Looks like Plex might be causing the problem. I always have plex running and it appears as though if Plex makes a request for a file on the share before OS X is done re-mounting it after sleep, it kills the whole process.
    Shouldn't the OS be robust enough to handle a situation like this?

  • Lets speed up resume from sleep

    So I am a laptop user and most everything works, but suspend(I rarely power down) is a little slow, or should I say resuming from suspend.  I counted it to be around 20-25s to come up.  I did some poking around and started editing some of my suspend scripts in /usr/lib/pm-utils/sleep.d.  I removed the suspend resume network manager because I use Arch Assistant and netcfg2.  That didn't seem to make a real difference (maybe a second).  The next thing I changed was the netcfg script.  I changed the netcfg2 all-resume/resume to run in the background via a & at the end and that seemed to make a big difference.  Suspend was a few seconds faster and resume now took around 10s.  So the question I have for all of you experts is what other scripts can be tweaked or added to the background to speed up the resume process?  By the way my network has seemed to work just fine and I can ping addresses as soon as the system awakes.
    Lets see if we can get arch to resume in 2 seconds!  If it can already enlighten me please.

    You can do a little test... Issue:
    echo "mem" > /sys/power/state
    as root.  That will send your computer to sleep without running any scripts on suspend/resume.  Time how long it takes to resume from sleep.  There is a chance that the system will not resume properly, since that method uses no hardware specific quirks, so be warned, but it should give you an idea of how fast it can be made to work or, in other words, what the hardware/kernel limitations are.
    10 seconds sounds about right, by the way.  2 seconds?  No way!

  • 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?

  • 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.

  • X220 very slow reconnecting to WiFi when resuming from sleep

    So my X220 with the Intel 6205 card is having issues reconnecting to WiFi when resuming from sleep or hibernation. It takes about a minute for it to do so, though occasionally it will reconnect right away. Maybe 1 out of 20. When doing a cold boot or restart, it connects immediately upon the desktop showing up.
    This was not always the case, in fact when I first got my X220 in June, I have not had this issue.... In fact, I don't know when it started happening, but it was maybe a couple months ago. I just thought it was my old router going bad. Well I got a new router, and it still happens. I have the latest Intel WiFi drivers from Lenovo, and I even tried downgrading to the previous driver from Intel's site. Still the same problem. I tried setting a default profile in access connections, and that does not help. In fact, it behaves the same way if I totally uninstall access connections as well. In fact I tried this on three different brand routers, and I can reproduce it on all of them (Asus, Netgear & TP-Link) so I think this is not a router issue. Other devices in the house reconnect right away with no issues (iPhone 4, PS3, Mac desktop, Dell laptop).
    I currently have BIOS 1.24, but this was happening with 1.21 and 1.23 as well. My X220 originally came with 1.16, and I haven't updated it until 1.21. Unfortunately I don't remember that far back, if the problem started occuring then.
    There was a brief discussion about this in another thread, but it went nowhere so perhaps this will get more attention. At least one other user reported the same issue.
    Here's a clip of exactly what happens. When i press the button or open the lid from sleep, the windows wifi icon will start spinning for a few seconds, then turn into an X. then only about a minute later, does it quickly connect to the wifi and I have full signal. Manually clicking on the icon and selecting the access point does not speed up the process. It will only connect when it wants to, about a minute after resuming from sleep/hibernation.
    http://youtu.be/dmboeA7HBgg
    | X220 i7-2620M | 12.5" IPS | Intel 520 Series 180GB Main SSD | Mushkin 120GB mSATA SSD | 8GB RAM | Intel 6205 WiFi | BT | Win7 Pro 64 SP1 |
    Solved!
    Go to Solution.

    Normally when a laptop running windows tries to connect to a network, it may also seek to identify certain components on the network, for example, asking the router "Who are you?". In your case, maybe the config are corrupted because the network address entries are messed up. Queries send out to the network come back with no replies, and the computer waited for the default time till timeout and it gives up.
    Try this one at a time, reboot, or try all at once and reboot
    TCP/IP stack repair options for use with Vista or 7.
    Start, Programs\Accessories and right click on Command Prompt, select "Run as Administrator" to open a command prompt.
    Reset WINSOCK entries to installation defaults: netsh winsock reset catalog
    Reset IPv4 TCP/IP stack to installation defaults. netsh int ipv4 reset reset.log
    Reset IPv6 TCP/IP stack to installation defaults. netsh int ipv6 reset reset.log
    Reboot the machine.

  • 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

  • GTX660 Twin Frozr 3 OC and resume from sleep problem

    Hi,
    My 660 twin frozr performs perfectly in game/bench and standard operation but I get consistent error messages when resuming from sleep 'hybrid, S3).
    Messages are : either "the graphic driver did not respond and has recovered" or a BSOD "driver verifier has detected violation" or "DPC watchdog violation"
    My system :
    -Windows 8 64bits
    -MSI 660 TF3 OC at stock speed
    -MB: Gigabyte H77N WiFi, BIOS F2 then F3C
    -i5 3470 at stock speed
    -RAM: 2x4GB Crucial ballistic tactical low profile 12800 (XMP profile 1 at 1600MHz 1.35V), OK for hours at memtest86
    -PSU: Seasonic G-360. 360W seem low power but 12V single rail is 30A and it powers my system at full load flawlessly (OCCT, game, unigine bench and so on)
    What I have tried :
    -reinstall windows 8, MB drivers (chipset, WiFi...)
    -updated the bios from F2 to latest (but beta) F3C
    -nvidia 310.90whql, then 314.07whql (using driver fusion for cleaning)
    The resume from sleep issue is still there
    Then I tried:
    -the 660 TF in a old core2duo with a MSI P35neo MB and vista 32bits. It resumes with the notification "the driver did not respond and has recovered successfully. nvlddmkm..." No BSOD but got this notification each time
    -then I tried the old ATI HD4670 in my new PC and the resume/sleep works like a charm.

    OK, I had to make a bootable USB drive with DOS because nvflash is not 64bits compatible.
    My S/N is 602-v287-050B1212022370 (checked on the box).
    What is in the rep.txt you ask :
    NVIDIA Firmware Update Utility (Version 5.127)
    Adapter: D14P2-35             (10DE,11C0,1462,2871) H:--:NRM B:01,PCI,D:00,F:00
    The display may go *BLANK* on and off for up to 10 seconds during access to the EEPROM depending on your display adapter and output device.
    Identifying EEPROM...
    EEPROM ID (7F,9D22) : PMC Pm25LD020 2.7-3.6V 2048Kx1S, page
    Reading adapter firmware image...
    Image Size            : 98816 bytes
    Version               : 80.06.28.00.39
    ~CRC32                : F75220C8
    OEM String            : NVIDIA
    Vendor Name           : NVIDIA Corporation
    Product Name          : GK106 Board - 20300000
    Product Revision      : Chip Rev   
    Device Name(s)        : D14P2-35
    Board ID              : E307
    PCI ID                : 10DE-11C0
    Subsystem ID          : 1462-2871
    Hierarchy ID          : Normal Board
    Chip SKU              : 400-0
    Project               : 2030-0000
    CDP                   : N/A
    Build Date            : 09/17/12
    Modification Date     : 11/01/12
    UEFI Support          : No
    UEFI Version          : N/A
    Sign-On Message       : GK106 P2030 SKU 0 VGA BIOS
    MSINV287MS.204
    VBIOS copied with GPU-Z : http://speedy.sh/mvjdk/GK106orig8006280039.rom

  • 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.

  • 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).

  • I7 iMac with Bootcamp 3.1 and Windows7 64-bit won't resume from sleep

    When I try to resume from sleep, by clicking the magic mouse button, the screen comes up and I can move the mouse around but the bluetooth keyboard does not work and I can't launch any programs. Have to use the rear button to force a power off and restart.
    Is anyone able to resume from sleep okay and carry on using Windows 7? If so, any tips? Thanks in advance, very frustrating.

    I don't have an iMac, and it seems those have some design "issues" to say the least. I'd say yes, motherboard and/or firmware (UEFI or SMC, or both) could be buggy and at fault.
    Other than resetting SMC and running Apple Hardware Test, not sure what else or next to try.
    I've seen a number of BIOS updates out in the last months for my PC motherboards that have definitely improved sleep, S3, hibernation - EVGA, Gigabytes, and Intel - all X58 vs P55 (Lynnfield Core i5/7 LGA 1156) the iMac uses.
    http://anandtech.com/cpuchipsets/showdoc.aspx?i=3634
    http://en.wikipedia.org/wiki/IntelCorei5
    First I switched to Windows Vista/7, then I switched to build-my-own and custom parts. Love the looks of iMac, came close at one point, but I prefer the specs, options, and configure for my own needs in hard drives, graphics over cool factors.
    The iMac even in 2008 when it came with Penryn 64-bit processors never got 64-bit Vista/Boot Camp drivers, and that was why I didn't buy iMac back then, just lack of support I guess, and not seeing the market and need (for a good solid Windows desktop machine by Apple).

  • 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

Maybe you are looking for