USB 6009 lock-ups?

Hello,
I'm having a strange problem with my newly aquired USB 6009. I've written an app to read the temperature from a temperature controller using the 6009 and that all works fine. However, the problem comes when I port this code into another application. The code is intended to run in a parallel loop to the main execution loop, to continuously read the temperature whilst other data is captured and process (all done in the main loop). Both applications run quite happily when separate. When I bring them together the applications sometimes, but not all the time, refuse to quit and just lock up. I have no idea what is happening as it is not a case of one loop remaining running (I've tried separate stop buttons) and they will run together quite happily. The problem only comes when I hit the button that terminates the main loop (this also triggers the other loop to stop - I'm sure this bit works as I've used the same method in another vi).
The main loop should, in theory, just close. The loop with the USB reads (using DAQmx Base) will stop and then clear the task (DAQmx Base Clear I think). Sometimes the DAQmx Base Clear runs and the program stops fine, other times it runs and the program locks, other times it locks as soon as I hit the quit button.
Any thoughts as I'm completely stumped on this one? Like I say, apart from the one button triggering both loops to terminate there is no link between the two loops.
My only thought is it could be a USB issue as the PC also has a USB keyboard and mouse. I know from my home experience, when for instance plugging in my camera, it can cause the USB to lock if, say, my USB modem is running.

See the thread
http://forums.ni.com/ni/board/message?board.id=250&message.id=13722
John Weeks
WaveMetrics, Inc.
Phone (503) 620-3001
Fax (503) 620-6754
www.wavemetrics.com

Similar Messages

  • USB CAUSING LOCK-UPS

    Hi,
      30-40% of the time when I use my front usb it will cause Win XP to lock up and I have to hit the reset button.  Has anyone else experienced this and also any remedies?  It happens with my scanner, gamepad and ipaq.  Setup=Win XP prof w/ service pack 1, KT3ultra2, AMD 1600xp, power supply is 400 watts.  
    Thanx

    Hi Maesus,
      I have AMI bios version 3.31a.  I can't find the usb version on XP (I only know how to get to it on Win 98SE).  It's the one that came with Win XP.  If it matters, the VIA driver I'm using is v4.42.  Lastly the USB connectors are the ones built into the front panel of my case.  I wired it up according to the manual.  
      Again, the unusual thing is when it doesn't lock-up everything works fine.
    Thanx again for your help

  • Connecting lock-in amplifier to USB-6009/6211

    I am working on re-setting up a labview environment in the lab I work at. We are using a SR810 DSP lock-in amplifier and want to bring the data into labview. The labview code says that in the past we used a USB-6009 to read in data from the lock-in amplifier. The output ports on the lock-in are an RS232(DCE), a IEEE-488 port, and a preamp port. Is there someway to feed one of these outputs into the DAQ that we have. Thanks

    An RS232 or GPIB connection directly to the computer would be best, but if you insist on using the 6009, run a line from the CH1 outut BNC on the front panel of the lockin into the DAQ device. Note that this is a -10 to 10 V output and that the mapping to the actual LIA voltage depends on the sensitivity setting of the lockin (see pgs 4-2 and 4-12 of the 810 manual). 

  • Total lock-ups with fan running - translate system.log file please!?

    Hi, all. My late 2005 2.3 gig dual G5 has been experiencing random lock ups for as long as I can remember. My system is up to date and I have tested each pair of the 5 gigs of ram that I have and the system freezes with each pair. It can happen at any time, when I am doing absolutely nothing, for example, overnight. I am at my wits end!
    Here's the system log file for the latest freezes. Can anyone tell me what's going on here??? I really need to get to the root of this problem. Thanks so so much in advance.
    Apr 12 17:32:52 Marc-Weinbergs-Computer kernel[0]: AFP_VFS afpfs_Reconnect: connect on /Volumes/Macintosh HD failed 89.
    Apr 12 17:32:52 Marc-Weinbergs-Computer kernel[0]: AFP_VFS afpfs_unmount: /Volumes/Macintosh HD, flags 524288, pid 62
    Apr 12 17:44:46 Marc-Weinbergs-Computer /Library/Application Support/FLEXnet Publisher/Service/11.03.005/FNPLicensingService: Started\n
    Apr 12 17:44:46 Marc-Weinbergs-Computer /Library/Application Support/FLEXnet Publisher/Service/11.03.005/FNPLicensingService: This service performs licensing functions on behalf of FLEXnet enabled products.\n
    Apr 12 18:01:06 Marc-Weinbergs-Computer KernelEventAgent[62]: tid 00000000 received unknown event (256)
    Apr 12 18:01:49 Marc-Weinbergs-Computer KernelEventAgent[62]: tid 00000000 received unknown event (256)
    Apr 12 18:08:29 Marc-Weinbergs-Computer diskarbitrationd[69]: SDCopy [1056]:36091 not responding.
    Apr 12 18:16:18 Marc-Weinbergs-Computer KernelEventAgent[62]: tid 00000000 received unknown event (256)
    Apr 12 18:16:53 Marc-Weinbergs-Computer KernelEventAgent[62]: tid 00000000 received unknown event (256)
    Apr 12 19:24:12 Marc-Weinbergs-Computer ntpd[191]: time reset -0.650307 s
    Apr 13 01:05:45 Marc-Weinbergs-Computer ntpd[191]: time reset -0.496917 s
    Apr 13 03:15:03 Marc-Weinbergs-Computer cp: error processing extended attributes: Operation not permitted
    Apr 13 07:15:03 Marc-Weinbergs-Computer postfix/postqueue[1778]: warning: Mail system is down -- accessing queue directly
    Apr 13 03:15:03 Marc-Weinbergs-Computer cp: error processing extended attributes: Operation not permitted
    Apr 13 15:53:53 Marc-Weinbergs-Computer KernelEventAgent[62]: tid 00000000 received unknown event (256)
    Apr 13 15:53:54 Marc-Weinbergs-Computer KernelEventAgent[62]: tid 00000000 received unknown event (256)
    Apr 13 22:15:48 localhost kernel[0]: standard timeslicing quantum is 10000 us
    Apr 13 22:15:47 localhost mDNSResponder-108.6 (Jul 19 2007 11: 33:32)[63]: starting
    Apr 13 22:15:48 localhost kernel[0]: vmpagebootstrap: 506550 free pages
    Apr 13 22:15:47 localhost memberd[70]: memberd starting up
    Apr 13 22:15:49 localhost kernel[0]: migtable_maxdispl = 70
    Apr 13 22:15:49 localhost kernel[0]: Added extension "com.firmtek.driver.FTATASil3132E" from archive.
    Apr 13 22:15:49 localhost kernel[0]: Added extension "com.firmtek.driver.Sil3112DeviceNub" from archive.
    Apr 13 22:15:49 localhost kernel[0]: Copyright (c) 1982, 1986, 1989, 1991, 1993
    Apr 13 22:15:49 localhost kernel[0]: The Regents of the University of California. All rights reserved.
    Apr 13 22:15:49 localhost kernel[0]: using 5242 buffer headers and 4096 cluster IO buffer headers
    Apr 13 22:15:49 localhost kernel[0]: AppleKauaiATA shasta-ata features enabled
    Apr 13 22:15:49 localhost kernel[0]: DART enabled
    Apr 13 22:15:47 localhost DirectoryService[75]: Launched version 2.1 (v353.6)
    Apr 13 22:15:49 localhost kernel[0]: FireWire (OHCI) Apple ID 52 built-in now active, GUID 001451ff fe1b4c7e; max speed s800.
    Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
    Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
    Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
    Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
    Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
    Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
    Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
    Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
    Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
    Apr 13 22:15:48 localhost lookupd[71]: lookupd (version 369.5) starting - Sun Apr 13 22:15:48 2008
    Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
    Apr 13 22:15:49 localhost kernel[0]: Extension "com.microsoft.driver.MicrosoftKeyboardUSB" has no kernel dependency.
    Apr 13 22:15:49 localhost kernel[0]: AppleSMUparent::clientNotifyData nobody registed for 0x40
    Apr 13 22:15:49 localhost kernel[0]: Security auditing service present
    Apr 13 22:15:49 localhost kernel[0]: BSM auditing present
    Apr 13 22:15:49 localhost kernel[0]: disabled
    Apr 13 22:15:49 localhost kernel[0]: rooting via boot-uuid from /chosen: 82827EDF-0263-3B93-BEED-4B114E820B85
    Apr 13 22:15:49 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
    Apr 13 22:15:49 localhost kernel[0]: Got boot device = IOService:/MacRISC4PE/ht@0,f2000000/AppleMacRiscHT/pci@9/IOPCI2PCIBridge/k2-sat a-root@C/AppleK2SATARoot/k2-sata@0/AppleK2SATA/ATADeviceNub@0/IOATABlockStorageD river/IOATABlockStorageDevice/IOBlockStorageDriver/ST3320620AS Media/IOApplePartitionScheme/AppleHFS_Untitled1@10
    Apr 13 22:15:49 localhost kernel[0]: BSD root: disk0s10, major 14, minor 12
    Apr 13 22:15:49 localhost kernel[0]: jnl: replay_journal: from: 8451584 to: 11420160 (joffset 0x952000)
    Apr 13 22:15:50 localhost kernel[0]: AppleSMU -- shutdown cause = 3
    Apr 13 22:15:50 localhost kernel[0]: AppleSMU::PMU vers = 0x000d00a0, SPU vers = 0x67, SDB vers = 0x01,
    Apr 13 22:15:50 localhost kernel[0]: HFS: Removed 8 orphaned unlinked files
    Apr 13 22:15:50 localhost kernel[0]: Jettisoning kernel linker.
    Apr 13 22:15:50 localhost kernel[0]: Resetting IOCatalogue.
    Apr 13 22:15:50 localhost kernel[0]: Matching service count = 1
    Apr 13 22:15:50 localhost kernel[0]: Matching service count = 1
    Apr 13 22:15:50 localhost kernel[0]: Matching service count = 1
    Apr 13 22:15:50 localhost kernel[0]: Matching service count = 1
    Apr 13 22:15:50 localhost kernel[0]: Matching service count = 1
    Apr 13 22:15:50 localhost kernel[0]: Matching service count = 3
    Apr 13 22:15:50 localhost kernel[0]: NVDANV40HAL loaded and registered.
    Apr 13 22:15:50 localhost kernel[0]: PowerMac112ThermalProfile::start 1
    Apr 13 22:15:50 localhost kernel[0]: PowerMac112ThermalProfile::end 1
    Apr 13 22:15:50 localhost kernel[0]: SMUNeo2PlatformPlugin::initThermalProfile - entry
    Apr 13 22:15:50 localhost kernel[0]: SMUNeo2PlatformPlugin::initThermalProfile - calling adjust
    Apr 13 22:15:50 localhost kernel[0]: PowerMac112ThermalProfile::adjustThermalProfile start
    Apr 13 22:15:50 localhost kernel[0]: IPv6 packet filtering initialized, default to accept, logging disabled
    Apr 13 22:15:50 localhost kernel[0]: BCM5701Enet: Ethernet address 00:14:51:61:ee:78
    Apr 13 22:15:50 localhost kernel[0]: BCM5701Enet: Ethernet address 00:14:51:61:ee:79
    Apr 13 22:15:51 localhost lookupd[86]: lookupd (version 369.5) starting - Sun Apr 13 22:15:51 2008
    Apr 13 22:15:51 localhost kernel[0]: jnl: replay_journal: from: 21611008 to: 7857152 (joffset 0x952000)
    Apr 13 22:15:51 localhost kernel[0]: jnl: replay_journal: from: 673280 to: 24382976 (joffset 0x952000)
    Apr 13 22:15:51 localhost kernel[0]: jnl: replay_journal: from: 3890176 to: 6294016 (joffset 0x7d01000)
    Apr 13 22:15:51 localhost diskarbitrationd[69]: disk0s10 hfs 82827EDF-0263-3B93-BEED-4B114E820B85 NewestSeagate /
    Apr 13 22:15:52 localhost kernel[0]: NVDA,Display-A: vram [90020000:10000000]
    Apr 13 22:15:52 localhost mDNSResponder: Adding browse domain local.
    Apr 13 22:15:53 localhost kernel[0]: hfs mount: enabling extended security on Maxtor
    Apr 13 22:15:53 localhost diskarbitrationd[69]: disk1s3 hfs 0DBE2113-B1F5-388F-BF70-2E366A095330 Maxtor /Volumes/Maxtor
    Apr 13 22:15:54 localhost kernel[0]: NVDA,Display-B: vram [94000000:08000000]
    Apr 13 22:15:54 Marc-Weinbergs-Computer configd[67]: setting hostname to "Marc-Weinbergs-Computer.local"
    Apr 13 22:15:54 Marc-Weinbergs-Computer /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow: Login Window Application Started
    Apr 13 22:15:56 Marc-Weinbergs-Computer diskarbitrationd[69]: disk2s3 hfs 971CABB3-C211-38FC-8E91-6B4F8EA5FA20 B08-09-07 /Volumes/B08-09-07
    Apr 13 22:15:56 Marc-Weinbergs-Computer loginwindow[110]: Login Window Started Security Agent
    Apr 13 22:15:57 Marc-Weinbergs-Computer kernel[0]: AppleBCM5701Ethernet - en1 link active, 1000-Mbit, full duplex, symmetric flow control enabled
    Apr 13 22:15:57 Marc-Weinbergs-Computer configd[67]: AppleTalk startup
    Apr 13 22:15:57 Marc-Weinbergs-Computer TabletDriver[119]: #### GetFrontProcess failed to get front process (-600)
    Apr 13 22:15:59 Marc-Weinbergs-Computer configd[67]: posting notification com.apple.system.config.network_change
    Apr 13 22:16:00 Marc-Weinbergs-Computer configd[67]: posting notification com.apple.system.config.network_change
    Apr 13 22:16:00 Marc-Weinbergs-Computer configd[67]: executing /System/Library/SystemConfiguration/Kicker.bundle/Contents/Resources/enable-net work
    Apr 13 22:16:00 Marc-Weinbergs-Computer configd[67]: posting notification com.apple.system.config.network_change
    Apr 13 22:16:01 Marc-Weinbergs-Computer lookupd[123]: lookupd (version 369.5) starting - Sun Apr 13 22:16:01 2008
    Apr 13 22:16:01 Marc-Weinbergs-Computer kernel[0]: HFS: Removed 2 orphaned unlinked files
    Apr 13 22:16:01 Marc-Weinbergs-Computer diskarbitrationd[69]: disk3s3 hfs CDA8BCC5-0CE4-33E8-A910-4B0952DBC230 FullBU-09-07 /Volumes/FullBU-09-07
    Apr 13 22:16:04 Marc-Weinbergs-Computer configd[67]: target=enable-network: disabled
    Apr 13 22:16:05 Marc-Weinbergs-Computer configd[67]: AppleTalk startup complete
    Apr 13 22:16:09 Marc-Weinbergs-Computer TabletDriver[237]: #### GetFrontProcess failed to get front process (-600)
    Apr 13 22:16:09 Marc-Weinbergs-Computer launchd[241]: com.wacom.wacomtablet: exited with exit code: 253
    Apr 13 22:16:09 Marc-Weinbergs-Computer launchd[241]: com.wacom.wacomtablet: 9 more failures without living at least 60 seconds will cause job removal
    Apr 13 22:16:29 Marc-Weinbergs-Computer /Applications/DiskWarrior.app/Contents/MacOS/DiskWarriorDaemon: [Sun Apr 13 22:16:28 EDT 2008] : ATA device 'ST3320620AS', serial number '6QF0L6LR', reports it is functioning at a temperature of 95.0F (35C) degrees.
    Apr 13 22:16:29 Marc-Weinbergs-Computer /Applications/DiskWarrior.app/Contents/MacOS/DiskWarriorDaemon: [Sun Apr 13 22:16:28 EDT 2008] : Spare blocks for ATA device 'ST3320620AS', serial number '6QF0L6LR', appear to still be available. (Total Available: 36) (Use Attempts: 0)
    Apr 13 22:16:29 Marc-Weinbergs-Computer /Applications/DiskWarrior.app/Contents/MacOS/DiskWarriorDaemon: [Sun Apr 13 22:16:29 EDT 2008] : ATA device 'ST3320620AS', serial number '6QF0LGS4', reports it is functioning at a temperature of 100.4F (38C) degrees.
    Apr 13 22:16:29 Marc-Weinbergs-Computer /Applications/DiskWarrior.app/Contents/MacOS/DiskWarriorDaemon: [Sun Apr 13 22:16:29 EDT 2008] : Spare blocks for ATA device 'ST3320620AS', serial number '6QF0LGS4', appear to still be available. (Total Available: 36) (Use Attempts: 0)
    Apr 13 22:16:29 Marc-Weinbergs-Computer /Applications/DiskWarrior.app/Contents/MacOS/DiskWarriorDaemon: [Sun Apr 13 22:16:29 EDT 2008] : ATA device 'ST3320620AS', serial number '9RV000FC', reports it is functioning at a temperature of 95.0F (35C) degrees.
    Apr 13 22:16:29 Marc-Weinbergs-Computer /Applications/DiskWarrior.app/Contents/MacOS/DiskWarriorDaemon: [Sun Apr 13 22:16:29 EDT 2008] : Spare blocks for ATA device 'ST3320620AS', serial number '9RV000FC', appear to still be available. (Total Available: 36) (Use Attempts: 0)
    Apr 13 22:16:29 Marc-Weinbergs-Computer /Applications/DiskWarrior.app/Contents/MacOS/DiskWarriorDaemon: [Sun Apr 13 22:16:29 EDT 2008] : ATA device 'Maxtor 6B300S0', serial number 'B6211G0H', reports it is functioning at a temperature of 89.6F (32C) degrees.
    Apr 13 22:16:29 Marc-Weinbergs-Computer /Applications/DiskWarrior.app/Contents/MacOS/DiskWarriorDaemon: [Sun Apr 13 22:16:29 EDT 2008] : Spare blocks for ATA device 'Maxtor 6B300S0', serial number 'B6211G0H', appear to still be available. (Total Available: 63) (Use Attempts: 0)
    Apr 13 22:16:54 Marc-Weinbergs-Computer /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder: _TIFFVSetField: tiff data provider: Invalid tag "Copyright" (not supported by codec).\n
    Apr 13 22:16:54 Marc-Weinbergs-Computer /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder: _TIFFVSetField: tiff data provider: Invalid tag "Copyright" (not supported by codec).\n
    etc.

    Hi-
    The machine seems to be having trouble with loading certain drivers, but, as this isn't a crash log, and doesn't show the "hang-up" or freeze, it's hard to tell.
    Noted possibilities are:
    -Microsoft keyboard (possible USB power problem)
    -firmtek driver (from archive) questionable due to the "archive" annotation
    -Wacom tablet driver, causing system problems
    Running in Safe mode without freezes would help to determine if one of these drivers is the problem.
    Other possibilities are outdated drivers, or simply a need to reinstall the OS.
    If unnecessary, removing the driver(s) would be a good idea.
    External USB and Firewire devices are all suspect, should all be disconnected, revert to Apple keyboard, and test system performance. Adding one device at a time, and testing each will be necessary to clear each device.
    I have experienced system trouble when a Wacom tablet was not connected, but the driver was left installed.
    Disabling the driver from Startup items may be necessary to test without the Wacom tablet connected.

  • Random Lock ups

    I'm using K9N2-SLI plat with Bios 3.5, AMD64 X2 6400+ Black Ed., 4GB ram (2x2GB Cas 4-4-4-12 T2 matched set), XFX 8800GTS(92) 512, Corsair TX650, Artic Cooler Freezer64 CPU H/S running Vista64 Home Premium Sp2. I'm having random lock-ups during 3D games. Sometimes it locks up after 30 mins in game or sometimes it locks up after days of playing, I can't get it to reproduce the lock up at will. I have read alot of post about this motherboard and it seems it comes down to power supply. I had a New Apevia Beast 2 rail system but after reading the posts I returned it for new Corsair TX650. At full load CPU cores never go above 47c and Idles around 30-31. Ran mem test over night with no errors. Did notice in Mem Test it stated Ram was set at Cas 4-5-5-18 T2. I went to BIOS and set the mem for Volt 2.0 Cas 4-4-4-12 T2. This did reduce the lock-ups to the point I thought I had it fixed. Than today I locked up twice. When it locks up computer becomes unresponsive last sound repeats for few seconds and the only way to resume is to press restart button. I have tried with Cool n'quite on and off, DOT is never been on. Computer runs fine in 2d operations. It's only when I go into 3d games. Video Card has been tested in other machine and is working fine. My game sometime requires me to stay logged in over night to Sell goods. Every morning this last week computer has froze sometime during the night. Crysis plays fine for hours, It seems it happens in not so demanding games, Aion, Knight Online and Wow. All power plugs are plugged, fresh install of Vista, Newest drivers from web site, Bios update via the Forum USB key app. Would really like a reliable computer. What am I missing? Let me know if you need any other info.

    OK I ran single stick and it locked up quicker. I went to BIOS used optimized defaults with only changing the volts to 2.0. and it locked up again. It's lockups seem longer if I change mem setting to 4-4-4-12 T2. I used CPU Z and noticed few things.
    The memory report from CPU-Z:
    DIMM #            1
       SMBus address      0x50
       Memory type      DDR2
       Module format      Regular UDIMM
       Manufacturer (ID)   A-Data Technology (7F7F7F7FCB000000)
       Size         2048 MBytes
       Max bandwidth      PC2-6400 (400 MHz)
       Part number      EXTREME DDR2 800+
       Number of banks      2
       Data width      64 bits
       Correction      None
       Nominal Voltage      1.80 Volts
       EPP         yes (2 profiles)
       XMP         no
    JEDEC timings table      CL-tRCD-tRP-tRAS-tRC @ frequency
       JEDEC #1      3.0-3-3-9-12 @ 200 MHz
       JEDEC #2      4.0-4-4-12-16 @ 266 MHz
       JEDEC #3      5.0-5-5-18-23 @ 400 MHz
    EPP timings table      CL-tRCD-tRP-tRAS-tRC-CR @ frequency (voltage)
       EPP profile #1 (full)   4.0-4-4-12-22-2T @ 400 MHz (2.000 Volts)
       EPP profile #2 (full)   4.0-4-4-11-20-2T @ 400 MHz (2.000 Volts)
    since I was using EPP profile 1 I noticed that motherboard is running my memory at 4-4-4-12-24(EPP profile shows should be 22)-2T. Should I change to match memory? or should I try JEDEC #3 @ 400MHZ
    Next thing I noticed was The chipset is stated as 740a not the 750a
    Chipset
    Northbridge      NVIDIA nForce 740a SLI rev. A2
    Southbridge      NVIDIA nForce 740a SLI MCP rev. A2
    Graphic Interface      PCI-Express
    PCI-E Link Width      x16
    PCI-E Max Link Width   x16
    Memory Type      DDR2
    Memory Size      4096 MBytes
    Channels         Dual
    Memory Frequency              400.0 MHz (CPU/7)
    CAS# latency (CL)              4.0
    RAS# to CAS# delay (tRCD)   4
    RAS# Precharge (tRP)           4
    Cycle Time (tRAS)               12
    Bank Cycle Time (tRC)          24
    Command Rate (CR)             2T
    I've tried loser setting 5-5-5-18 and still locks up.

  • Please help! Major problems (performan​ce and lock-ups) with brand new W520 with Intel 520 SSD

    My company primarily uses HP machines but I've been a long time IBM (now Lenovo) fan so I recently had IT purchase me a new Lenovo W520 (product ID 42763LU).
    Once the machine arrived I had them do the following:
    Remove the 500GB HDD and replace it with an Intel 520 series 240GB SSD
    Remove the optical drive and install the 500GB hard drive that came with the machine in the optical bay (with the bay adapter of course)
    Format both drives and put a preconfigured windows 7 64-bit image on the SSD
    A general summary of the system is the following:
    Intel i7-2860QM CPU
    8GB RAM
    NVIDIA Quadro 1000M
    Intel 520 240GB SSD (primary HDD) [SSDSC2CW240A3]
    Hitachi 500GB HDD (optical bay) [HTS727550A9E365]
    Intel Advanced-N 6205 network adapter
    TouchChip Fingerprint Scanner
    The machine was a few days delayed getting to me due to "hard drive driver issues" (that's what I was told). When I received the machine I immediately noticed that it was much slower than I expected (I have a custom built i5 HTPC at home running windows 7 on a Crucial SATA III SSD that I was comparing it to) and I was experiencing frequent hangs (ranging from 30 seconds to multiple minutes), super long boot times, general “slowness” at times, and occasional lock-ups. Since our "baseline" laptop here at work is the "equivalent" HP workstation my IT guys have been less than helpful in helping me to solve this issue. Being reasonably computer savvy I decided to try to try to fix the issue myself. I performed the following “troubleshooting” steps:
    1. One of the first issues (errors) I noticed in the event viewer was errors related to the optical drive. Clearly the image they installed on the machine was not from a machine with the same hardware configuration. So, I decided to just wipe the machine and perform a fresh install of windows 7 from the disks (well, USB). After spending multiple days installing windows, performing updates, making sure all the drivers were current, and installing only the critical software I need, I was disappointed to realize that although I fixed the optical drive errors the machine was still slow, was hanging, and locking up regularly.
    2. Removed the cover on the machine and removed/reinstalled the drive to verify it was secure.Everything looked good.
    3. Verified the latest firmware is installed on all my Intel hardware. Everything seemed up to date.
    4. I performed a number of troubleshooting steps like booting the machine with/without the battery, with/without the HDD in the optical bay, installed/removed from the docking station, etc. and none of these things helped (also a note – occasionally when running on the battery I was hearing a strange “buzz” or “static” sound coming from the area around the SSD).
    5. Next I did some internet research and learned quite a few things. First, it sounds like others have had similar problems with this machine and/or SSD combo and there were quite a few options suggested to “fix” these issues. The general consensus for troubleshooting steps were:
    5.1. Download and install the latest Intel chipset drivers and AHCI controller drivers (overwriting whatever windows installs during updates).This didn’t fix anything.
    5.2. Turn off PCI express link state power management in the power manager. This didn’t fix anything.
    5.3. Disable superfetch, prefetch, indexing, defragmentation, page file, system restore, and hibernate. A few of these were already disabled by windows so in those cases I just verified they were disabled in the services and application editor. These things may have slightly increased performance but did not fix the major hang/lockup issues I was having.
    5.4. I followed online steps to edit the registry to disable the PCI link power management by adding ports, adding the required variables, and setting them all to 0. This did seem to have fixed the hangs and/or lock-ups but the machine is still much slower than I would expect (boot times are still pretty slow and it does “stutter” when I’m doing more than one thing at a time. Also a note here – I have the Intel SSD toolbox installed and I noticed that it was giving me a warning for DIPM not being optimized. I made the mistake of clicking “Tune!” and then started having the hang/lock-up issues again. I went back into the registry and sure enough the PCI link power management variables for ports 0 and 1 were set back to 1. I set them back to 0 and the hangs have gone away. I will not be “tuning” the DIPM through the Intel SSD toolbox again…
    6. I also fixed a couple of other minor errors I was seeing in the event viewer by disabling benign services and/or making slight timeout modifications (I researched each issue on the internet to verify they were benign before I implemented any changes). These fixes didn't seem to do anything other than make some of the errors/warnings go away. So, the list of errors/warnings has become much smaller but I’m still getting the following (maybe an issue, maybe not?):
    Event ID 37 for every processor saying that they are in a reduced performance state for xx seconds since the last report
    Event ID 10002 - WLAN Extensibility Module has stopped
    Event ID 4001 - WLAN AutoConfig service has successfully stopped
    Event ID 27 – Intel® 82579LM Gigabit Network Connection link is disconnected
    I suspect the WLAN errors have something to do with windows fighting with the Lenovo access connection tools?
    7. Since the machine still seemed slow I downloaded the program AS SSD and checked the performance of the SSD. When I compared my performance numbers to the benchmark numbers I found onlineI was very surprised to discover that I’m getting about 50% of the performance that I should (values below are read/write).
    Seq: 262.11 / 188.32 (s/b 504.58 / 298.28) [MB/s]
    4K: 15.83 / 44.92 (s/b 21.70 / 62.60) [MB/s]
    4K-64Thrd: 165.23 / 154.46 (s/b 241.38 / 234.08) [MB/s]
    Acc.time: 0.218 / 0.294 (s/b .0186 / 0.208) [ms]
    Score: 207 / 208 (s/b 314 / 327)
    Overall Score: 533 (s/b 797)
    One more note - it seems like my cooling fan is running at a high speed almost all of the time. This is probably one of my power settings (I think I have it set for max performance) but it's even doing this when there is no load (i.e. I'm using IE and just vieweing webpages - like right now).
    So, I apologize for such a long post but I’ve spent countless hours researching and troubleshooting this problem and haven’t been able to figure out what the heck is wrong here. Am I missing something simple or do you guys think I have a SSD and/or problem with the machine itself? To say that any and all help would be greatly appreciated would be a massive understatement – I’m on the verge of pulling my hair out and I really need this machine working as quickly as possible!
    Please let me know if you have any suggestions and/or need additional information. Thanks in advance for your help!
    -Erik

    Lol gotcha about the drive as an option. I didn't go SSD with mine. Do you have the latest firmware on your drive? It is supposed to be v1.97. Just checking (ah and I see item 3 so guess so). Do you have the SSD drive toolbox software installed?
    http://downloadcenter.intel.com/SearchResult.aspx?​lang=eng&ProductFamily=Solid+State+Drives+and+Cach​...)
    Seems some useful tools are in there. I can't say much beyond that with the drive. Oh. Why does your fan always run at high speed? Can you describe that?  I mean, are we troubleshooting the right kind of issue? Is there anything else going on with your system? I saw about the reduced core speeds message. what are your system loads like? Anything causing high cpu utilization? Could be something other than the drive causing your low numbers and lockups.

  • Multiple Panics, Lock Ups and Freezes

    My MacBook Pro running 10.8.3 has been having some random shut downs and lock ups lately, the latest of which took the internal boot drive totally offline. I was able to recover it after booting to my external recovery drive and running DiskWarrior 4 as Disk Utility simply said I needed to repair the drive before mounting it, but then said it was unrepairable after attempting to do so.
    After the DiskWarrior repair, the Mac booted from it's internal drive like there was nothing wrong, but an hour or so later, I had another lock up where everything froze up and was unresponsive and then after a restart I got another hour or so before it shut itself down and then restarted itself, so I'm obviously less than thrilled with the situation.
    This is the factory drive which came with the MacBook Pro when purchased new in January of this year, so I have a hard time believing the drive is physically bad, though I guess anything is possible. Another thing that has me thinking it's not the hardware is that the machine runs fine when booted to the external recovery drive and has no errors or any of the symptoms I've been experiencing.
    Anyway, I've been looking at the panic reports, but I'm honestly not well versed in what any of this means, so I'm hoping one of the experts can chime in and maybe point me in the right direction as I'm running out of ideas :/
    Interval Since Last Panic Report:  2467 sec
    Panics Since Last Report:          1
    Anonymous UUID:                    BBC20339-6AE8-82EA-4368-DCBBCC912FF4
    Anonymous UUID:                    BBC20339-6AE8-82EA-4368-DCBBCC912FF4
    Thu May  2 13:44:42 2013
    panic(cpu 6 caller 0xffffff8025cb7e95): Kernel trap at 0xffffff7fa741c064, type 14=page fault, registers:
    CR0: 0x0000000080010033, CR2: 0x0000000000000010, CR3: 0x00000000443ae021, CR4: 0x00000000001606e0
    RAX: 0x0000000000000001, RBX: 0xffffff81c60a6000, RCX: 0xffffff8048c44000, RDX: 0xffffff81f7773a38
    RSP: 0xffffff81f7773b60, RBP: 0xffffff81f7773b60, RSI: 0x0000000000000000, RDI: 0x0000000000000000
    R8:  0x0000000000000000, R9:  0x00000000000003ff, R10: 0xffffffffffffffff, R11: 0x00000000ffffffff
    R12: 0xffffff81c60a6000, R13: 0x0000000000000000, R14: 0x0000000000000002, R15: 0x0000000000000000
    RFL: 0x0000000000010246, RIP: 0xffffff7fa741c064, CS:  0x0000000000000008, SS:  0x0000000000000010
    Fault CR2: 0x0000000000000010, Error code: 0x0000000000000000, Fault CPU: 0x6
    Backtrace (CPU 6), Frame : Return Address
    0xffffff81f7773800 : 0xffffff8025c1d626
    0xffffff81f7773870 : 0xffffff8025cb7e95
    0xffffff81f7773a40 : 0xffffff8025ccd4dd
    0xffffff81f7773a60 : 0xffffff7fa741c064
    0xffffff81f7773b60 : 0xffffff7fa7405d64
    0xffffff81f7773bb0 : 0xffffff7fa7405cba
    0xffffff81f7773bd0 : 0xffffff7fa73e17ae
    0xffffff81f7773c00 : 0xffffff7fa62b03a0
    0xffffff81f7773c40 : 0xffffff7fa62b030f
    0xffffff81f7773c60 : 0xffffff7fa62b575c
    0xffffff81f7773cf0 : 0xffffff7fa62ade50
    0xffffff81f7773d20 : 0xffffff7fa62feb8b
    0xffffff81f7773d70 : 0xffffff8026032e7b
    0xffffff81f7773dc0 : 0xffffff80260634f7
    0xffffff81f7773e30 : 0xffffff8025c97fef
    0xffffff81f7773e80 : 0xffffff8025c20aed
    0xffffff81f7773eb0 : 0xffffff8025c10448
    0xffffff81f7773f00 : 0xffffff8025c1961b
    0xffffff81f7773f70 : 0xffffff8025ca5dd6
    0xffffff81f7773fb0 : 0xffffff8025ccdd43
          Kernel Extensions in backtrace:
             com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0 xffffff7fa62a4000->0xffffff7fa62dbfff
                dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7fa6266000
             com.apple.NVDAResman(8.1)[A26D2A3D-C06F-3A0F-BCFF-901A98C93C3D]@0xffffff7fa62fb 000->0xffffff7fa6608fff
                dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7fa6266000
                dependency: com.apple.iokit.IONDRVSupport(2.3.7)[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xff ffff7fa62e7000
                dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0 xffffff7fa62a4000
             com.apple.GeForce(8.1)[A15BB65E-3501-340F-87CB-2FD2BAD33E35]@0xffffff7fa73de000 ->0xffffff7fa74aafff
                dependency: com.apple.NVDAResman(8.1.0)[A26D2A3D-C06F-3A0F-BCFF-901A98C93C3D]@0xffffff7fa62 fb000
                dependency: com.apple.iokit.IONDRVSupport(2.3.7)[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xff ffff7fa62e7000
                dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7fa6266000
                dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0 xffffff7fa62a4000
    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: 3EB7D8A7-C2D3-32EC-80F4-AB37D61492C6
    Kernel slide:     0x0000000025a00000
    Kernel text base: 0xffffff8025c00000
    System model name: MacBookPro9,1 (Mac-4B7AC7E43945597E)
    System uptime in nanoseconds: 187720354206
    last loaded kext at 185678984299: com.apple.driver.AudioAUUC          1.60 (addr 0xffffff7fa768f000, size 32768)
    loaded kexts:
    com.kaspersky.nke          1.0.1d41
    com.kaspersky.kext.klif          3.0.0d23
    com.apple.driver.AudioAUUC          1.60
    com.apple.iokit.IOBluetoothSerialManager          4.1.3f3
    com.apple.filesystems.autofs          3.0
    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.driver.AppleHDA          2.3.7fc4
    com.apple.GeForce          8.1.0
    com.apple.iokit.IOBluetoothUSBDFU          4.1.3f3
    com.apple.driver.AppleUpstreamUserClient          3.5.10
    com.apple.driver.ACPI_SMC_PlatformPlugin          1.0.0
    com.apple.iokit.BroadcomBluetoothHCIControllerUSBTransport          4.1.3f3
    com.apple.driver.AppleMikeyDriver          2.3.7fc4
    com.apple.nvidia.NVDAStartup          8.1.0
    com.apple.driver.SMCMotionSensor          3.0.3d1
    com.apple.driver.AppleSMCLMU          2.0.3d0
    com.apple.driver.AppleIntelHD4000Graphics          8.1.0
    com.apple.driver.AppleIntelFramebufferCapri          8.1.0
    com.apple.iokit.IOUserEthernet          1.0.0d1
    com.apple.Dont_Steal_Mac_OS_X          7.0.0
    com.apple.driver.ApplePolicyControl          3.3.0
    com.apple.driver.AppleSMCPDRC          1.0.0
    com.apple.driver.AppleLPC          1.6.0
    com.apple.driver.AppleMuxControl          3.3.0
    com.apple.driver.AppleBacklight          170.2.5
    com.apple.driver.AppleMCCSControl          1.1.11
    com.apple.driver.AppleUSBTCButtons          237.1
    com.apple.driver.AppleIRController          320.15
    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.iokit.SCSITaskUserClient          3.5.5
    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.AppleFWOHCI          4.9.6
    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.AppleACPIButtons          1.7
    com.apple.driver.AppleRTC          1.5
    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.iokit.IOSerialFamily          10.0.6
    com.apple.kext.triggers          1.0
    com.apple.driver.DspFuncLib          2.3.7fc4
    com.apple.iokit.IOAudioFamily          1.8.9fc11
    com.apple.kext.OSvKernDSPLib          1.6
    com.apple.nvidia.gk100hal          8.1.0
    com.apple.NVDAResman          8.1.0
    com.apple.iokit.IOFireWireIP          2.2.5
    com.apple.driver.IOPlatformPluginLegacy          1.0.0
    com.apple.iokit.AppleBluetoothHCIControllerUSBTransport          4.1.3f3
    com.apple.driver.AppleThunderboltEDMSink          1.1.8
    com.apple.driver.AppleThunderboltEDMSource          1.1.8
    com.apple.driver.AppleThunderboltDPOutAdapter          1.8.9
    com.apple.driver.X86PlatformPlugin          1.0.0
    com.apple.driver.AppleHDAController          2.3.7fc4
    com.apple.iokit.IOHDAFamily          2.3.7fc4
    com.apple.iokit.IOAcceleratorFamily          30.14
    com.apple.iokit.IOSurface          86.0.4
    com.apple.iokit.IOBluetoothFamily          4.1.3f3
    com.apple.driver.AppleSMC          3.1.4d2
    com.apple.driver.IOPlatformPluginFamily          5.3.0d51
    com.apple.driver.AppleSMBusPCI          1.0.11d0
    com.apple.driver.AppleGraphicsControl          3.3.0
    com.apple.driver.AppleBacklightExpert          1.0.4
    com.apple.iokit.IONDRVSupport          2.3.7
    com.apple.driver.AppleSMBusController          1.0.11d0
    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.iokit.IOSCSIMultimediaCommandsDevice          3.5.5
    com.apple.iokit.IOBDStorageFamily          1.7
    com.apple.iokit.IODVDStorageFamily          1.7.1
    com.apple.iokit.IOCDStorageFamily          1.7.1
    com.apple.iokit.IOAHCISerialATAPI          2.5.1
    com.apple.iokit.IOSCSIArchitectureModelFamily          3.5.5
    com.apple.driver.AppleThunderboltNHI          1.6.3
    com.apple.iokit.IOThunderboltFamily          2.2.6
    com.apple.iokit.IOUSBUserClient          5.5.5
    com.apple.iokit.IOEthernetAVBController          1.0.2b1
    com.apple.iokit.IO80211Family          522.4
    com.apple.iokit.IONetworkingFamily          3.0
    com.apple.iokit.IOFireWireFamily          4.5.5
    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
    System Profile:
    Model: MacBookPro9,1, BootROM MBP91.00D3.B08, 4 processors, Intel Core i7, 2.6 GHz, 16 GB, SMC 2.1f173
    Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In, 384 MB
    Graphics: NVIDIA GeForce GT 650M, NVIDIA GeForce GT 650M, PCIe, 1024 MB
    Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x0000, 0x4B4238475F44335F534F31363030434C3130
    Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x0000, 0x4B4238475F44335F534F31363030434C3130
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xF5), Broadcom BCM43xx 1.0 (5.106.98.100.16)
    Bluetooth: Version 4.1.3f3 11349, 2 service, 11 devices, 1 incoming serial ports
    Network Service: Ethernet, Ethernet, en0
    Serial ATA Device: APPLE HDD TOSHIBA MK7559GSXF, 750.16 GB
    Serial ATA Device: HL-DT-ST DVDRW  GS31N
    USB Device: hub_device, 0x8087  (Intel Corporation), 0x0024, 0x1a100000 / 2
    USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x8509, 0x1a110000 / 3
    USB Device: hub_device, 0x8087  (Intel Corporation), 0x0024, 0x1d100000 / 2
    USB Device: hub_device, 0x0424  (SMSC), 0x2513, 0x1d180000 / 3
    USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0252, 0x1d183000 / 6
    USB Device: IR Receiver, apple_vendor_id, 0x8242, 0x1d182000 / 5
    USB Device: BRCM20702 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0x1d181000 / 4
    USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x821d, 0x1d181300 / 8
    Model: MacBookPro9,1, BootROM MBP91.00D3.B08, 4 processors, Intel Core i7, 2.6 GHz, 16 GB, SMC 2.1f173
    Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In, 384 MB
    Graphics: NVIDIA GeForce GT 650M, NVIDIA GeForce GT 650M, PCIe, 1024 MB
    Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x0000, 0x4B4238475F44335F534F31363030434C3130
    Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x0000, 0x4B4238475F44335F534F31363030434C3130
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xF5), Broadcom BCM43xx 1.0 (5.106.98.100.16)
    Bluetooth: Version 4.1.3f3 11349, 2 service, 11 devices, 1 incoming serial ports
    Network Service: Ethernet, Ethernet, en0
    Serial ATA Device: APPLE HDD TOSHIBA MK7559GSXF, 750.16 GB
    Serial ATA Device: HL-DT-ST DVDRW  GS31N
    USB Device: hub_device, 0x8087  (Intel Corporation), 0x0024, 0x1a100000 / 2
    USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x8509, 0x1a110000 / 3
    USB Device: hub_device, 0x8087  (Intel Corporation), 0x0024, 0x1d100000 / 2
    USB Device: hub_device, 0x0424  (SMSC), 0x2513, 0x1d180000 / 3
    USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0252, 0x1d183000 / 6
    USB Device: IR Receiver, apple_vendor_id, 0x8242, 0x1d182000 / 5
    USB Device: BRCM20702 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0x1d181000 / 4
    USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x821d, 0x1d181300 / 8

    1. This comment applies to malicious software ("malware") that's installed unwittingly by the victim of a network attack. It does not apply to software, such as keystroke loggers, that may be installed deliberately by an intruder who has hands-on access to the victim's computer. That threat is in a different category, and there's no easy way to defend against it. If you have reason to suspect that you're the target of such an attack, you need expert help.
    OS X now implements three layers of built-in protection specifically against malware, not counting runtime protections such as execute disable, sandboxing, system library randomization, and address space layout randomization that may also guard against other kinds of exploits.
    2. All versions of OS X since 10.6.7 have been able to detect known Mac malware in downloaded files, and to block insecure web plugins. This feature is transparent to the user, but internally Apple calls it "XProtect." The malware recognition database is automatically checked for updates once a day; however, you shouldn't rely on it, because the attackers are always at least a day ahead of the defenders.
    The following caveats apply to XProtect:
    It can be bypassed by some third-party networking software, such as BitTorrent clients and Java applets.
    It only applies to software downloaded from the network. Software installed from a CD or other media is not checked.
    3. Starting with OS X 10.7.5, there has been a second layer of built-in malware protection, designated "Gatekeeper" by Apple. By default, applications and Installer packages downloaded from the network will only run if they're digitally signed by a developer with a certificate issued by Apple. Software certified in this way hasn't necessarily been tested by Apple, but you can be reasonably sure that it hasn't been modified by anyone other than the developer. His identity is known to Apple, so he could be held legally responsible if he distributed malware. That may not mean much if the developer lives in a country with a weak legal system (see below.)
    Gatekeeper doesn't depend on a database of known malware. It has, however, the same limitations as XProtect, and in addition the following:
    It can easily be disabled or overridden by the user.
    A malware attacker could get control of a code-signing certificate under false pretenses, or could find some other way to bypass Apple's oversight, or the oversight could fail in a particular case due to human error.
    For most purposes, applications recognized by Gatekeeper as signed, including App Store products, can be considered safe. Note, however, that at least one trojan for iOS (not for OS X) was briefly distributed by a developer in Russia through the iTunes App Store. That store is under the same oversight by Apple as the Mac App Store, so the protection shouldn't be considered absolute. App Store products may prompt for access to private data, such as your contacts. Think before granting that access. OS X security is based on user input. Never click anything reflexively.
    4. Starting with OS X 10.8.3, a third layer of protection has been added: a "Malware Removal Tool" (MRT). MRT runs automatically in the background when you update the OS. It checks for, and removes, malware that may have evaded the other protections via a Java exploit (see below.) MRT also runs when you install or update the Apple-supplied Java runtime (but not the Oracle runtime.) Like XProtect, MRT is presumably effective against known attacks, but maybe not against unknown attacks. It notifies you if it finds malware, but otherwise there's no user interface to MRT.
    5. Beyond XProtect, Gatekeeper, and MRT, there’s no evidence of any benefit from other automated protection against malware. The first and best line of defense is always your own intelligence. With the possible exception of Java exploits, all known malware circulating on the Internet that affects a fully-updated installation of OS X 10.6 or later takes the form of so-called "trojan horses," which can only have an effect if the victim is duped into running them. The threat therefore amounts to a battle of wits between you and the malware attacker. If you're smarter than he thinks you are, you'll win.
    That means, in practice, that you never use software that comes from an untrustworthy source, or that does something inherently untrustworthy. How do you know what is trustworthy?
    Any website that prompts you to install a “codec,” “plug-in,” "player," "extractor," or “certificate” that comes from that same site, or an unknown one, is untrustworthy.
    A web operator who tells you that you have a “virus,” or that anything else is wrong with your computer, or that you have won a prize in a contest you never entered, is trying to commit a crime with you as the victim. (Some reputable websites did legitimately warn visitors who were infected with the "DNSChanger" malware. That exception to this rule no longer applies.)
    Pirated copies or "cracks" of commercial software, no matter where they come from, are unsafe.
    Software of any kind downloaded from a BitTorrent or from a Usenet binary newsgroup is unsafe.
    Software that purports to help you do something that's illegal or that infringes copyright, such as saving streamed audio or video for reuse without permission, is unsafe. All YouTube "downloaders" are in this category, though not all are necessarily harmful.
    Software with a corporate brand, such as Adobe Flash Player, must be downloaded directly from the developer’s website. If it comes from any other source, it's unsafe.
    Even signed applications should not be trusted if they do something unexpected, such as asking for permission to access your contacts or your location for no apparent reason.
    6. Java on the Web (not to be confused with JavaScript, to which it's not related, despite the similarity of the names) is a weak point in the security of any system. Java is, among other things, a platform for running complex applications in a web page, on the client. That was always a bad idea, and Java's developers have proven themselves incapable of implementing it without also creating a portal for malware to enter. Past Java exploits are the closest thing there has ever been to a Windows-style virus affecting OS X. Merely loading a page with malicious Java content could be harmful.
    Fortunately, client-side Java on the Web is obsolete and mostly extinct. Only a few outmoded sites still use it. Try to hasten the process of extinction by avoiding those sites, if you have a choice. Forget about playing games or other non-essential uses of Java.
    Java is not included in OS X 10.7 and later. Discrete Java installers are distributed by Apple and by Oracle (the developer of Java.) Don't use either one unless you need it. Most people don't. If Java is installed, disable it — not JavaScript — in your browsers.
    Regardless of version, experience has shown that Java on the Web can't be trusted. If you must use a Java applet for a task on a specific site, enable Java only for that site in Safari. Never enable Java for a public website that carries third-party advertising. Use it only on well-known, login-protected, secure websites without ads. In Safari 6 or later, you'll see a lock icon in the address bar with the abbreviation "https" when visiting a secure site.
    Follow the above guidelines, and you’ll be as safe from malware as you can practically be. The rest of this comment concerns what you should not do to protect yourself from malware.
    7. Never install any commercial "anti-virus" or "Internet security" products for the Mac, as they all do more harm than good, if they do any good at all. If you need to be able to detect Windows malware in your files, use the free software  ClamXav — nothing else.
    Why shouldn't you use commercial "anti-virus" products?
    Their design is predicated on the nonexistent threat that malware may be injected at any time, anywhere in the file system. Malware is downloaded from the network; it doesn't materialize from nowhere.
    In order to meet that nonexistent threat, the software modifies or duplicates low-level functions of the operating system, which is a waste of resources and a common cause of instability, bugs, and poor performance.
    By modifying the operating system, the software itself may create weaknesses that could be exploited by malware attackers.
    8. ClamXav doesn't have these drawbacks. That doesn't mean it's entirely safe. It may report email messages that have "phishing" links in the body, or Windows malware in attachments, as infected files, and offer to delete or move them. Doing so will corrupt the Mail database. The messages should be deleted from within the Mail application.
    ClamXav is not needed, and should not be relied upon, for protection against OS X malware. It's useful only for detecting Windows malware. Windows malware can't harm you directly (unless, of course, you use Windows.) Just don't pass it on to anyone else.
    A Windows malware attachment in email is usually easy to recognize. The file name will often be targeted at people who aren't very bright; for example:
    ♥♥♥♥♥♥♥♥♥♥♥♥♥♥!!!!!!!H0TBABEZ4U!!!!!!!.AVI♥♥♥♥♥♥♥♥♥♥♥♥♥♥.exe
    ClamXav may be able to tell you which particular virus or trojan it is, but do you care? In practice, there's seldom a reason to use ClamXav unless a network administrator requires you to run an anti-virus application.
    9. The greatest harm done by security software, in my opinion, is in its effect on human behavior. It does little or nothing to protect people from emerging threats, but if they get a false sense of security from it, they may feel free to do things that expose them to higher risk. Nothing can lessen the need for safe computing practices.
    10. It seems to be a common belief that the built-in Application Firewall acts as a barrier to infection, or prevents malware from functioning. It does neither. It blocks inbound connections to certain network services you're running, such as file sharing. It's disabled by default and you should leave it that way if you're behind a router on a private home or office network. Activate it only when you're on an untrusted network, for instance a public Wi-Fi hotspot, where you don't want to provide services. Disable any services you don't use in the Sharing preference pane. All are disabled by default.

  • Constant lock ups with Leopard!

    I find myself having to hold in the power button to turn my computer off almost everyday now! I am not sure what is causing these constant lock ups! Ever since upgrading to Leopard have I noticed this. Yesterday It happened when trying to open iTunes. Today it happened when I clicked on MAIL. The icon just bounces in the dock and nothing happens. I hit FORCE QUIT and that doesn't work either.
    Do I need to clear something out or get rid of something? Even when I try to restart my computer sometimes that will lock up too! The only way to get around any of these issues is to hold in the power button to turn the whole computer off, wait a few seconds and turn it back on. Once its back on, then I have full functionality out the computer again but its getting on my nerves that I have to do this all to often!
    I think they are some cool features with Leopard but I am experiencing way to many bugs/problems with it to be 100% happy with it.
    As I am writing this posting, I just clicked on my APPLE icon in the top left of the screen and then clicked ABOUT THIS MAC to make sure I was using the most current version, and NOTHING happened!

    Try reinstalling. It sounds like you did an upgrade from an earlier version that may have been corrupt to start with. You may be able to do the following:
    How to Perform an Archive and Install
    An Archive and Install will NOT erase your hard drive, but you must have sufficient free space for a second OS X installation which could be from 3-9 GBs depending upon the version of OS X and selected installation options. The free space requirement is over and above normal free space requirements which should be at least 6-10 GBs. Read all the linked references carefully before proceeding.
    1. Be sure to use Disk Utility first to repair the disk before performing the Archive and Install.
    Repairing the Hard Drive and Permissions
    Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported, then quit DU and return to the installer.
    If DU reports errors it cannot fix, then you will need Disk Warrior (4.0 for Tiger) and/or TechTool Pro (4.5.2 for Tiger) to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
    2. Do not proceed with an Archive and Install if DU reports errors it cannot fix. In that case use Disk Warrior and/or TechTool Pro to repair the hard drive. If neither can repair the drive, then you will have to erase the drive and reinstall from scratch.
    3. Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When you reach the screen to select a destination drive click once on the destination drive then click on the Option button. Select the Archive and Install option. You have an option to preserve users and network preferences. Only select this option if you are sure you have no corrupted files in your user accounts. Otherwise leave this option unchecked. Click on the OK button and continue with the OS X Installation.
    4. Upon completion of the Archive and Install you will have a Previous System Folder in the root directory. You should retain the PSF until you are sure you do not need to manually transfer any items from the PSF to your newly installed system.
    5. After moving any items you want to keep from the PSF you should delete it. You can back it up if you prefer, but you must delete it from the hard drive.
    6. You can now download a Combo Updater directly from Apple's download site to update your new system to the desired version as well as install any security or other updates. You can also do this using Software Update.

  • Verify Disk results, confusing.. Can they be the cause of system lock ups?

    I have been experiencing strange freezes on my Mac Pro 2008 system.
    My boot disk is a 50% full 128GB SSD from Crucial and is running beautifully fast however for the past couple of weeks my system often freezes for anything from 3 seconds to 30 seconds and then the Finder restarts.
    After the Finder restarts everything continues running smoothly. As if nothing ever happend, no error reports, no apps crashed, nothing.
    I have verified disk permissions and verified the disk itself in Disk Utility but I am not quite sure what these results mean and if they could be the cause of these random lock ups.
    here are the results:
    Verify permissions for “Boot Disk”
    Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.
    Group differs on "private/etc/hostconfig", should be 0, group is 20.
    Permissions verification complete
    Verifying volume “Boot Disk”
    Performing live verification.
    Checking Journaled HFS Plus volume.
    Checking extents overflow file.
    Checking catalog file.
    Missing thread record (id = 5888152)
    Incorrect number of thread records
    Checking multi-linked files.
    Checking catalog hierarchy.
    Invalid volume directory count
    (It should be 184294 instead of 184295)
    Checking extended attributes file.
    Checking volume bitmap.
    Checking volume information.
    The volume Boot Disk was found corrupt and needs to be repaired.
    Error: This disk needs to be repaired. Start up your computer with another disk (such as your Mac OS X installation disc), and then use Disk Utility to repair this disk.
    I would really appreciate it if someone that knows their way around this stuff could help me troubleshoot this.
    As for the problem of the system locking up it does not happen in the same application consistently.
    Often it happens in Firefox but it could equally often happen when working in Photoshop, browsing files in the Finder or trying to access the Spotlight search via the keyboard shortcut.
    When the system locks up I get the spinning beach ball and I can still move the mouse and click and even still access CMD+TAB app switcher, switch spaces and all those things, just applications become non responsive.
    If you need any more details please let me know.
    Thanks for reading,
    Jannis

    These are innocuous errors that you may safely ignore. However the disk error is a problem. Do the following:
    Repairing the Hard Drive
    Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger and Leopard.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors, then quit DU and return to the installer. Now restart normally.
    If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.

  • P7n Dimaond Vista 64 bit lock-ups

    Hi, I'm experiencing random hard lock ups of my newly built Vista 64bit PC
    I've reinstalled the OS 3 times, i have all the latest drivers.
    I've ran memtest several times and the vista memory diag tool with no errors, and on individual sticks. i have stress tested my CPU and GPU with no errors many times.
    it sometimes freezes 5 mins after booting up, when surfing the web, when on screen-save,r when typing in word and when playing games, sometimes it will be fine for hours then suddenly just freeze up.
    I see nothing in the Event Viewer.
    My setup:
    MSI p7n Diamond with latest official BIOS version fomr the MSI site.
    Intel e8400 @ 3.00GHz (stock)
    XFX 9800 GTX Black Edition
    4x1GB Corsair DDR2 XMS2 Ram
    Antec Quattro 1000W SLI PSU
    Trust 5.1 Sound Card.
    Hitatchi SATA HDD
    Pioneer SATA DVD/RW
    Zalman 9700NT CPU cooler.
    I updated the BIOS using MSI live update, but it was freezing before the update aswell.
    I cant find any pattern to the freez-ups it seems entirely random.
    I have manually changed the ram voltage in BIOS to 2.1V (manufacturers reccomendation) and changed timings.
    However even at stock values it still freezes
    Thanks for reading

    Quote from: cliffo88 on 23-September-08, 01:56:38
    I updated the BIOS using MSI live update, but it was freezing before the update aswell.
    I cant find any pattern to the freez-ups it seems entirely random.
    YIKES
    Whatever you do, never attempt to update the BIOS of a system that is freezing randomly, especially via MSI Live Update.  In fact, you'd be well advised to avoid MSI Live Update entirely.
    The most commonly suggested method for flashing BIOS is via USB disk method and only after booting to DOS, not Windows.  Even in these conditions, if there are hardware issues that are still preventing the system from running stable (e.g. failing PSU, excessive heat, etc.), you should not attempt to flash the BIOS. 
    Attempting a BIOS flash under any of these conditions is risking permanent and irreparable damage to your motherboard.
    As for your Vista 64 lockups, I personally am not convinced that Vista drivers are completely reliable yet, much less Vista 64.  Another possibility is that your PSU is failing.

  • After Hotsynching a Palm Treo 680, its Hotsynch stuck in loop, lock ups, etc.

    Hello,
    My father is having problem with his Palm Treo 680 (unlocked). Before the incident, he Hotsynched between his Treo and his Dell Optiplex machine (Windows 2000 SP4 with all updates; USB connection).
    The PDA went stuck in a Hotsynch screen on the PDA even if it is disconnected and hard resetted (battery removal since there is no hole). Eventually, the issue stopped (don't know what he did). However, there are still random lock ups and the looping Hotsynch again (no specific times and patterns). Also removing the extra memory cards didn't help either. Also, he reported that his phone didsn't ring either from incoming calls.
    Does anyone know what's going on? Is the PDA dying since he uses it daily all almost all day when he is awake? His warranty expired already, he said. It seems like a lot of people had problems from my Google searches.
    FYI if it helps, the Hotsynch logs BEFORE the problems (he didn't install anything new -- only data changes and updates): http://pastebin.ca/678475
    Thank you in advance.
    Post relates to: Treo 680 (Unlocked GSM)
    Post relates to: Treo 680 (Unlocked GSM)

    This behavior has been reported by users whose phones got wet in the connector area.
    Was this the case in yours?
    WyreNut
    Post relates to: Centro (AT&T)
    I am a Volunteer here, not employed by HP.
    You too can become an HP Expert! Details HERE!
    If my post has helped you, click the Kudos Thumbs up!
    If it solved your issue, Click the "Accept as Solution" button so others can benefit from the question you asked!

  • USB Devices lock-up iMac 2011

    2011 iMac 3.4Ghz i7 SSD+2TB 2GB AMD 16GB Corsair RAM
    I noticed I was experiencing random lock-ups and freezes during the first few weeks of owning the iMac.
    I went down the line of changes I made to the system.
    RAM Upgrade, software installs.
    I went with a bare OS, stock memory, still experiencing lock-ups.
    added everything back, still experiencing lock-ups.
    kept everything unplugged for two weeks, played itunes movies in quicktime on loops (10 total, 5 form the ssd and 5 from the hdd) to see if one or the other would crash the system. Two weeks straight no crash.
    Plugged my iPhone in to sync and update, after a few hours over 8hours) i came back to the system froze & locked. no mouse movement or keyboard input (caps lock key wont turn on and the seconds in the top clock were stuck).
    hard restarted, left it run for a week nothing, plugged in my apple wired keyboard, the next day hard freeze/lock-up.
    this was repeated with each usb port, within a few hours to a few days the system lock-up freeze with any usb devices plugged in.
    it would not do this with FIreWire devices or audio cable or ethernet cable attached just USB.
    is there any way to resolve this without getting the logic board replaced? or is this a firmware/software issue?
    other than that the system is amazingly fast and one of the best.

    This is the error protocol I get in Console:
    8/17/11 6:10:01 AM          com.apple.usbmuxd[38]          HandleUSBMuxDictionary client 0x10030a560-iTunes/com.apple.iTunes using library usbmuxd-211 built on Jan 13 2011 at 04:19:31, running usbmuxd-211 built on Feb  8 2011 at 13:49:43
    8/17/11 6:11:01 AM          com.apple.usbmuxd[38]          HandleUSBMuxDictionary client 0x10030a560-iTunes/com.apple.iTunes using library usbmuxd-211 built on Jan 13 2011 at 04:19:31, running usbmuxd-211 built on Feb  8 2011 at 13:49:43
    8/17/11 6:12:01 AM          com.apple.usbmuxd[38]          HandleUSBMuxDictionary client 0x101d00920-iTunes/com.apple.iTunes using library usbmuxd-211 built on Jan 13 2011 at 04:19:31, running usbmuxd-211 built on Feb  8 2011 at 13:49:43
    8/17/11 6:38:53 AM          DirectoryService[11]          Improper shutdown detected
    8/17/11 6:38:52 AM          com.apple.launchd[1]          *** launchd[1] has started up. ***
    8/17/11 6:38:53 AM          blued[17]          Apple Bluetooth daemon started
    8/17/11 6:38:55 AM          mDNSResponder[18]          mDNSResponder mDNSResponder-258.21 (May 26 2011 14:40:13) starting
    8/17/11 6:38:55 AM          configd[15]          network configuration changed.
    8/17/11 6:38:55 AM          configd[15]          setting hostname to "Anexometas-iMac.local"
    8/17/11 6:38:56 AM          com.apple.kextd[10]          Can't load /System/Library/Extensions/IOSerialFamily.kext/Contents/PlugIns/InternalModemSu pport.kext - no code for running kernel's architecture.
    8/17/11 6:38:56 AM          com.apple.kextd[10]          Failed to load /System/Library/Extensions/IOSerialFamily.kext/Contents/PlugIns/InternalModemSu pport.kext - (libkern/kext) requested architecture/executable not found.
    8/17/11 6:38:56 AM          com.apple.kextd[10]          Load com.apple.driver.InternalModemSupport failed; removing personalities.
    8/17/11 6:38:56 AM          fseventsd[48]          event logs in /Volumes/Macintosh HD 2/.fseventsd out of sync with volume.  destroying old logs. (249678 1 251431)
    8/17/11 6:38:56 AM          fseventsd[48]          log dir: /Volumes/Macintosh HD 2/.fseventsd getting new uuid: 129AD7BD-08D0-46CC-BA19-0949EEA1F589
    8/17/11 6:38:56 AM          fseventsd[48]          event logs in /.fseventsd out of sync with volume.  destroying old logs. (249828 4 251431)
    8/17/11 6:38:56 AM          /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow[44 ]          Login Window Application Started
    8/17/11 6:38:56 AM          bootlog[55]          BOOT_TIME: 1313588332 0
    8/17/11 6:38:57 AM          com.apple.usbmuxd[36]          usbmuxd-211 built on Feb  8 2011 at 13:49:43 on Feb  8 2011 at 13:49:43, running 64 bit
    8/17/11 6:38:57 AM          fseventsd[48]          log dir: /.fseventsd getting new uuid: FCEA12C2-52A7-426E-93BD-6FF4A42D4221
    8/17/11 6:38:58 AM          airportd[66]          failed to snag beacon
    8/17/11 6:38:58 AM          loginwindow[44]          Login Window Started Security Agent
    8/17/11 6:38:59 AM          loginwindow[44]          Login Window - Returned from Security Agent
    8/17/11 6:38:59 AM          loginwindow[44]          USER_PROCESS: 44 console
    8/17/11 6:38:59 AM          com.apple.launchd.peruser.502[98]          (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
    8/17/11 6:39:01 AM          configd[15]          network configuration changed.
    8/17/11 6:39:01 AM          UserEventAgent[118]          **** ERROR: SCNetworkSignatureCopyActiveIdentifiers returned nil
    8/17/11 6:39:01 AM          com.apple.launchd.peruser.502[98]          (com.apple.Kerberos.renew.plist[124]) Exited with exit code: 1
    8/17/11 6:39:01 AM          com.apple.usbmuxd[36]          HandleUSBMuxDictionary client 0x101c043b0-iTunesHelper/com.apple.iTunesHelper using library usbmuxd-211 built on Jan 13 2011 at 04:19:31, running usbmuxd-211 built on Feb  8 2011 at 13:49:43
    8/17/11 6:42:52 AM          com.apple.usbmuxd[36]          HandleUSBMuxDictionary client 0x101c045e0-iTunes/com.apple.iTunes using library usbmuxd-211 built on Jan 13 2011 at 04:19:31, running usbmuxd-211 built on Feb  8 2011 at 13:49:43
    8/17/11 6:42:52 AM          WindowServer[73]          kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    8/17/11 6:42:52 AM          com.apple.WindowServer[73]          Wed Aug 17 06:42:52 Anexometas-iMac.local WindowServer[73] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    8/17/11 6:49:00 AM          /System/Library/CoreServices/CCacheServer.app/Contents/MacOS/CCacheServer[ 130]          No valid tickets, timing out
    8/17/11 6:55:09 AM          [0x0-0x19019].com.apple.iTunes[173]          Successfully connected to the Intel plugin
    8/17/11 6:55:09 AM          [0x0-0x19019].com.apple.iTunes[173]          Version from driver for Certificates 1
    8/17/11 6:55:12 AM          com.apple.launchd.peruser.502[98]          (com.apple.AirPortBaseStationAgent[126]) Exited: Killed
    8/17/11 6:55:12 AM          com.apple.launchd.peruser.502[98]          ([0x0-0xb00b].com.apple.iChatAgent[134]) Exited: Killed
    8/17/11 6:55:12 AM          loginwindow[44]          DEAD_PROCESS: 44 console
    8/17/11 6:55:12 AM          shutdown[208]          halt by maxstanley:
    8/17/11 6:55:12 AM          shutdown[208]          SHUTDOWN_TIME: 1313589312 459712
    8/17/11 6:55:12 AM          mDNSResponder[18]          mDNSResponder mDNSResponder-258.21 (May 26 2011 14:40:13) stopping
    8/17/11 6:55:12 AM          DirectoryService[11]          BUG in libdispatch: 10K549 - 1960 - 0x10004004
    8/17/11 6:55:12 AM          imagent[127]          Quit - notifying about shutdown
    8/17/11 6:55:12 AM          WindowServer[73]          hidd died. Reestablishing connection.
    8/17/11 6:55:12 AM          imagent[127]          Quit - shutting down daemon
    8/17/11 6:55:12 AM          imagent[127]          [Warning] imagent shutting down
    8/17/11 6:55:12 AM          imagent[127]          Unable to create APS daemon connection: (ipc/mig) server died
    8/17/11 6:55:12 AM          imagent[127]          Unable to set enabled topics: (ipc/send) invalid destination port
    8/17/11 6:55:12 AM          /Applications/FaceTime.app/Contents/PrivateFrameworks/IMCore.framework/ima gent.app/Contents/MacOS/imagent[127]          BUG in libdispatch: 10K549 - 1960 - 0x10004004
    8/17/11 6:56:38 AM          com.apple.launchd[1]          *** launchd[1] has started up. ***
    8/17/11 6:56:39 AM          blued[17]          Apple Bluetooth daemon started
    8/17/11 6:56:39 AM          mDNSResponder[18]          mDNSResponder mDNSResponder-258.21 (May 26 2011 14:40:13) starting
    8/17/11 6:56:39 AM          configd[14]          network configuration changed.

  • Pages '08 lock ups

    A couple months ago, I started having issues with Pages '08. It would lock up while I was typing, or even something as simple as scrolling the page down. All I would get was the little rainbow wheel and a locked up document. At first I thought it was just the one file I was working on, but now it happens all the time. It locks up so bad sometimes that it forces a restart of the computer. No other programs are having this issue. Should i just reinstall Pages '08 from the disc or what. Cause this has made my main wordprocessing program completely useless. I'm on Mac OSX 10.5.8

    Update:
    Well I think I got it figured out. For some reason, the spell checker was causing the problem. I've always had it set to "Check spelling as you type", but for some reason that is now causing Pages to lock up. So my work around is to simply turn off the "Check Spelling as you type" option, and now there are no more lock ups.

  • Terca 9100 lock ups

    Hi!
    I recently got my hands on a second hand tecra 9100. I got it free since the previous owner complained about random lock ups or freezes. As i've testaed the laptop myself i experienced this aswell. It can freeze just about anytime but i've never had it running flawlessly for more than 20 minutes i recon. Sometimes it also refuses to start up. I do not know if this is a lock up in the initial startup sequence.
    Anyway it will lock up even in bios and i have dissassembled it and put it back together, replaced the RTC battery (with a non rechargable) and removed any hardware not crucial for useage (i.e WiFi card, extra RAm modules, modem card).
    I'm clueless, anyone got any idea of what to try next?
    Regards Simon

    I think you cant fix it by yourself
    In your case the ASP should check the notebook and if necessary replace the faulty part/device.

  • R835 P56X lock ups

    From day 1 (purchased a month ago) I'm still having lock ups with this laptop!  After few hours of use the screen goes black (sometimes blue), if I try to revive it the fan kicks in at full speed sounding like a leaf blower!
    I've reinstalled Win7 with the latest drivers, installed a new SSD instead of the HD and this problem keeps re-occuring randomly (daily)!
    I certainly would appreciate any ideas!

    I replaced my HDD with a OCZ Vertex 3 SSD for my R835-P56x.  It boot in seconds and runs nice and fast, but I get lock-ups and BSOD after several hours (as described above).  Not sure if it had the problem with the HDD, because I didnt use the PC very long before upgrading.  I am also running a 800MB Dataram RAM Disk (Version 3.5.130) for browser cache, which I suspect could be the culprit.   My bios is 3.90 (7/31/2012).
    Portege R835-P56x, i5 2410M, 16GB RAM, Vertex 3 SSD 240GB.

Maybe you are looking for