System process constantly writing to disk

While dealing with another hard drive Problem, ive noticed in Ressource Monitor, that the process 'System' is constantly writing to my main drive.
Sometimes its about 100-200 KiB/sec, today ive watched it for a while, and its writing action was 1.5 MiB/sec for quite a while! Later on it was about 300-400 KiB/sec.
Why does this process write so much data to my disk? Considering Windows running times, this adds up to multiple times the size of my hard drive.
Anyone knows whats going on here?

I have a similar, though less severe issue that hopefully someone can help me with.  The System process (pid 4) on my dual core Vaio laptop is writing to disk appx. once every 500ms.  This is not performance impacting and I considered it just a
minor annoyance until I recently installed a SSD.  Since SSD lifetimes are limited by write/erase cycles, I'm concerned these writes are deteriorating my SSD; not good since they're expensive and I LOVE the performance; boots in appx. 15s, instant IE,
etc.
As with the original poster here, the same activity persists in safe mode.  Per SSD optimization guidelines I've read elsewhere, I've disabled all fetching (super, pre, etc.), indexing and all logging except Application, Security & System but the
writes persist.
Im using the latest (very recent) driver from Intel (Intel 5 Series 4 Port SATA AHCI Controller 10.8.0.1003 10/17/2011).  I've tried other drivers and while the write pattern seems to change (drive activity light no longer blinks), Resource Monitor
shows they're still there.  They also cause an additional issue of consuming CPU (?) which doesn't occur with the "recommended" driver I just mentioned.
Anyone know what these writes may be and if/how I can/should stop them?  Thanks.
(BTW, love the caffiene->code quote :-)

