Logic X CPU Overload with External HD, or HD Overload with Internal HD

System is MBP Mid-2010 with 4gb. I created a 3 audio track + 1 drummer track session. If the session is on the internal drive, then upon playback, I can see in the system usage display in the transport that there is a huge burst of hard disk usage close to 100% which then drop back to a low load within 10-20 seconds. Problem is that in some cases, it prompts the system overload error message, about 1/3 of the time.
Instead, I copied the session on an external FW800 drive (G-Technology). I no longer have any hard rive overload issues, but now it is the CPU which is almost fully utilized between 70-90%, also generating an overload error.
So I'm not really sure what to do here? What is the correct setup to have neither overload, or at least eliminate the initial HD overload?
Help appreciated

Try this...
Download Etrecheck from here...
http://www.etresoft.com/etrecheck
Install....
Now load the project where you are seeing high CPU usage in Logic and then run Etrecheck.. posting up the full report here when it's done...
That may shed some light on the true cause of your issue... as normally FW800 connected drives are very easy on CPU usage unlike USB external drives
Cheers..
Nigel

Similar Messages

  • Logic 8 CPU overload for absolutely no reason

    I'm too familiar with this, which is what I'm getting for just one project that I recently started:
    "Logic Pro: Disk is too slow or System Overload."
    There's nothing wrong with my computer. It's a 2 x 2.8 Quad-Core Intel Xeon with 8 GB of memory. And here's a picture of what's on this project. Essentially NOTHING.
    I'm panning back and forth between audio regions (consisting of clips from different songs) on two different tracks fading in and out. Nothing fancy. Yet the first time (only the first time) the playhead encounters the next region, the CPU overload window pops up. I mean....really? Why? I have no idea why this is. I am running on Logic 8.0.2 but I see no reason to "upgrade" as this version is not CPU overloading on any other project.

    There are a few threads on this topic already, including one a couple of days ago. They should get you started with some ideas about how to approach the problem.
    Marcus

  • CPU Overload (-10010) with Logic 9.0.2 and SL 10.6.2 after clean install

    Whether using the demo song (Numbers Game), or a new song even with just a couple of instruments (EXS) and a single audio track I get a CPU overload -10010 or -1009 message sometimes every few seconds, sometimes every 30 minutes.
    I thought perhaps a conflict with drivers or other software, so I have tried a clean install of SL10.6, updated to 10.6.2, loaded Logic Pro, updated to 9.0.2, and added NO OTHER SOFTWARE AT ALL, and used internal audio, still same problem.
    This seems to be a bug in Logic or SL. What can I do?
    Message was edited by: ebjornard

    This is no bug, your system is telling you that it cannot handle the full load of this song. Try Freezing tracks with heavy CPU-using plugins on them.
    Also, check (and bookmark!) these docs:
    http://support.apple.com/kb/TA24535?viewlocale=en_US
    http://support.apple.com/kb/HT3161
    http://support.apple.com/kb/HT2375
    and especially:
    http://discussions.apple.com/thread.jspa?threadID=2175192&tstart=0

  • Help with Mainstage 3.1 CPU overload issue

    I was using Kontakt 5, UVI Workstation and Pianoteq 5 in MainStage 3 without any issues.
    Since I updated to MS 3.1, The CPU is always above 100% !!! I am facing audio dropouts and it is absolutely impossible to play a show
    Is anyone else facing the same issue? Any tips to help reduce CPU overload will be helpful.
    I have Contact and UVI workstation running from an external hard disk. I thought that might be the issue but i tried with a keyboard template set in MS 3.1 and still while playing CPU usage shoots to 100% plus!
    I am on a MacBook Pro (Retina, 13-inch, Late 2013), 2.4 GHz Intel Core i5, 8 GB 1600 MHz DDR3.

    Try to get the Mainstage 3.0.4 from a timemachine backup.
    Try to update all your programs like pianotec.
    For me, 3.1 feels better concerning timing/ latency. This might cause more stress for the processors.
    My system i7 2,2 GHz is always getting hot, fans go crazy. There's a limit: Better than 64 Samples buffer is not possible.
    To be serious: A real Piano needs  0,25ms to produce a sound. We have to deal with 4ms. That's bad. So you could increase buffersize to 128 and try playing? It makes no big difference if you play the poor 4ms ore poor 6ms for example. In every case we are far away from the real thing.
    Check, if you activated the "savety buffer" checkbox in audiodriver window.
    If you can't find 3.0.4., you could try to reduce the installed channelstrips in your patches. Effects in concert level should be reduced. Evt. you have Efx in busses that are not needed in most patches. So cancel them in concertlevel and install them in selected patches.
    I replaced a spacedesigner reverb with an reverb outside the system, it's processed from the interface. Same with a chorus.
    I tested a newer MacbookPro retina, that was not better than mine. The difference was, it produced little dropouts every 10 seconds.
    Hopefuly there will be a update for 3.1 soon.
    And be serious: Before 3.1 you could play a show without dropouts, but was it fun? Mainstage urgently needs better latency capabilities, generally.

  • CPU Issues with music production. LOGIC 8

    CPU Issues with music production.
    Hey guys. I bet this sort of question has been asked so many times, but i really have spent a long time searching google to get an answer. I have had no luck. I found many things on the subject, but nothing about this exact situation.
    Okay, I have a Macbook 4.1 which has 2gb of ram, 2.1 GHz Intel core 2 duo processor, and a 111 gb HD with a rpm of 5400.
    I have been having major CPU overloads whilst using Logic 8, And it is much worse when using Pro Tools 7.2 M-Powered.
    Now, im not that knowledgeable with computer stuff, but I have a plan.
    Im about to upgrade my ram to 4gb, and im getting a new hard drive that will be 320 gb and will be 7200 rpm and 16gb cache (whatever that means).
    I believe that having a hard drive at 7200 rpm is pretty essential for music programs like these.
    Now hopefully this will help me with the CPU, as i have found out I cant upgrade the processor as its soldered on.
    Will this machine be able to handle Logic Pro 8 after the mod??
    The real question i guess is: Is a "2.1 GHz Intel Core 2 Duo" processor enough to happily run logic 8?
    P.S I will not be recording audio. I use the synths etc included.
    Thanks in advance guys.

    Alexander Farrar wrote:
    Okay, I have a Macbook 4.1 which has 2gb of ram, 2.1 GHz Intel core 2 duo processor, and a 111 gb HD with a rpm of 5400.
    111Gigs is a small disk
    How much free space in your system disk?
    when a disk contain files from over than 80% and only about 20% is free the speed of the hard drive goes down... some disk can loose more than 50% of fast addressing speed
    Leopard require at least 50GB free space for run without problem!
    for better performance up to 1/3 of the disk size should be required...
    I have been having major CPU overloads whilst using Logic 8, And it is much worse when using Pro Tools 7.2 M-Powered.
    you use Logic with a Digidesign Drivers?
    try to disconnect the Digi device and use Internal Audio of your Mac...
    maybe only that can solve your issue.
    Im about to upgrade my ram to 4gb, and im getting a new hard drive that will be 320 gb and will be 7200 rpm and 16gb cache (whatever that means).
    buying a 320GB at 7200?
    I suggest you a 500GB at 5400 RPM
    the 7200 Hard drive are not so good for stay inside Macbook chassis
    the working temperature in a 7200 RPM disk should be cause slower speed than a more cool/fresh 5400 RPM
    The temperature rise up if disk is full over than 1/3 of its capabilities...
    (this rules are related with Disk performance but can be affected also CPU power in the real time processing because the system run on the same disk)
    The hard drive temperature is strictly related with disk speed performance
    and logic use a lot of streaming from to disc access for the EXS24 virtual memory and other Instruments and Synths...
    *this can be the primary cause of CPU spikes*
    I believe that having a hard drive at 7200 rpm is pretty essential for music programs like these.
    I suggest a 500GB 5400 RPM!
    G

  • Different CPU Overload

    I read the earlier post about CPU overload. I am not getting the overload error message, Logic just stops when the CPU bar is slammed into the red. I am not using any plug-ins or effects, I do have 48 channels of audio I am trying to mix. I have been using Logic for over a year and a half now and this is a new problem. Is there something else I can check to discover why suddenly I have this overload problem?

    Different CPU Overload
    this is OP question...
    I try to answer directly to you:
    Yes!!!
    *There are different Logic overloads on different CPUs + audio device*
    the overlaods message are strictly related with your CPU + Audio interface + RAM ammout and speed + Front Buss speed + Firewire, USB, PCI cards...
    *also external drives spinndown can cause overloads message*
    in a Pro Studio... I use workstation without external device...
    all Firewire and USB device must be disconnected.. also bluetooth must be off...
    (don't use bluetooth Mouse in Professional recording studio)
    *Also File sharing and Wirless Airport must be turned to OFF!!!*
    (OS X is a multitasking system... this is a great advantage for everyone... except for Professional Live processing power request... reduce to minimum the background running process is a must to avoid overloads and CPU spikes)
    The audio cards that require CPU cycles are...
    1) PCI or PCIe cards... Near to 0.1% CPU demand
    2) Firewire... a little bit more (about from 3% to 8%.. depend about firewire Chip set and drivers) of CPU demand
    3) USB = maximum CPU load power request... (more than 10% to 25% and more.. and this percentage rise up related with number of tracks)
    (approximately percentage are stryctly related with CPU.. if G4 or G5 or Intels)
    *So CPU overload are different and strictly related with your hardware!!!*
    G

  • What setting should I use for Abbey Road drums?  Getting a cpu overload issue

    What setting should I use for Abbey Road drums (i.e. multi-output, stereo, etc)?  Getting a cpu overload issue.  I have a macbook pro, 4 gb ram, running Logic Pro 9.  Just 3 tracks of drums and a few real instrument tracks.  Can't find a guide in the manual for either Kontakt or Logic.  Thanks in advance!

    Hi
    AR drums are complete resource (CPU) hogs. They work better if you turn off as many of the AR internal plugins as you can.
    See section 4 (?) of the AR manual, which you can find within Kontakt (In the library area of Kontakt click hold the small "i" on the right of the "AR drummer" Library).
    Alternatively, your only solution is to increase the I/O buffer in Preferences:Audio, with the associated increase in latency
    CCT

  • CPU Overloads: What to try?

    I know this is a tired subject but considering that it doesn't seem the CPU overload and application instability can be solved in the current version of Logic, just wondering if anyone has a good work around.
    Basically, I find that while using 3rd party plugins (i.e. Kontakt 2, Omnisphere), I can get about 8 or 9 tracks before I begin to have routine application crashes, overload message, etc. Freezing does not change this (and the activity monitor shows a massive jump in real memory from 2.0 gigs to 16TB with the addition of a 9th track depending on the size of the instruments i'm using). This also has nothing to do with buffer size.
    I realize that Logic has limitations in the collective size of the plugins that can be loaded (up to 2.7 gigs of 3rd party plugins) so I'm wondering if I wanted to at least double the number of soft synth instruments I can load up what could I do? I've heard some people add more hardware like another Mac or something like Muse receptor which can load your plugins through logic but doesn't tap into Logic resources. Not sure how this works though, or if there's a better idea out there.
    Any heavy soft synth users out there?

    and the activity monitor shows a massive jump in real memory from 2.0 gigs to 16TB
    It's a known issue with Kontakt that it can only handle 2 Gigs, adjust the DFD settings and reduce the number of voices to 128 (12MB) that will free up quite a lot of RAM. Also you can open a standalone version of Kontakt and wire it via the IAC Bus giving you another 2 Gigs if you have enough RAM installed. With Kontakt update 3.5 the 2 Giga limit will be gone but that doesn't help so much as Logic will still be a 32 Bit application in which the limit still is about 2,7 Gigs of physical and 3,5 Gigs of virtual RAM.
    Besides that enter the word "overload" in the search field of this Forum and you will get thousands of posts about that tiring topic...

  • CPU Overload?  Really?

    Hey Guys
    I'm running a pretty simple project - 5 tracks of audio and about 10 VIs including Addictive Drums and RPs Blue, with some UAD-2 plugs on most of them. Even with my buffer size being huge, I'm still seeing on of my processors spike. This gives an overload error and stops playback. Usually when sections change and new instruments enter the arrange.
    Opening Activity Monitor doesn't reflect what is showing in Logic's CPU meters. They are just idling.
    Any thoughts?

    Hey pan,
    Thanks for the link. I've had the same issue as decribed above for a while now, but I have it when I use BFD2. So in both cases it's a software instrument that nails the CPU. It is not BFD's fault for sure. It's the the audio interface issue in my case for sure. I tested it by installing a fresh copy of 10.5.6 on a drive, installing Logic and nothing else, and installing BFD... problem still happens... even happens now with Kontakt.
    The issue is burried within Logic. No one's claimed it to be a problem at Apple, nor do I expect them to. What will likely happen is that at some point they'll release a bug fix and this problem will magically go away.
    To the original poster, 2 things to keep in mind:
    1- This problem is exacerbated if you're using 88.2 (or higher) sample rate
    2- This problem is exacerbated by a very small buffer, try to stick around 256 or larger.
    3- Since you're using UAD like I am, if you set your buffer to 512 or less, be sure to set your Process Buffer Range to Small. If you set it to 1024, set the PBR to Medium. This is as per the technotes on the UAD site.
    The nice-ing doesn't do anything, it makes logic redraw faster because more resources are allocated to it. The article Pan points to is INVALUABLE for sure and depicts the issue very clearly. Obviously Apple knows about it. Short of a change in architecture, I don't know how we'd get past this problem... but I'm all ears (no pun intended)
    R

  • CPU overload after only 2 audio tracks

    Hello
    Could anyone please put me in the right direction and possibly let me know if I am missing something.
    My CPU (suddenly, as it was quite fine a few days ago) is clipping while using Logic Pro only after recording 2 audio guitar tracs.
    I am going through a MOTU card that has been updated to the latest version to no avail.
    the computer as well as Logic have been rebooted with the same dilemma.
    The problem is as well being exhibited in other songs previously recorded with no issues.
    Any insight would be tremendously appreciated...
    thank you
    RJC

    Nothing has changed?
    Do you have Automatc Updates enabled, did OSX update, are you using any new or different plugins?
    What sample frequency and bit-depth are you recording at?      Example:  44.1kHz  24-bit
    What is the Preferences/Audio I/O Buffer setting?
    And... is your head drive getting close to full?

  • High CPU Load with Alesis Multimix Usb 2.0 mixer

    Hi everybody,
    i'm still playing around with logic studio 9, mainly mainstage 2.1.1 for a possible future live use.
    Today i tried to use my Alesis Multimix 8 usb2.0, just as the output devices, using software instruments with a m-audio keystation.
    I always get cpu peak load when playing notes, with every patch, either internal apple instrument or third party au instruments, when idle cpu load goes to about 40%...
    If i revert back to internal output / internal input, cpu load drastically goes down to 10% idle and max 50-60% with internal instruments,max 80% with 2-3 layers of third party au instruments (Omnisphere, loungelizard, m-tron)...
    I know that Alesis mac drivers for snow leopard are at a beta stage, but am i the only one experiencing this or is it a known problem?
    Thanks,
    Alex.

    Gotenks82 wrote:
    Hi Pan,
    i made a different test today...
    I know it's not the same but i tried using a guitar rig on mainstage (guitar on channel1 in the mixer), and even with 256 samples i ALWAYS get 100% cpu usage...
    then closed mainstage and opened NI Guitar Rig 3 as standalone, using the alesis as interface, with 64 samples as buffer, i cannot go over 13-14% of CPU usage (Hi quality enabled)... I know that mainstage adds more effects than the ones i selected in guitar rig 3, but the HUGE difference in cpu usage cannot be just that, i mean...
    It could be if one of the effects Mainstage was using is Space Designer.
    If it is using Space Designer try using a lesser reverb, like Gold.
    USB doesn't use that much more CPU so that's not the problem.
    You are comparing two separate guitar setups, correct? Or do you mean you're opening Guitar Rig 3 in Mainstage?
    pancenter-
    As I understand it you are opening completely different setups, correct.

  • Artsd giving me 'CPU overload' problem.

    Hello everybody,
    I've just installed Arch Linux, along with X, KDE, and the like. Now, when I boot into KDE, I get this error message saying "Sound server fatal error: cpu overload, aborting".
    The error message appears in an artsmessage window.
    My computer becomes very slow before I get this error as artsd uses 99% of cpu before it crashes. I found this out using the `top` command.
    I have alsa and all of it's modules compiled. The alsa module is also inserted into DAEMONS array.
    So.. what does one do in this situation? Thanks.

    I just tried that. The utility tells me everything is good.
    So I decide to try something new. I log in as root and start KDE. Artsd doesn't crash anymore, and it only eats up half of my CPU.
    top - 00:34:26 up 14 min, 1 user, load average: 2.94, 2.56, 1.38
    Tasks: 80 total, 3 running, 77 sleeping, 0 stopped, 0 zombie
    Cpu(s): 74.7% us, 25.3% sy, 0.0% ni, 0.0% id, 0.0% wa, 0.0% hi, 0.0% si
    Mem: 739740k total, 350724k used, 389016k free, 54072k buffers
    Swap: 987956k total, 0k used, 987956k free, 192836k cached
    PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
    10466 root 25 0 1796 984 780 R 43.3 0.1 1:48.52 top
    9400 jeezus84 25 0 10460 6040 4052 R 41.6 0.8 5:22.37 artsd
    12407 root 15 -1 151m 19m 2580 S 2.0 2.8 0:04.58 X
    12659 root 15 0 30176 15m 11m S 2.0 2.1 0:00.57 konsole
    1 root 16 0 1388 504 444 S 0.0 0.1 0:00.85 init
    2 root RT 0 0 0 0 S 0.0 0.0 0:00.00 migration/0
    3 root 34 19 0 0 0 S 0.0
    I get a new window that pops up now, as soon as I log into KDE as root.
    It's another artsmessage window, but this one says:
    " Sound server informational message:
    Error while initializing the sound driver:
    device: default can't be opened for playback (Device or resource busy)
    The sound server will continue, using the null output device."
    So, i'm stumped. I was going to get rid of the arch installation of alsa, and reinstall from the files i find at the alsa website, but I can't remove alsa using Pacman because other programs need it.
    Any advice is greatly appreciated. Aside from this minor wrinkle, i'm thoroughly impressed with Arch Linux. Having used Gentoo before this, it's embodies everything I liked about Gentoo without any of the bloody compiling. Good show.

  • Mobo won't work with internal or external isdn

    2 of my buddy's bought themself 875P FISR mobo's, after i highly recomended it to them.  
    the mobo's run great except for this one major bug on it
    you cant connect a isdn modem to it.
    we've tested 2 isdn modems(pci internal & usb external) on both mobo's and they both do the same thing --> crash on isdn installation gives out some weird message irq not less or equal??????
    both of these mobo's have the latest bios's installed on them(3.2) and we've tried clearing the NV ram/rom or something like that and that didn't seem to work + reinstalling winXP pro
    Is this a known issue or is this a new prob.
    their system specs:
    both antec true 550 watt psu's
    both 3Ghz CPU's with HT
    both 1Gig Transcend Ram
    both MSI 875P FISR Mobo
    pc 1.    
       runs sata raid0 with 2 X 120gig drives(very fast)
       transcend radeon 9600 XT
       standard cooling.
       onBoard sound
    pc 2.
       single 120 sata hdd(not so fast)
              heculeze 9800 SE
       Peltier cooling system
       some 7.1 hometheater thing
    Pleaze help.

    Quote
    irq not less or equal
    There is a lot of documentation for that same error all over the web I was having the same trouble a while back with no relation to isdn at all. I was never able to pin it down. It was fixed with a reinstall.
    You might want to do a 'google' on that error message and do a search on it at MS site too. Maybe with isdn in the search string too.
    Make sure you have all your drivers for the motherboard updated, chipset etc...
    As well as the driver for the modem itself. ISDN being a technology that is somewhat on the way out the door is receiving less and less support from the Manufacturers. Are your Modem drivers for XP specifically ? There is a good chance that a Win9.x driver would not work properly.
    I had ISDN for a couple years. It was better than regular dialup but overall it was a major pain in the arse. Partially becuase the modem I had was a junkie one. It plugged up to serial. Thereby limiting my max speed to 115 instead of the possible 128.  It was very sensitive to port settings and the like. Was too dadgummed expensive too.
    Good Luck, Hope I helped a lil.  
    Jagou

  • Config Manager Agent - after Hardware Inventory High CPU Usage with WMIPRSVE and very fast empty Battery

    Hi there,
    since a few days there is on some machines (40-60) a high cpu usage on one core (quad core cpu machines) with the WMIPRSVE.EXE if the HARDWARE INVENTORY CYCLE started.
    i try out some tests, read some forum articles and troubleshooting the WMI management but a real problem i doesn´t see.
    in some articles i read that hardware inventory runs about minutes up to more hours but some machines runs longer, someone more as 1 day.
    here an example of mine PC:
    at 8:07 i started Hardware Inventory Cycle, in the InventoryAgent.log i can see that some Collection Namespace are captured.
    after a few minutes there stopped and does nothing round about 5.9 hours or better, after 21436.097 Seconds.
    For any hints i am grateful. :)
    Inventory: *********************** Start of message processing. ***********************
    InventoryAgent 18.03.2015 08:09:56
    11088 (0x2B50)
    Inventory: Message type is InventoryAction InventoryAgent
    18.03.2015 08:09:56 11088 (0x2B50)
    Inventory: Temp directory = C:\WINDOWS\CCM\Inventory\Temp\
    InventoryAgent 18.03.2015 08:09:56
    11088 (0x2B50)
    Inventory: Clearing old collected files. InventoryAgent
    18.03.2015 08:09:56 11088 (0x2B50)
    Inventory: Opening store for action {00000000-0000-0000-0000-000000000001} ...
    InventoryAgent 18.03.2015 08:09:56
    11088 (0x2B50)
    CInvState::VerifyInventoryVersionNumber: Mismatch found for '{00000000-0000-0000-0000-000000000001}': 4.2 vs. 0.0
    InventoryAgent 18.03.2015 08:09:56
    11088 (0x2B50)
    Inventory: Version number mismatch; will do a Full report.
    InventoryAgent 18.03.2015 08:09:56
    11088 (0x2B50)
    Inventory: Action=Hardware, ReportType=ReSync, MajorVersion=5, MinorVersion=0
    InventoryAgent 18.03.2015 08:09:56
    11088 (0x2B50)
    Inventory: Initialization completed in 0.141 seconds
    InventoryAgent 18.03.2015 08:09:56
    11088 (0x2B50)
    Collection: Namespace = \\localhost\root\Microsoft\appvirt\client; Query = SELECT __CLASS, __PATH, __RELPATH, CachedLaunchSize, CachedPercentage, CachedSize, LaunchSize, Name, PackageGUID, TotalSize, Version, VersionGUID FROM Package; Timeout = 600 secs.
    InventoryAgent 18.03.2015 08:09:56
    7836 (0x1E9C)
    Failed to get IWbemService Ptr for \\localhost\root\vm\VirtualServer Namespace: 8004100E
    InventoryAgent 18.03.2015 08:10:02
    7836 (0x1E9C)
    Failed to enumerate instances of VirtualMachine: 8004100E
    InventoryAgent 18.03.2015 08:10:02
    7836 (0x1E9C)
    Collection: Namespace = \\.\root\cimv2\sms; Query = SELECT __CLASS, __PATH, __RELPATH, AddressWidth, BrandID, CPUHash, CPUKey, DataWidth, DeviceID, Family, Is64Bit, IsHyperthreadCapable, IsMobile, IsTrustedExecutionCapable, IsVitualizationCapable, Manufacturer,
    MaxClockSpeed, Name, NormSpeed, NumberOfCores, NumberOfLogicalProcessors, PCache, ProcessorId, ProcessorType, Revision, SocketDesignation, Status, SystemName, Version FROM SMS_Processor; Timeout = 600 secs.
    InventoryAgent 18.03.2015 08:10:02
    7836 (0x1E9C)
    Collection: Namespace = \\.\root\CCM\powermanagementagent; Query = SELECT __CLASS, __PATH, __RELPATH, Requester, RequesterInfo, RequesterType, RequestType, Time, UnknownRequester FROM CCM_PwrMgmtLastSuspendError; Timeout = 600 secs.
    InventoryAgent 18.03.2015 08:10:03
    7836 (0x1E9C)
    Collection: Namespace = \\.\root\cimv2; Query = SELECT __CLASS, __PATH, __RELPATH, Availability, Description, DeviceID, Manufacturer, Name, Status FROM Win32_IDEController; Timeout = 600 secs.
    InventoryAgent 18.03.2015 08:10:03
    7836 (0x1E9C)
    Collection: Namespace = \\.\root\cimv2\sms; Query = SELECT __CLASS, __PATH, __RELPATH, BinFileVersion, BinProductVersion, Description, ExecutableName, FilePropertiesHash, FilePropertiesHashEx, FileSize, FileVersion, HasPatchAdded, InstalledFilePath, IsSystemFile,
    IsVitalFile, Language, Product, ProductCode, ProductVersion, Publisher FROM SMS_InstalledExecutable; Timeout = 600 secs.
    InventoryAgent 18.03.2015 08:10:03
    7836 (0x1E9C)
    Collection: Namespace = \\.\root\cimv2; Query = SELECT __CLASS, __PATH, __RELPATH, DefaultIPGateway, DHCPEnabled, DHCPServer, DNSDomain, DNSHostName, Index, IPAddress, IPEnabled, IPSubnet, MACAddress, ServiceName FROM Win32_NetworkAdapterConfiguration; Timeout
    = 600 secs. InventoryAgent
    18.03.2015 14:06:43 7836 (0x1E9C)
    Collection: Namespace = \\.\root\Nap; Query = SELECT __CLASS, __PATH, __RELPATH, description, fixupState, friendlyName, id, infoClsid, isBound, percentage, registrationDate, vendorName, version FROM NAP_SystemHealthAgent; Timeout = 600 secs.
    InventoryAgent 18.03.2015 14:06:43
    7836 (0x1E9C)
    Collection: Namespace = \\.\root\cimv2\sms; Query = SELECT __CLASS, __PATH, __RELPATH, AdditionalProductCodes, CompanyName, ExplorerFileName, FileDescription, FilePropertiesHash, FileSize, FileVersion, FolderPath, LastUsedTime, LastUserName, msiDisplayName,
    msiPublisher, msiVersion, OriginalFileName, ProductCode, ProductLanguage, ProductName, ProductVersion, SoftwarePropertiesHash FROM CCM_RecentlyUsedApps; Timeout = 600 secs.
    InventoryAgent 18.03.2015 14:06:43
    7836 (0x1E9C)
    Collection: Namespace = \\.\root\cimv2; Query = SELECT __CLASS, __PATH, __RELPATH, BankLabel, Capacity, Caption, CreationClassName, DataWidth, Description, DeviceLocator, FormFactor, HotSwappable, InstallDate, InterleaveDataDepth, InterleavePosition, Manufacturer,
    MemoryType, Model, Name, OtherIdentifyingInfo, PartNumber, PositionInRow, PoweredOn, Removable, Replaceable, SerialNumber, SKU, Speed, Status, Tag, TotalWidth, TypeDetail, Version FROM Win32_PhysicalMemory; Timeout = 600 secs.
    InventoryAgent 18.03.2015 14:07:02
    7836 (0x1E9C)
    Collection: Namespace = \\.\root\cimv2; Query = SELECT __CLASS, __PATH, __RELPATH, Availability, Description, DeviceID, InstallDate, Manufacturer, Name, PNPDeviceID, ProductName, Status FROM Win32_SoundDevice; Timeout = 600 secs.
    InventoryAgent 18.03.2015 14:07:02
    7836 (0x1E9C)
    Collection: Namespace = \\.\root\cimv2; Query = SELECT __CLASS, __PATH, __RELPATH, Caption, ClassGuid, ConfigManagerErrorCode, ConfigManagerUserConfig, CreationClassName, Description, DeviceID, Manufacturer, Name, PNPDeviceID, Service, Status, SystemCreationClassName,
    SystemName FROM Win32_USBDevice; Timeout = 600 secs.
    InventoryAgent 18.03.2015 14:07:12
    7836 (0x1E9C)
    Collection: 62/74 inventory data items successfully inventoried.
    InventoryAgent 18.03.2015 14:07:12
    7836 (0x1E9C)
    Inventory: Collection Task completed in 21436.097 seconds
    InventoryAgent 18.03.2015 14:07:12
    7836 (0x1E9C)
    Inventory: 12 Collection Task(s) failed. InventoryAgent
    18.03.2015 14:07:12 7836 (0x1E9C)
    Inventory: Temp report = C:\WINDOWS\CCM\Inventory\Temp\25bf01b2-12fc-4eea-8e97-a51b3c75ba50.xml
    InventoryAgent 18.03.2015 14:07:12
    7836 (0x1E9C)
    Inventory: Starting reporting task. InventoryAgent
    18.03.2015 14:07:12 7552 (0x1D80)
    Reporting: 4381 report entries created. InventoryAgent
    18.03.2015 14:07:13 7552 (0x1D80)
    Inventory: Reporting Task completed in 1.030 seconds
    InventoryAgent 18.03.2015 14:07:13
    7552 (0x1D80)
    Inventory: Successfully sent report. Destination:mp:MP_HinvEndpoint, ID: {5541A94A-BED9-4132-AE54-110CB6896F02}, Timeout: 80640 minutes MsgMode: Signed, Not Encrypted
    InventoryAgent 18.03.2015 14:07:13
    7552 (0x1D80)
    Inventory: Cycle completed in 21453.570 seconds
    InventoryAgent 18.03.2015 14:07:30
    7552 (0x1D80)
    Inventory: Action completed. InventoryAgent
    18.03.2015 14:07:30 7552 (0x1D80)
    Inventory: ************************ End of message processing. ************************
    InventoryAgent 18.03.2015 14:07:30
    7552 (0x1D80)
    Collection: Namespace = \\.\root\cimv2; Query = SELECT __CLASS, __PATH, __RELPATH, Caption, ClassGuid, ConfigManagerErrorCode, ConfigManagerUserConfig, CreationClassName, Description, DeviceID, Manufacturer, Name, PNPDeviceID, Service, Status, SystemCreationClassName,
    SystemName FROM Win32_USBDevice; Timeout = 600 secs.
    InventoryAgent 18.03.2015 14:07:12
    7836 (0x1E9C)
    Collection: 62/74 inventory data items successfully inventoried.
    InventoryAgent 18.03.2015 14:07:12
    7836 (0x1E9C)
    Inventory: Collection Task completed in 21436.097 seconds
    InventoryAgent 18.03.2015 14:07:12
    7836 (0x1E9C)
    Inventory: 12 Collection Task(s) failed. InventoryAgent
    18.03.2015 14:07:12 7836 (0x1E9C)
    Inventory: Temp report = C:\WINDOWS\CCM\Inventory\Temp\25bf01b2-12fc-4eea-8e97-a51b3c75ba50.xml
    InventoryAgent 18.03.2015 14:07:12
    7836 (0x1E9C)
    Inventory: Starting reporting task. InventoryAgent
    18.03.2015 14:07:12 7552 (0x1D80)
    Reporting: 4381 report entries created. InventoryAgent
    18.03.2015 14:07:13 7552 (0x1D80)
    Inventory: Reporting Task completed in 1.030 seconds
    InventoryAgent 18.03.2015 14:07:13
    7552 (0x1D80)
    Inventory: Successfully sent report. Destination:mp:MP_HinvEndpoint, ID: {5541A94A-BED9-4132-AE54-110CB6896F02}, Timeout: 80640 minutes MsgMode: Signed, Not Encrypted
    InventoryAgent 18.03.2015 14:07:13
    7552 (0x1D80)
    Inventory: Cycle completed in 21453.570 seconds
    InventoryAgent 18.03.2015 14:07:30
    7552 (0x1D80)
    Inventory: Action completed. InventoryAgent
    18.03.2015 14:07:30 7552 (0x1D80)
    Inventory: ************************ End of message processing. ************************
    InventoryAgent 18.03.2015 14:07:30
    7552 (0x1D80)

    InventoryAgent 18.03.2015 08:10:03
    7836 (0x1E9C)
    Collection: Namespace = \\.\root\cimv2; Query = SELECT __CLASS, __PATH, __RELPATH, DefaultIPGateway, DHCPEnabled, DHCPServer, DNSDomain, DNSHostName, Index, IPAddress, IPEnabled, IPSubnet, MACAddress, ServiceName FROM Win32_NetworkAdapterConfiguration; Timeout
    = 600 secs. InventoryAgent
    18.03.2015 14:06:43 7836 (0x1E9C)
    Collection: Namespace = \\.\root\Nap; Query = SELECT __CLASS, __PATH, __RELPATH, description, fixupState, friendlyName, id, infoClsid, isBound, percentage, registrationDate, vendorName, version FROM NAP_SystemHealthAgent; Timeout = 600 secs.
    InventoryAgent 18.03.2015 14:06:43
    7836 (0x1E9C)
    Looks like something in one or both of those wmi queries.  it goes from 8:10:03 to 14:06:43 right around there.  6 hours to do that... 
    try running those queries from wbemtest manually; and see which one just never finishes.
    Standardize. Simplify. Automate.

  • [linux] 9.0.115.0 causes CPU 100% with firefox

    The 9.0.115.0 version of FlashPlayer causes 80-100% CPU
    consumption with latest Firefox on linux.
    The only solution I found, I get back to the 48... Can you
    fix it? Can you help me?

    I have the same problem with 9.0.115.0 in Linux.
    I have posted a bug-report to Adobe support last week - no
    reaction yet.
    Good site for testing is:
    http://www.lanik.us/misc/ff-flash-test.html

Maybe you are looking for