That doesn't happen here lotty but I often have to stop and restart iTunes to get it to display properly and/or link with my iPad. That seems to depend more on what else is running on the machine at the time. I've never had memory running away with it though or had to restart the machine.
You may wish to involve Technical Support with this because it certainly shouldn't be happening....unless you've caught one of the world's first iPad viruses which I doubt.
Based on my experience dealing with this memory leak I am going to save myself some time, avoid tech support and just work around the problem. I posted as a courtesy to other users.
OK thanks. You might just want to check the iTunes has full permiissions for all processs in Firewall. It also juust occurred to me, you weren't restoring all 3 at once were you?
Confirming itunes with full permissions. And only syncing ... one ipad at a time (i did chuckle at the notion of trying to sync multiple ipads concurrently).
..if that is indeed possible. I only have 1 so can't test that wild theory. Thanks for posting and sorry I don't have a good idea for the problem.
Sounds like it could be the same as the fwpclnt.sys problem. If you were at or close to out of memory due to the nonpaged problem another process needing such memory would fail its request and if that failure was no handled properly due to the assumption that kernel memory is almost never exhausted on todays machines, then your other software, particularly drivers, would be left in a bad state until a reboot occurred. This all caused because McAfee is leaking nonpaged memory like a sieve.
I would be very careful because yes you could brick a device with this problem.
Funny you don't see the connection Peter having posted on both threads. The fact that you can sync an ipod on a machine that isn't yet at the limit does not mean this is not the problem. You need a machine that fwplclnt.sys has consumed all of the memory on.
I also have 8GB and that 7.3GB line is where things fall apart for me as well. I think this is due to the 75% of memory threshold for the nonpaged pool. As it reaches 6.2GB of nonpaged consumed things fall apart. Assuming another 1.1GB of actual applications and windows running that is your 7.3GB. You can verify by looking at windows task manager Performance tab the Nonpaged number in the Kernel Memory box. I would not start an ipad sync if it is any where near 75% of your total ram, and you should be seriously considering a reboot at that point unless you want to lose data or risk corruption.
The real problem may indeed by in windows, but the problem we are all having is that McAfee is now usingthe problematic driver. Prior to september our machines were not exhibiting this behaviour, I am not aware of any amazing new feature that McAfee brought me to justify the new problems. Go back to the old way you were doing it, it worked better.
Heck I forgot I posted this. But anyway I think its the same memory leak issue I have been dealing with since 7/30/12 when McAfee rolled out new build. As I posted in detail
As you suggest in your post I just watch my memory and reboot often when I am going to do heavy I/O tasks including syncing my ipads and other "i" devices. Just for reference, on my ipad rebuild that had 55GB+ of data .. it took me about 6 reboots to completly finish syncing the ipad. Interesting here the sync process just stops and the PC does not crash per se. But the only way to progress through the full sync is to reboot the PC and start the sync again. If you do not reboot boot the sync process will not recognize the ipad. Once the initial full sync / rebuild further maintainece syncs are mostly done without requiring a reboot . I have learned to always run the resource monitor with memory view up in the corner of my screen. Ridiculous but necessary and effective.
As discussed in the link above the root issue relates to a function call into the kernal. McAfee has blamed it on Microsoft as you can read in the post but the back and forth in the link outlines another view that points the finger squarely back at McAfee. Once the memory hits that critical level around 7.3 GB .. then all kinds sorts of problems are triggered which renders the event log somewhat useless for pointing to a real root cause. Again as documented in this link the root failure presents in the memory dumps under a driver called something like netsys.??? .. it takes everyhting down .. the McAfee engineers remoted into my PC and captured all kinds of memory dumps etc .. I think all that is covered in the posting.
Bottom line we just have to wait for the fix but one temporary and free solution outlined in this post and that works for me is to completely uninstall McAfee, run the MCPR.exe tool, reboot, then install the FREE microsoft security essentials. That takes all of 15 minutes and you are likely to find your PC functioning normally. For me normal is having my PC run 7 days or more without reboot if not longer.