Similar Messages

  • Kworker, jbd2 constantly writing to disk

    I have read earlier posts on jbd2 journal writing to disk constantly.
    These posts are several months old, but since about 4 kernel updates back, I have similar issues, which I cannot resolve.
    I have a few systems on Arch Linux and I observe it on two systems with an ext3 partition.
    Have tried "noatime, commit=60" in "/etc/fstab".
    Tried "Storage=volatile", "RuntimeMaxUse=25M" in "/etc/systemd/journald.conf"
    I ran my system with only a bash shell, systemd (212-1) and the kernel (3.13.7-1).
    Iotop shows [kworker/*:*] with 0.05% I/O access every other second,
    with jbd2 every 10 seconds actually writing to disk (despite commit=60).
    I hear my laptop harddrive often clicking so it is kind of annoying.
    related discussion on Ubuntu Launchpad
    related discussion on Ubuntu forum
    related discussion on Arch Linux forum
    related discussion on Arch Linux forum
    related discussion on Arch Linux forum
    A minute or so of kernel debug output, only running systemd and bash shell:
    [ 3625.942255] kworker/u16:3(1274): WRITE block 699941776 on sda3 (8 sectors)
    [ 3625.942260] kworker/u16:3(1274): WRITE block 700448896 on sda3 (8 sectors)
    [ 3625.942265] kworker/u16:3(1274): WRITE block 700710920 on sda3 (8 sectors)
    [ 3625.942270] kworker/u16:3(1274): WRITE block 700711032 on sda3 (8 sectors)
    [ 3625.942275] kworker/u16:3(1274): WRITE block 700711120 on sda3 (8 sectors)
    [ 3625.942280] kworker/u16:3(1274): WRITE block 700724344 on sda3 (8 sectors)
    [ 3625.942290] kworker/u16:3(1274): WRITE block 704643080 on sda3 (8 sectors)
    [ 3625.942295] kworker/u16:3(1274): WRITE block 704643416 on sda3 (8 sectors)
    [ 3625.942300] kworker/u16:3(1274): WRITE block 704643464 on sda3 (8 sectors)
    [ 3625.942305] kworker/u16:3(1274): WRITE block 704656376 on sda3 (8 sectors)
    [ 3625.942310] kworker/u16:3(1274): WRITE block 705167424 on sda3 (8 sectors)
    [ 3625.942319] kworker/u16:3(1274): WRITE block 705691656 on sda3 (8 sectors)
    [ 3625.942324] kworker/u16:3(1274): WRITE block 705691992 on sda3 (8 sectors)
    [ 3625.942329] kworker/u16:3(1274): WRITE block 705692584 on sda3 (8 sectors)
    [ 3625.942334] kworker/u16:3(1274): WRITE block 705715184 on sda3 (8 sectors)
    [ 3625.942339] kworker/u16:3(1274): WRITE block 743443568 on sda3 (8 sectors)
    [ 3625.942391] kworker/u16:3(1274): WRITE block 743443600 on sda3 (8 sectors)
    [ 3625.942397] kworker/u16:3(1274): WRITE block 768345896 on sda3 (8 sectors)
    [ 3625.942412] kworker/u16:3(1274): WRITE block 128 on sda3 (8 sectors)
    [ 3625.942418] kworker/u16:3(1274): WRITE block 176 on sda3 (8 sectors)
    [ 3625.942423] kworker/u16:3(1274): WRITE block 516423696 on sda3 (8 sectors)
    [ 3625.942428] kworker/u16:3(1274): WRITE block 516423832 on sda3 (8 sectors)
    [ 3625.942432] kworker/u16:3(1274): WRITE block 516952488 on sda3 (8 sectors)
    [ 3625.942437] kworker/u16:3(1274): WRITE block 520617984 on sda3 (8 sectors)
    [ 3625.942441] kworker/u16:3(1274): WRITE block 520880128 on sda3 (8 sectors)
    [ 3625.942446] kworker/u16:3(1274): WRITE block 520884264 on sda3 (8 sectors)
    [ 3625.942451] kworker/u16:3(1274): WRITE block 698875920 on sda3 (8 sectors)
    [ 3625.942460] kworker/u16:3(1274): WRITE block 699138080 on sda3 (8 sectors)
    [ 3625.942465] kworker/u16:3(1274): WRITE block 699138128 on sda3 (8 sectors)
    [ 3625.942472] kworker/u16:3(1274): WRITE block 699138784 on sda3 (8 sectors)
    [ 3625.942477] kworker/u16:3(1274): WRITE block 699138792 on sda3 (8 sectors)
    [ 3625.942481] kworker/u16:3(1274): WRITE block 699139120 on sda3 (8 sectors)
    [ 3625.942485] kworker/u16:3(1274): WRITE block 699139128 on sda3 (8 sectors)
    [ 3630.956821] kworker/u16:3(1274): WRITE block 520897816 on sda3 (64 sectors)
    [ 3640.986172] kworker/u16:0(1137): WRITE block 703786032 on sda3 (128 sectors)
    [ 3640.986195] kworker/u16:0(1137): WRITE block 81030272 on sda3 (32 sectors)
    [ 3670.367351] jbd2/sda3-8(115): WRITE block 401139384 on sda3 (8 sectors)
    [ 3670.367450] jbd2/sda3-8(115): WRITE block 401139392 on sda3 (8 sectors)
    [ 3670.367457] jbd2/sda3-8(115): WRITE block 401139400 on sda3 (8 sectors)
    [ 3670.367462] jbd2/sda3-8(115): WRITE block 401139408 on sda3 (8 sectors)
    [ 3670.367465] jbd2/sda3-8(115): WRITE block 401139416 on sda3 (8 sectors)
    [ 3670.367470] jbd2/sda3-8(115): WRITE block 401139424 on sda3 (8 sectors)
    [ 3670.367473] jbd2/sda3-8(115): WRITE block 401139432 on sda3 (8 sectors)
    [ 3670.367476] jbd2/sda3-8(115): WRITE block 401139440 on sda3 (8 sectors)
    [ 3670.367480] jbd2/sda3-8(115): WRITE block 401139448 on sda3 (8 sectors)
    [ 3670.367483] jbd2/sda3-8(115): WRITE block 401139456 on sda3 (8 sectors)
    [ 3670.367486] jbd2/sda3-8(115): WRITE block 401139464 on sda3 (8 sectors)
    [ 3670.367489] jbd2/sda3-8(115): WRITE block 401139472 on sda3 (8 sectors)
    [ 3670.367492] jbd2/sda3-8(115): WRITE block 401139480 on sda3 (8 sectors)
    [ 3670.367496] jbd2/sda3-8(115): WRITE block 401139488 on sda3 (8 sectors)
    [ 3670.367499] jbd2/sda3-8(115): WRITE block 401139496 on sda3 (8 sectors)
    [ 3670.367502] jbd2/sda3-8(115): WRITE block 401139504 on sda3 (8 sectors)
    [ 3670.367506] jbd2/sda3-8(115): WRITE block 401139512 on sda3 (8 sectors)
    [ 3670.367509] jbd2/sda3-8(115): WRITE block 401139520 on sda3 (8 sectors)
    [ 3670.367512] jbd2/sda3-8(115): WRITE block 401139528 on sda3 (8 sectors)
    [ 3670.658084] jbd2/sda3-8(115): WRITE block 401139536 on sda3 (8 sectors)
    Last edited by MDykstra (2014-05-02 09:04:51)

    Hi, I'm bumping this since I'm having the same issue. I've been reading the last entire week a lot of threads about that, but they're pretty old and they didn't solved anything. I read this whole thread, tried everything, but nothing of that worked...
    https://bbs.archlinux.org/viewtopic.php?id=113516&p=1
    https://bugzilla.kernel.org/show_bug.cgi?id=39072
    Using commit=60 does nothing. I've disabled tlp too, and used hdparm alone, but neither worked. I'm completely lost.
    I'd really appreciate any help, because I'm afraid of breaking my HDD and, unfortunately, I can't afford a new one...

  • Spotlight mds bringing down system, constantly leaking RAM & disk access

    Spotlight is going rampant here.
    The mds (metadata server, aka Spotlight) process is constantly accessing the disk and writing some data to it, filling it until there is no space left on the device. I cannot find out what file it is writing to. I've tried with fsevener which sadly didn't help.
    mds is also eating up all the CPU cycles it can get leaving my system fully loaded at all times.
    The mds process is also taking up inceasingly huge amounts of memory, causing permanent swapping of memory and bringing the system to a grinding halt. (Cache Hits go down below 1%, About 250.000 pageins happen per minute.) Memory Footprint is going up to several hundred MB or real RAM.
    $ vm_stat
    Mach Virtual Memory Statistics: (page size of 4096 bytes)
    Pages free: 53166.
    Pages active: 275736.
    Pages inactive: 135633.
    Pages wired down: 59698.
    "Translation faults": 10217862.
    Pages copy-on-write: 136166.
    Pages zero filled: 5983710.
    Pages reactivated: 96772.
    Pageins: 1236330.
    Pageouts: 77113.
    Object cache: 24391 hits of 1183451 lookups (2% hit rate)
    (This is 95 minutes after reboot. Only running: Finder, Terminal, LaunchBar, Safari, Mail)
    This bahaviour goes until the disk is full and I get a "low disk space" warning. Then mds crashes, the system frees up the (temporary?) files written by the process and also frees the RAM taken up by it. Resulting in even more swapping, as the system tries to page-in other processes now. Subseqently the system launches a new mds process and the game starts over.
    Things I've tried to remedy:
    Rebuilt spotlight index several times. Including totally deleting the .Spotlight-V100 folder on local volumes. Doesn't help, takes about 16 to 20 hours to rebuild on my machine, so is not a thing one wants to just-try.
    Reinstalled 10.5.5 Combo Update, doesn't help. Privileges are repaired.
    Turn off spotlight completely: Does indeed stop the madness, but now I cannot find anything on my system. So this is not a solution at all.
    I've tried to keep the index small by excluding more and more stuff in the privacy settings of the Spotlight PreferencePane. This doesn't solve the problem either.
    My System:
    PowerBook G4 1.5GHz
    2GB RAM (Maximum) (Tested with ASD ok, Rember ok. Different RAM modules, also ok.)
    160GB HD (5GB free) (SMART ok, Blockscan ok, Filesystem ok, File privileges ok)
    Mac OS X 10.5.5 (9F33) including Security Update 2008/007 (no further updates available)
    Any help or suggestions are welcome. I'm happy to provide any further details you may need.
    Best regards
    Pepi

    J D McIninch wrote:
    This probably isn't Spotlight so much as one of the index plugins (mdimporters). Spotlight itself is very robust, however, all it takes is a single bad indexing plugin. MDS, basically, identifies a file type and loads in a list of plugins that are registered for that file type and executes a routine in the plugin to grab the metadata. If the plugin is improperly written, it can go haywire.
    Thanks for the suggestion, I already had checked that.
    I don't have any custom (read non-apple provided) Spotlight or QuickLook Plug-Ins on my system. So it is unlikely that it is related to a custom .mdimporter Plug-In. (Might be a buggy Apple one going rampant though.)
    I've personally found Spotlight to be quite a solid technology as well. Just the user interface provided by Apple is terrible and especially useless in the Finder (Taking away functionality, or making it horrific to use since Tiger… but that is another story.)
    What was the last application that you installed prior to it going crazy? Perhaps one of the last 2-3...
    Failing that, you can wipeout the metadata database for a Volume like so (from Terminal.app):
    *sudo mdutil -E /Volumes/yourvolumehere*
    ... or '/' in place of '/Volumes/...' for the local disk. You can turn off metadata indexing for a volume entirely like so:
    As I already said, rebuilding the index from scratch doesn't help. Completely deleting it, and rebuilding doesn't remedy as well.
    *sudo lsof | grep mdimporter*
    ... which might help you understand what's being used to index, and this:
    /System/Library/Spotlight/Chat.mdimporter/Contents/MacOS/Chat
    /System/Library/Spotlight/iCal.mdimporter/Contents/MacOS/iCal /System/Library/Spotlight/Mail.mdimporter/Contents/MacOS/Mail
    Nothing fancy here.
    I ran a diff on my daily installation report and it gives me these app, that have been modified (Installed or updated in the last 31 days.)
    /Applications/Address Book.app
    /Applications/Adium.app
    /Applications/AppleScript/Script Editor.app
    /Applications/Automator.app
    /Applications/Carbon Copy Cloner.app
    /Applications/Dashboard.app
    /Applications/Dictionary.app
    /Applications/DVD Player.app
    /Applications/Expose.app
    /Applications/Flip4Mac/WMV Player.app
    /Applications/iCal.app
    /Applications/iChat.app
    /Applications/iPhoto.app
    /Applications/iSync.app
    /Applications/iTunes.app
    /Applications/JollysFastVNC.app
    /Applications/Mail.app
    /Applications/OmniFocus.app
    /Applications/Photo Booth.app
    /Applications/Preview.app
    /Applications/Safari.app
    /Applications/Skitch.app
    /Applications/Spaces.app
    /Applications/StuffIt/StuffIt Expander.app
    /Applications/StuffIt 12/StuffIt Expander.app
    /Applications/Time Machine.app
    /Applications/Utilities/Activity Monitor.app
    /Applications/Utilities/Bluetooth File Exchange.app
    /Applications/Utilities/ColorSync Utility.app
    /Applications/Utilities/Directory Utility.app
    /Applications/Utilities/Directory.app
    /Applications/Utilities/Disk Utility.app
    /Applications/Utilities/Keychain Access.app
    /Applications/Utilities/Migration Assistant.app
    /Applications/Utilities/Network Utility.app
    /Applications/Utilities/Podcast Capture.app
    /Applications/Utilities/RAID Utility.app
    /Applications/Utilities/Remote Install Mac OS X.app
    /Applications/Utilities/Terminal.app
    /Applications/Utilities/VoiceOver Utility.app
    /Applications/Utilities/X11.app
    /System/Library/CoreServices/Apple80211Agent.app
    /System/Library/CoreServices/AppleFileServer.app
    /System/Library/CoreServices/Automator Launcher.app
    /System/Library/CoreServices/Automator Runner.app
    /System/Library/CoreServices/AVRCPAgent.app
    /System/Library/CoreServices/Bluetooth Setup Assistant.app
    /System/Library/CoreServices/BluetoothAudioAgent.app
    /System/Library/CoreServices/BluetoothUIServer.app
    /System/Library/CoreServices/CCacheServer.app
    /System/Library/CoreServices/CoreServicesUIAgent.app
    /System/Library/CoreServices/DiskImageMounter.app
    /System/Library/CoreServices/Dock.app
    /System/Library/CoreServices/File Sync.app
    /System/Library/CoreServices/FileSyncAgent.app
    /System/Library/CoreServices/Finder.app
    /System/Library/CoreServices/Help Viewer.app
    /System/Library/CoreServices/Installer.app
    /System/Library/CoreServices/Kerberos.app
    /System/Library/CoreServices/KerberosAgent.app
    /System/Library/CoreServices/loginwindow.app
    /System/Library/CoreServices/ManagedClient.app
    /System/Library/CoreServices/NetAuthAgent.app
    /System/Library/CoreServices/Network Diagnostics.app
    /System/Library/CoreServices/Network Setup Assistant.app
    /System/Library/CoreServices/OBEXAgent.app
    /System/Library/CoreServices/ODSAgent.app
    /System/Library/CoreServices/PreferenceSyncClient.app
    /System/Library/CoreServices/Problem Reporter.app
    /System/Library/CoreServices/RemoteManagement/ARDAgent.app
    /System/Library/CoreServices/Screen Sharing.app
    /System/Library/CoreServices/Spotlight.app
    /System/Library/CoreServices/SystemUIServer.app
    /System/Library/CoreServices/VerifiedDownloadAgent.app
    As you can see, there is nothing special in there as well. Just Apple Apps, and a few non-suspicious ones from my point of view.
    Tom in London wrote:
    rather than mess around with all of this and maybe fix it until the next Spotlight problem manifests itself, why not just disable Spotlight with Spotless, and use EasyFind instead? Easyfind finds everything, has more options, is reliable, and doesn't cause problems .... and doesn't eat up any space on your hard drive.
    ...and doesn't find what I need. Thanks for the suggestions though. As I said, totally disabling Spotlight is not an option. I'll stay far away from mysterious tools, as I know what I am doing in a Terminal.
    Best regards
    Pepi

  • Process does I/O, shows up on Disk Activity within Resource Monitor as System process

    I've written some software that performs a significant amount of file I/O. What is odd is that on Resource Monitor, I see the large amount of I/O being read/written to the files my process is writing --- except the process that is indicated under
    Disk Activity is the System process, not my process. My code is standard C++ (no direct calls to the Windows API), console mode. Can anyone explain why this occurs? Is this some artifact of console mode programs that I am stuck with? Thanks.

    Hi all, am intending to do some editing on me and my gf's pictures, and I need to assure her that it's not going to go onto the internet (she's extremely private).
    You could do whatever you need to do in Lightroom with the Internet unplugged, then your questions are moot

  • Why is Premiere 6 giving a "Error writing file (disk full?)" message?

    Hello helpful experts,
    I'm using Premiere 6 on a Windows 7 machine.
    I have a file imported in to the timeline and it is set to play in reverse via the speed setting being set to -100 and it plays back in the preview window correctly, in reverse, when I click the play button.
    But when I do a  "File>Export Timeline>Movie" command I get an error message saying "An error occurred while making the movie. Error writing file (disk full?)"... but my hard drive is not nearly full, with over 30 gigs left open on it... and my RAM usage gadget shows over half of my RAM capacity is unused.
    Now previously, weeks ago on a different project, I was getting this same error message for a while when I would hit enter to preview my movie on the timeline (but that worked itself out somehow and eventually stopped giving me that error message).  But when I went to save and export, then I would not get the error message... now, it is just the opposite... I'm now getting the error message when trying to do an export and save the movie.
    And also now when I hit enter to preview, as opposed to just clicking the play button on the preview window, Premiere is going through the process of saving the movie since it is saving a temporary preview file... hopefully, since I'm getting this error message, I can find the temporary preview file and save it as my exported AVI file.
    But I still shouldn't be getting this error message when trying to save, or when trying to preview, as I did for a while a couple of weeks ago.
    Does anyone know about the erroneous error message that says, "An error occurred while making the movie. Error writing file (disk full?)"
    Thanks,
    numetro

    Depending on your hard drive size, P6 may be confused... since drives were not as large when it was written
    For Win7 64bit Pro or Ultimate (or Enterprise?) this is ONE example of using Virtual XP http://forums.adobe.com/thread/702693?tstart=0
    This is saved from an OLD message that may help
    File size limits by disk format type
    Fat = 2 Gig maximum file size
    Fat32 = 4 Gig
    NTFS = ?Terrabytes?
    Message saved from Premiere forum
    John Acocks - 07:52am Apr 17, 2003 Pacific
    I am unable to complete captures because I get a message
    that says "capture stopped because disk was full." What
    does this mean?
    Daniel Conklin - 08:02am Apr 17, 2003 Pacific (#1 of 2)   
    If you are using a Pinnacle card, a possible solution to
    this is to right click on the recycle bin, and set the
    percentage on your media drive to less than 2%.
    There a several other possible causes as well, but you
    need to supply some info about your system. How are you
    capturing and what format is your video? How big is
    your hard drive?
    Jeff Schell - 09:57am Apr 17, 2003 Pacific (#2 of 2)   
    this is one of my favorite error messages. Basically,
    you've chosen an incorrect setting in your DV settings.
    (Odds are you have DV settings). If so, read on:
    1. The DV format is very rigid. Meaning that if you
       make changes to the format, it cannot export as
       requested, because your movie file must match every
       single spec exactly.
    2. When Premiere goes to export a project, the DV codec
       says "Whoa. I can't do anything, because the settings
       don't match."
    3. Then Premiere comes back to you and has to report an
       error. (Don't shoot the messenger). Unfortunately,
       Premiere doesn't know why it wasn't able to export a
       movie. So it says to you, "Um... I can't make the movie.
       Um... maybe your hard drives are full?"
    It's a complete guess. And has nothing to do with your harddrives.
    Check your project settings and/or your export settings. Make
    sure you have chosen one of the "presets" that will specify
    every correct setting for you. Make sure it is one of the DV
    presets, if you are using DV video, or make sure it is one of
    the presets supplied by your capture card manufacturer (in this
    case I'm going to guess Pinnacle or Matrox.)
    To choose a preset, go to Project > Settings Viewer, and then
    click on the project settings column, and then click 'load' to
    load a correct preset. Do the same with export settings.

  • System volume information using most disk resources?

    I have a Toshiba satellite p755-S5381 running windows 7 64 bit with a 750 GB HDD. For the last several months it occasionally gets slow even when few programs are running. When I check the resource manager the system process is reading and writing in the System Volume Information folder on both the main "C" drive and an extra partition "E" drive which contains a window 8 install. I have tried defragmenting and disk check but neither had any effect on the level of disk use. What could be causing this? It is really reducing the performance of the computer.

    Satellite P755-S5381
    the system process is reading and writing in the System Volume Information folder on both the main "C" drive and an extra partition "E" drive which contains a window 8 install.
    That's the shadow-copy function which provides both System Restore points and backup versions of individual files. You can turn it off entirely by disabling the Volume Shadow Copy service in Services (services.msc).
    And you can adjust it. Open System Properties (sysdm.cpl). On the System Protection tab, select a partition and click Configure. You'll probably want to turn it off for your E partition and make some adjustments for your C partition.
    -Jerry

  • System Process Running out of Control - Overheating!

    The other day I arrived home and went to check my e mail and found my computer running at full tilt with the fans going all out and the case quite hot.  I thought maybe I had left dashboard open all day as I have done this before with similar results, but this was not the case.  
    I quit all programs and re started and the computer started to run at close to full process.  
    I ran software update and installed the RAW and system update that was available, re started still there.  I ran disk utility to check/repair permissions until they were good.  
    I ran the onyx cleaning set of stuff that clears cashes and histories.  
    When looking at the process monitor it shows the processor running at close to 3/4 but even with programs open in the background it shows them using little to none as expected with the process monitor on top of the list using some processor, but the little color chart below that shows process separated by programs and system show the system process running quite high.  
    Lastly I noted that when I restart and then let the computer sit for a few minutes at the log in screen  the system must be running hard again because the fans come on.  I do not know what is causing this or what next step I should take to remediate it, please help!
    Jerome

    Hi, C Jerome. If your Powerbook were actually overheating, it would put itself to sleep, so you needn't worry that it's in danger of damaging itself. I can understand your interest in calming and quieting it, though.
    First, how full is your hard drive? At least 10% of its capacity or 5GB, whichever is larger, should be free at all times. If you get down to much less than that, the processor and hard drive must work very hard cycling data in and out of virtual memory, and you run a substantial risk of system crashes, hard drive directory corruption and consequent loss of data.
    Do you have disk indexing turned on? Indexing your drive is only useful if you use Find By Content searches (I'm not sure that's what Spotlight calls them, because I don't use Tiger). Indexing can consume an enormous amount of processor cycles and generate a lot of heat, in addition to taking up a significant amount of hard drive space. If you don't need it, turn it off.

  • Process "mdworker" Writes to Disk Every 10 Seconds

    I noticed disk activity occurring every 10 seconds while my computer was idle. In Activity Monitor I could see this writing going on and at the same time the process "mdworker" would tick up just a little bit of processor activity. A Restart didn't help. The following is what I did to make it stop. I've seen many posts on here with a similar problem so maybe this info will be helpful to someone.
    I brought up a Terminal window and entered the following command:
    sudo fs_usage -w -f filesys
    That will show youa continuous list of all processes that are reading/writing to disk (use Control-c to make it stop). I found mdworker doing a fair amount of disk activity every 10 seconds. But the important thing is that it was the identical activity every 10 seconds, and the common thing in almost every entry was "Default Folder X". So I concluded that it was having trouble indexing something about Default Folder's data. (mdworker is used to index your data via Spotlight.) After uninstalling and reinstalling Default Folder, the constant writing stopped and has yet to happen again.
    If you're having a problem similar to this you may find this method of identifying the culprit and fixing it useful.

    Try this, courtesy of Baltwo. It will delete the Spotlight V-100 index and then force Spotlight to re-index.
    Be absolutely certain to only copy/paste these commands exactly. DO NOT try to type these in. One typo or wrong space in the first one could wipe your drive competely. Hit return after each.
    Delete the entire Spotlight directory and reindex, running these commands in the Terminal app:
    *sudo rm -R /.Spotlight-V100*
    *sudo mdutil -i on /*
    *sudo mduitl -E /*
    https://discussions.apple.com/message/12988300#12988300

  • He system software on this startup disk only functions on the original media

    i welcom.ith a warning ofantheer on my g4 when my frieend told it to boot os 9.2 after boot thee first disk wasnt finished loading now the g4 wont boot it goes to the system the system software mon this startup disk only functions on the original media not if copied to another drive. Has a restart tab but at this point it has frozen and the mouse and keyboard do not functiuon. NEED HELP

    Did this machine work before you tried to install 9.2?
    you may not have the correct cd. i think you need the restore cd that came with the machine.
    Where did you get the cd?  black or grey?
    We need your exact machine.
    Query by serial number
    "A serial number is a unique, identifying number or group of numbers and letters assigned to an individual piece of hardware or software. It's used for various things depending on the product / brand but what is your Mac's serial number for and more importantly... what is it hiding and what can it do for you ?"
    http://www.appleserialnumberinfo.com/Desktop/index.php
    >i welcom.ith a warning ofantheer on my g4
    >when my frieend told it to boot os 9.2
    why?
    does the cd boot into the software installation process?
    Where you able to pick what disk to install onto?
    >after boot thee first disk wasnt finished loading
    Could be a damaged disc.  How long did you wait?
    >now the g4 wont boot
    We understand this line.
    >it goes to the system the system software mon
    Don't understand this.  What appears on the screen?
    >this startup disk only functions on the original media not if copied to another drive.
    & your point is?  You need to use the installation software to install.  You cannot copy the cd. 
    >Has a restart tab but at this point it has frozen and the mouse and keyboard do not functiuon.
    I don't understand this.  Can you take a picture & post here.
    >NEED HELP
    Don't we all.
    You are allow to edit your posts for 15 minutes.  The edit is to the upper right in a sidebar.
    Plese spell check the document before posting.

  • IMovie - Console message: Error writing to disk!   App indicates nothing..

    My daughter spent hours working in iMovie v7.1.4, building a project. The system choked, in the end we went through a reboot and tried to reopen the project file. It indicated a 0s duration, with no pictures, music, etc...
    Upon research, I notice that in the console messages, there are about 100+ messages in the following format. The application never once indicated there was an issue.
    iMovie [[<PID>]] Project '/Users/<user>/Movies/iMovie Projects.localized/My First Project.rcproject' - save: Error writing to disk!
    She was working in a user account that has parental restrictions. Not sure if this has any bearing...
    Has anyone else ever had an issue like this? Where console indicates write errors, yet the application does not.

    I would run Disk Utility and repair permissions. If that does not fix it, check to make sure that she has write access to the drive.

  • Windows 8.1 unresponsive with system process at 25% CPU

    I have a Toshiba L50-A with an Intel i5-4200U CPU running Windows 8.1 with all current updates installed.  At random times (varying from 1 to 15 days but averaging once every 3 days) the "System" process begins using approximately 25% of my
    CPU with the usage spread across the 4 logical processors.  Using Sysinternals Process Explorer I can see that the thread using the CPU is "ntoskrnl.exe!ExfAcquirePushLockExclusive+0xb54".  Once this starts running, tasks (like Process
    Explorer) continue to run but  I cannot initiate any new task (like Xperf) and can sometimes shut down tasks until the system finally locks up completely.  I can find no way to interrupt this condition and have to hard power down the system.  I
    have investigated all the drivers associated with my peripherals and believe they are up to date.  I have also run a  severe CPU and Memory test tool for 24 hours and found no issues.  I cannot identify anything which changed in my system which
    triggered this but when it first manifested it sometimes went 10 or 15 days between occurrences so it could have been a fix or driver but I cannot identify that connection.  Can anyone give me an idea of how to investigate this further or what steps I
    can take to provide more pertinent data?
    Thanks,
    Keith 

    Hi Ckeithh,
    Did this issue occur recently ,Have you installed any software recently?
    To analyze this issue ,I recommend you to work with the Windows Performance Toolkit. It is included in the Windows Acccessment and Deployment Kit.
    Here is a link for downloading the tool
    WPT: WPR/Xperf: Capture high cpu, disk i/o, file, registry, networking, Private bytes, Virtual bytes, Paged Pool/Nonpaged pool and/or application slowness
    http://blogs.technet.com/b/yongrhee/archive/2012/11/23/wpr-xperf-capture-high-cpu-disk-i-o-file-registry-networking-private-bytes-virtual-bytes-paged-pool-nonpaged-pool-and-or-application-slowness.aspx
    I recommend you to  try this tool to capture the process ,if you have troubles in analyzing this . Please upload the files you captured to the Onedrive and paste the link here.If this tool can`t be performed, please post back.
    Meanwhile, I recommend to get into safe mode to work with the predefined drivers and services to have a analysis.
    As for the "ntoskrnl.exe!ExfAcquirePushLockExclusive+0xb54",here is a link for reference:
    Push Locks – What are they?
    http://blogs.msdn.com/b/ntdebugging/archive/2009/09/02/push-locks-what-are-they.aspx
    Best regards  

  • System Image Restore Fails "No disk that can be used for recovering the system disk can be found"

    Greetings    
                                        - Our critical server image backup Fails on one
    server -
    Two 2008 R2 servers. Both do a nightly "Windows Server Backup" of Bare Metal Recovery, System State, C:, System Reserved partition, to another storage hard drive on the same machine as the source. Active Directory is on the C: The much larger D: data
    partition on each source hard drive is not included.
    Test recovery by disconnecting 500G System drive, booting from 2008R2 Install DVD, recovering to a new 500G SATA hard drive.
    Server A good.
    Server B fails. It finds the backed-up image, & then we can select the date we want. As soon as the image restore is beginning and the timeline appears, it bombs with "The system image restore failed. No disk that can be used for recovering the system
    disk can be found." There is a wordy Details message but none of it seems relevant (we are not using USB etc).
    At some point after this, in one (or two?) of the scenarios below, (I forget exactly where) we also got :
    "The system image restore failed. (0x80042403)"
    The destination drive is Not "Excluded".
    Used   diskpart clean   to remove volumes from destination drive. Recovery still errored.
    Tried a second restore-to drive, same make/model Seagate ST3500418AS, fails.
    Tried the earliest dated B image rather than the most recent, fail.
    The Server B backups show as "Success" each night.
    Copied image from B to the same storage drive on A where the A backup image is kept, and used the A hardware to attempt restore. Now only the latest backup date is available (as would occur normally if we had originally saved the backup to a network location).
    Restore still fails.         It looks like its to do with the image rather than with the hardware.
    Tried unticking "automatically check and update disk error info", still fail.
    Server A  SRP 100MB  C: 50.6GB on Seagate ST3500418AS 465.76GB  Microsoft driver 6.1.7600.16385   write cache off
    Server B  SRP 100MB  C: 102GB  on Seagate ST3500418AS 465.76GB  Microsoft driver 6.1.7600.16385   write cache off
    Restore-to hard drive is also Seagate ST3500418AS.
    http://social.answers.microsoft.com/Forums/en-US/w7repair/thread/e855ee43-186d-4200-a032-23d214d3d524      Some people report success after diskpart clean, but not us.
    http://social.technet.microsoft.com/Forums/en-US/windowsbackup/thread/31595afd-396f-4084-b5fc-f80b6f40dbeb
    "If your destination disk has a lower capacity than the source disk, you need to go into the disk manager and shrink each partition on the source disk before restoring."  Doesnt apply here.
    http://benchmarkreviews.com/index.php?option=com_content&task=view&id=439&Itemid=38&limit=1&limitstart=4
    for 0x80042403 says "The solution is really quite simple: the destination drive is of a lower capacity than the image's source drive." I cant see that here.
    Thank you so much.

    Hello,
    1. While recovering the OS to the new Hard disk, please don't keep the original boot disk attached to the System. There is a Disk signature for each hard disk. The signature will collide if the original boot disk signature is assigned to the new disk.
    You may attach the older disk after recovering the OS. If you want to recover data to the older disk then they should be attached as they were during backup.
    2. Make sure that the new boot disk is attached as the First Boot disk in hardware (IDE/SATA port 0/master) and is the first disk in boot order priority.
    3. In Windows Recovery Env (WinRE) check the Boot disk using: Cmd prompt -> Diskpart.exe -> Select Disk = System. This will show the disk where OS restore will be attempted. If the disk is different than the intended 2 TB disk then swap the disks in
    correct order in the hardware.
    4. Please make sure that the OS is always recovered to the System disk. (Due to an issue: BMR might recover the OS to some other disk if System disk is small in size. Here the OS won't boot. If you belive this is the case, then you should attach the
    bigger sized disk as System disk and/or exclude other disks from recovery). Disk exclusion is provided in System Image Restore/Complete PC Restore UI/cmdline. 
    5. Make sure that Number and Size of disks during restore match the backup config. Apart from boot volumes, some other volumes are also considered critical if there are services/roles installed on them. These disks will be marked critical for recovery and
    should be present with minimum size requirement.
    6. Some other requirements are discussed in following newsgroup threads:
    http://social.technet.microsoft.com/Forums/en-US/windowsbackup/thread/871a0216-fbaf-4a0c-83aa-1e02ae90dbe4
    http://social.technet.microsoft.com/Forums/en-US/windowsbackup/thread/9a082b90-bd7c-46f8-9eb3-9581f9d5efdd
    http://social.technet.microsoft.com/Forums/en-US/windowsbackup/thread/11d8c552-a841-49ac-ab2e-445e6f95e704
    Regards,
    Vikas Ranjan [MSFT]
    ------- This information is provided as-is without any warranties, implicit or explicit.-------

  • HELP iTunes wont open but runs in system process on xp64 pro

    iTunes was working just the other week. Now all of the sudden it wont open. However it will be running in my system processes taking up 36,752k
    I've searched the forums and tried the suggestions also installing and uninstalling and upgrading to the latest version. iTunes very rarely gives me a problem and nothing major has happened to my system. I need a fix for this ASAP I use iTunes just about every day!!
    Thanks,
    Nick

    Yeah great thanks, but i've been using it on xp64 for a year already with no problems
    Xp64 doesnt have problems running 32bit programs for me
    However there's got to be some kind of registry for this.

  • How to tell if the AE programm is called from (1) SYSTEM PROCESS REQUEST or (2) page run control request

    We just wrote an AE program and is called through the vanilla SYSTEM PROCESS REQUEST.
    It's running on a daily basis ie. with RECURRENCE.
    Now we need to call the same program through the regular page run control request.
    But we are not how to recognize from inside the AE program if whether it's been called from SYSTEM PROCESS REQUEST or RUN CONTROL REQUEST.
    Any of you might have suggestion ?
    Any technique or workaround is also appreciated.
    THANKS in Advance .

    This AE pgm is currently automatically called from SYSTEM PROCESS REQUEST on a daily basis to load data from an input file deposited on the server ready for pickup.
    We would like to use the same AE pgm ( thus using the same validation and loading logic ) to load the same file format but defined by the user ( via attachment load ) as needed any time during the day.
    The user will initiate this AE pgm online ( ie. from a page with his parameters ).
    Currently, the pgm now already runs automatically daily and we wish to make it also available to be run by user anytime in the day
    To achieve that, we would need to know:
    Is the AE pgm ran by (a) the user or by the (b) SYSTEM PROCESS REQUEST so that the program can decide of where to take input file.
    (a) Take from an attachment defined by user or (b) from the input file already deposited on the server for pickup
    That is the reason why we try to detect who called the AE pgm in order decide where to pickup the input file.
    Your help is much appreciated as I do researches but so far haven't gotten a concluded decision.
    Thank you.
    Message was edited by: Kel_123

  • X200s on Windows XP Pro - System process around 50% after Standby or Hibernate

    I have an x200s with the SU9300 1.2Ghz processor.  I'm running with a clean installation of Windows XP Pro.  I noticed less-than-expected battery life and found that after leaving the computer on for a number of hours (let's say overnight) and returning from Standby or Hibernate, I find that my "System" process takes up around 20-55% but usually hovers at 49-50% when the machine is idle.  The "System Idle Process" will take up the remaining 50%.  This is observed in the Windows Task Manager.
    On my x60s with a core duo processor (and all my other desktops and laptops) the System process will  usually be 0% when idle and the "System Idle Process" will be at 99%. 
    A restart of the computer will fix this issue until I go into Standby or Hibernate again.  I usually went for days and sometimes weeks without restarting my x60s.  This issue will cause me to get 30% less battery life and will make my system slower to respond, even when I'm typing this post, for example. 
    Anyone have experience or thoughts on this?  Thank you

    Any thoughts from anyone out there?

Maybe you are looking for