Yoga 13 freezes 1-2 times a day
hello, i bougt a Lenovo yoga 13 a couple days ago. the yoga freezes 1-2 times per day. the Screen Shows the frozen application, the Keyboard, touchpad or mouse didnt Response. i watched into the logfile and DptfPolicyLpmServiceHelper is the last entry before the Crash. i uninstalled the Dynamic Platform and Thermal Framework, but it doesnt help. any ideas what i could do?
Solved!
Go to Solution.
hi jeanclaude,
Welcome to the Lenovo Community.
Your problem might be similar to the first question on this thread.
Can you try to disable this service called "ymc" or Yoga Mode Control by doing the following:
1. Open control panel and type "Local services" in search box
2. Click on Local services, scroll down to ymc, right click > properties > stop > startup type - disabled.
3. Restart laptop and the keyboard and mouse disabling problem should be fixed.
Credits goes to Hasan10.
Let me know your findings
Cheers
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!
Similar Messages
-
Iphone 4 keeps freezing/crashing several times a day. help!!!
iphone 4 keeps freezing/crashing several times a day.
its been doing it since i got the phone a couple of weeks ago. when i got it i sync'd it and put all my apps from my ipod touch on to it. they were all fine on the touch which was running os4
-
Help: G5 Crashes, Locks Up, Freezes, 3/4 Times A Day!
I have Powermac G5 1.6 ppc, and it crashes 3 to 4 or 5 times a day. When it crashes, if ther is any music playing in itunes, it will skip, and then you can't move the mouse, or even hit force quit.
I have to turn it on and off with power button.
I have done new install, disk repair, virus scans, and even checked crash log. When the computer restarts it acts as if there was never a crash.
I also isolated all programs to see if it was a program, and it would still lock up.
I am getting really ticked about this, because this is my 2nd apple computer. Not sure why I keep giving them all my hard earned cash.virus scans
What are you using? Anti-virus software is usually a big cause.
Apple changes something and it breaks the AV, or the AV software itself gets exploited. Norton and McAfee both have been avenues for root level exploits in Mac's.
My advise is to do this:
1: backup and c boot from the Tiger install disk (check the disk if it's smudged, see if you can get it exchanged)
2: Select Disk utility, Erase w/Zero and come back later.
(zeroing rewrites the bad sector map and other things, making better writes, usually only needed once per drive unless you have a security issue or potentially damaged the drive during handling)
3: Install Tiger and combo update to 10.4.7 w/security update
4: Don't install AV or any other software, just see if the KP's (kernel panicks) continue.
5: If everything is fine then move on with iLife '06
6: If everything is fine then move on with apps that don't require a admin password to install. Go on like that until the cause shows itself again.
7: Clone your boot drive through out this process, this way you can easily "rewind" to a state before the change occured.
If you still have problems with just a basic OS install, then you need to start looking at a hardware, firmware issue.
Here's how to clone your boot drive.
http://discussions.apple.com/thread.jspa?messageID=2765117�
You can search Macupdate.com for "Rember". It's a GUI front for "Memtest" which you can easily test your RAM for defects. -
Mac Mini Experiencing Hard Freeze 3-4 Times Per day...
About 10 days ago, my mid-2011 Mac Mini started experiencing a hard freeze wherein I would get the spinning beachball and slowly each open app would be come unresponsive and my only resort was to hold down the power button to restart. Upon reboot, the system would work fine for about an hour then the freeze would start again. I've rolled back my configuration to a state prior to the freezing, and in desperation, have done a completely clean re-install of the OS.
System specs:
Mid-2011 Mac Mini 2.7 GHz Core i7
16 GB RAM
256GB SSD
750GB HDD
Attached to a 27" LED Cinema Display, and an Airport Extreme Basestation/TimeCapsule (TimeMachine temporarily disabled)
I've been reading the logs, but don't really know how to interpret them so I've included a a number of postings right up until I force the reboot.
Thanks in advance!
Log below: The system performs fine until 12:15 or so
Sep 6 12:03:56 Kriss-Mac-mini.local WindowServer[94]: CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
Sep 6 12:04:05 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendAttachNotification (thread 0x7fff7d227180): sending attach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _GetAddrInfoReplyReceivedCallback matched.
Sep 6 12:04:05 Kriss-Mac-mini.local usbmuxd[44]: _AMDeviceConnectByAddressAndPort (thread 0x100781000): IPv4
Sep 6 12:04:27 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendDetachNotification (thread 0x7fff7d227180): sending detach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _BrowseReplyReceivedCallback got bonjour removal.
Sep 6 12:06:31 Kriss-Mac-mini.local WindowServer[94]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10ba04eb0
Sep 6 12:06:31 Kriss-Mac-mini.local WindowServer[94]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10ba04f40
Sep 6 12:06:31 Kriss-Mac-mini.local WindowServer[94]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10ba04fd0
Sep 6 12:06:31 Kriss-Mac-mini.local WindowServer[94]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10ba05090
Sep 6 12:06:31 Kriss-Mac-mini.local WindowServer[94]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x1009dfbc0
Sep 6 12:06:31 Kriss-Mac-mini.local WindowServer[94]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x1009dfc50
Sep 6 12:06:31 Kriss-Mac-mini.local WindowServer[94]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x1009dfce0
Sep 6 12:06:31 Kriss-Mac-mini.local WindowServer[94]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10ba04e20
Sep 6 12:06:44 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendAttachNotification (thread 0x7fff7d227180): sending attach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _GetAddrInfoReplyReceivedCallback matched.
Sep 6 12:06:44 Kriss-Mac-mini.local usbmuxd[44]: _AMDeviceConnectByAddressAndPort (thread 0x100781000): IPv4
Sep 6 12:06:55 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendDetachNotification (thread 0x7fff7d227180): sending detach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _BrowseReplyReceivedCallback got bonjour removal.
Sep 6 12:07:38 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendAttachNotification (thread 0x7fff7d227180): sending attach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _GetAddrInfoReplyReceivedCallback matched.
Sep 6 12:07:38 Kriss-Mac-mini.local usbmuxd[44]: _AMDeviceConnectByAddressAndPort (thread 0x100781000): IPv4
Sep 6 12:07:49 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendDetachNotification (thread 0x7fff7d227180): sending detach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _BrowseReplyReceivedCallback got bonjour removal.
Sep 6 12:08:36 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendAttachNotification (thread 0x7fff7d227180): sending attach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _GetAddrInfoReplyReceivedCallback matched.
Sep 6 12:08:36 Kriss-Mac-mini.local usbmuxd[44]: _AMDeviceConnectByAddressAndPort (thread 0x100781000): IPv4
Sep 6 12:08:47 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendDetachNotification (thread 0x7fff7d227180): sending detach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _BrowseReplyReceivedCallback got bonjour removal.
Sep 6 12:09:33 Kriss-Mac-mini.local com.apple.qtkitserver[759]: *** WARNING: -[NSImage compositeToPoint:operation:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.
Sep 6 12:09:33 Kriss-Mac-mini.local com.apple.qtkitserver[759]: *** WARNING: -[NSImage compositeToPoint:fromRect:operation:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.
Sep 6 12:09:33 Kriss-Mac-mini kernel[0]: Sandbox: sandboxd(769) deny mach-lookup com.apple.coresymbolicationd
Sep 6 12:09:35 Kriss-Mac-mini.local sandboxd[769] ([759]): com.apple.qtkits(759) deny mach-lookup com.apple.printtool.agent
Sep 6 12:10:15 Kriss-Mac-mini.local com.apple.qtkitserver[777]: CGAffineTransformInvert: singular matrix.
Sep 6 12:10:15 --- last message repeated 3 times ---
Sep 6 12:10:15 Kriss-Mac-mini.local com.apple.qtkitserver[777]: CGSGetWindowBounds: Invalid connection
Sep 6 12:10:25 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendAttachNotification (thread 0x7fff7d227180): sending attach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _GetAddrInfoReplyReceivedCallback matched.
Sep 6 12:10:25 Kriss-Mac-mini.local usbmuxd[44]: _AMDeviceConnectByAddressAndPort (thread 0x100781000): IPv4
Sep 6 12:11:00 Kriss-Mac-mini com.apple.launchd[1] (com.apple.coremedia.videodecoder[776]): Exit timeout elapsed (20 seconds). Killing
Sep 6 12:11:01 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendDetachNotification (thread 0x7fff7d227180): sending detach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _BrowseReplyReceivedCallback got bonjour removal.
Sep 6 12:11:09 Kriss-Mac-mini.local WindowServer[94]: CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
Sep 6 12:11:15 --- last message repeated 1 time ---
Sep 6 12:11:15 Kriss-Mac-mini com.apple.launchd[1] (com.apple.coremedia.videodecoder[782]): Exit timeout elapsed (20 seconds). Killing
Sep 6 12:11:24 Kriss-Mac-mini.local com.apple.qtkitserver[777]: CGAffineTransformInvert: singular matrix.
Sep 6 12:11:24 --- last message repeated 1 time ---
Sep 6 12:11:24 Kriss-Mac-mini.local com.apple.qtkitserver[777]: CGSGetWindowBounds: Invalid connection
Sep 6 12:11:47 Kriss-Mac-mini com.apple.launchd[1] (com.apple.coremedia.videodecoder[786]): Exit timeout elapsed (20 seconds). Killing
Sep 6 12:12:35 Kriss-Mac-mini.local com.apple.qtkitserver[777]: CGSGetWindowBounds: Invalid connection
Sep 6 12:12:58 Kriss-Mac-mini com.apple.launchd[1] (com.apple.coremedia.videodecoder[790]): Exit timeout elapsed (20 seconds). Killing
Sep 6 12:13:06 Kriss-Mac-mini.local com.apple.qtkitserver[777]: CGSGetWindowBounds: Invalid connection
Sep 6 12:13:10 Kriss-Mac-mini com.apple.launchd[1] (com.apple.coremedia.videodecoder[794]): Exit timeout elapsed (20 seconds). Killing
Sep 6 12:15:12 Kriss-Mac-mini com.apple.launchd[1] (com.apple.coremedia.videodecoder[806]): Exit timeout elapsed (20 seconds). Killing
Sep 6 12:15:22 Kriss-Mac-mini com.apple.launchd[1] (com.apple.coremedia.videodecoder[809]): Exit timeout elapsed (20 seconds). Killing
Sep 6 12:15:51 Kriss-Mac-mini com.apple.launchd[1] (com.apple.coremedia.videodecoder[816]): Exit timeout elapsed (20 seconds). Killing
Sep 6 12:16:07 Kriss-Mac-mini com.apple.launchd[1] (com.apple.coremedia.videodecoder[818]): Exit timeout elapsed (20 seconds). Killing
Sep 6 12:17:10 Kriss-Mac-mini com.apple.launchd[1] (com.apple.coremedia.videodecoder[823]): Exit timeout elapsed (20 seconds). Killing
Sep 6 12:17:24 Kriss-Mac-mini com.apple.launchd[1] (com.apple.coremedia.videodecoder[825]): Exit timeout elapsed (20 seconds). Killing
Sep 6 12:18:22 Kriss-Mac-mini.local Locum[829]: Connection with distnoted server was invalidated
Sep 6 12:19:05 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendAttachNotification (thread 0x7fff7d227180): sending attach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _GetAddrInfoReplyReceivedCallback matched.
Sep 6 12:19:05 Kriss-Mac-mini com.apple.launchd[1] (com.apple.coremedia.videodecoder[766]): Exit timeout elapsed (20 seconds). Killing
Sep 6 12:19:05 Kriss-Mac-mini.local usbmuxd[44]: _AMDeviceConnectByAddressAndPort (thread 0x100781000): IPv4
Sep 6 12:20:01 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendDetachNotification (thread 0x7fff7d227180): sending detach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _BrowseReplyReceivedCallback got bonjour removal.
Sep 6 12:23:55 Kriss-Mac-mini.local Google Chrome Helper[844]: Unsure about the internals of CFAllocator but going to patch them anyway. If there is a crash inside of CFAllocatorAllocate, please report it at http://crbug.com/117476 . If there is a crash and it is NOT inside of CFAllocatorAllocate, it is NOT RELATED. DO NOT REPORT IT THERE but rather FILE A NEW BUG.
Sep 6 12:23:55 Kriss-Mac-mini.local Google Chrome Helper[845]: Unsure about the internals of CFAllocator but going to patch them anyway. If there is a crash inside of CFAllocatorAllocate, please report it at http://crbug.com/117476 . If there is a crash and it is NOT inside of CFAllocatorAllocate, it is NOT RELATED. DO NOT REPORT IT THERE but rather FILE A NEW BUG.
Sep 6 12:23:55 Kriss-Mac-mini.local Google Chrome Helper[844]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver.active" (1100)
Sep 6 12:23:56 Kriss-Mac-mini.local Google Chrome Helper[845]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver.active" (1100)
Sep 6 12:23:58 Kriss-Mac-mini.local Google Chrome Helper[847]: Unsure about the internals of CFAllocator but going to patch them anyway. If there is a crash inside of CFAllocatorAllocate, please report it at http://crbug.com/117476 . If there is a crash and it is NOT inside of CFAllocatorAllocate, it is NOT RELATED. DO NOT REPORT IT THERE but rather FILE A NEW BUG.
Sep 6 12:23:59 Kriss-Mac-mini com.apple.launchd[1] (com.apple.coremedia.videodecoder[835]): Exit timeout elapsed (20 seconds). Killing
Sep 6 12:24:01 Kriss-Mac-mini.local Google Chrome Helper[847]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver.active" (1100)
Sep 6 12:24:01 Kriss-Mac-mini.local Google Chrome Helper EH[848]: Unsure about the internals of CFAllocator but going to patch them anyway. If there is a crash inside of CFAllocatorAllocate, please report it at http://crbug.com/117476 . If there is a crash and it is NOT inside of CFAllocatorAllocate, it is NOT RELATED. DO NOT REPORT IT THERE but rather FILE A NEW BUG.
Sep 6 12:27:54 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendAttachNotification (thread 0x7fff7d227180): sending attach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _GetAddrInfoReplyReceivedCallback matched.
Sep 6 12:27:54 Kriss-Mac-mini.local usbmuxd[44]: _AMDeviceConnectByAddressAndPort (thread 0x100781000): IPv4
Sep 6 12:28:45 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _handle_timer heartbeat detected detach for device 0xc-10.0.1.117:0!
Sep 6 12:28:52 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendDetachNotification (thread 0x7fff7d227180): sending detach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _BrowseReplyReceivedCallback got bonjour removal.
Sep 6 12:46:04 Kriss-Mac-mini.local ScreenSaverEngine[887]: moduleFromLegacyDefaults: <ScreenSaverDefaults: 0x7fc57321f5a0>
Sep 6 12:46:04 Kriss-Mac-mini.local ScreenSaverEngine[887]: Attempted search for modules of unknown type (4)
Sep 6 12:46:04 Kriss-Mac-mini.local ScreenSaverEngine[887]: *** WARNING: -[NSImage compositeToPoint:operation:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.
Sep 6 12:46:04 Kriss-Mac-mini.local ScreenSaverEngine[887]: *** WARNING: -[NSImage compositeToPoint:fromRect:operation:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.
Sep 6 12:49:01 Kriss-Mac-mini kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=891[GoogleSoftwareUp] clearing CS_VALIDI looked these up and none of the network profiles list these MAC addresses. Strange.
I went to dinner and when I returned the computer was frozen again. These strange entries appeared in the log:
Sep 6 15:33:07 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10d657190
Sep 6 15:33:07 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10d62bb70
Sep 6 15:33:07 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10d6570c0
Sep 6 15:33:07 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x100e6f130
Sep 6 15:33:07 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10d680450
Sep 6 15:33:07 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10d63b650
Sep 6 15:33:07 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10d6804e0
Sep 6 15:33:07 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10d6805a0
Sep 6 15:33:14 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10c5edd40
Sep 6 15:33:14 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10c517540
Sep 6 15:33:14 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x1009b1150
Sep 6 15:33:14 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10c5d2120
Sep 6 15:33:14 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10c5de420
Sep 6 15:33:14 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10c51e650
Sep 6 15:33:14 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10cd8b020
Sep 6 15:33:14 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10cdfb8f0
Sep 6 15:57:58 Kriss-Mac-mini.local Dock[128]: CGSSetWindowTransformAtPlacement: Singular matrix [inf 0.000 0.000 inf]
Sep 6 15:58:00 Kriss-Mac-mini.local Dock[128]: Unable to open IOHIDSystem (e00002bd)
Sep 6 15:58:00 Kriss-Mac-mini kernel[0]: virtual bool IOHIDEventSystemUserClient::initWithTask(task_t, void *, UInt32): Client task not privileged to open IOHIDSystem for mapping memory (e00002c1)
Sep 6 16:02:35 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendDetachNotification (thread 0x7fff75469180): sending detach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _BrowseReplyReceivedCallback got bonjour removal.
Sep 6 16:02:40 Kriss-Mac-mini.local WindowServer[80]: Created shield window 0xdf for display 0x0424faa4
Sep 6 16:02:40 Kriss-Mac-mini.local WindowServer[80]: device_generate_desktop_screenshot: authw 0x0(0), shield 0x0(0)
Sep 6 16:02:40 Kriss-Mac-mini.local WindowServer[80]: device_generate_lock_screen_screenshot: authw 0x0(0), shield 0x0(0)
Sep 6 16:03:50 Kriss-Mac-mini kernel[0]: PM notification cancel (pid 322, Transmit)
Sep 6 16:03:50 Kriss-Mac-mini kernel[0]: IOPMrootDomain: idle cancel
Sep 6 16:06:17 Kriss-Mac-mini kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=352[GoogleSoftwareUp] clearing CS_VALID
Then I rebooted. Curious about the screenshot entry. I'm stumped. -
X completely freezes a few times per day
I just don't know where to start on this... My system freezes up and not even caps lock works. I have enabled sysrq, and I can Alt-SysRq-E back to the console.
Here is a CPU backtrace, task trace, and memory dump I got from sysrq just after it froze up: https://gist.github.com/andreasjansson/ … ce9801386b
Is there anything I can do to better debug this?
Many thanks,
AndreasI think I figured it out. I managed to get a stack trace of X after if froze up, and found a call in libGL towards the end of the trace. I uninstalled nvidia libGL and installed the mesa version instead. Since then X hasn't crashed.
-
Hallo, I am so frustrated, please help. I have curve 8520. It freezes so many times a day. If it does not freeze totally the trackpad (mouse) jumps to icons I don't want to be. I have already done the following. I took out battery and sim card (1000 times), I have deleted all applications I have downloaded. I press alt lglg option 1000 times. I made sure all icons are closed. Please help with suggestion. I am not techno boffen so please explain in detail.
tx
wernerI have used Firefox since it first came out, and always loved it. Firefox 4.0.1 is a different story. This must be one of the worst software upgrades across the board, of any software package I have ever used. I have stuck with it for a few weeks, and I have now finally given up.
Constant crashes, constant freezes, many plugins no longer work, my favorite among them, i.e PDF plugin to see PDF files inside the browser. AppTabs disappear over and over.
I have downgraded back to 3.6.17 and hope things will be better again. -
Why does my iPad air keep freezing, it's only 2 days old
I have an iPad air that I was bought for Christmas. It keep freezing a few times a day, can anyone tell me if they have experienced this, what I am doing wrong or how I can fix this.
It's not turning on at all, it turned off and won't respond to any buttons. I've tried to charge and all it does it turn on to the apple screen than turn back off, and does this the whole time while on the charger. I tried recoverying it through itunes also, and that didn't work either.
-
OS X freezes few times per day
Hello. I've a problem with my Macbook Pro Retina 15". Few times per day system freeze. After freeze and manual reboot (power button) sometimes system have a problem with boot (i need turn on and off few times). Now i check in logs when i open Diablo 3 and have something like this:
24.07.2014 17:56:59,158 WindowServer[135]: CGXMuxCapture: Starting
24.07.2014 17:56:59,158 WindowServer[135]: CGXMuxCapture: Acquired
24.07.2014 17:56:59,159 WindowServer[135]: Display 0x4280642 captured by conn 0x1cc8f
24.07.2014 17:56:59,202 Diablo III[28354]: *** WARNING: Method convertPointFromBase: in class NSView is deprecated on 10.7 and later. It should not be used in new applications.
24.07.2014 17:56:59,394 Diablo III[28354]: *** WARNING: Method convertRectToBase: in class NSView is deprecated on 10.7 and later. It should not be used in new applications.
24.07.2014 17:57:31,000 kernel[0]: NVDA(OpenGL): Channel exception! Exception type = 0x8 DMA Engine Error (FIFO Error 8)
24.07.2014 17:57:31,000 kernel[0]: 4443564e 00000118 88c93bc5 01f794e7 00000001 00000014 d3793533 46d3a4a6
24.07.2014 17:57:31,000 kernel[0]: 4614f297 e71edccf 00088301 000000e1 12f2500a 081d0a4d 1002a0ad 20001801
24.07.2014 17:57:31,000 kernel[0]: 30002800 02803800 0c828040 00500048 00601258 01080d22 808e8010 81042202
24.07.2014 17:57:31,000 kernel[0]: 22188093 1001080d 02808a84 9c820422 0e2268b4 84100108 22028180 80a6b805
24.07.2014 17:57:31,000 kernel[0]: 030a0880 0a00149a 1f138222 41100008 81200218 9b862808 5000480c 60015802
24.07.2014 17:57:31,000 kernel[0]: 78007064 01019000 0a000198 00138a03 13923d0a 24380a3a 0e000000 01000000
24.07.2014 17:57:31,000 kernel[0]: 490000e0 0100000f 49000000 0000000b 47000000 ff000304 ff000000 ff000000
24.07.2014 17:57:31,000 kernel[0]: ff000000 ff000000 ff000000 0a000000 1d13c220 00100008 e480a818 12200bf7
24.07.2014 17:57:31,000 kernel[0]: 03300828 a7a6a038 0dd7b0b6 48028040 00000000 4443564e
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to start of command buffer processing!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,835 WindowServer[135]: CGXMuxCapture: Released
24.07.2014 17:57:31,835 WindowServer[135]: Display 0x4280642 released by conn 0x1cc8f
24.07.2014 17:58:18,000 bootlog[0]: BOOT_TIME 1406217498 0The logic board is defective and must be replaced under warranty.
-
My screen freezes and popup message says I need to do a shutdown and then restart. It does it sometimes 2 times a day. Im new to apple and need help.
Bad or incompatible RAM is, more often then not, the cause of most Kernel Panics. It could also just need to be reset.
Here's the most used site for Resolving Kernel Panics. Please do all the steps in order, even if you don't think you need to do a certain step.
Here is a great MacFixIt article.
Good Luck!
DALE -
IMac Freezing Several Times a Day
My iMac is freezing several times a day. It started out just when I went to wake it from sleep in the morning, but now it is more often. I read about similar issues on the discussion boards and have taken the following actions: I have gone into Disk Utility and run "Verify Disk" and received "The volume Macintosh HD appears to be ok." I also used the Activity Monitor to check CPU activity, RAM availability, Hard Disk availability, etc. and everything seems fine there (57.4 GB open). However, when I checked Console Messages, there have been none since 1/16 at 4:37pm. It has been over a month since the freezing issue has been going on (& becoming more frequent) so I wonder if there is a relation/cause there? Any help welcome -- thanks!
See if the Disk is issuing any S.M.A.R.T errors in Disk Utility...
http://support.apple.com/kb/PH7029
old: http://docs.info.apple.com/article.html?path=DiskUtility/10.5/en/duh1896.html
Hello, see how many of these you can answer...
See if the Disk is issuing any S.M.A.R.T errors in Disk Utility...
http://support.apple.com/kb/PH7029
Open Activity Monitor in Applications>Utilities, select All Processes & sort on CPU%, any indications there?
How much RAM & free Disk space do you have also, click on the Memory & Disk Usage Tabs.
Open console in Applications>Utilities, check the system log for the date/time of the last problem & the Startup right after that for clues.
In the Memory tab of Activity Monitor, are there a lot of Pageouts? -
Help! I guess I can restore it to original factory settings but I am afraid of losing everything. If it helps the iPad is NOT jailbroken. Any ideas or do I have to wait for a future update?
Just to clarify. Once I am done with the iPad and push the sleep button (upper right corner) or just let it sleep from inactivity for a couple minutes, the issue happens when I try to wake it up. I can see the unlock screen with the pin pad but the iPad becomes unresponsive and I cannot enter the numbers or I can enter the numbers but it freezes right after that while the pin pad is still visible. The only thing that fixes it is to hold the home and sleep button for 10-15 seconds and wait a minute for the whole thing to reboot. At that point it usually works. Still, what I liked about the iPad was the convenience of being immediately ready and now I have to reboot many times per day.
I have an iPad2 with the latest update (6.01) and it is not jail broken. Apple help me please! -
I don't see the plug-in container in the Windows Task manager since the last update of Firefox and now FF is freezing multiple times a day (since the previous update, before yesterday's). It takes several minutes after I see this until it unfreezes, and it's quicker to "end task" and re-start Firefox than wait. This most often seems to happen when the computer's been idle for awhile, rather than when I'm using it.
Make sure that you allow the plugin-container process in the firewall.
*http://kb.mozillazine.org/Plugin-container_and_out-of-process_plugins -
Macbook pro 2011 freezing multiple times a day
I've had my 13" macbook pro (early 2011) for 10 months now and it's always frozen fairly regulary like once a week, but recently i freezes multiple times a day and says all my alpications are not responding and won't let me force quit so my only option is to restart the computer everytime.
It seems like the problem mostly occurs whilst browsing the internet, but i have reinstalled both firefox and chrome and still have the same problem.
Anyone any ideas on how to fix it as restarting and loosing work all the time is getting anoying now.
Also I'd like to do a hardware check as my year warenty is almost up but pressing and holding 'd' on start up doesn't work - has this changed?Try the following
1. SMC Reset http://support.apple.com/kb/HT3964
2. PRAM Reset http://support.apple.com/kb/PH4405
3. Safe Mode http://support.apple.com/kb/PH4373
Also Use Disk Utility to Repair Disk Permissions.
To find Disk Utility: Go to Finder> Applications> Utilities> Disk Utilities
Once there click on Macintosh HD in the left column to highlight it.
Then click Repair Disk Permissions.
Keep me updated, there is another option if these do not work. -
BT keyboard and mouse freeze one or two times a day
New iMac, started freezing up about once or twice a day after a couple of weeks. Took a few occurrences to realise it was a KB/mouse problem rather than the computer itself. looking at forum posts it seems to be a common problem, though not often both devices at once. Powering the Mac off and then on again fixes the problem every time. Battery strength is good on both devices.
As suggested in several posts, I've tried removing the BT .plist file and rebooting. Assistant took some time to relocate the KB and mouse but managed eventually. However problem still recurring.
Next time it froze, plugged in a Logitech mouse which worked ok and the BT mouse started working immediately too (why would it do that?), but not the keyboard. BT Preferences say both devices connected, and paired and discoverable. Tried to run Set Up, says 'not found' (for mouse also, even though it's working). Turning the Mac off and on again restored normality.
Hung again twice today already. Following another post advice, I've removed Bluetooth from the Networking list (although it wasn't connected to anything). But it's just hung again while i was typing this (at least powering off then on again doesn't lose any data)
I'm new to Macs, so please excuse my descriptions of the problem being more anecdotal than technical. If anyone can suggest a logical course of action to resolve this problem, I'd be grateful.I spent some time around to read all posts here and there.
I've got a brand new 20" imac with BT mighty mouse & a wired keyboard
My mouse used to freeze once or twice a day.
I used to type ctrl & space bar to open spotlight, type "bt" to get acces to bt panel in pref system, which was enough to reconnect.
I found two issues when reading things in forums:
Some people are facing a hardware issue with the metallic part behind the mouse cover being too folded to make a proper contact
Some other, like me, are facing a software issue. The problem appeared juste before 10,5,6 release, with an airport package.
I downloaded on apple website an older airport package and installed this:
airport utility.app 5.3.2 (instead of 5.4.1)
airport base station agent.app 1.5 (instead of 1.5.1)
com.apple.airportbasestationagent.plist dated 29may2008
These files are to be found there:
http://support.apple.com/downloads/AirPortUtility_5_3_2_forLeopard
And you'll need "pacifist" shareware to be allowed to install older versions
A bit complicate, but 3 days now and I didn't have any freezing! -
Mouse/keyboard freezing machine around same time every day
Using a silver tower G5 here and around the same time every day for the past week I've had to power down the machine. The mouse and keyboard just freeze. About a week ago we did put this on a KVM to switch between this and a G4 connected to a SCSI scanner. The KVM has only PS/2 ports so we're using the Belkin Y PS/2 to USB adapters. The problem seemed to have started a day or so after starting to use the KVM but I'm not sure if this is related to the freezing problem. Here's what's in the Console around the time of the freeze:
Mac OS X Version 10.4.8 (Build 8L127)
2007-03-06 12:18:21 -0500
2007-03-06 12:18:22.606 SystemUIServer[76] lang is:en
Mar 6 12:18:26 metros-power-mac-g5 ntpdate[105]: no servers can be used, exiting
Mar 6 12:18:26 metros-power-mac-g5 VersionCueCS2Daemon[167]: warning: VersionCueCS2Daemon not started by mach_init process (parent pid: 1)
Mar 6 12:18:26 metros-power-mac-g5 VersionCueCS2Daemon[167]: Unknown plist format in 'com.apple.sharing.firewall' - 'firewall'
2007-03-06 12:19:04.634 Finder[77] CFLog (0): CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
Adobe LM Service: Started
AdobeLM Service
Power Mac G5 (2.1) Mac OS X (10.4.8) 2.5 GB RAMRob Kudyba-
Too many adapters. For troubleshooting purposes can you go with a mouse and keyboard connected as directly as possible?
Do you know what Adobe LM is? That seems to be buggering things up a little.
If you still have the errors after trying it with as few adapters as possible, try repairing your startup disk.
Luck-
-DaddyPaycheck
Maybe you are looking for
-
Upgrade HDD on Macbook Pro with Lion
Here is the senario: I have a MacBook Pro with Mac OS X Lion installed. I have the stock 250 GB Drive installed packed with all my crucial data and applications. I have come to the point where I would need a bigger 720 GB Hard Drive. I understanding
-
Accounting document not generated in plant abroad
Hi Gurus, our client is using plant abroad functionality. Here the the issue is when here is tranferring stock from plant in abroad, accounting document is not generating. Please tell me where the issue would be. Thanks and regards, Babu
-
How to hide/disable Spotlight on a client by using Workgroup Manager
Dear Apple Pro's I'm looking for a script or Policy whatever to hide/disable spotlight on a client. Iam using WGM for policy's to disable some applications, but I can not find an option disable spotlight on a client. I hide a lot directory's systemfi
-
Windows 7 shows only N but it is connecter by ac standard
HI, netsh wlan show drivers Sterownik : Intel(R) Dual Band Wireless-AC 7260 Producent : Intel Corporation Dostawca : Intel Data : 2014-12-08 Wersja
-
I've just been performing software updates to my Mac. When I restarted my machine to update the Firmware software my machine crashed. When I try to do a restart all I get is a blank screen. Can anyone give some ideas of what to do?